Thanks, Allen. I hadn't thought of that. But it seems to have the drawback that I have to use <a href="http://myopenid.com">myopenid.com</a> not only as my provider, but as my claimed identifier. I prefer to use my own ClaimedId and delegate to <a href="http://myopenid.com">myopenid.com</a>, but that means an automated RP cannot extract the hCard unless I host it myself on my server, I believe.<br>
I mean, I guess I could program the RP to follow the ClaimedId to the delegate Id and look for an hCard there, but that feels wrong somehow.<br><br><div class="gmail_quote">On Sat, May 31, 2008 at 10:46 AM, Allen Tom <<a href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Hi Andrew,<br>
<br>
If you just want to read public information that's available for an
OpenID, then have you considered embedding microformatted data (like an
hCard) onto the page referenced by the OpenID? For instance, if the
OpenID was someone's Profile Page, the RP could just read the hCard on
the page to extract the public information for that OpenID.<br>
<br>
You could do this today with OpenIDs from MyOpenID and Flickr.<br>
<br>
Allen<br>
<br>
<br>
<br>
<br>
<br>
Andrew Arnott wrote:
<blockquote type="cite"><div><div></div><div class="Wj3C7c">Attribute Exchange seems to rely on being part of an
authentication message as opposed to being able to work when in
OpenID's no-authentication extension mode. I get this from section <a href="http://openid.net/specs/openid-attribute-exchange-1_0.html#identifier-definition" target="_blank">3.1</a>
of the AX spec getting the subject identifier from the authentication
part of the message.<br>
<br>
My suggestion would be that if we can, in a subsequent version of AX,
allow AX to stand alone without OpenID having to send an authentication
request at the same time, then given an OpenID URL by itself, people
can query against it. Now, most information would probably need to be
kept private, but perhaps some information, like contact information,
can be made available provided the requestor respond to a CAPTCHA or
something like that. That would be up to the individual OPs and their
users of course as to which information to be willing to disseminate,
but the power of the feature is there.<br>
<br>
What do you think?<br clear="all">
<br>
-- <br>
Andrew Arnott
</div></div><pre><hr size="4" width="90%"><div class="Ih2E3d">
_______________________________________________
general mailing list
<a href="mailto:general@openid.net" target="_blank">general@openid.net</a>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a>
</div></pre>
</blockquote>
<br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Andrew Arnott