search

inspire-eu-validation / download-service

Abstract Test Suite for the Technical Guidance for the implementation of INSPIRE Download Services
Creative Commons Zero v1.0 Universal
2 stars 4 forks source link

A.13.IR221.TGR13.datasetidentifiers #63

Closed jensscheerlinck closed 8 years ago

jensscheerlinck commented 8 years ago

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685

Comment

äthe dataset identifier code and dataset identifier namespace must be present in the metadata document of the service' is too vague. What does äbe present' mean? Included somewhere in the document or in specific elements?

Proposed Change

Clarify.

thijsbrentjens commented 8 years ago

We should mention the specific metadata elements then. In this case I think that it is okay, but we have to be careful that the Download ATS will not become a Metadata ATS too. Then it would be better to define a cross-cutting issue or a metadata ATS issue and refer to that from this test.

In service metadata, the Coupled resource (identificationInfo[1]/*/operatesOn) shall be used for this. However, this element does not necessarily contain a code and namespace element, making testing very hard.

thijsbrentjens commented 8 years ago

Because the 2nd bullet is more about testing consistency between the ATOM feed and the related metadata document(s), my proposal is to:

  1. create a test in another / separate ATS (on interoperability or consistency) to test consistency between metadata documents and service documents
  2. remove the second bullet from A.13.IR221.TGR13.datasetidentifiers and refer in the notes to the test of the previous point.
nmtoken commented 8 years ago

I don't think there is a requirement in the implementing regulation to have a dataset identifier code and dataset identifier namespace, this is just one option ~ Spatial Data Set Identifier maps to RS_Identifier. [INS NS] tells us the Spatial Data Set Identifier parameter shall contain the Unique Resource Identifier which does _NOT _ imply an HTTP-URI. The alternative option is that the Spatial Data Set Identifier maps to MD_Identifier, which can be a UUID for example.

thijsbrentjens commented 8 years ago

Discussed in the call on resolution.

Conclusion:

  1. flag all issues regarding Cross-component consistency / interoperability. This issue should be flagged
  2. remove the second bullet from A.13.IR221.TGR13.datasetidentifiers and refer in the notes to the test of the previous point.

TODO: Finalize this if the label for flagging cross component consistency is added.