This is old. See the [[CMDI 1.2/Specification#Terminology|Terminology section of the CMDI 1.2 specification]] for up-to-date descriptions!

----

 CLARIN Metadata component::
 An aggregation of metadata elements and components (recursive structure) aimed at describing a specific aspect of a resource. The metadata component has a name and may be linked to a concept in a registry itself.

 CLARIN Metadata Profile::
 A specification of an aggregation of metadata components that can be (re-) used to create metadata descriptions. The profile is not intrinsically different from a component itself except that it is used to describe all relevant aspects of a resource or collection.  The profile contains a specification of components together with specifications of cardinality, mandatory presence, default values and guidance for applications. The profile can be exported into a suitable XML schema.

 CLARIN XML metadata schema::
 An XML-Schema (different flavors exist: W3C, DTD, RNG) that formally defines a metadata description as built up from metadata components.

 CLARIN metadata template::
 A (partly) filled in component or metadata description that can be used to store frequently used metadata information, e.g. an Actor that features often in a corpus. The template is not stored in a global registry but in a user’s private workspace.

 Metadata element:: 
 (Metadata descriptor) An atomic part of a metadata description. A combination of a name and value that together with the other metadata elements form the metadata descriptions describing the associated resource. Within a metadata schema a metadata element is characterized by a name and a value domain. The value domain can be a finite vocabulary or a regular expression constraining the value.  A CLARIN metadata element also provides a link to a concept in a registry that could provide vocabularies and constraints.

 Metadata schema:: 
 In general a specification of a set of metadata elements.  Strictly speaking the syntax or structure is not part of it but in the case of a structured set such as is possible in the component model, the semantics of the elements can be influenced by a container component and thus makes the structure indispensable to understand a metadata description.

 Accepted Registry::
 An accepted registry provides concepts (data categories) that are accepted by the CLARIN community to be used to describe language resources. ISOcat (as specified by ISO TC37/SC4) and DublinCore are examples of such accepted registries. We expect that the metadata elements are standardized by being defined in accepted registries such as ISO TC37/SC4 and DublinCore. Components and profiles, however, are not standardized and users can create their own ones.