<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-2022-jp"><base href="x-msg://1238/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">FYI:<div>Ruby implementation of the normalization logic is here.<br><a href="https://gist.github.com/nov/5915858">https://gist.github.com/nov/5915858</a></div><div><br><div>Ruby built-in URI parser seems not so useful in this case.<br><div><br><div><div>On 2013/07/03, at 10:16, Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">The version of Discovery on bitbucket at<span class="Apple-converted-space"> </span><a href="http://openid.bitbucket.org/openid-connect-discovery-1_0.html" style="color: purple; text-decoration: underline; ">http://openid.bitbucket.org/openid-connect-discovery-1_0.html</a><span class="Apple-converted-space"> </span>has a proposed fix to #856<span class="Apple-converted-space"> </span><a href="https://bitbucket.org/openid/connect/issue/856/discovery-uri-grammar-definition-doesnt" style="color: purple; text-decoration: underline; ">https://bitbucket.org/openid/connect/issue/856/discovery-uri-grammar-definition-doesnt</a><span class="Apple-converted-space"> </span>for working group review.  In particular, it updated the normative text to clarify that no input normalization is performed when the input contains an explicit scheme such as "acct" that matches the RFC 3986 scheme ":" path-rootless syntax.  I did not push this out to<span class="Apple-converted-space"> </span><a href="http://openid.net/specs/openid-connect-discovery-1_0.html" style="color: purple; text-decoration: underline; ">http://openid.net/specs/openid-connect-discovery-1_0.html</a><span class="Apple-converted-space"> </span>yet because I believe that the working group should review the fix before we apply it as an errata change.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">You can view the diffs at<span class="Apple-converted-space"> </span><a href="https://bitbucket.org/openid/connect/commits/ed8be80869c7" style="color: purple; text-decoration: underline; ">https://bitbucket.org/openid/connect/commits/ed8be80869c7</a>.  In particular, I’d like working group input on whether using the RFC 3986 scheme ":" path-rootless syntax is the right fix.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">You can also view the diffs as tracked changes in the attached Word doc.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">                                                                Best wishes,<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">                                                                -- Mike<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div></div><span><openid-connect-discovery-1_0-17 2-Jul-13 diffs.docx></span>_______________________________________________<br>Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net" style="color: purple; text-decoration: underline; ">Openid-specs-ab@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" style="color: purple; text-decoration: underline; ">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br></div></blockquote></div><br></div></div></div></body></html>