Metadata Principles

The following principles have been provided by Traugott:

• It is important to formulate requirements and usage scenarios motivating metadata solutions

• There should be an explicit data model

• The solution must be formed in accordance with the Dublin Core Abstract Model (DCAM)

• Namespaces, vocabularies and persistent resource identifiers must be established and maintained

• It must be documented as an Application Profile according to the CEN standard

• It should be compatible with the Eprints Application Profile

• The format should follow DC encoding guidelines, incl. the evolving versions for the DCAM

• Test usage and evaluation, both reg. creation and retrieval, is needed for iterative design improvements

• The solution should be submitted to the KIM working group for advice and future certification

• Metadata creation, quality assurance and enhancement tools are necessary

• It must be made possible to access the metadata via standardised protocols such as OAI

Terminology

Try to clear up following terms:

• Data model

• Content Model

• Profile / Metadata Profile

• Application Profile
  "In DCMI usage, an application profile is a declaration of the metadata terms an organization, information resource, application, or user community uses in its metadata. In a broader sense, it includes the set of metadata elements, policies, and guidelines defined for a particular application or implementation." see http://dublincore.org/documents/usageguide/glossary.shtml

• Metadata set

• Metadata specification
  In eSciDoc, the metadata specification lists the elements used

• Elements - values; Complex elements.

• Encoding schemas

• Label vs. name
  The label is the string used on the interface?

• Item; item types etc.

Comitée européen de normalisation

Dublin Core

Dublin Core Abstract Model

Kompetenzzentrum Interoperable Metadaten

Open Archives Initiative

Dublin Core Metadata Initiative

Enhanced Scientific Documentation