[tdwg-tapir] r1245 - in tapir: 1.0/schema dev/schema

[svn at rs.tdwg.org]

Author: RenatoDeGiovanni
Date: 2007-07-19 03:11:10 +0200 (Thu, 19 Jul 2007)
New Revision: 1245

Modified:
   tapir/1.0/schema/tapir.xsd
   tapir/dev/schema/tapir.xsd
Log:
Included documentation about dc:language.


Modified: tapir/1.0/schema/tapir.xsd
===================================================================
--- tapir/1.0/schema/tapir.xsd	2007-07-19 00:40:57 UTC (rev 1244)
+++ tapir/1.0/schema/tapir.xsd	2007-07-19 01:11:10 UTC (rev 1245)
@@ -1606,14 +1606,19 @@
 			</xsd:element>			
 			<xsd:element ref="dc:language" maxOccurs="unbounded">
 				<xsd:annotation>
-					<xsd:documentation></xsd:documentation>
+					<xsd:documentation>Language of content that can be returned by search 
+						and inventory responses. This element must follow RFC 4646 
+						and use language codes specified by the IANA Language Subtag 
+						Registry. More than one language can be specified, in case 
+						the provider can serve content in multiple languages. When 
+						there is no linguistic content, "zxx" must be used.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>			
 			<xsd:element ref="dc:subject" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>Subject and Keywords.Typically, a Subject will be expressed as keywords,
+					<xsd:documentation>Subject and Keywords. Typically, a Subject will be expressed as keywords,
 						key phrases or classification codes that describe a topic
-						of the resource.  Recommended best practice is to select 
+						of the resource. Recommended best practice is to select 
 						a value from a controlled vocabulary or formal 
 						classification scheme</xsd:documentation>
 				</xsd:annotation>

Modified: tapir/dev/schema/tapir.xsd
===================================================================
--- tapir/dev/schema/tapir.xsd	2007-07-19 00:40:57 UTC (rev 1244)
+++ tapir/dev/schema/tapir.xsd	2007-07-19 01:11:10 UTC (rev 1245)
@@ -1606,14 +1606,19 @@
 			</xsd:element>			
 			<xsd:element ref="dc:language" maxOccurs="unbounded">
 				<xsd:annotation>
-					<xsd:documentation></xsd:documentation>
+					<xsd:documentation>Language of content that can be returned by search 
+						and inventory responses. This element must follow RFC 4646 
+						and use language codes specified by the IANA Language Subtag 
+						Registry. More than one language can be specified, in case 
+						the provider can serve content in multiple languages. When 
+						there is no linguistic content, "zxx" must be used.</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>			
 			<xsd:element ref="dc:subject" minOccurs="0">
 				<xsd:annotation>
-					<xsd:documentation>Subject and Keywords.Typically, a Subject will be expressed as keywords,
+					<xsd:documentation>Subject and Keywords. Typically, a Subject will be expressed as keywords,
 						key phrases or classification codes that describe a topic
-						of the resource.  Recommended best practice is to select 
+						of the resource. Recommended best practice is to select 
 						a value from a controlled vocabulary or formal 
 						classification scheme</xsd:documentation>
 				</xsd:annotation>