New ATSs/ETSs for the integration of Good Practice "Data and Service Linking Simplification"

[fabiovinci]

Dear Community,

this message is to inform you that the ATSs/ETSs for the integration of the Good Practice "Data and Service Linking Simplification" into the Reference Validator are under development and the related tests will be soon available.

Good Practice includes two main parts:

• Part A (Section 8): "Data-Service Linking Simplification. Requirements classes", which includes requirements/recommendations to be added/updated in the relevant TGs, and in particular:
  • Section 8.1: INSPIRE Data Set Metadata Resource Locator, which requires:
    • Change in the MD TG (Issue #108)
    • New ATS/ETS: “Conformance Class 8: INSPIRE data sets and data set series linked service metadata”
  • Section 8.2: INSPIRE Network Service Metadata Coupled Resource, which requires:
    • Change in the MD TG (Issue #108)
    • Change in the Service TGs (Issues #105, #110 and #112)
• Part B (Section 9): Use of INSPIRE conformant standard capabilities documents, which requires:
  • Update of the ATS/ETS for View Service
  • Update of the ATS/ETS for Download Service - WFS
  • Update of the ATS/ETS for Download Service - ATOM

The new ATS “Conformance Class 8: INSPIRE data sets and data set series linked service metadata” is already available, so any comment/suggestion is more than welcome.

Status updates will follow in this discussion.

[fabiovinci]

Dear Community,

we inform you that the “Conformance Class 8: INSPIRE data sets and data set series linked service metadata” is available on the staging instance and it is ready for testing.

You will find it, as preselected, in the "Advanced options" menu.

Feel free to test it and report any problem/suggestion/comment through the issue tracker.

[hogredan]

Thank you for the opportunity to test the new Conformance Class 8.

However, this new Conformance Class should no longer be preselected when publishing it in the production environment, as the requirements from the good practice do not have to be fulfilled by all data sets metadata.

[fabiovinci]

Dear @hogredan,

it was decided to set the new Conformance Class 8 selected by default, to “force” the users to provide and encode the Resource Locator elements as requested by the Good Practice for different reasons:

• the multiplicity of this element is zero or more, but it is "mandatory if a URL is available to obtain more information on the resource, and/or access related services."
• the INSPIRE legal framework requires that data sets are made available through View and Download services, which in turn implies that at least two resource locator elements need to be expressed in the data set metadata: one for a View Service and one for a Download Service.
• setting up the correct resource locators is important for the connection between the data set and the services that provide access to it (e.g. it facilitates the machine-to-machine element recognition made by an INSPIRE software implementation such as the INSPIRE Geoportal).

In any case, this is our proposal and may be subject to review.

[hogredan]

Dear @fabiovinci ,

this would break existing implementations with well-working data-service coupling and would mean (if I am right) that CC 8 is also used to check the conformity of dataset metadata in the INSPIRE monitoring.

And this was not agreed in the MIG-T. The simplified data-service coupling is only an alternative approach and to be used in parallel with the current one (as described in the TG documents on metadata, view services and download services). Thus, the current approach must remain valid!

Therefore, in our view, the new CC should not be selected by default.

[fabiovinci]

Dear @hogredan,

there are no issues with the existing implementations as CC8 can always be deselected and was not used in the monitoring.

The current approach remains valid and compliance with CC8 is only a "recommendation" for users who are not implementing the "Data and Service Linking Simplification" good practice.

[fabiovinci]

Dear Community,

we inform you that the sample metadata "Dataset_metadata_2.0_example.xml" was updated to be compliant with Conformance Class 8.

It now contains the two "Resource Locator" elements encoded according to the Good Practice "Data and Service Linking Simplification".

[fabiovinci]

Dear Community,

we inform you that Part A. Data-Service Linking Simplification. Requirements classes of the Good Practice was implemented.

All the required TG changes were included in the latest TG release and the new Conformance Class 8 is available in the production instance of the Reference Validator.