Presumably the RP has downloaded the OP's entire XRDS document. In that case, the RP just looks through the type URIs advertised until it finds a single AX attribute Type URI that matches any of the known three patterns, then it chooses that pattern to use. I don't think that's ugly, personally, even if there were 100 type URIs to sift through. But I've never seen an OP advertise that many type URIs, so it doesn't seem to be too much of a problem.<div>
<br></div><div>Rather than standardizing on a new type URI to indicate which pattern to use, which would require some work and agreement, we could expend that same effort just standardizing on a single pattern that everyone should use. <br clear="all">
--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre<br>
<br><br><div class="gmail_quote">On Fri, Jul 10, 2009 at 9:29 AM, George Fletcher <span dir="ltr"><<a href="mailto:gffletch@aol.com">gffletch@aol.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
That will work (though I don't remember seeing any at the time we were implementing OpenID 2.0 RP support). If I understand correctly, you are doing some pattern matching against the Type URIs to determine which schema is being used. Also, if the OP supports 10s or 100s of attributes then this gets pretty ugly. I'd prefer a single URI the represents the schema being used. The rest is pretty simple from there.<br>
<br>
Of course it's possible I misunderstood.<div class="im"><br>
<br>
Thanks,<br>
George<br>
<br>
Andrew Arnott wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
George,<br>
<br>
Are you sure they're not defined? AX has attribute Type URIs. I've been an advocate that OPs publish all their supported AX attribute Type URIs in their XRDS document so that RPs know what they might expect from the OP, as well as discern which format of type URI that OP supports. Some OPs do just this, and DotNetOpenAuth (the RP part) automatically detects this from the OP's XRDS and sends either sreg or one of the three known AX type URI formats out there based on what it sees in the XRDS.<br>
<br>
--<br>
Andrew Arnott<br>
"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre<br>
<br>
<br></div><div class="im">
On Fri, Jul 10, 2009 at 8:48 AM, George Fletcher <<a href="mailto:gffletch@aol.com" target="_blank">gffletch@aol.com</a> <mailto:<a href="mailto:gffletch@aol.com" target="_blank">gffletch@aol.com</a>>> wrote:<br>
<br>
Sure, or just define it in the XRDS for the OP. But those aren't<br>
currently defined.<br>
<br>
Thanks,<br>
George<br>
<br>
<br>
SitG Admin wrote:<br>
<br>
One other issue is that AX supports multiple schema and<br>
there is currently no way for the OP to advertise which<br>
schema it's using. So an RP has to build it's own mapping<br>
table to know what to send to the OP when using AX.<br>
<br>
<br>
Common key/API with "schema translation table" AX link?<br>
<br>
-Shade<br>
<br>
_______________________________________________<br>
general mailing list<br></div>
<a href="mailto:general@openid.net" target="_blank">general@openid.net</a> <mailto:<a href="mailto:general@openid.net" target="_blank">general@openid.net</a>><div class="im"><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
<br>
<br>
</div></blockquote>
<br>
</blockquote></div><br></div>