- From: Peter Krauss <ppkrauss@gmail.com>
- Date: Thu, 7 May 2015 12:27:57 -0300
- To: Wes Turner <wes.turner@gmail.com>
- Cc: W3C Vocabularies <public-vocabs@w3.org>
- Message-ID: <CAHEREttzfaS7cte4RJiEtCWw5f6NKfpjcEYKmT4UMDj5cTJBdQ@mail.gmail.com>
2015-05-07 11:25 GMT-03:00 Wes Turner <wes.turner@gmail.com>: > So, AFAICT, the options, for the UN/CEFACT code "SEC" are: > > > 1. https://example.un.org/ns/cefact/codes/SEC > 2. http://example.un.org/ns/cefact#SEC > 3. urn:x-un-cefact:SEC > 4. SEC > > In terms of preference, I'd vote for 2, 3, 1, 4. > > Good! My vote for preferences is 3, 1, 2 - - - - Rationale: as discussed here before, all "standarizable URN" have an well-knowed (for user community) URN-Resolver, that is, an URL for this resolver. For webservice endpoints perspective, (and CoolURL recommendation, http://www.w3.org/TR/cooluris/ ), the "/SEC" is preferible than "#SEC". Example1: http://dx.doi.com is the well-knowed resolver for "urn:x-doi" URNs. So, with SchemaOrg we can define a property urlUrnResolver to remember that a URL is a URN-Resolver... p. ex. *<a itemprop="urlUrnResolver" href="http://dx.doi.org/10.1038/ncomms7368 <http://dx.doi.org/10.1038/ncomms7368>">doi:10.1038/ncomms7368</a>* Example2: of course, for *a priori* URNs or IANA URNs we can omit the resolver, p. ex. <span *itemprop="urn">urn:x-doi:**10.1038/ncomms7368</span> *or <span *itemprop="urn">**urn:issn:2041-1723</span>.* > On Thu, May 7, 2015 at 6:42 AM, Peter Krauss <ppkrauss@gmail.com> wrote: > >> >> >> 2015-05-07 5:36 GMT-03:00 Bernard Vatant <bernard.vatant@mondeca.com>: >> >>> (...) But to put in bluntly, in many cases, well-maintained codes for >>> standardized identities (languages, countries, towns, units ...) are more >>> sustainable ways to share identities than URIs, >>> >> >> >> Perhaps I am not understanding, but there are some conceptual mistake? >> "codes" in this sense, for me, are URNs; and URNs are URIs... Incremental >> examples: >> >> * "codes" are things controlled at https://github.com/datasets >> >> * the code of "Avestan" is "ae" in >> https://github.com/datasets/language-codes >> >> * in my context (ex. my house or my LAN) I can use my URN definition, >> * "urn:x-ok-datasets:language-codes:ae" * >> that is the "alpha2" column in >> https://github.com/datasets/language-codes/blob/master/data/language-codes.csv >> >> and the "URN Resolution" is the conversion from "alpha2" column to >> the "English" column. >> ... And so on... In the same URN-x-ok schema are many other code >> types, >> like "*urn:x-ok-datasets:country-codes:us*" defined by >> https://github.com/datasets/country-codes/ >> we are not hostages of IANA, we can use URN for any code. >> >> so, codes are URNs ... We can agree about the "*code is URN*" assertion? >> >> >
Received on Thursday, 7 May 2015 15:28:26 UTC