Microid mailing list

["Eran Sandler" <eran AT yedda.com>]

I think it's up to the site generating the microid.

For example, if at Yedda we want to use email instead of OpenID we will
genereate it according to the format Yaniv suggest:

<meta name="microid"
content="email+url:sha256:e5de55ef248b5f8b06d38253cac0ae725d6455fb">

After all, I'm generating the id so I know what do to.

When a verifier comes and see this microid content, it will know that it
needs to hash the email using SHA256, hash the URL using SHA256 and hash
both of them together using SHA256 to get the microid value.

The verifier will have to understand that the value "email" refers to email
and if it is replaced with openid it is openid.

I don't really see the problem you are talking about...

Eran

-----Original Message-----
From: Peter Saint-Andre [mailto:stpeter AT jabber.org] 
Sent: Wednesday, December 06, 2006 7:34 PM
To: Evan Prodromou
Cc: eran AT yedda.com; microid AT lists.ibiblio.org
Subject: Re: [Microid] MicroID hashing algorithm(s) and normalization

Evan Prodromou wrote:
> On Wed, 2006-06-12 at 09:13 -0700, Peter Saint-Andre wrote:
> 
>> That's fine by me. But we do need to think about the data definitions.
>> I'm thinking especially of OpenID. For example, how do we clearly
>> differentiate between a regular old HTTP URL and an OpenID URL (the
>> latter is simply an instance of the former, but how to we know that
>> programmatically)?
> 
> We know that programmatically because an OpenID identifies a person and
> thus goes in the first slot of the MicroID. Any other URL representing a
> resource like a Web page goes in the second slot.

But how do we know programmatically when we create the microid that a
given URL is an OpenID?

/psa