Despite it being a best practice, currently only a handful of OpenID Consumer sites support the association of multiple OpenID identifiers to a single “account”. This is important to create redundancy to make the loss of an identifier less catastrophic.
Sign in with 
OpenID
It's true that this is important.
However, most implementations currently only associate the OpenID during the registration process to the user's account and do not allow editing of it at all - from my experience.
I think that this will get done later - in the sense of "nice-to-have". At least there should be relational tables for user_ID <=> OpenID in most applications already.
I think this muddies the water a bit, since a large part of the OpenID pitch is single sign-on. "Why would you want multiple OpenID's?" people likely think.
I suppose it's true that most people won't use delegation and therefore should treat OpenIDs as keys.
Jeremy Dunck - 1st March 2007 15:15 - #