"2008-01-14" . "A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/language) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation."@en . . "Language"@en . . "A language of the resource."@en . . . . "1999-07-02" . "A language of the resource."@en-us . "Language"@en-us . . . . "Recommended best practice is to use RFC 3066 [RFC3066],\n which, in conjunction with ISO 639 [ISO639], defines two-\n and three-letter primary language tags with optional\n subtags. Examples include \"en\" or \"eng\" for English,\n \"akk\" for Akkadian, and \"en-GB\" for English used in the\n United Kingdom."@en-us . . . . "A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document \"DCMI Metadata Terms\" (http://dublincore.org/documents/dcmi-terms/) for an explanation."@en-us . "Recommended practice is to use either a non-literal value representing a language from a controlled vocabulary such as ISO 639-2 or ISO 639-3, or a literal value consisting of an IETF Best Current Practice 47 [[IETF-BCP47](https://tools.ietf.org/html/bcp47)] language tag."@en . "A language of the intellectual content of the resource."@en-us . "Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646]."@en-us . . . . . "Language" . . . . "1999-07-02"^^ . . .