wiki:CMDI 1.2/Specification

Version 4 (modified by Twan Goosen, 10 years ago) (diff)

added 'draft' to title to indicate this is not final (which is obvious now...)

Component Metadata Infrastructure (CMDI) 1.2 [DRAFT]


The goal of the Component Metadata Infrastructure (CMDI) specification...


The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in RFC2119.


CLARIN federated content search, an interface specification to allow searching within resource content of repositories.
A Persistent identifier is a long-lasting reference to a digital object.

Normative References

Key words for use in RFCs to Indicate Requirement Levels, IETF RFC 2119, March 1997,
Namespaces in XML 1.0 (Third Edition), W3C, 8 December 2009,

Non-Normative References

XML Media Types, IETF RFC 3023, January 2001,

Typographic and XML Namespace conventions

The following typographic conventions for XML fragments will be used throughout this specification:

  • <prefix:Element>
    An XML element with the Generic Identifier Element that is bound to an XML namespace denoted by the prefix prefix.
  • @attr
    An XML attribute with the name attr
  • string
    The literal string must be used either as element content or attribute value.

The following XML namespace names and prefixes are used throughout this specification. The column "Recommended Syntax" indicates which syntax variant SHOULD be used by the Endpoint to serialize the XML response.

Prefix Namespace Name Comment Recommended Syntax
cmd CMDI instance prefixed

CMDI Component Metadata Model

CMDI Component and Profile Specification Level

CMDI Instance Level

Normative Appendix

Non-normative Appendix

Attachments (12)

Download all attachments as: .zip