At some point, the weak link will be humans trying to disambiguate http://joe.example.org/ from http://joe.example.org/2 (or http://joe.example.org/#2). I don't think there's a big difference between the two in that context, and I don't think that OID2 needs to solve this more deeply than allowing unique-URL. But would this be an additional requirement placed on OPs?
(Query: I assume a 302 redirect from http://joe.example.org to http://joe.example.org/2 will work?) Has there been a discussion about an extension to map to/from i-numbers via AX? If there were a generic attribute you could stuff an i-number or a hash of an internal ID in there to help solve the disambiguation problem. Alternatively it'd be nice to have a way to ask when the account was created, if the OP is amenable. -John > _______________________________________________ specs mailing list specs@openid.net http://openid.net/mailman/listinfo/specs
