Difference between revisions of "ac:metadataLanguage"

From TDWG Terms Wiki
Jump to: navigation, search
m (Created page with "{{Concept |label=Metadata Language |is defined by=ac:metadataLanguage |concept type=property |definition=Language of description and other metadata (but not necessarily of the...")
 
(fixed newline issue)
 
(15 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
__NOINDEX__
 +
<span style="background-color:#ffc; padding:5px; color:#f00;border:1px solid #f00;">'''Warning''': This is not the current version of this document. It is kept for archival purposes. For up-to-date information, go to https://tdwg.github.io/ac/termlist/#ac_metadataLanguage</span><br /><br />
 +
 +
 
{{Concept
 
{{Concept
 
|label=Metadata Language
 
|label=Metadata Language
|is defined by=ac:metadataLanguage
 
|concept type=property
 
 
|definition=Language of description and other metadata (but not necessarily of the image itself) represented in ISO639-1 or -3.
 
|definition=Language of description and other metadata (but not necessarily of the image itself) represented in ISO639-1 or -3.
|notes=This is NOT {{NS dcterms | language}}, which is about the resource, not the metadata. Metadata Language is deliberately single-valued, imposing a requirement that multi-lingual metadata be represented as separate, complete, metadata records in which also the language-neutral items appear. Consumers can re-combine records by identity of multimedia Resource IDs (which are highly recommended to supply). In the face of metadata records of several languages for the same resource, this normative document offers no guidance as to how to disambiguate what language applies to what metadata. To disambiguate this, the metadata provider can provide a separate AC object for each different MetadataLanguage, each such AC object referring to the same multimedia resource Identifier. This comes at a cost of repeated data for the "language neutral" metadata items, but the alternative is to have a complex hierarchical structure for an AC object. Nothing in this document would prevent an implementer, e. g. of an XML-Schema representation, from providing a fully hierarchical schema and disambiguating that way. Users of a particular implementation should consult documentation specific for that implementation on this point, but it should always be correct, if convenient, to provide one metadata record per language.  
+
|notes=This is NOT {{NS dcterms | language}}, which is about the resource, not the metadata. Metadata Language is deliberately single-valued, imposing for unstructured serializations a requirement that multi-lingual metadata be represented as separate, complete, metadata records. Audubon Core requires that each record also contains the language-neutral terms. In the absence of this requirement, metadata consumers would need to known which terms are language-neutral and merge these terms from all provided metadataLanguages into a single record. Metadata consumers may re-combine the information based on the dcterms:identifier that identifies the multimedia resource.
|hidden notes=Crosswalk: NBII = Language of Cataloging; KeyToNature = {{NS k2n | Metadata_Language }}; DublinCore = {{NS dcterms | language}} referring to a "metadata resource".; Morphbank = "English"
+
 +
Nothing in this document would, however, prevent an implementer, e. g. of an XML-Schema representation, from providing a fully hierarchical schema in which language neutral terms occur only a single time, and only the language-specific terms are repeated in a way that unambiguously relates them to a metadata language. In RDF it may be a simple repetition of plain literals associated with a language (e.g. xml:lang attribute in RDF/XML). The language attribute would then be required in Audubon Core and would replace ac:metadataLanguage.
 +
 
 +
Required.
 +
|is defined by={{ACTERMLIST}}#ac:metadataLanguage <!-- for ac at least, this pagename is also the term name -->
 +
|concept type=property
 +
|hidden notes=Crosswalk: NBII = Language of Cataloging; KeyToNature = {{NS k2n | Metadata_Language }}; Dublin Core = {{NS dcterms | language}} referring to a "metadata resource".; Morphbank = "English"
 +
}}
 +
{{Concept scheme relation
 +
|scheme=Audubon Core Development
 +
|property cardinality=1..1
 
}}
 
}}
 
{{Concept relation
 
{{Concept relation
|relation=skos: in scheme
+
|relation=skos: collection
|internal page=Audubon Core
+
|internal page=Audubon Core Management Vocabulary
 
}}
 
}}
 
{{Concept relation
 
{{Concept relation
 
|relation=skos: collection
 
|relation=skos: collection
|internal page=Management Vocabulary
+
|internal page=Audubon Core Layer 1
 
}}
 
}}
 +
<noinclude>'''References'''<br/><references/></noinclude>

Latest revision as of 13:04, 5 March 2020

Warning: This is not the current version of this document. It is kept for archival purposes. For up-to-date information, go to https://tdwg.github.io/ac/termlist/#ac_metadataLanguage

Scheme: Audubon Core Development Pencil.png
Collections: Audubon Core Management Vocabulary Pencil.png, Audubon Core Layer 1 Pencil.png
Metadata Language
Search for values Crystal Clear action find.png
Metadata Language: Language of description and other metadata (but not necessarily of the image itself) represented in ISO639-1 or -3.

Notes: This is NOT dcterms:language [1], which is about the resource, not the metadata. Metadata Language is deliberately single-valued, imposing for unstructured serializations a requirement that multi-lingual metadata be represented as separate, complete, metadata records. Audubon Core requires that each record also contains the language-neutral terms. In the absence of this requirement, metadata consumers would need to known which terms are language-neutral and merge these terms from all provided metadataLanguages into a single record. Metadata consumers may re-combine the information based on the dcterms:identifier that identifies the multimedia resource.

Nothing in this document would, however, prevent an implementer, e. g. of an XML-Schema representation, from providing a fully hierarchical schema in which language neutral terms occur only a single time, and only the language-specific terms are repeated in a way that unambiguously relates them to a metadata language. In RDF it may be a simple repetition of plain literals associated with a language (e.g. xml:lang attribute in RDF/XML). The language attribute would then be required in Audubon Core and would replace ac:metadataLanguage.

Required.
The given value was not understood.
The given value was not understood.

Constraints in the context of Audubon Core Development:

References
  1. dcterms = http://dublincore.org/documents/dcmi-terms/