logo

Core Metadata Schema (version 3.00 beta)

Introduction

Documents which are exchanged between different co-operators should be accompanied by metadata which keep a trace of the processing on the document and inform the addressee about the document. All Institutions have to use the same schema which simplifies the understanding and re-use of the information transferred.

The schema as well as its extension mechanism was adopted by the Interinstitutional Metadata Maintenance Committee (IMMC).

This document first describes the relationship between the different components such as the core metadata element set, the predefined values imported from the authority tables and finally the extension mechanism and schema. Afterwards the naming conventions as well as the use of namespaces are taken into consideration. Finally the data types, element definitions and extension elements are explained. The annexes illustrate different components.

Architecture

The approach consists of different layers of schema components. The core metadata element set which is common and mandatory to all document types is defined in the CM fragment, which at the same time could be used as the schema entry point. Normally it will be imported to the cm_common_extensions fragment which contains additional definitions which are specific for the different document types. While the core metadata element set is not supposed to undergo any changes, the cm_common_extensions will be adapted to the various document types which have to be taken into account.

Both components integrate lists of predefined values which are either taken from authority tables adopted by the IMMC or are still in a provisional status. The following picture illustrates these relations:

Architecture of the schemaLegend: S: schema, SF: schema fragment

Whenever a new and relevant authority table is adopted by the IMMC, it will replace the provisional list. In general, the values of the authority tables will not be modified, the list may only be completed.

Naming conventions

The tag names are supposed to provide the user with a rough idea about the role of a given element within an instance. Names of any type definitions (simple and complex) which are not predefined in the xs namespace are preceded by the prefix "t_".

In the case that elements have equal roles in different contexts, but with different structures, they are suffixed with the name of their specific context; ex. identifier_procedure vs identifier_work.

Element names like work, expression and manifestation refer to the FRBR standard for metadata organisation and encoding.

Namespace

All components of the schema have their own namespace and consequently their own prefix:

ComponentNamespacePrefix
core metadatahttp://publications.europa.eu/resource/core-metadata/v3cm
core metadata transmissionhttp://publications.europa.eu/resource/core-metadata-transmission/v3cmt
cm common extensionshttp://publications.europa.eu/resource/core-metadata-extensions/v3cmext
at: corporate-bodyhttp://publications.europa.eu/resource/authority/corporate-bodycob
at: countryhttp://publications.europa.eu/resource/authority/countrycou
at: eventhttp://publications.europa.eu/resource/authority/eventeve
at: file-typehttp://publications.europa.eu/resource/authority/file-typefor
at: languagehttp://publications.europa.eu/resource/authority/languagelng
at: multilingualhttp://publications.europa.eu/resource/authority/multilingualmul
at: procedurehttp://publications.europa.eu/resource/authority/procedureproc
at: product-formhttp://publications.europa.eu/resource/authority/product-formpfo
at: resource-typehttp://publications.europa.eu/resource/authority/resource-typeres
at: rolehttp://publications.europa.eu/resource/authority/rolerol
at: subdivisionhttp://publications.europa.eu/resource/authority/subdivisionsub
at: treatyhttp://publications.europa.eu/resource/authority/treatytre


Last updated: Monday, 27 April 2015