W3C home > Mailing lists > Public > public-esw-thes@w3.org > April 2004

Re: URIs for Concepts: Best Practices

From: David Menendez <zednenem@psualum.com>
Date: Fri, 23 Apr 2004 02:05:08 -0400
To: David Menendez <zednenem@psualum.com>
Cc: Charles McCathieNevile <charles@w3.org>, Kal Ahmed <kal@techquila.com>, "'public-esw-thes@w3.org'" <public-esw-thes@w3.org>
Message-id: <r02000200-1033-2C8370E294EC11D8AF23000393758032@[10.0.1.5]>

I wrote:

> Alternately, if I'm correct in thinking that HTTP lets you use
> Content-ID, you could identify specific representations using cid:
> URIs.

Maybe something like this:

    GET /term/Dog HTTP/1.1
    Host: www.example.org
    ...more fields...

--

    202 Found
    Content-Type: application/rdf+xml
    Content-ID: <12345@www.example.org>
    ...more fields...
    
    <?xml version='1.0'?>
    <rdf:RDF ...xmlns declarations...>
      <rdfs:Class rdf:about=''>
        <rdfs:label>Dog</rdfs:label>
        <rdfs:subClassOf rdf:resource='Pet'/>
      </rdfs:Class>
      
      <rdf:Description rdf:about='cid:12345@www.example.org'>
        <dc:creator>Example.org</dc:creator>
        <dc:date>2004-04-21T02:00:00Z</dc:date>
      </rdf:Description>
    </rdf:RDF>

This very clearly distinguishes the description of the resource
<http://www.example.org/term/Dog> from the description of its
representation <cid:12345@www.example.org>. Plus, if example.org changes
the descripton of </term/Dog>, they have to generate a new content ID.
-- 
David Menendez <zednenem@psualum.com> <http://www.eyrie.org/~zednenem/>
Received on Friday, 23 April 2004 02:05:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:38:52 GMT