We wonder about the same questions.<div><br></div><div>For URL validation use cases (which frequently are different then single-signon), we think it makes sense to provide an OpenID endpoint that returns those URLs as claimed URLs (whether they are Blogger URLs, Google Profile URLs, Youtube URLs, etc.<br>
<div><br></div><div>However most of the demand we are seeing for returning Profile URLs is when they are combined with single-signon, and in those cases the relying parties do want a way to get them as an AX attribute. In Google's case it gets further complicated by the fact that user's have different "profiles" at Google that they might want returned, and forcing users to pick one for each RP hurts usability. And then further complicated by the fact that some RPs only want to accept profile URLs of a certain type. And more complicated still by the fact that most Google users don't have a profile of any type, so being asked to create one during a sign-on process is extremely confusing.</div>
<div><br></div><div><br></div><div><div class="gmail_quote">On Fri, Jul 10, 2009 at 1:39 PM, Allen Tom <span dir="ltr"><<a href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Would it make sense for Profile URLs to be OpenIDs, or should the Profile URL be an attribute that is shared via AX?<br>
<br>
What about users who already have both a Profile and an OpenID (with different urls) from their OP? Should the Profile URL be delegated to the OpenID, or should they be kept separate?<br>
<br>
In the interest of interop, it would be great if the community could come up with best practices for combining Profiles and OpenIDs.<br><font color="#888888">
<br>
Allen</font><div><div></div><div class="h5"><br>
<br>
Eric Sachs wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Only a subset of GoogleProfile users register a username, but yes, for those users that is the common request we get.<br>
<br>
</blockquote>
</div></div></blockquote></div><br></div></div>