- From: Nicholas Car via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Jan 2019 23:48:06 +0000
- To: public-dxwg-wg@w3.org
Tokens for identifying profiles are seen in use in APIs such as Epimorphic's ELDA and CSIRO's pyLDAPI, e.g.: * OGC using a SISSVoc implementation of ELDA, 'alternates' view (profile) in use: <http://www.opengis.net/def/ogc?_view=alternates> * Aust Gov using pyLDAPI to deliver a DCAT (rev) view of a dataset, in Turtle: <http://linked.data.gov.au/dataset/gnaf?_view=dcat&_format=text/turtle> So in the first case, the profile (view) token used is 'alternates', in the second its 'dcat'. There may be no URI equivalent for the first (it's listing of available profiles and, unless defined with a standard, may be replaced with mechanics specified in Profiles Conneg) clearly however the second use, of dcat, is equivalent to profile identification via DCAT namespace URI. Yes, it would be an option to URL encode the DCAT namespace URI yielding http://linked.data.gov.au/dataset/gnaf?_view=http%3A%2F%2Fwww.w3.org%2Fns%2Fdcat%23&_format=text/turtle but this is ugly and long. All we are really dealing with is the equivalent of `@prefix dcat: <http://www.w3.org/ns/dcat#>` for convenience of use. This Issue's question is whether adms:identifier can describe identifier use like that. We've not been using URIs - encoded or unencoded - as tokens. -- GitHub Notification of comment by nicholascar Please view or discuss this issue at https://github.com/w3c/dxwg/issues/453#issuecomment-452504617 using your GitHub account
Received on Tuesday, 8 January 2019 23:48:07 UTC