Skip to content
Permalink
1.3
Go to file
 
 
Cannot retrieve contributors at this time
178 lines (148 sloc) 16.6 KB

Conformance class: INSPIRE Profile based on EN ISO 19115 and EN ISO 19119

This conformance class is part of the Abstract Test Suite for the INSPIRE Metadata Technical Guidance.

Standardization target type

ISO 19115/19119 metadata record

Dependencies

Direct dependencies

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

Specification Conformance class Parameters
ISO 19115 n/a n/a
ISO 19119 n/a n/a

Indirect dependencies

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

Specification Conformance class Related resource Parameters
INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119 XML encoding XML document (MD_Metadata) encoding = ISO/TS 19139 or CSW ISO AP 1.0.0

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 INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119, version 1.3
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

TG Requirement coverage

Based on requirement numbering in TG MD.

Req# Description Covered by test(s) IR reference(s)
1 hierachyLevel mandated Hierarchy IR MD, Part B 1.3, Part D 1
2 MD_ScopeCode values Hierarchy IR MD, Part B 1.3, Part D 1
3 Resource Locator for data linkage Dataset linkage IR MD, Part B 1.4
4 Resource Locator for service linkage Service linkage IR MD, Part B 1.4
5 Unique Resource Identifier code is mandatory Dataset identification IR MD Part B 1.5
6 Use RS_Identifier if URI codeSpace provided Dataset identification IR MD Part B 1.5
7 operatesOn as a reference Coupled resource
8 Resource language is mandated Dataset language IR MD Part B 1.7
9 ISO 19139 codes used for language Dataset language IR MD Part B 1.7
10 Use MD_TopicCategoryCode values in topicCategory Dataset topic IR MD Part B 2.1
11 Use language neutral name in topicCategory Dataset topic IR MD Part B 2.1
12 Use language neutral name for serviceType Service type IR MD Part B 2.2
13 Provide at least one keyword Keyword IR MD Part B 3.1
14 Use theme for the only dataset keyword Dataset keyword IR MD Part B 3.1
15 Use category for the only service keyword Service keyword IR MD Part B 1.5, Article 4, part D  
16 Use citation for other controlled keywords Vocabulary IR MD Part B 3.2
17 Cite the originating controlled vocabulary Vocabulary IR MD Part B 3.2
18 At least title and date for controlled vocabulary citations Vocabulary IR MD Part B 3.2
19 Group keywords from the same controlled vocabulary Keywords in vocabulary IR MD Part B 3.2
20 Use the minimum geographic bounding box Geographic bounding box IR MD Part B. 4.1
21 At least two decimals for coordinates Geographic bounding box IR MD Part B. 4.1
22 Use at least one of INSPIRE temporal reference types Ds temporal IR MD Part B. 5.1
23 Use at least one ISO 19115 temporal reference types Ds temporal IR MD Part B. 5.1
24 Gregorian calendar and ISO 8601 date as defaults nothing to test, always true IR MD Part B 5
25 Single creation date mandatory Resource creation date IR MD Part B 5.4
26 Only one dataQualityInfo Lineage IR MD Part B. 2.6
27 Spatial resolution as either scale or ground sample distance Ds spatial resolution IR MD Part B. 2.6
28 Degree of conformity mandatory Dataset conformity IR MD Part B. 2.8
29 Use DQ_DomainConsistency for spec. conformity Ds specification IR MD Part B. 7.2
30 Declare both limitations on "public access" and "constraints on access and use" Dataset public access INSPIRE, Article 13
31 At least one MD_Contraints even if no limitations Dataset public access n/a
32 Expressing limitations on public access Dataset public access n/a
33 No conditions and unknown conditions Dataset access use  IR MD Part B. 8.2
34 Terms and conditions either embedded or linked Dataset access use IR MD Part B. 8.2
35 Responsible organisation name and email Responsible party contact info IR MD Part B. 3.5
36 MD_DataIdentification and SV_ServiceIdentification for responsible party info Responsible party contact info IR MD Part B. 3.5
37 Metadata point of contact organisation name and email Metadata contact IR MD Part B. 10.1
38 Metadata point of contact role code 'pointOfContact' Metadata contact role n/a
39 Metadata language is mandatory Language IR MD Part B. 10.3

Test

This Conformance Class contains the following tests:

Identifier Status
Hierarchy Ready for review
Dataset keyword Ready for review
Service keyword Ready for review
Dataset identification Ready for review
Dataset linkage Ready for review
Service linkage Ready for review
Dataset language Ready for review
Dataset topic Ready for review
Service type Ready for review
Keyword Ready for review
Vocabulary Ready for review
Keywords in vocabulary Ready for review
Geographic bounding box Ready for review
Dataset temporal Ready for review
Lineage Ready for review
Dataset conformity Ready for review
Dataset specification Ready for review
Dataset public access Ready for review
Dataset access use Ready for review
Responsible party contact info Ready for review
Metadata contact Ready for review
Metadata contact role Ready for review
Language Ready for review
Dataset spatial resolution Ready for review
Resource creation date 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 questions

Should these be excluded or included in the ATS? Or added as requirements in the TG MD?

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
You can’t perform that action at this time.