W3C home > Mailing lists > Public > public-sweo-ig@w3.org > June 2007

Re: [Fwd: Re: What if an URI also is a URL]

From: Ivan Herman <ivan@w3.org>
Date: Thu, 07 Jun 2007 10:09:48 +0200
Message-ID: <4667BD4C.2080006@w3.org>
To: Dan Brickley <danbri@danbri.org>
CC: SWD Working Group <public-swd-wg@w3.org>, 'W3C SWEO IG' <public-sweo-ig@w3.org>, Tim Berners-Lee <timbl@w3.org>, Leo Sauermann <leo.sauermann@dfki.de>
Dan,

on the SWEO side Leo Sauermann & co have taken the initiative to write
up something, and they are in discussion on the TAG

http://www.w3.org/mid/465DA1A6.6030506@dfki.de

although the impression I have is that the discussion on the thread has
a bit bifurcated from Leo's original request for help. If you could
help/participate with Leo on that, this may end up as a SWEO 'note'.

I am not sure the SWD has the manpower to do something there.

Yes, an FAQ would definitely be good for this, but I think the note of
Leo should be finalized first...

Ivan

Dan Brickley wrote:
> SWD, SWEO,
> 
> With a SW Interest Group chair's hat on .... "help!"
> 
> This perma-thread (the question of URIs for people, HTTP content
> negotiation, meaning of #blah IDs etc) has been rumbling along for
> years. It is getting really embarrassing that this stuff keeps coming
> up. Can we do something here? A Faq or TAG finding or wiki page or ...
> ... something, anything, to help the mailing lists move along to more
> fruitful topics of discussion?
> 
> Apologies for the x-post, this problem is split a little across groups.
> 
> cheers,
> 
> Dan
> 
> ------------------------------------------------------------------------
> 
> Subject:
> Re: What if an URI also is a URL
> From:
> Jon Hanna <jon@hackcraft.net>
> Date:
> Wed, 06 Jun 2007 16:20:49 +0100
> To:
> Tim Berners-Lee <timbl@w3.org>
> 
> To:
> Tim Berners-Lee <timbl@w3.org>
> CC:
> "Lynn, James (Software Escalations)" <james.lynn@hp.com>, "r.j.koppes"
> <rikkert@rikkertkoppes.com>, www-rdf-interest@w3.org
> 
> 
> 
> Tim Berners-Lee wrote:
>> This is the web architecture.   The client strips off the '#me'  and
>> acceses the dcoument
>> <http://www.example.com/mophor> (if it hasn't already for some other
>> id in the same document).
>> The server sends back a document telling it about
>> <http://www.example.com/mophor#me> and maybe other things.
> 
> When a client is looking at what it received from
> http://www.example.com/mophor it doesn't know that's the only possible
> view upon http://www.example.com/mophor (indeed it might know the
> opposite if there is a Vary header)
> 
> When the client is interpretting #me in a way that is based on the
> content-type of what it received from http://www.example.com/mophor it
> is more tightly concerned with a particular document.
> 
> Since the mechanism for a fragment identifier is based on the document
> type, which seems if anything even more tied to documents than
> http://www.example.com/mophor
> 
> 

-- 

Ivan Herman, W3C Semantic Web Activity Lead
URL: http://www.w3.org/People/Ivan/
PGP Key: http://www.cwi.nl/%7Eivan/AboutMe/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf


Received on Thursday, 7 June 2007 08:09:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:17:38 GMT