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

Re: WebID definition proposal with hash urls

From: Henry Story <henry.story@bblfish.net>
Date: Fri, 16 Nov 2012 10:23:58 +0100
Cc: public-xg-webid@w3.org
Message-Id: <4F3E6E22-DE81-4850-84C7-A38CF347BE4B@bblfish.net>
To: Kingsley Idehen <kidehen@openlinksw.com>

On 16 Nov 2012, at 01:24, Kingsley Idehen <kidehen@openlinksw.com> wrote:

> On 11/15/12 6:27 PM, Henry Story wrote:
>> The way to change the spec is to propose textual spec changes. Could those who wish
>> to support the #url simpliciations please put forward some clear text that the editors
>> can add to the spec, so that people can then vote on it.
>> 
>> I think this does simplify the spec, and it does not break anything, since we had already
>> agreed to Turtle and RDFa being a MUST.
>> 
>> Currently we have is:
>> 
>> WebID:
>> 
>> <blockquote src=" https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/index-respec.html " >
>> A URI that refers to an Agent - Person, Robot, Group or other thing that can have Intentions. The WebID should be a URI which when dereferenced returns a representation whose description uniquely identifies the Agent who is the controller of a public key. In our example the WebID refers to Bob. A WebID is usually a URL with a #tag, as the meaning of such a URL is defined in the document refered to by the WebID URL without the #tag .
>> </blockquote>
>> 
>> WebID Profile
>> 
>> <blockquote src=" https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/index-respec.html" >
>> A structured document asserting the relationship between the Subject (identified by his WebID) and his Public Keys using relationships as defined by the Resource Description Framework [RDF-CONCEPTS] and published at the URL location of the Subject's WebID. Dereferencing the WebID should return the Profile Page in one of a number of formats. The Server must publish the document in at least the RDFa [RDFA-CORE] serialization format or in Turtle [TURTLE-TR]. The document may be published in a number of other RDF serialization formats, such as RDF/XML [RDF-PRIMER], or N3 [N3]. Any other serializations that intend to be used by the WebID Protocol must be transformable automatically and in a standard manner to an RDF Graph, using technologies such as GRDDL [GRDDL-PRIMER].
>> </blockquote>
> 
> +1

> 
>> 
>> 
>> Proposal 1: with hash urls
>> ===========================
>> 
>> 
>> a) A WebID is a URI [1] whose scheme is either "http" or "https" and that contains a fragment identifier.
>> The WebID denotes an Agent ( Person, Organisation, Group, Software, ...). The URI without the hash denotes the WebID Profile.
> 
> -1
> 
> 
>> 
>> b) A WebID Profile is a web resource that MUST by default return a TURTLE document, but that
>> can return other RDF serialisation formats if requested through content negotiation. The RDF
>> graph expressed by this turtle document MUST contain a number of relations containing the WebID
>> that uniquely identify the referent of the WebID.
> 
> -1
> 
> 
>> 
>> Proposal 2:
>> ==========
>> 
>> like proposal 1 but
>> 
>> b) the WebID Profile MUST either return RDFa or Turtle
>> 
>> 
>> 
>> 
>> [1] http://tools.ietf.org/html/rfc3986
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Social Web Architect
>> http://bblfish.net/
>> 
> The current definition for which I gave a +1 is superior to the alternatives proposed.
> 
> If I was to reword the current definition (for which I voted +1) I would say something along the lines of:
> 
> A WebID is a URI that *denotes* an Agent - Person, Robot, Group or other thing that can have Intentions. When de-referenced (or looked up) this kind of URI returns a document that uniquely describes its referent -- the denoted Agent. In our example, a WebID *denotes* Bob, it takes the form of an HTTP URL with a #tag or fragment identifier, and returns an RDF document that describes Bob.

ok, so what you are suggesting is to remove the public key as the only identifying 
description from a WebID Profile Document.

I think there seems to be consensus on that from everyone.

It does mean the WebID Authentication over TLS spec needs to be altered so that it describes
the WebID Profile document as requiring a public key.

> 
> 
> 
> 
> -- 
> 
> Regards,
> 
> Kingsley Idehen	
> Founder & CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
> Twitter/Identi.ca handle: @kidehen
> Google+ Profile: https://plus.google.com/112399767740508618350/about
> LinkedIn Profile: http://www.linkedin.com/in/kidehen
> 
> 
> 
> 
> 

Social Web Architect
http://bblfish.net/



Received on Friday, 16 November 2012 09:24:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 16 November 2012 09:24:34 GMT