<HTML>
<HEAD>
<TITLE>Re: [WRAP] Name space and prefix - OpenID Harmonization</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>As a datapoint – OAuth 1.0a deliberately did not change the version string from 1.0 to 1.0a, and it was determined that the version parameter did not add any value. I can’t quite recall the reasoning behind this off the top of my head though.<BR>
<BR>
Big +10000 to trying to harmonize OpenID and Oauth WRAP.<BR>
Allen<BR>
<BR>
<BR>
<BR>
On 2/25/10 8:22 PM, "Nat Sakimura" <<a href="sakimura@gmail.com">sakimura@gmail.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
On Fri, Feb 26, 2010 at 11:55 AM, Dick Hardt <<a href="dick.hardt@gmail.com">dick.hardt@gmail.com</a>> wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
On 2010-02-25, at 4:11 PM, Nat Sakimura wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi<BR>
<BR>
This may have come up earlier but ... <BR>
<BR>
I think Wrap should have a namespace / versioning syntax. <BR>
Invariably, it will evolve, and will require version number etc. so, it seems better to me to have one from the beginning. <BR>
<BR>
e.g., <BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>wrap_ns=<a href="http://whatever/wrap/1.0">http://whatever/wrap/1.0</a><BR>
wrap_client_id ... <BR>
</SPAN></FONT></BLOCKQUOTE></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Versioning was discussed. I don't recall the details, but it was decided it did not add value.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
I actually think it does. <BR>
Perhaps not in the initial version, but in the future for sure. <BR>
So, it is better to have it in the design from the beginning. <BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
I would go further. Why is underscore '_' is used for the delimiter? <BR>
If we make it dot '.', it will improve the future compatibility with OpenID. <BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Or OpenID could change to using '_' :-)<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
If you use '_' as the namespace delimiter, then '_' should be disallowed in the parameter name, which is not the case right now. <BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>So, we could do something like: <BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>openid.ns=<a href="http://whatever/wrap/1.0">http://whatever/wrap/1.0</a><BR>
openid.client_id ...<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
The same applies for OpenID. For an unknown reason, though OpenID has namespace so that we write: <BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>openid.ns= <a href="http://specs.openid.net/auth/2.0">http://specs.openid.net/auth/2.0</a><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
the prefix "openid" is fixed. We should be able to change it like: <BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>wrap.ns=<a href="http://specs.openid.net/auth/2.0">http://specs.openid.net/auth/2.0</a><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Now, the third point. <BR>
<BR>
Could we not try to harmonize the variable names between the two specs? <BR>
<BR>
OpenID is in use widely, so it is kind of hard to change it, <BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Interesting assumption. At IIW we discussed OpenID v Next that was NOT backward compatible. It would seem that there is an oppportunity to make changes to OpenID as well as OAuth WRAP.<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
yes. The above also requires changes on the OpenID side, but I am seeing an opportunity to make the transition smoother. <BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>so I would request Wrap community to come closer. <BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
WRAP followed OAuth, which has much broader adoption from what I know than OpenID<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Arguably yes, but at the same time, 'wrap_' is not 'oauth_' ;-)<BR>
</SPAN></FONT><BLOCKQUOTE><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
IMHO, we should try to harmonize/unite instead of fragmenting. <BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Agreed, but perhaps the changes could happen in OpenID or a combination?<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Definitely in combination. <BR>
<BR>
It is good that OpenID Foundation finally can start creating WGs again. <BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<FONT COLOR="#888888">-- Dick<BR>
</FONT><BR>
_______________________________________________<BR>
specs mailing list<BR>
<a href="specs@lists.openid.net">specs@lists.openid.net</a><BR>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>