W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > December 2021

[dxwg] Example 59 servesDataset vs Distribution/accessService -- source of interoperability problem (#1436)

From: Stephen Richard via GitHub <sysbot+gh@w3.org>
Date: Wed, 08 Dec 2021 22:02:27 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issues.opened-1074882631-1639000946-sysbot+gh@w3.org>
smrgeoinfo has just created a new issue for https://github.com/w3c/dxwg:

== Example 59 servesDataset vs Distribution/accessService -- source of interoperability problem ==
The dataset access information in [Example 59](https://w3c.github.io/dxwg/dcat/#ex-service-gsa) is of course technically valid, but would be problematic in an environment where most access information is represented as distributions.  The distribution approach for this example would look like:

  rdf:type dcat:Dataset ;
  rdfs:comment "lots of other stuff here...";
  dcat:distribution [
	a dcat:Distribution;
	rdfs:comment "other properties here... blank node here for convienence";
	dcat:accessService ga-courts:jc-esri, ga-courts:jc-wfs, ga-courts:jc-wms;

The sparql query to pull the access information with this encoding is completely different from the approach in the example. Clients harvesting or working with metadata that might take either approach would have to write a more complex query or do some other preprocessing.   Both approaches work, but hopefully in a given catalog one or the other would be used consistently. 

(also comment in #1435 about used of dcterms:conformsTo and dcterms:Type for dcat:DataServices applies here as well)

Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1436 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 December 2021 22:02:29 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:38 UTC