Skip to content

Latest commit

 

History

History
 
 

common

Common requirements for XML Encoded INSPIRE metadata

This group describes metadata elements that shall be used in the same way in all the Conformance Classes.

This set of requirements does not comprise a Conformance Class, but it is referred to from the others Conformance Classes of the implementation of "INSPIRE dataset and service metadata based on ISO/TS 19139:2007" INSPIRE Metadata based on the corresponding technical guidance TG MD.

Note: It is in Ready for review stage, none of the tests have an official INSPIRE MIG approval.

Standardization target type

ISO/TS 19139:2007 Geographic information Metadata XML schema implementation.

Dependencies

Direct dependencies

A direct dependency is another conformance class whose requirements must be met by the metadata record, too.

There is not direct dependencies for this set of requirements.

Indirect dependencies

An indirect dependency is another conformance class whose requirements must be met by a related resource.

There is not indirect dependencies for this set of requirements.

External document references

Abbreviation Document name
INSPIRE Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE)
IR MD COMMISSION REGULATION (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata
TG MD Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007, version 2.0
REG INSPIRE Registry
ISO 19115 ISO 19115:2003 Geographic information - Metadata
ISO 19119 ISO 19119:2005 Geographic information - Services
ISO 19108 ISO 19108:2002 Geographic information -- Temporal schema
ISO 8601 ISO 8601:2004 Data elements and interchange formats -- Information interchange -- Representation of dates and times
ISO 639-2/B ISO 639-2/B: Codes for the Representation of Names of Languages

TG Requirement coverage

Based on requirement numbering in TG MD.

Req# Description Covered by test(s) IR reference(s)
C.1 XML Schema xml-schema
C.2 Root Element root-element
C.3 Encoding of Code List Values code-list-value
C.4 Encoding of Free Text Values free-text
C.5 Language Code metadata-language-code
C.6 Metadata Point of Contact md-point-of-contact
C.7 Metadata Date md-date
C.8 Resource Title resource-title
C.9 Resource Abstract resource-abstract
C.10 Responsible Organisation responsible-organisation
C.11 Temporal References temporal-reference
C.12 Not More than one Date of Creation max-1-date-of-creation
C.13 Not More than one Date of Last Revision max-1-date-of-last-revision
C.14 Temporal Extent temporal-extent
C.15 Keyword Originating CV keyword-originating-cv
C.16 Group Keywords by CV group-keywords-by-cv
C.17 Limitations on Public Access limitations-on-public-access
C.18 Conditions for Access and Use conditions-for-access-and-use
C.19 Geographical Bounding Box bounding-box
C.20 Conformity Statement conformity
C.21 Conformity Specification conformity-specification
C.22 Conformity Degree conformity-degree

Test

This Conformance Class contains the following tests:

Identifier Status
xml-schema Ready for Review
root-element Ready for Review
code-list-value Ready for Review
free-text Ready for Review
metadata-language-code Ready for Review
md-point-of-contact Ready for Review
md-date Ready for Review
resource-title Ready for Review
resource-abstract Ready for Review
responsible-organisation Ready for Review
temporal-reference Ready for Review
max-1-date-of-creation Ready for Review
max-1-date-of-last-revision Ready for Review
temporal-extent Ready for Review
keyword-originating-cv Ready for Review
group-keywords-by-cv Ready for Review
limitations-on-public-access Ready for Review
conditions-for-access-and-use Ready for Review
bounding-box Ready for Review
conformity Ready for Review
conformity-specification Ready for Review
conformity-degree Ready for Review

Some additional metadata tests are available in the conformance class 'Metadata for interoperability'. These tests are separated from above because they have a different timeline for implementation.

Vocabulary

Empty characterstring: ISO/TS 19139 allows (if proper namespaces are available) to express any characterstring as either gco:CharacterString, gmd:Anchor or gmd:PT_FreeText.

To check an element for having an empty CharacterString, each of these representations should be considered. The PT_FreeText element can be used to supply multilingual values for a CharacterString. If only PT_FreeText is used the validator should check if a value of the string is available in the main language of the document. gmx:Anchor is typically used to reference a URI on which additional information is available. The validator could retrieve the resource at the URI in the gmx:Anchor to validate, if that content is available.

Some examples for valid string content:

  <gmd:keyword>
    <gco:CharacterString>Addresses</gco:CharacterString>
  </gmd:keyword>

or

  <gmd:keyword>
    <gmx:Anchor xlink:href="http://www.eionet.europa.eu/gemet/en/inspire-theme/5297/">Addresses</gmx:Anchor>
  </gmd:keyword>

or

<abstract xsi:type="PT_FreeText_PropertyType">
  <gco:CharacterString>Brief narrative summary of the content of the
resource</gco:CharacterString>
  <!--== Alternative values ==-->
  <PT_FreeText>
    <textGroup>
      <LocalisedCharacterString locale="locale-fr">Résumé succint du contenu du jeu de données</LocalisedCharacterString>
    </textGroup>
    <textGroup>
      <LocalisedCharacterString locale="locale=it">
        Succinta descrizione del contenuto della risorsa
      </LocalisedCharacterString>
    </textGroup>
  </PT_FreeText>
</abstract>

Open issues

XML namespace prefixes

The following prefixes are used to refer to the corresponding XML namespaces in all test descriptions:

Prefix Namespace
gmd http://www.isotc211.org/2005/gmd
gco http://www.isotc211.org/2005/gco