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

Re: Simple Straw Poll re. Hash URI Specificity and WebID Definition

From: Stéphane Corlosquet <scorlosquet@gmail.com>
Date: Wed, 21 Nov 2012 11:35:27 -0500
Message-ID: <CAGR+nnHrTpAYkYpLyM++UcmSnHiBbgJfNq=yf=L+Rq3ZFa3hAg@mail.gmail.com>
To: Alexandre Bertails <bertails@w3.org>
Cc: public-webid <public-webid@w3.org>, Henry Story <henry.story@bblfish.net>, Kingsley Idehen <kidehen@openlinksw.com>, "public-rww@w3.org" <public-rww@w3.org>
On Wed, Nov 21, 2012 at 11:27 AM, Alexandre Bertails <bertails@w3.org>wrote:

> On 11/21/2012 11:04 AM, Henry Story wrote:
>
>> I am not sure the RWW mailing list is the right place to send this
>> message,
>> as they have not followed the debate. I think we need a wiki page that
>> lists
>> the pros and cons of each of the issues below, if you are going to bring
>> new
>> people to the conversation.
>>
>> On 21 Nov 2012, at 16:49, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>>
>>  All,
>>>
>>> As per a variety of threads re. the matter of the definition of a WebID,
>>> I kindly request a simple +1, -1, or 0 vote on the following issue of
>>> concern:
>>>
>>> Should a WebID be defined specifically as a hash based HTTP URI?
>>>
>>
>> "Specifically" is not clear.
>>
>
> It's not clear because the definition is not complete. I mean, it's
> missing the goal (identity) and some other "constraints" (like the
> default serialization format).
>

These should be discussed and voted on separately. The type of URI and the
serialization formats are orthogonal issues. Let's hammer the hash vs.
hashless URI here, and discuss Turtle later on in a separate poll.

Steph.


>
> Voting without those will not solve anything. I would vote "again" for
> the definition we had agreed upon at TPAC [1].
>
> [[
> RESOLUTION: "A WebID is a hash HTTP URI which denotes an Agent. You
> can GET an RDF model as TURTLE.
> ]]
>
> Alexandre.
>
> [1] http://www.w3.org/2012/10/30-**webid-minutes.html#webid-**definition<http://www.w3.org/2012/10/30-webid-minutes.html#webid-definition>
>
>
>
>> In terms of language we can use MUST, SHOULD etc.
>>
>> So perhaps you can rephrase it in those terms.
>>
>> [1] a WebID MUST be a an HTTP hash uri
>> [2] a WebID SHOULD be an HTTP hash uri
>> [3] a WebID SHOULD be any HTTP hash uri
>>
>> in all cases of course we agree that the URI MUST refer to an agent as
>> described in the current spec.
>>
>> Is this better?
>>
>>
>>
>>> Note:
>>> Most of use are extremely time challenged, and really need to make
>>> decisions and set priorities re. this matter. Thus, I would like those with
>>> a vested interest in this matter to vote.
>>>
>>> This is an informative endeavor.
>>>
>>> Poll Question:
>>> Do you support defining a WebID *specifically* as a hash based HTTP URI?
>>>
>>> --
>>>
>>> Regards,
>>>
>>> Kingsley Idehen
>>> Founder & CEO
>>> OpenLink Software
>>> Company Web: http://www.openlinksw.com
>>> Personal Weblog: http://www.openlinksw.com/**blog/~kidehen<http://www.openlinksw.com/blog/~kidehen>
>>> Twitter/Identi.ca handle: @kidehen
>>> Google+ Profile: https://plus.google.com/**112399767740508618350/about<https://plus.google.com/112399767740508618350/about>
>>> LinkedIn Profile: http://www.linkedin.com/in/**kidehen<http://www.linkedin.com/in/kidehen>
>>>
>>>
>>>
>>>
>>>
>>>
>> Social Web Architect
>> http://bblfish.net/
>>
>>
>
>


-- 
Steph.
Received on Wednesday, 21 November 2012 16:35:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 November 2012 16:35:56 GMT