W3C home > Mailing lists > Public > www-tag@w3.org > June 2006

RE: CURIEs: A proposal

From: Misha Wolf <Misha.Wolf@reuters.com>
Date: Tue, 13 Jun 2006 14:04:18 +0100
To: "Henry S. Thompson" <ht@inf.ed.ac.uk>, www-tag@w3.org
Cc: public-rdf-in-xhtml-tf@w3.org, newsml-2@yahoogroups.com
Message-id: <A29ADE959C70A1449470AA9A212F5D800203FC4C@LONSMSXM06.emea.ime.reuters.com>

Hi Henry,

> My initial reaction is similar to Stuart's -- there's a lot to 
> agree with here, but
>
> 1) I think we do better to keep QNames (shorthand for an *expanded
>    name* which is a pair of an absolute IRI and an NMTOKEN local
>    name) and CURIEs (shorthand for an IRI) clearly distinguished
>    conceptually;
>
> 2) We think seriously about an alternative to the ':' as the
>    separator for CURIEs.

I seem to be having a real problem contesting the accepted reality
that a CURIE is a shorthand for an IRI.  As I explained in my 
Edinburgh presentation, what the IPTC requires is a {prefix, suffix} 
tuple, associated with two IRIs:
  -  one corresponding to the prefix,
  -  one corresponding to some combination of the prefix and the 
     suffix.

As you and others pointed out in Edinburgh, the most obvious way
of combining prefix and suffix would yield illegal fragment IDs, 
given that many of the suffix values are numeric.  The available 
solutions appear to be:

S1.  Define a new media-type, which allows numeric fragment IDs.  
     This approach would prevent the use of HTML or HTML/RDF pages 
     for documenting taxonomies.

S2.  Don't use numeric suffix values.  This approach to reality was, 
     I'm pleased to say, recognised as ostrich-like when the W3C and 
     the IETF accepted IRIs as real-world constructs and URIs as 
     mangled IRIs, to be used in those environments which can't cope 
     with IRIs.

S3.  Define a construction rule which avoids these problems, eg:
        <prefixIRI> & "#_" & <suffix>

This reminds me that simple concatenation:
     <prefixIRI> & <suffix>
would be broken as we would have to end the <prefixIRI> with a "#".
This would mean that the page corresponding to a taxonomy as a whole 
would be identified by, eg:
     http://example.org/taxonomy1#
My reading of the relevant specs suggests that this would be wrong.

Regards,
Misha
------------------- NewsML 2 resources ------------------------------
http://www.iptc.org         | http://www.iptc.org/std-dev/NAR/1.0
http://www.iptc.org/std-dev | http://groups.yahoo.com/group/newsml-2


To find out more about Reuters visit www.about.reuters.com

Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
Received on Tuesday, 13 June 2006 13:04:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:40 GMT