Re: [dxwg] dcat:accessURL - check constraints

OK. Another observation: in the proposed model, the `accessService` link is a part of the DCAT 'backbone', which is something of a promotion compared with the role of `accessURL` inn DCAT-2014. i.e. its no longer just a link to an external resource denoted by a URL, its a link to a resource which is now a first-class part of DCAT, often listed in the same catalog. 

In order to complete this, I think the definition and `usageNote` of `accessURL` should be modified, because they refer rather too strongly to URL, while we need the specialized usage to be a 'link' or possibly (rarely) a nested blank-node.  I'm looking in the [RDF representation](https://github.com/w3c/dxwg/blob/gh-pages/dcat/rdf/dcat.ttl). 

**Currently:**

`rdfs:comment` "Could be any kind of URL that gives access to a distribution of the dataset. E.g. landing page, download, feed URL, SPARQL endpoint. Use when your catalog does not have information on which it is or when it is definitely not a download."

`vann:usageNote` "The value is a URL.
          If the distribution(s) are accessible only through a landing page (i.e. direct download URLs are          not known), then the landing page link should be duplicated as accessURL on a distribution." 

**Proposed:** 

`rdfs:comment` "Link to a resource that gives access to a distribution of the dataset. E.g. landing page, feed URL, SPARQL endpoint. Use for all cases except a simple download link, in which case downloadURL is preferred."

`vann:usageNote` "If the distribution(s) are accessible only through a landing page (i.e. direct download URLs are not known), then the landing page link should be duplicated as accessURL on a distribution." 

-- 
GitHub Notification of comment by dr-shorthair
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/124#issuecomment-387004579 using your GitHub account

Received on Monday, 7 May 2018 09:04:03 UTC