Actually, that was because PHP variables does not allow '.' to be in it ... <br><br><div class="gmail_quote">On Tue, Mar 2, 2010 at 10:07 AM, Nat Sakimura <span dir="ltr"><<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Goodness... <div><br></div><div>Then what would be a good character for a delimiter? </div><div>Or do we just use '_' for it and stop using '_' for the readability? </div>
<div><br></div><div><font color="#888888">=nat</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Tue, Mar 2, 2010 at 9:26 AM, Joseph Smarr <span dir="ltr"><<a href="mailto:jsmarr@gmail.com" target="_blank">jsmarr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
FYI, one reason OAuth/WRAP use _ instead of . is that PHP (stupidly) converts all . to _ in query var names, so it's just easier not to fight that, esp when you have to compute signatures. So if we're naming any new params, I'd strongly argue for _ over . as the delimiter. Yes it's dumb, but PHP is not going away any time soon, so this is the clear pragmatic choice. js<br>
<br><div class="gmail_quote"><div><div></div><div>On Thu, Feb 25, 2010 at 8:22 PM, Nat Sakimura <span dir="ltr"><<a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div>
<br><br><div class="gmail_quote"><div>On Fri, Feb 26, 2010 at 11:55 AM, Dick Hardt <span dir="ltr"><<a href="mailto:dick.hardt@gmail.com" target="_blank">dick.hardt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><br><div><div><div>On 2010-02-25, at 4:11 PM, Nat Sakimura wrote:</div><br><blockquote type="cite">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><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
wrap_ns=<a href="http://whatever/wrap/1.0" target="_blank">http://whatever/wrap/1.0</a><br>wrap_client_id ... </blockquote></blockquote><div><br></div></div><div>Versioning was discussed. I don't recall the details, but it was decided it did not add value.</div>
<div><div><br></div></div></div></div></blockquote><div><br></div></div><div>I actually think it does. </div><div>Perhaps not in the initial version, but in the future for sure. </div><div>So, it is better to have it in the design from the beginning. </div>
<div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><div></div><br><blockquote type="cite"><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></blockquote><div><br></div></div><div>Or OpenID could change to using '_' :-)</div></div></div></blockquote><div><br></div>
</div><div>If you use '_' as the namespace delimiter, then '_' should be disallowed in the parameter name, which is not the case right now. </div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div><div><br></div><br><blockquote type="cite">
So, we could do something like: <br><br><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
openid.ns=<a href="http://whatever/wrap/1.0" target="_blank">http://whatever/wrap/1.0</a></blockquote><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
openid.client_id ...</blockquote><br>The same applies for OpenID. For an unknown reason, though OpenID has namespace so that we write: <br><br><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
openid.ns= <a href="http://specs.openid.net/auth/2.0" target="_blank">http://specs.openid.net/auth/2.0</a></blockquote><br>the prefix "openid" is fixed. We should be able to change it like: <br><br><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
wrap.ns=<a href="http://specs.openid.net/auth/2.0" target="_blank">http://specs.openid.net/auth/2.0</a></blockquote><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, </blockquote><div><br></div></div>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.</div>
</div></blockquote><div><br></div></div><div>yes. The above also requires changes on the OpenID side, but I am seeing an opportunity to make the transition smoother. </div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div><br><blockquote type="cite">so I would request Wrap community to come closer. <br></blockquote><div><br></div></div><div>WRAP followed OAuth, which has much broader adoption from what I know than OpenID</div>
<div><div><br></div></div></div></div></blockquote><div><br></div></div><div>Arguably yes, but at the same time, 'wrap_' is not 'oauth_' ;-)</div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div><div></div><blockquote type="cite"><div><br></div><div>IMHO, we should try to harmonize/unite instead of fragmenting. <br></div></blockquote><div><br></div></div></div>
<div>Agreed, but perhaps the changes could happen in OpenID or a combination?</div></div></blockquote><div><br></div></div><div>Definitely in combination. </div><div><br></div><div>It is good that OpenID Foundation finally can start creating WGs again. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><font color="#888888"><div>-- Dick</div></font></div><br>
_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
<br></blockquote></div></div></div><div><div><div></div><div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
<p></p></div></div>
-- <br></div><div><div></div><div>
You received this message because you are subscribed to the Google Groups "OAuth WRAP WG" group.<br>
To post to this group, send email to <a href="mailto:oauth-wrap-wg@googlegroups.com" target="_blank">oauth-wrap-wg@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href="mailto:oauth-wrap-wg%2Bunsubscribe@googlegroups.com" target="_blank">oauth-wrap-wg+unsubscribe@googlegroups.com</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/group/oauth-wrap-wg?hl=en" target="_blank">http://groups.google.com/group/oauth-wrap-wg?hl=en</a>.<br>
</div></div></blockquote></div><br>
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups "OAuth WRAP WG" group.<br>
To post to this group, send email to <a href="mailto:oauth-wrap-wg@googlegroups.com" target="_blank">oauth-wrap-wg@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href="mailto:oauth-wrap-wg%2Bunsubscribe@googlegroups.com" target="_blank">oauth-wrap-wg+unsubscribe@googlegroups.com</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/group/oauth-wrap-wg?hl=en" target="_blank">http://groups.google.com/group/oauth-wrap-wg?hl=en</a>.<br>
</blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en">http://twitter.com/_nat_en</a><br>