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

WebID definition proposal with hash urls

From: Henry Story <henry.story@bblfish.net>
Date: Fri, 16 Nov 2012 00:27:28 +0100
Message-Id: <9D9713D2-7AEA-4D06-A35D-B1F5FB7D848D@bblfish.net>
To: "public-webid@w3.org" <public-webid@w3.org>
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>


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. 

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.

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/



Received on Thursday, 15 November 2012 23:27:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:54:39 UTC