Re: Publishing updated spec documents.

Big milestone.  Congrats and good work...

Sent from my iPad

> On 7 Mar 2014, at 10:31 am, Andrei Sambra <andrei.sambra@gmail.com> wrote:
> 
> Hi everyone,
> 
> It is my pleasure to let you know that Stéphane has published the specs, which are now available at http://www.w3.org/2005/Incubator/webid/spec/. Please allow me to congratulate everyone one more time on the progress that has been made!
> 
> Best,
> Andrei
> 
> 
>> On Mon, Mar 3, 2014 at 1:42 PM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>>> On 3/3/14 12:16 PM, bergi wrote:
>>> Am 25.02.2014 17:17, schrieb Andrei Sambra:
>>>> > Hi all,
>>>> > 
>>>> > I would like to formally invite everyone to review the current version
>>>> > of the specs for WebID [1] and WebID-TLS [2] so that we can have a
>>>> > formal call this Friday (Feb 28th), at the usual time [3]. The purpose
>>>> > of this call will be to agree on the contents of the new documents so
>>>> > that the editors can finally publish them.
>>>> > 
>>>> > Best,
>>>> > Andrei
>>>> > 
>>>> > 
>>>> > [1] https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html
>>>> > [2] https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/tls-respec.html
>>>> > [3] http://www.w3.org/2005/Incubator/webid/wiki/Main_Page#Meetings
>>> Can we remove the HTTP protocol restriction from the Identity spec? I
>>> think the idea for the separation was to have an abstract/generic
>>> definition of WebID, and a separate spec for initial implementation
>>> (i.e., WebID+TLS). This abstract definition should just reference IRIs
>>> (without scheme), so in the future other specs could be based on our
>>> work. At the same time, people who implement WebID+TLS today with RDF
>>> (and thus HTTP) can be sure they support the whole spec.
>>> 
>>> bergi
>>> 
>>> 
>>> 
>> 
>> I am sure you know this was the subject of a protracted debate. The issue was concluded when TimBL explained (in a manner I accepted) the reasoning behind HTTP specificity in regards to WebIDs. It simply boils down to "Web" meaning "World Wide Web" and the "World     Wide Web" being an HTTP based linked document network . 
>> 
>> The net effect of this approach is that we can look at the role of identifiers re., networks as follows:
>> 
>> 1. URLs -- HTTP URIs that denote documents and by their very nature enable the creation of linked document networks (aspect of the Web the world knows and uses)
>> 2. WebIDs -- HTTP URIs that denote agents and by their very nature enable the creation of linked data networks (aspect of the Web the world is beginning to understand via the Linked Open Data cloud) . 
>> 
>> In the future, in the absolute worst case, we have NetIDs which are basically resovable IRIs that by their very nature enable the creation of linked data networks be it at the Web or Internet level (e.g., an Internet of Things where denotation is based on this kind of IRI). 
>> 
>> I hope this clears up matters. We really need to get the basic WebID spec out, as soon as possible. 
>> -- 
>> 
>> Regards,
>> 
>> Kingsley Idehen       
>> Founder & CEO 
>> OpenLink Software     
>> Company Web: http://www.openlinksw.com
>> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
>> Twitter Profile: https://twitter.com/kidehen
>> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
>> LinkedIn Profile: http://www.linkedin.com/in/kidehen
>> 
>> 
>> 
>> 
>