Hi Markus,
I agree it's unusual, but I think in DC they were also considering the possibility to have the content of dc:language in natural language. You can see an example in their own documentation:
http://dublincore.org/2006/12/18/dces.rdf#
Anyway, the documentation also says that "Recommended best practice is to use a controlled vocabulary such as RFC 3066 [RFC3066]", which is what you're suggesting.
I'll try to list some alternatives in another message.
Regards, -- Renato
Hi there, This really is weird. I was confident that the xml schema language data type was used. This defines natural language identifiers as defined by RFC 3066. http://www.w3.org/TR/xmlschema-2/#language http://www.ietf.org/rfc/rfc3066.txt
But when I looked up the tapir schema, it makes use of the dublin core schema that then states the following:
<xs:element name="language" substitutionGroup="any"/> <xs:element name="any" type="SimpleLiteral" abstract="true"/> <xs:complexType name="SimpleLiteral"> <xs:complexContent mixed="true"> <xs:restriction base="xs:anyType"> xs:sequence <xs:any processContents="lax" minOccurs="0" maxOccurs="0"/> </xs:sequence> <xs:attribute ref="xml:lang" use="optional"/> </xs:restriction> </xs:complexContent> </xs:complexType>
So you can use anything for the dc:language element AND tag it with an optional xml:lang attribute. Thats weird:
<dc:language xml:lang="en">swuaheli</dc:language>
Markus