B.3

Extending DMF

Rule 7: Any extension of DMF has to be handled in a new metadata class.

A DMF Profile can add a new resource type.

Rule 8: In this case, it shall specify the DMF Metadata elements applicable to the new resource type, i.e. for each applicable DMF Metadata element, its cardinality, its domain of value, and its specific constraints.

A DMF profile can define new properties of existing DMF Complex Type and implicitly make them applicable to the DMF Metadata elements as part of a profile metadata class.

Rule 9: In this case, it shall specify for each new property of the complex type, its cardinality, its domain of value and its specific constraints.

A DMF profile can define new codelists.

Rule 10: Values for this list of codes have to be defined and made accessible to the audience of the profile. As long as the implementation of the new codelist uses either a URI Scheme compatible with the DMF’s one or the DMF generic codelist implementation; it is not seen as an extension of DMF. Thus, any extension of the codelist is not seen as an extension of DMF. However, any restriction of the domain of value or any new constraints applicable to the existing DMF metadata elements have to be expressed as additional requirements in a profile metadata class.

A DMF Profile may define metadata elements which are not in scope with the ISO metadata standards and the DMF/Defence metadata extensions of ISO 19115.

Rule 11: In this case, the full documentation of the concepts (conceptual schema, data dictionary, etc) and their XML Schema Implementation shall be made available.