Coupled resource implementation is not compliant
Closed this issue · 5 comments
ISO requirement for the operatesOn element is the following:
Thus the link should point to a MD_DataIdentification XML element.
However in the current proposal the link will point to the MD_Metadata element.
Suggestion: Addition of #MD_DataIdentification at the end of the URL would make the proposal compliant with ISO.
Austria suggests in its national md-guidline to use a http-URI as INSPIRE-UniqueRessourceIdentifier. This URI is redirected to the md-record at the national geoportal (automatically by the responsible authority).
Using this URI as CR ... identifies, where relevant, the target spatial dataset(s) of the service through their unique ressource identifier ...(unfortunately not iso complient ...).
We would welcome beeing able to keep our approach.
2022-02-25 Discussion:
Based on the discussion hold in the 2nd meeting for the 'Remapping of the extended capabilities', corresponding to Part B of the work of MIWP Sub-group on Action 2.3.2 'Simplification of Data and Service Linking', it was agreed to relax the implementation of the Coupled Resource by making the linkage to the #MD_DataIdentification section of the metadata an optional feature (i.e. pointing to the URL of the metadata, with or without the additional #MD_DataIdentification pointer)
(See specific agreement in the [minutes of the meeting](TG Requirement 3.6 of the INSPIRE Technical Guidelines on Metadata v2.1.0 (TG MD)))
Rationale
Although ISO 19119:2005 requires that the target of the operatesOn element (Coupled Resource) is the #MD_DataIdentification class of the linked dataset metadata, due to the different existing metadata implementations, it was agreed to allow a more simple implementation the Coupled Resource linkage containing the URL of the metadata, with or without the additional #MD_DataIdentification pointer.
As a result, TG Requirement 3.6 of the INSPIRE Technical Guidelines on Metadata v2.1.0 (TG MD) needs to be changed.
Additionally, an explanatory note will be added to the TG MD in order to explain this simplification.
Changes to the current INSPIRE framework
In Section 4.1.2.4 of the TG MD:
1. Replace current TG Requirement 3.6:
TG Requirement 3.6: metadata/2.0/req/sds/coupled-resource
Links pointing to the online metadata descriptions of data sets provided by the described service shall be given using srv:operatesOn element.
The multiplicity of this element is 0..n.
This property shall be implemented by reference. The xlink:href attribute of each of the srv:operatesOn elements shall contain a URI pointing to the gmd:MD_DataIdentification element of the metadata record of the provided the data set or data set series.
with this new text:
TG Requirement 3.6: metadata/2.0/req/sds/coupled-resource
Links pointing to the online metadata descriptions of data sets provided by the described service shall be given using srv:operatesOn element.
The multiplicity of this element is 0..n.
This property shall be implemented by reference. The xlink:href attribute of each of the srv:operatesOn elements shall contain a URI pointing to the metadata record of the provided data set or data set series.
2. Add the following TG Recommendation, and subsequent Explanatory note and Example, just after the amended TG Requirement 3.6:
TG Recommendation:
TG Recommendation X.Y:
In order to be fully compliant with [ISO 19119], the URI contained in the xlink:href attribute of each of the srv:operatesOn elements should specifically point to the gmd:MD_DataIdentification element of the metadata record of the provided data set or data set series.
Explanatory note:
NOTE: The different practices in the implementation of the Coupled Resource element in existing metadata is acknowledged. Despite [ISO 19119] requires that the target of the operatesOn elements (Coupled Resource) is the #MD_DataIdentification class of the linked dataset metadata, this technical guidelines allows a more simple approach for the service-data set linking by allowing, in the xlink:href attribute of each of the srv:operatesOn elements, the use of URI values with or without the #MD_DataIdentification pointer.
Example:
/gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:operatesOn:
<srv:operateson xlink:href="http://example.com/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=f9ee6623-cf4c-11e1-9105-0017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full> </srv:operateson>Example X.Y: Coupled resource link given using the srv:operatesOn element with URL pointing to the metadata record of the provided data set or data set series, without any fragment identifier specifically pointing to the gmd:MD_DataIdentification element.
Pending to propose an URI example.
A working Austrian URI example could be: https://data.inspire.gv.at/9db8a0c3-e92a-4df4-9d55-8210e326a7ed