Re: [keyassure] WebID at W3C and keyassure

[Phillip Hallam-Baker <[e-mail]>]

On Fri, Feb 11, 2011 at 10:06 AM, Henry Story <[e-mail]>wrote:
>
>
> Let's start from first principles. As far as internet users are concerned,
> an Internet user identifier is [e-mail]
>
>
> In WebID we consider essentially an http url such as
> http://bblfish.net/#me as it is immediately dereferenceable,
>
>

dereference, desmesherence.

What matters to the user is that they have a simple identifier that they can
give to other people, put on letterhead, business cards, read over the
telephone.

Tim didn't intended the URLs to even be visible to the end user. The address
bar was an ad-hoc invention that appeared in Mosaic. In the original
NeXTstep browser you had to dig into a menu to find the url.


If you are proposing infrastructure then make it work for the user first and
only then think about the hacks you might employ for backwards
compatibility.

Here we have the DNS, there is a discovery mechanism that was originally
designed to resolve [e-mail], use it the way it was designed.


If keys are going to be of the slightest use as end user keys they have to
bind to SMTP and Jabber addresses in any case.

What you have here is a URI scheme itself. You should think in terms of the
canonical form being:

webid:[e-mail]

The URL you gave might be something that ended up being a mapping returned
for retrieval/resolution purposes but that is all.


-- 
Website: http://hallambaker.com/