- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Jan 2019 13:16:41 +0000
- To: public-dxwg-wg@w3.org
@nicholascar , @rob-metalinkage , I still don't understand how tokens of this type (i.e., namespace prefixes), can be used as global identifiers, and not as something that is relative to the service / API. I can buy a usage scenario where (a) I ask a service to list the available profiles, (b) I get the list of URIs and corresponding tokens/prefixes, and (c) I make a query using the token mapping to a given profile URI. But in this case the token cannot be included in the definition of a profile, as it may vary from service to service. BTW, I would not bank at all on the fact that we have _de facto_ standard namespace prefixes. One example is `dc:` / `dct:` / `dcterms:` which are all used for http://purl.org/dc/terms/ (where `dc:` is also used for http://purl.org/dc/elements/1.1/). And another one is the use of `vcard:` and `vcard2006:` for http://www.w3.org/2006/vcard/ns# (where `vcard:` is also used for http://www.w3.org/2001/vcard-rdf/3.0#). And finally `geo:`, used for GeoSPARQL, although it was already widely used for the W3C Basic Geo vocabulary. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/453#issuecomment-452692732 using your GitHub account
Received on Wednesday, 9 January 2019 13:16:43 UTC