The MCP is a type 2 profile of ISO19115 implemented in XML using ISO19139. This means that:

  1. Any element of ISO19115 can be used in the MCP
  2. New elements have been added using the approved extension procedures for ISO19115 and the XML implementation of ISO19139
  3. Controlled vocabularies for certain metadata elements (also known as code lists) and rules for validating metadata records from ISO19115 have been extended and new controlled vocabularies and rules for checking validity have been added

Type 1 profiles of ISO19115 are simpler than type 2 profiles because they do not add new elements. Examples of type 1 profiles are the ANZLIC Metadata profile and the WMO (World Meteorological Organisation) profile version 1.2.

XML Fragments

This manual uses fragments of XML to describe the MCP. Some familiarity with the following XML concepts is required:

  • namespaces
  • elements and attributes
  • schemas

The basic concepts and ideas behind XML can be found at and other places on the internet.

For brevity and to help understanding, fragments of XML will be written as follows:

  • using a different font and background
  • indented where possible to help reading
  • where an XML element, including the start tag, end tag and content, is too long to show on a single line, it shall break across more than one line automatically
  • content not relevant to the purpose of the fragment will be replaced by an ellipsis (...)

XML Conventions

These conventions reuse and extend the conventions set out in the WMO Core Metadata Profile v1-2 Manual by Jeremy Tandy. The conventions are as follows:

  • The schema documents (see XSD) and codelists for the Marine Community Profile extend those used for ISO19139 and ISO19136. They are available online at
  • The schema documents for ISO19139 are included with the MCP schema documents. They are also available from the ISO TC211 website (see also ISO TC211).
  • A number of different namespaces are used to separate metadata elements into packages for easier management or to include XML implementations of other standards such as GML. The result is that an MCP metadata record will incorporate multiple namespaces as follows:
  • The root element when shown shall be mcp:MD_Metadata
  • The root element should have an attribute called xsi:schemaLocation which contains a value or set of values hinting at the physical location of schemas which may be used for validation. Since this attribute provides only a hint validating parsers are allowed to ignore it and use other means of locating the relevant schemas.
  • An example of the complete namespace declaration for an MCP metadata record is:

Example of complete namespace declaration for an MCP metadata record


The example of the complete namespace declaration of an MCP metadata record shown above has explicit namespace prefixes for each namespace used in the document. This is the recommended and preferred practice for MCP metadata records.

  • Codelist elements from the mcp namespace should use the appropriate URL for the codeList attribute. For mcp elements the codelist URL is The name of the codelist element should be attached to the URL. For example, for the codelist element, mcp:MD_TemporalAggregationUnitCode, the codelist URL must be: An example of a codelist element from an MCP metadata record is:

Example of a codelist element from an MCP 2.0 metadata record

MCP XML Schemas (XSDs)

The schema documents (see XSD) and codelists for the Marine Community Profile are available online at

As the MCP is under development and contributing organisations develop and change metadata elements, code lists and content rules, an experimental version of the MCP exists at

MCP Implementations

The following versions of the MCP have been implemented as plugin metadata schemas for version 2.10.x of GeoNetwork opensource (see GeoNetwork):

  • Version 2.0 (described by this document)
  • Version 2.1 experimental (this document plus experimental extensions under development by users of the MCP)
  • Version 1.4
  • Version 1.5 experimental (=1.4 + experimental extensions)

You can obtain a complete release of GeoNetwork version 2.10.x with the MCP configured and ready to use in the ANZMEST package of GeoNetwork 2.10.x for AU/NZ users at A beta release of the ANZMEST package of GeoNetwork 3.1.x can be built by cloning and building the develop branch from the github repository at An installer release of 3.1.x with MCP 2.0 will be available from the sourceforge site from December 2015.