- From: Tim Berners-Lee <timbl@w3.org>
- Date: Thu, 5 Apr 2012 13:02:10 +0100
- To: Phil Archer <phila@w3.org>
- Cc: "public-lod@w3.org" <public-lod@w3.org>
Sent from my portable device. On Apr 3, 2012, at 16:58, Phil Archer <phila@w3.org> wrote: > Again, thanks everyone for the quick and useful responses. > > @Gannon, @Andy - you are right that the issue of sex/gender is far from straightforward (they're not even the same thing I've learned!) However, I need to offer 'something' even if it's not ideal and then work on the longer term. > > @Sarven - SDMX looks very useful indeed, hadn't seen that they cover gender - great. > > But it doesn't answer the more general point (I was using sex/gender as an example - there are other terms for which the value space should be a controlled vocabulary that doesn't necessarily have a URI). > > Here's my plan of action: > > Short term: the limitation here is that all I'm chartered/empowered to do is to define the terms (actually I'm planning to use schema:gender). I am not, and I don't believe the EU (current project paymasters) or the GLD WG/W3C more generally is not, in a position to set up some sort of de-referencing system. Well actually you are. The world loses when RDF terms can't be looked up to yield useful information, or when things supporting Uris rot, so a W3C policy is if in doubt to allow a group at or loosely affiliated with W3c to set up a persistent supporting document. The emphasis for me is on the machine-readable bit -- it should of course point to online human-readable documentation where it can but also carry as many tips for machines as possible We could look at the idea of setting up fit example a w3.org/ns/iso/5006 space even to hold machine-readable info about frozen stuff ISO has not learned to support S linked data yet. If we do a few, future ISO standards might get the message and be supported by ISO. Note the namespace does NOT imply W3c rec track, or any process. That is the point, that as the process and status change, the URI will not. So people won't have to recode. (It would obviously be nice, from the bootstrap point of view, to have stuff usable for automatically building a Ui, like a regexp for valid strings in the lexical space. That is another interesting thread ...) > Even up Purls means that we're in effect condoning a value space (and I have at least 3 on my radar for just this term alone - Gannon pointed to some useful info from LoC which might make 4, plus SDMX makes 5). > > So I'm going to have to fudge it for now and say 'provide an identifier' and may leave it at that. I'd like to offer more guidance but it may not be sensible to do so (and btw. these vocabularies have to work in XML as well as RDF). > > Longer term... I think I'll drop a line to Norman Paskin at the DOI Foundation... > > Phil. > > > On 03/04/2012 16:22, John Erickson wrote: >> Gannon raises a valid point, BUT it is important to remember that ISO >> is a *publisher* and DOI is fundamentally a publishing industry thing. >> >> So while they might not be inclined to support Cool URIs for their own >> sake, they might be DOI adopters for the sake of The Bottom Line... >> >> On Tue, Apr 3, 2012 at 11:19 AM, Gannon Dick<gannon_dick@yahoo.com> wrote: >>> There are just some things outside of the Web's bailiwick, and the >>> properties of people in that class. The problem is that you are never sure >>> if you are naming the property on rudely calling the property holder names. >>> ISO declines to play, the LOC declines differently >>> http://id.loc.gov/authorities/subjects/sh91003756 and simple classes don't >>> exist. I think you've hit a limit, not on Cool Uri's necessarily, but maybe >>> on philosophy. >>> >>> ________________________________ >>> From: John Erickson<olyerickson@gmail.com> >>> To: David Booth<david@dbooth.org> >>> Cc: Phil Archer<phila@w3.org>; "public-lod@w3.org"<public-lod@w3.org> >>> Sent: Tuesday, April 3, 2012 9:53 AM >>> Subject: Re: Datatypes with no (cool) URI >>> >>> On Tue, Apr 3, 2012 at 10:38 AM, David Booth<david@dbooth.org> wrote: >>>> On Tue, 2012-04-03 at 14:33 +0100, Phil Archer wrote: >>>>> [ . . . ] The actual URI for it is >>>>> >>>>> http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=36266 >>>>> (or rather, that's the page about the spec but that's a side issue for >>>>> now). >>>>> >>>>> That URI is just horrible and certainly not a 'cool URI'. The Eurostat >>>>> one is no better. >>>>> >>>>> Does the datatype URI have to resolve to anything (in theory no, but in >>>>> practice? Would a URN be appropriate? >>>> >>>> It's helpful to be able to click on the URI to figure out what exactly >>>> was meant. How about just using a URI shortener, such as tinyurl.com or >>>> bit.ly? >>> >>> David's good point raises an even bigger point: why isn't ISO minting >>> DOI's for specs? >>> >>> Or, at least, why can't ISO manage a DOI-equivalent space that would >>> rein-in bogusly-long URIs, make them more manageable, and perhaps more >>> functional e.g. CrossRef's Linked Data-savvy DOI proxy >>> <http://bit.ly/HcStYl> >>> >>> >>> -- >>> John S. Erickson, Ph.D. >>> Director, Web Science Operations >>> Tetherless World Constellation (RPI) >>> <http://tw.rpi.edu> <olyerickson@gmail.com> >>> Twitter& Skype: olyerickson >>> >>> >>> >> >> >> > > -- > > > Phil Archer > W3C eGovernment > http://www.w3.org/egov/ > > http://philarcher.org > +44 (0)7887 767755 > @philarcher1 > >
Received on Thursday, 5 April 2012 16:59:07 UTC