Skip to content
Permalink
1.3
Go to file
 
 
Cannot retrieve contributors at this time
34 lines (21 sloc) 2.27 KB

Dataset specification

Purpose: For every conformity statement, one citation of the product specification or user requirement against which data is being evaluated must be given.

Prerequisites

Test method

The test first checks if there is at least one specification. In case there is none, a warning is thrown. It then performs the following checks

  • The specification must contain an element of type gmd:CI_Citation/gmd:title which should not be an empty characterstring
  • The specification must contain an element of type gmd:CI_Citation/gmd:date[./*/gmd:dateType/*/text()='{type}']/*/gmd:date, where {type} is one of 'creation', 'revision' and 'publication'.
  • The specification has gmd:DQ_DomainConsistency as a parent element.

Reference(s)

Test type: Automated

Notes

The test method does not explicitly state if the test applies only to datasets, dataset series, or also services. TG MD sections 2.8 and 2.8.2 are not clear on this point, either. For example, section 2.8.2 says: "If a spatial data service is an INSPIRE Network service, use this element to report the relevant INSPIRE Network Implementing Rule to which it conforms." The test has therefore been implemented as a common test in the ETSs.

The test method states that a warning is thrown, if a metadata record does not contain a specification. The ETS only checks requirements, i.e. it detects failures. Therefore, it does not report warnings.

##Contextual XPath references

The namespace prefixes used as described in README.md.

Abbreviation XPath expression (relative to gmd:MD_Metadata)
specification ./gmd:dataQualityInfo/*/gmd:report/*/gmd:result/*/gmd:specification
You can’t perform that action at this time.