Improve mapping to dcat:Distribution

[streino]

Currently the XSLT maps resources to dcat:Distribution iif gmd:URL contains "?request=getcapabilities" or CI_OnLineFunctionCode is one of "download", "offlineAccess", "order".

The INSPIRE Technical Guidance defines other cases we believe should be mapped to dcat:Distribution. The summary below is our interpretation.

If this is of interest and we can reach a common interpretation, we would be willing to contribute a PR.

Resource pointing to a service (the description of a service)

Conditions

• gmd:URL set.
• gmd:protocol set to any ProtocolValue except OGC Catalogue Service for the Web, File for download or Web Address (URL).
• gmd:applicationProfile set to "view" or "download".

INSPIRE Technical Guidance

section 3.3 :

The class described in this section requires that the Resource Locator element points to the set of additional information about a service resource (i.e. "Get Download/View Service Metadata" operation).
Additionally, the class described in this section requires the presence of gmd:protocol and gmd:applicationProfile, paired with the defined codelist values from the INSPIRE Registry. This would imply fulfilling this portion of the simplification described here.

TG 8.1

TG 8.2

Resource pointing to the data of a service

Conditions

Same as above except gmd:applicationProfile.

• gmd:URL set.
• gmd:protocol set to any ProtocolValue except OGC Catalogue Service for the Web, File for download or Web Address (URL).
• gmd:applicationProfile not set.

INSPIRE Technical Guidance

section 3.3 :

The presence of additional Resource Locator elements, pointing to the data set itself (e.g. "Get Spatial Data Set" request of a Download Service), is allowed, due to the multiplicity expressed by TG Requirement 1.8. Consequently, these additional Resource Locator elements should avoid at least the use of the gmd:applicationProfile element specified below, in order to reduce the complexity of a machine-to-machine element recognition made by an INSPIRE software implementation such as the INSPIRE Geoportal.

[jakubklimek]

@streino Could you elaborate, preferrably using examples, what would the distributions look like? Do you suggest creating a "downloadable file" distribution for "Resource pointing to the data of a service" and a data service distribution for "Resource pointing to a service (the description of a service)"?

In addition, the "view" applicationProfile seems like a human UI, not a machine accessible data / service distribution, so maybe it would be better suited for a landing page (dcat:landingPage) or documentation (foaf:page)?