At the very least, the 2.x series of changes should investigate the net-net adoption of all of the features of OpenID and prioritize and de-prioritize accordingly.<div><br></div><div>Supporting XRIs have been reported to add complexity to the discovery code, and further, seem to have little adoption in the mainstream and few implementations in the wild. I'd be eager to hear specific stats that contradict that sentiment, but I don't want to hold on to features purely out of nostalgia.</div>
<div><br></div><div>This points to yet another reason why I worry about the v.Next naming: if we can't even cut, cut, cut from the 2.0 spec to create a leaner, simpler protocol that's easier to implement and support, I have a hard time imagining how we're going to arrive at a simpler, stream-lined technology when v.Next sounds like it's chartered to include everything and the kitchen sink. </div>
<div><br></div><div>Perhaps along with the MRD/PRD that Brian Kissel wants, we should also produce a DRD — a developer requirements document — that provides insight into which features of OpenID have actually been implemented by the most successful OPs (based on market adoption and usage). That is, in order to be taken into consideration for this requirements document, you have to have already deployed a public OpenID Provider and have people using it.</div>
<div><br></div><div>It seems that that would be a useful filter to gather real-world feedback that can lead us forward for 2.x.</div><div><br></div><div>Chris</div><div><br><br><div class="gmail_quote">On Mon, May 31, 2010 at 7:05 PM, John Bradley <span dir="ltr"><<a href="mailto:jbradley@mac.com">jbradley@mac.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Dick,<br>
<br>
You know that XRI is used by multiple OP. It is not something a RP site demands.<br>
<br>
In discovery going forward we need to look at how and if XRI identifiers are supported.<br>
<br>
Because LRDD and XRI are so close you can normalize a XRI by adding @<a href="http://xri.net" target="_blank">xri.net</a> to the end and doing webfinger/LRDD resolution to get a XRD.<br>
<br>
People may be opposed to XRI on philosophical grounds, and want it removed.<br>
<br>
Breaking peoples openID without a good reason should be avoided.<br>
<br>
I prefer to look at it as coming up with a suitable discovery flow and then determining what identifier formats are appropriate.<br>
<br>
If at the end of the day XRI can't be supported we will discover that. I would prefer not to make that a precondition.<br>
<br>
There are a number of equally under-utilized features of AX we could look at:)<br>
<br>
John B.<br>
<div><div></div><div class="h5"><br>
<br>
On 2010-05-31, at 9:48 PM, Dick Hardt wrote:<br>
<br>
><br>
> On 2010-05-31, at 6:33 PM, Nat Sakimura wrote:<br>
><br>
>> I do not understand why we need to remove XRI.<br>
>> XRI being complex etc. is an illusion or badly written code.<br>
>> If XRI is complex, acct: URI is complex, too.<br>
>> They virtually are the same thing from the processing point of view.<br>
>> Keeping the identifier compatibility is really important for the RPs and Users.<br>
><br>
> I don't think there is much usage of URI, and many sites are not supporting it. Removing under utilized features that are not adding value simplifies the specs and implementations.<br>
><br>
> Nat: do you know of sites that are heavily using XRIs?<br>
><br>
> -- Dick<br>
> _______________________________________________<br>
> board mailing list<br>
> <a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
> <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
<br>
</div></div><br>_______________________________________________<br>
board mailing list<br>
<a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Chris Messina<br>Open Web Advocate, Google<br><br>Personal: <a href="http://factoryjoe.com">http://factoryjoe.com</a><br>Follow me on Buzz: <a href="http://buzz.google.com/chrismessina">http://buzz.google.com/chrismessina</a> <br>
...or Twitter: <a href="http://twitter.com/chrismessina">http://twitter.com/chrismessina</a> <br><br>This email is: [ ] shareable [X] ask first [ ] private<br>
</div>