W3C home > Mailing lists > Public > public-webid@w3.org > February 2013

Re: WebID 1.0 -- Section 3 -- Removal of Note

From: Henry Story <henry.story@bblfish.net>
Date: Sun, 17 Feb 2013 14:23:33 +0100
Cc: public-webid <public-webid@w3.org>
Message-Id: <F6E9F9E5-20AD-411E-AA91-0E5F8C351F08@bblfish.net>
To: Melvin Carvalho <melvincarvalho@gmail.com>

On 17 Feb 2013, at 13:59, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

> "Note
> Hash URIs are encouraged when choosing a WebID since 303 redirects require an extra HTTP request for an Agent to get from the WebID to the WebID Profile. All examples in the spec will use such hash URIs."
> https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html#the-webid-http-uri
> This has come up in some other threads.  
> Leaving the # vs slash "perma debate" aside may I propose that this part is removed.  
This is issue-74
> While, I am in favour of the sentiment of using # URIs but I dont see any evidence that this note will have the desired effect.  Why even mention 303s at all?  All the examples use # URIs so, imho, this point is not really needed, and may add confusion to implementers.  

We are mentioning 303s because we need to mention the relation between the WebID and the Profile document. We need to tie these together, since otherwise there is nothing to say about WebIDs. 

There are two ways WebIDs get related to the profile document: either the hash to non hash relation, or the 303s link. Speaking of 303s is just a consequence of allowing them  into our scope per definition.  


Social Web Architect

Received on Sunday, 17 February 2013 13:24:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:05:49 UTC