WebID-ISSUE-74 (flow new def through spec): revised WebID definition must be flowed through conceptual spec, removing hashURI specificity [WebID definition]

WebID-ISSUE-74 (flow new def through spec): revised WebID definition must be flowed through conceptual spec, removing hashURI specificity [WebID definition]

http://www.w3.org/2005/Incubator/webid/track/issues/74

Raised by: Ted Thibodeau
On product: WebID definition

This is a larger task than the definition revision (ACTION-59), and is closely tied to the split of "Conceptual" and "WebID-over-TLS Protocol" specs (ACTION-57), but may require several specific decisions along the way, and several related actions.

for example...

=== quote begins ===
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.
=== quote ends ===

As Kingsley says, "This note is simply unnecessary. All the examples are based on hash URIs (as decided by the WG) which has the desired effect of encouraging the use of hash-based HTTP URIs."

Received on Friday, 8 February 2013 17:05:26 UTC