Re: Option 1 - HTTP 303 Re: Towards a TAG consideration of CURIEs

On Apr 10, 2007, at 6:38 AM, Richard Cyganiak wrote:
> On 10 Apr 2007, at 03:50, Alan Ruttenberg wrote:
>> On Apr 9, 2007, at 1:58 PM, Tim Berners-Lee wrote:
>>> I would recommend that each document be available in both HTML  
>>> and RDF using content negotiation or just RDF with a style sheet  
>>> that makes it legible, or just HTML with GRDDL.
>> -1 for content negotiation. (very un-semantic web like to have non- 
>> inspectable communications, and confusion about what a name=URI  
>> means)
>
> Not a fair characterization of conneg. It would be implemented by  
> having the (required!) 303 redirect point to either an HTML or RDF  
> document based on client preferences. As Chimezie says, the HTML  
> and RDF documents should point to each other.

"should" and "do" are not coincident. It would be desirable if the  
architecture made it easier to do what is correct, and harder to do  
what is not.

> Thus all communications are inspectable, and it's clear what the  
> names mean -- there's one for the domain object, one for the HTML  
> document, one for the RDF document.

They are not inspectable as RDF, or to a SPARQL endpoint. I don't  
count running parsing html headers as "inspectable" from a SW point  
of view.

Can you send me a pointer to a deployed example of this? For example  
I am terminally confused by FOAF. What does the name  "http:// 
xmlns.com/foaf/0.1/" refer to?

What does this mean (from foaf rdf)?   <rdfs:isDefinedBy  
rdf:resource="http://xmlns.com/foaf/0.1/"/>

How does a SW agent get the rdf for http://xmlns.com/foaf/0.1/ 
Organization ?

wget http://xmlns.com/foaf/0.1/Organization --header='Accept:  
application/rdf+xml'
--08:41:03--  http://xmlns.com/foaf/0.1/Organization
            => `Organization'
Resolving xmlns.com... 208.113.134.174
Connecting to xmlns.com|208.113.134.174|:80... connected.
HTTP request sent, awaiting response... 303 See Other
Location: http://xmlns.com/foaf/0.1/ [following]
--08:41:04--  http://xmlns.com/foaf/0.1/
            => `index.html'

wget http://xmlns.com/foaf/0.1/ --header='Accept: application/rdf+xml'

GET /foaf/0.1/ HTTP/1.0
User-Agent: Wget/1.10.2
Accept: application/rdf+xml
Host: xmlns.com
Connection: Keep-Alive

HTTP/1.1 200 OK
Date: Tue, 10 Apr 2007 12:52:44 GMT
Server: Apache/1.3.37 (Unix) mod_throttle/3.1.2 DAV/1.0.3 mod_fastcgi/ 
2.4.2 mod_gzip/1.3.26.1a PHP/4.4.4 mod_ssl/2.8.22 OpenSSL/0.9.7e
Last-Modified: Sun, 29 Jan 2006 22:38:45 GMT
ETag: "338923b-2d925-43dd43f5"
Accept-Ranges: bytes
Content-Length: 186661
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html


----

Here's a random example of rdf content negotiation that I googled for  
- typical confusion over names.

http://simile.mit.edu/issues/browse/PIGGYBANK-9

wget http://crschmidt.net/julie/doap --header='Accept: text/html'
--08:57:35--  http://crschmidt.net/julie/doap
            => `doap.2'
Resolving crschmidt.net... 64.92.170.181
Connecting to crschmidt.net|64.92.170.181|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3,160 (3.1K) [text/html]

wget http://crschmidt.net/julie/doap --header='Accept: application/rdf 
+xml'
--08:56:21--  http://crschmidt.net/julie/doap
            => `doap'
Resolving crschmidt.net... 64.92.170.181
Connecting to crschmidt.net|64.92.170.181|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,540 (1.5K) [application/rdf+xml]

-Alan

Received on Tuesday, 10 April 2007 13:11:45 UTC