+1 to public per se public.
If embedding microformats (or rdf) into public URIs is the solution to
pulling public data, what's the right way to push it. Most of that
tech seems pretty focused on feeds, but it's a bit silly to imagine an
avatar feed.
--
j
On Dec 9, 2009, at 9:49 PM, Allen Tom wrote:
If Avatar/Profile photo and display name are considered “public”
data, then perhaps we could short-circuit this AX stuff by returning
the URL to the user’s public profile, and the RP can just use
microformats to extract the name/photo via hCard.
Allen
On 12/8/09 10:06 PM, "John Panzer" <[email protected]> wrote:
For my use cases, the important things are, unscientifically,
1. Display name
2. Avatar / photo
3. Preferred link to human-readable online presence -- profile,
blog, whatever strikes their fancy.
_______________________________________________
specs mailing list
[email protected]
http://lists.openid.net/mailman/listinfo/openid-specs
_______________________________________________
specs mailing list
[email protected]
http://lists.openid.net/mailman/listinfo/openid-specs
