Support #3817

Linkage checker is reporting errors for metadata files made according to Metadata TG version 2.0

Added by Maxim Iurie 6 months ago. Updated 6 months ago.

Status:NewStart date:30 Jan 2020
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Linkage Checker
Target version:-
Submitting Organisation:Essensys Software Knowledge-Base relevant?:Yes
Proactive:Yes Keyword #1:
Country:RO - Romania Keyword #2:
Originating UI: Keyword #3:

Description

We confirm as well that metadata files made according to Metadata TG version 2.0 are triggering errors in the Linkage Checker as reported in issue #3815 .

The Metadata TG version 2.0, see section "Reading guidance and transition period" at page X states:

"To facilitate a smooth transition from version 1.3 to version 2.0, a transitional period of 3 years has been defined, starting from 19 December 2016. During this period, the metadata records compliant with both version 1.3 and 2.0 implementations will be considered as “compliant with the INSPIRE Technical Guidelines for Metadata”. During the transitional period, the validator used in the INSPIRE geoportal will validate against and will provide validation reports for both versions 1.3 and 2.0. The better result will be used for the value of the compliance meter. After the transitional period, the geoportal will only validate against version 2.0."

However the linkage cheker is trigering errors if the metadata files are made according to the TG version 2.0.

Indded there is a disclaymer at https://inspire-geoportal.ec.europa.eu/linkagechecker.html that is stating

DISCLAIMER: This web application is used in the context of supporting MS data providers with publishing their resources (Data Sets / Services) in the INSPIRE Geoportal. It cannot be considered as a full INSPIRE compliance test. For checking the compliance with INSPIRE Technical Guidelines, only the INSPIRE Reference Validator should be used. If inconsistencies found between the checks performed by the INSPIRE Geoportal and the Reference Validator, please report them here.

How it should be considered that the metadata files for the data set, view and download services are corectly linked:

1. That the first page of the Linkage checker is indicating the result of the linkage aspect with 7 green check boxes.

2. That the report that is available on click to "View the Evaluation report" shows no errors, including 100% interoperability.

In case that second option is the corect one, than we noticed that the linckage cheker is showing errors for metadata files made according to version 2.0 of the TG.

 

We split these errors in two categories:

1. Errors related to REQUIREMENTS in Metadata TG version 2.0.

2. Errors related to RECCOMANDATIONS in Metadata TG version 2.0.

For the first case there are two issues:

A. Related to conditions for access and use

<!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->
<!--  START In order to validate for version 1.3 it should look like this: -->
<gmd:resourceConstraints>
<gmd:MD_Constraints>
<gmd:useLimitation>
<gco:CharacterString>no conditions apply</gco:CharacterString>
</gmd:useLimitation>
</gmd:MD_Constraints>
</gmd:resourceConstraints>
<gmd:resourceConstraints>
<gmd:MD_LegalConstraints>
<gmd:accessConstraints>
<gmd:MD_RestrictionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode>
</gmd:accessConstraints>
<gmd:otherConstraints>
<gco:CharacterString>no limitations</gco:CharacterString>
</gmd:otherConstraints>
</gmd:MD_LegalConstraints>
</gmd:resourceConstraints>
<!--END In order to validate for version 1.3 it should look like this:-->
 
<!-- START In order to validate against version 2.0 it should look like this
<gmd:resourceConstraints>
<gmd:MD_LegalConstraints>
<gmd:useConstraints>
<gmd:MD_RestrictionCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions"/>
</gmd:useConstraints>
<gmd:otherConstraints>
<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/ConditionsApplyingToAccessAndUse/noConditionsApply">No conditions apply to access and use</gmx:Anchor>
</gmd:otherConstraints>
</gmd:MD_LegalConstraints>
</gmd:resourceConstraints>
<gmd:resourceConstraints>
<gmd:MD_LegalConstraints>
<gmd:accessConstraints>
<gmd:MD_RestrictionCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions"/>
</gmd:accessConstraints>
<gmd:otherConstraints>
<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/noLimitations">There are no limitations on public access to spatial data sets and services.</gmx:Anchor>
</gmd:otherConstraints>
</gmd:MD_LegalConstraints>
</gmd:resourceConstraints>
END In order to validate against version 2.0 it should look like this -->
<!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->

B. Related to spatial data service category (not applicable for data set). 

Example for download service, similar for view service.

<!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->
<!-- START SECTION for version 1.3 and for old validator from Linkage checker -->
<gco:CharacterString>infoFeatureAccessService</gco:CharacterString>
<!--END SECTION for version 1.3 and for old validator from Linkage checker -->
<!-- START section for version 2.0 on the official validator
END section for version 2.0 on the official validator -->
<!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->
 
In relation to point 2 there are a lot of errors reported by the Linkage checker if implementing recomandations from Metadata TG version 2.0.
For example:
a) providing <gmd:identifier> as <gmd:MD_Identifier> instead of <gmd:RS_Identifier> as strongly recommended in REC 1.1 of the TG version 2.0
b) providing identifier of the metadat file as a HTTP URI by using an anchor instead of providing a code as characterstring.
.....
we can continue the list, if necessary and if these issues are not known.
 
At least the issues from category 1 should be solved in the first place (1. Errors related to REQUIREMENTS in Metadata TG version 2.0.)
 
Best regards,
Iurie Maxim

History

#1 Updated by Maxim Iurie 6 months ago

In order to test:

 

Link to data set metdata according to version 2.0 of the TG: https://inspire.meteoromania.ro/WIGOS/MD-DS

Link to view service metdata according to version 2.0 of the TG: https://inspire.meteoromania.ro/WIGOS/MD-WMS

Link to download service metdata according to version 2.0 of the TG: https://inspire.meteoromania.ro/WIGOS/MD-WFS

 

 

Link to data set metdata according to version 1.3 of the TG: https://geoportal.meteoromania.ro/WIGOS/MD-DS

Link to view service metdata according to version 1.3 of the TG: https://geoportal.meteoromania.ro/WIGOS/MD-WMS

Link to download service metdata according to version 1.3 of the TG: https://geoportal.meteoromania.ro/WIGOS/MD-WFS

 

We are waiting for a feedback in order to understand if the linkage checker has an issue, or if we should change something within the implementation.

Also available in: Atom PDF