[wbs] response to 'WebID definition hash '

The following answers have been successfully submitted to 'WebID definition
hash ' (WebID Community Group) for The Apache Software Foundation by Henry
Story.


---------------------------------
What is a WebID?
----
Given that WebID's must refer to Agents, and that the WebID must be
associated with a profile document, (that returns a default representation)
the question here is which of the following restrictions one should have
for WebIDs. 


Note that a URI is defined by RFC3986 and is constructed as follows:


         foo://example.com:8042/over/there?name=ferret#nose
         \_/   \______________/\_________/ \_________/ \__/
          |           |            |            |        |
       scheme     authority       path        query   fragment

Please look at the detailed arguments for each position on the wiki before
selecting your preferences.


 For each of the three options please follow the select one of the options
as described below:

Please select the rank-order (1 to 3) for the options
you think are acceptable (i.e.  you can 
live with it), where 1  is the most preferred, 2 the next best and so on...
You also have a don’t mind and a don’t want option.
* [ 1 ] 
   Choice: 1. MUST be an HTTP(S) hash (#) URI: 
The precise definition is:
A WebID is a URI with an `http` or `https` scheme, which MUST contain a URI
fragment identifier and which uniquely denotes an Agent (Person,
Organization, Group, Device, etc.). The URI without the fragment identifier
denotes the WebID Profile page.

Please consider carefully the arguments for this position
 | 
* [ 2 ] 
   Choice: 2. MUST be an HTTP(S) URI and SHOULD be an HTTP(s) hash (#)
URI:
The precise definition is:

A WebID is a URI with an `http` or `https` scheme which uniquely denotes an
Agent (Person, Organization, Group, Device, etc.). This URI SHOULD include
a fragment identifier. For WebIDs with fragment identifiers the URI without
the fragment denotes the Profile Document. For WebIDs without fragment
identifiers an HTTP request on the WebID MUST return a 303 with a Location
header URI denoting the Profile Document.



Please consider carefully the arguments for this position
 | 
* [ Don’t want ] 
   Choice: 3. MUST be an HTTP(S) URI
The precise definition is:

A WebID is a URI with an `http` or `https` scheme which uniquely denotes an
Agent (Person, Organization, Group, Device, etc.). For WebIDs with fragment
identifiers the URI without the fragment denotes the Profile Document. For
WebIDs without fragment identifiers an HTTP request on the WebID MUST
return a 303 with a Location header URI denoting the Profile Document.



Please consider carefully the arguments for this position
 | 
Rationale: In order to get into the W3C  so that it can be made a standard
for a WG it will be important that we be able to distinguish WebID from
OpenId. Making a WebID just be an http URI will create issues in the
standard of how we differentiate ourselves from them. These and other
issues require maximum clarity and simplicity in the original formulation
of what a WebID is. Solution 3 inevitably opens up the whole redirect
debate and will very likely require the basic spec to explain it.


These answers were last modified on 26 January 2013 at 09:02:59 U.T.C.
by Henry Story

Answers to this questionnaire can be set and changed at
https://www.w3.org/2002/09/wbs/51933/webid-hash/ until 2013-02-01.

 Regards,

 The Automatic WBS Mailer

Received on Saturday, 26 January 2013 09:03:02 UTC