Re: Web Identity and Discovery - WebID 1.0

On 2/8/13 3:34 AM, Henry Story wrote:
>> >Here's another suggestion. Rather than conclude that the WebID spec is simpler with your controversial notice, why not wait for actual feedback from others about the need for such clarification?
> We are waiting for you to open an issue and propose some text for the section "The WEbID HTTP URI"
>
> https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html#the-webid-http-uri
>
> But this is as I said another issue.
>
> Henry
>
>

Ted,

As already requested, please open a issue with regards to the following 
snippet:

3. The WebID HTTP URI

The WebID HTTP URI must be one that dereferences to a document the user 
controls.

For example, if a user Bob controls https://bob.example/profile, then 
his WebID can be https://bob.example/profile#me.

NOTE
Hash URIs are encouraged when choosing a WebID since 303 redirects 
impact performance for clients. All examples in the spec will use such 
hash URIs.

Problem:

The note is simply unnecessary. All the examples are based on hash URIs 
which has the desired effect of encouraging the use of hash based HTTP 
URIs.

Henry:

As I've told you repeatedly, I understand the goal, but I differ 
(profoundly) with your approach here.

-- 

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