W3C home > Mailing lists > Public > public-webid@w3.org > November 2012

Re: hash/303, all use cases, requirements, thoughts, notes, approaches, use cases, user stories..

From: Henry Story <henry.story@bblfish.net>
Date: Thu, 22 Nov 2012 14:14:06 +0100
Cc: Stéphane Corlosquet <scorlosquet@gmail.com>, Alexandre Bertails <bertails@w3.org>, Kingsley Idehen <kidehen@openlinksw.com>, public-webid <public-webid@w3.org>, "public-rww@w3.org" <public-rww@w3.org>
Message-Id: <2AD3C01A-CD22-461B-8396-93CDAD29A455@bblfish.net>
To: nathan@webr3.org

On 21 Nov 2012, at 19:54, Nathan <nathan@webr3.org> wrote:

> Stéphane Corlosquet wrote:
>> On Wed, Nov 21, 2012 at 12:29 PM, Henry Story <henry.story@bblfish.net>wrote:
>>> On 21 Nov 2012, at 18:25, Nathan <nathan@webr3.org> wrote:
>>>> Henry Story wrote:
>>>>> http://www.w3.org/2005/Incubator/webid/wiki/WebID_Definition/hash
>>>> I'm unsure that anything could be captured here which hasn't already
>>> been captured by the exhaustive work of Jonathan Rees and others via
>>> www-tag and the awwsw tf, see:
>>>> http://www.w3.org/2001/tag/products/defininguris.html
>>> We can define WebIDs to be whatever we want I think.
>> We can. The question is whether we should!
>> option 1: define it the way we want (e.g. hash URIs only), and disregard
>> any on-going work by the TAG, which might resolve the issue with a solution
>> incompatible with the one we define today.
>> option 2: leave it open and generic in our definition of WebID, but
>> strongly encourage the use of hash URI via examples.
> Hi Steph,
> Wise words, I think the TAG have committed to not falling on either side of the debate, but rather fostering interop, so I doubt option 1 would be ever happen.

I hope they do a better job than the "Dereferencing HTTP URIs" document 
which leaves the simplest solution to the end with very little in form of explanation, 
whereas all the other solutions are given detailed explanation.

I am interested in the new finding, but I don't think we can wait around for them to be finished.
We can have a provisional solution in the meantime.

> That said, option 2 seems to be the only viable, non exclusive, way forward here - and it's been the approach many of us have adopted in communications and tooling for years.

This does leave "MUST be HTTP uri and SHOULD be an HTTP(s) hash (#) URI" 


which I am starting to like quite a bit myself, for reasons explained on the wiki.

Concerning the wiki

I have commented on different points people made, btw [bblfish: ...].

I don't think we have all the answers in - I am still waiting for Alexandre Bertails -
who was very vocal at both TPAC and last meeting in favour of the stronger answer 1.
Anyway, the picture is starting to clear.

Could people please consider each point they put down, and see if it really is a point in favor of a position  And also please make the points short and concise with pointers to extra material. (I'd like to remove rambling).


> ps: thanks for taking this to the TAG, I was glad to see it being raised their.
> Best,
> Nathan

Social Web Architect

Received on Thursday, 22 November 2012 13:14:41 UTC

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