MIWP-8 Final comment resolution meeting 2016-11-21

Monday, 21 November 2016, 14:30-16:30 CET

Connection details

Agenda

[14:30-16:15] Discussion of remaining open issues

  1. How to use unique identifiers to refer to specifications?
  2. How to use unique identifiers to refer to controlled vocabularies?
  3. Allowing the use of RS_Identifier for the unique resource identifier?
  4. How to specify the coordinate reference system for data sets with an indirect spatial reference (e.g. statistical data)?
  5. How to provide more detailed information on the service type?

[16:15-16:30] Next steps

Minutes

Attendees

Marie Lambois (FR), Peter Kochmann (DE), Christine Brendle (AT), Alejandro Guinea (ES), Lenka Rejentova (CZ), Ouns Kissiyar (Be), Javier Nogueras (ES), Ine de Visser (NL), Henrique Silva, André Serronha (PT), Angelo Quaglia, Michael Lutz (JRC)

Agreed resolutions

How to use unique identifiers to refer to specifications & controlled vocabularies?

  • RECOMMEND the use of Anchors in the title elements, e.g. "For references to well-known INSPIRE legal acts, technical guidance documents or conformance classes, the title element of the specification SHOULD be encoded using the gmd:title/gmx:Anchor element." plus
  • OFFER the use of "pre-cooked" CI_Citation elements provided in the inspire.ec.europa.eu namespace, e.g. "For references to well-known INSPIRE legal acts, technical guidance documents or conformance classes, the specification element MAY be encoded as a reference (using the xlink:href attribute of the gmd:specification element) to an XML fragment document containing the CI_Citation element of the relevant specification."
  • JRC to investigate how to provide XML fragments in different languages, preferrably using a single URI (i.e. through content negotiation)

Allowing the use of RS_Identifier for the unique resource identifier?

  • RS_Identifier will be allowed as an option, but MD_Identifier will be strongly recommended.
  • Explain that many applications only consider the code attribute and not the codeSpace
  • Make example 3.2 consistent with example 4.6
  • It would be nice to harmonise the examples in section 4.1.2.4 using the same data set metadata record, but this is currently not feasible (given the strict deadlines).

How to specify the coordinate reference system for data sets with an indirect spatial reference (e.g. statistical data)?

  • A reference system shall also be provided for data sets with indirect spatial reference, in the same way as CRSs (using the Anchor element).
  • Do not include a concrete example.
  • Include a note pointing to a discussion on the thematic clusters platform to come up with best practices on what URIs to use for these reference systems (URI of the data set or of its metadata record? ...)

How to provide more detailed information on the service type?

  • Include no specific recommendations on how to provide additional information on the detailed service type or sepcification.
  • Add a note saying that such information can be provided in several ways in the MD document, e.g. using keywords, gmd:transferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:linkage/gmd:protocol, serviceTypeVersion.

TG_Metadata_v2.0rc5.docx - rc5 sent to MIG for endorsement (clean) (1.24 MB) Michael Lutz, 23 Nov 2016 07:10 pm

TG_Metadata_v2.0rc5_vs_rc4.docx - rc5 sent to MIG for endorsement (with tracked changes) (1.25 MB) Michael Lutz, 23 Nov 2016 07:10 pm

TG_for_INSPIRE_MD_v2.0rc2_comments_NON-EDITORIAL_resolutions.docx - Final resolutions to non-editorial comments (111 KB) Michael Lutz, 23 Nov 2016 07:11 pm