2017.4 meeting #11 2019-07-17

Agenda and minutes of previous meeting approved. Some actions are still open:

• some actions requiring development by the Contractors have not yet been addressed

• issue #44 (about SLD extension to WMS) is waiting for some more examples from other countries, regarding extensions

• issue #53 (about the example of MD TG v.2.0 to be placed on the INSPIRE website): JRC thanks Antonio, Anja and James for the comments and the PRs, wich were integrated in the MD file. No other comments are made.

  • JRC to publish the sample MD TG v.2.0 for data sets on the IKB page

  • JRC to produce a sample MD TG v.2.0 for services and share it with the sub-group

• The production instance was finally moved from the sandbox (hosted by the JRC) to the cloud:
  • a redirection was setup to make the production instance of the validator available at http://inspire.ec.europa.eu/validator
  • this instance includes the new ETS on MD TG v.2.0 and View Services (WMS/WMTS)
• Over the last week there were some issues with the cloud production instance (the validator was down or not working properly):
  • the issue is under investigation

• #56 Error in WCS Core test: The ExtendedCapabilities section shall be provided in the path
  • There are valid reasons for both requiring the same path as WFS (consistency with WFS) and allowing a free choice of the path (semantic inconsistency with the purpose of the ExtendedCapabilites section).
    
  • Bart mentions that the same discussion came out also when writing the WCS TG. His preference is to be consistent with WFS.
  • It is decided to leave the discussion open and ask for more feedback by national WCS experts.

• All to ask feedback to WCS national experts and report the feedback in the GitHub issue.

• #69 Metadata dataset: The attribute code list is not correct
  • It is agreed that the Validator should only check the value of the codeListValue attribute, and not the value of the codeList attribute.
  • JRC is in contact with ISO, but there seems to be some confusion also on their side on what is the recommended authoritative URI.

• JRC to update the TG by:
  • removing all the footnotes and updating the corresponding requirements (if needed)
    
  • add a recommendation at the beginning of the TG (e.g. in Section 2.1.1) listing the recommended URIs of the ISO code lists
  • a similar solution might be done for the case of issue #52 about the language code list

• #70 Metadata dataset: Keyword originating CV (C.15)
  • The solution regarding the ISO code list is the one agreed in #69, i.e. the Validator should only check the value of the codeListValue attribute, and not the value of the codeList attribute.

• #71 Metadata dataset: limitations on public access (C.17)
  • The solution regarding the ISO code list is the one agreed in #69, i.e. the Validator should only check the value of the codeListValue attribute, and not the value of the codeList attribute.
  • Regarding the use of Anchor with a URI different than those allowed by the TG, it is agreed that the Validator should check that there is at least one instance of the gmd:otherConstraints with either an Anchor pointing to a URI or a gco:CharacterString.
    • the same applies to issue #72.
      

• Contractors to change the test, accordingly.

• #73 Metadata dataset: Character encoding
  • It is agreed that no error should be thrown when utf-8 is the only encoding.

• Contractors to change the test, accordingly.

• #74 Metadata service: Spatial Data Service Type (MD SDS 3.5)
  • The use of Anchor would make it possible to use labels in national languages.
  • However, the use of Anchor instead of codeSpace inside LocalName is not allowed by the schema.

• JRC to provide a proposal to solve the issue.
  

• The workshop is planned for October 1-2, 2019 at the JRC in Ispra:
  
  • the first day will be for users, the second day for developers
  • a survey was created to collect expressions of interest to attend the workshop and preferences on the topics to be covered (deadline: July 31)
  • a draft agenda will be circulated in August

AOB

• Issue #7: little feedback on this new functionality was received.
  

• All to provide feedback.

• The date of next meeting (after summer) will be communicated by JRC.