search

INSPIRE-MIF / helpdesk-geoportal

Community discussion for INSPIRE geoportal topics
11 stars 3 forks source link

TG Requirement 3.6: metadata/2.0/req/sds/coupled-resource #159

Closed Kate-Lyndegaard closed 10 months ago

Kate-Lyndegaard commented 11 months ago

Hi,

I would like know if our implementation of TG Requirement 3.6: metadata/2.0/req/sds/coupled-resource and specifically the use of xpointer, poses any problems for harvesting.

TG Requirement 3.6: metadata/2.0/req/sds/coupled-resource suggests several implementation options:

The reference to the gmd:MD_DataIdentification element can be implemented e.g. in the following ways: • Point to the gmd:MD_DataIdentification elements using so called fragment identifiers added at the end of the URL address of the metadata document separated by a hash mark "#"[39]. The value of the fragment identifier should either match the value of the id attribute of the referred gmd:MD_DataIdentification element or be another valid XPointer expression referring to the gmd:MD_DataIdentification element. This kind of URL forms a valid XPointer[40] that can be understood and resolved and verified precisely by clients. (see Example 4.4 and Example 4.5).Note that the id attribute of gmd:MD_DataIdentification is optional, so it may not always exist in the referred metadata record. See TG Recommendation 1.1 for more info. • Point to the gmd:MD_DataIdentification element by using the Unique Resource Identifier of the target spatial dataset itself. The URI needs to resolve to the gmd:MD_DataIdentification element, e.g. through a dedicated resolver service translating the URI into a CSW request. (see Example 4.6).

Here is an example of our implementation:

<srv:operatesOn xlink:href="https://test.haleconnect.de/services/bsp/org.640.7622a2da-d5c2-4668-8614-a98016cf4723/md/dataset/dataset1#xpointer%28%2F%2Fgmd%3AidentificationInfo%5B1%5D%2Fgmd%3AMD_DataIdentification%29" uuidref="a0c56c49-74d5-4847-860b-fc243edd4a30"/>

Here is an example of our WFS metadata:

https://test.haleconnect.de/services/bsp/org.640.7622a2da-d5c2-4668-8614-a98016cf4723/md/service/id_direct_download

Can you please tell me if the use of xpointer is the reason why our hosted services are not being harvested? Any insight would be greatly appreciated.