<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 2010-02-25, at 4:11 PM, Nat Sakimura wrote:</div><br class="Apple-interchange-newline"><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="webkit-indent-blockquote 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; position: static; z-index: auto; ">
wrap_ns=<a href="http://whatever/wrap/1.0">http://whatever/wrap/1.0</a><br>wrap_client_id ... </blockquote></blockquote><div><br></div><div>Versioning was discussed. I don't recall the details, but it was decided it did not add value.</div><div><br></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>Or OpenID could change to using '_' :-)</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">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">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">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>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><br><blockquote type="cite">so I would request Wrap community to come closer. <br></blockquote><div><br></div><div>WRAP followed OAuth, which has much broader adoption from what I know than OpenID</div><div><br></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>Agreed, but perhaps the changes could happen in OpenID or a combination?</div><div><br></div><div>-- Dick</div></body></html>