Thanks Mike, <div><br></div><div>Comments in-line: <br><br><div class="gmail_quote">2013/2/6 Mike Jones <span dir="ltr"><<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Updated versions attached that also address Brian Campbell’s review comments on Registration. The versions at
<a href="http://openid.bitbucket.org/" target="_blank">http://openid.bitbucket.org/</a> were also updated.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> -- Mike<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Mike Jones
<br>
<b>Sent:</b> Tuesday, February 05, 2013 7:12 PM<br>
<b>To:</b> 'Nat Sakimura'<br>
<b>Cc:</b> <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a> Group; Justin Richer<br>
<b>Subject:</b> RE: [Openid-specs-ab] Dynamic Client Registration<u></u><u></u></span></p>
</div>
</div><div class="im">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I’ve applied the parts of Nat’s discussion draft that implement working group decisions to the current registration draft. Changes applied are:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p><u></u><span style="font-size:11.0pt;font-family:Symbol;color:#1f497d"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Tracked wording changes intended to better harmonize with the OAuth registration draft<u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;font-family:Symbol;color:#1f497d"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Corrected version number to -15. (Apparently it had been erroneously incremented twice – once by me, once by Nat)<u></u><u></u></span></p>
<ul type="disc">
<li class="MsoNormal" style="margin-right:48.0pt">
<span lang="EN" style="font-family:"Verdana","sans-serif"">Fixed #746 - Deleted the
</span><span lang="EN" style="font-family:"Courier New";color:#003366">operation</span><span lang="EN" style="font-family:"Verdana","sans-serif""> parameter.
<u></u><u></u></span></li><li class="MsoNormal" style="margin-right:48.0pt">
<span lang="EN" style="font-family:"Verdana","sans-serif"">Fixed #745 - Deleted the
</span><span lang="EN" style="font-family:"Courier New";color:#003366">rotate_secret</span><span lang="EN" style="font-family:"Verdana","sans-serif""> operation.
<u></u><u></u></span></li><li class="MsoNormal" style="margin-right:48.0pt">
<span lang="EN" style="font-family:"Verdana","sans-serif"">Changed the Japanese client name to make it sound more natural.
<u></u><u></u></span></li><li class="MsoNormal" style="margin-right:48.0pt">
<span lang="EN" style="font-family:"Verdana","sans-serif"">Added optional </span>
<span lang="EN" style="font-family:"Courier New";color:#003366">issued_at</span><span lang="EN" style="font-family:"Verdana","sans-serif""> response value.
<u></u><u></u></span></li><li class="MsoNormal" style="margin-right:48.0pt">
<span lang="EN" style="font-family:"Verdana","sans-serif"">Added client update example.<u></u><u></u></span></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I did not apply these changes:</span></p></div></div></div></blockquote><div><br></div><div>So these are the discussion item. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><div class="im"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in">
<u></u><span style="font-size:10.0pt;font-family:Symbol;color:#1f497d"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Moved Terminology section out of Introduction to form an independent section and added several terminology definitions</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
– This would make the section hierarchy of registration different than all the other Connect specs</span></p></div></div></div></blockquote><div><br></div><div>OK. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple"><div><div class="im"><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added Client Read Request (GET)</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> – No working group decision to add this operation</span></p>
</div></div></div></blockquote><div><br></div><div>If the intended behavior of the "update" was in fact "replace", then having this is very useful. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple"><div><div class="im"><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added Client Delete Request (DELETE)</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> – No working group decision to add this operation</span> </p>
</div></div></div></blockquote><div><br></div><div>We should discuss whether we need some sort of deactivation. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple"><div><div class="im"><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added "Self URL"</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> – No working group decision to add this functionality</span><span style="font-family:"Verdana","sans-serif""><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added </span><tt><span style="font-size:10.0pt;color:#003366">_links</span></tt><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> – No working group
decision to add this functionality</span></p></div></div></div></blockquote><div><br></div><div>From my read, the working group intent was to have a clearly separated endpoint for the initial registration and subsequent operations. </div>
<div>While my proposal was achieving that in a backward compatible way<font face="courier new, monospace" size="1">[1]</font>, the current d15 does not have that. Instead, it is looking at the existence of client_id to switch the behavior. </div>
<div><br></div><div>While this SOA like architecture is OK (and in general, that's how OAuth is), having the ability for the server to indicate the link relations url is one step closer to <a href="http://en.wikipedia.org/wiki/HATEOAS">HATEOAS </a>(aka REST). In my proposal, <font face="courier new, monospace">_links.self.href</font> represents the link-relationship defined in <a href="http://tools.ietf.org/html/rfc5988">RFC5988 </a>and <a href="http://www.iana.org/assignments/link-relations/link-relations.xml">IANA Link Relations registry</a>. In addition, we probably should define a media-type for the response, such as <font face="courier new, monospace">application/json+oauth</font>, and define how the JSON should be serialized into URL form encoding (or JSON POST etc.) in the subsequent request. That will create a uniform interface. </div>
<div><br></div><div>To achieve this, syntactically, we would have three ways: HAL that I used and JSON Schema. If it were JSON Schema, it would have benn </div><div><font face="courier new, monospace">links.rel['self'][0].href</font> instead. I found HAL-wya of being <font face="courier new, monospace">_links.self.href</font> a bit easier on my eyes so I used HAL. </div>
<div><br></div><div>The third way is to use HTTP response header in the form of: </div><div><br></div><font face="courier new, monospace">Link: <<a href="https://server.example.com/clients/1234">https://server.example.com/clients/1234</a>>; rel="self";</font></div>
<div class="gmail_quote"><font face="courier new, monospace"> title="oauth client registration url"</font></div><div class="gmail_quote"><br></div><div class="gmail_quote">Arguably, this is the best way for OAuth, which is currently completely HTTP based. </div>
<div class="gmail_quote">Downside is that if we start having other binding (e.g., IMAP, XMPP, etc.), then we have to fall back to HAL or other ways. <br><div><br></div><div><span style="font-size:x-small">[1] by providing </span><font face="courier new, monospace" style="font-size:x-small">_links.self.href</font><span style="font-size:x-small"> as the registration URL + </span><font face="courier new, monospace" style="font-size:x-small">"?operation=client_update</font><span style="font-size:x-small">" </span></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><div class="im"><p class="MsoNormal" style="margin-left:.5in">
<span style="font-family:"Verdana","sans-serif""><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added Editor's Notes</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> – We should be tracking issues in the issue tracker instead</span></p>
</div></div></div></blockquote><div><br></div><div>Did you create tracker entries? </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple">
<div><div class="im"><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Cleaned up the indents</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> – Were there were no text changes from the original version, I tried
to keep the exact text from the original to facilitate diff’ing the .xml source. Where there were changes, I tried to keep Nat’s .xml formatting.</span></p></div></div></div></blockquote><div><br></div><div>IMHO, at some point before publishing, we should clean the indent. Perhaps creating a text without any text change but only the indent would be good. </div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><div class="im"><p class="MsoNormal" style="margin-left:.5in">
<span style="font-family:"Verdana","sans-serif""><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I also did not apply a big unlisted change, which had changed the semantics of Client Update from replace-all-fields to update-only-listed-fields
– No working group decision to change this functionality</span></p></div></div></div></blockquote><div><br></div><div>Actually, it was not very clear in d14 whether it was a replacement or update. It only had a non-normative (i.e., no MUST, SHOULD, etc.) text saying "<span style="font-family:verdana,charcoal,helvetica,arial,sans-serif;background-color:rgb(255,255,255)">Client Update Requests replace all previous parameters set for a </span><tt style="color:rgb(0,51,102);font-family:'Courier New',Courier,monospace;background-color:rgb(255,255,255)">client_id</tt><span style="font-family:verdana,charcoal,helvetica,arial,sans-serif;background-color:rgb(255,255,255)">." Were it to be a normative text, it had to state something like: </span></div>
<div><span style="font-family:verdana,charcoal,helvetica,arial,sans-serif;background-color:rgb(255,255,255)"><br></span></div><div><span style="font-family:verdana,charcoal,helvetica,arial,sans-serif;background-color:rgb(255,255,255)">Upon the receipt of the request, the server MUST update all the registered parameters set for a </span><span style="background-color:rgb(255,255,255);color:rgb(0,51,102);font-family:'Courier New',Courier,monospace">client_id</span><span style="background-color:rgb(255,255,255);font-family:verdana,charcoal,helvetica,arial,sans-serif"> in the request with the received value, MUST update all the registered parameters not included in the request but with a server default with the current server default value, and MUST delete any other previously registered parameters. </span></div>
<div><span style="background-color:rgb(255,255,255);font-family:verdana,charcoal,helvetica,arial,sans-serif"><br></span></div><div><span style="background-color:rgb(255,255,255);font-family:verdana,charcoal,helvetica,arial,sans-serif">This means </span></div>
<div><span style="background-color:rgb(255,255,255);font-family:verdana,charcoal,helvetica,arial,sans-serif"><br></span></div><div><span style="background-color:rgb(255,255,255);font-family:verdana,charcoal,helvetica,arial,sans-serif">(1) the client has to store all the returned value from the registration request [it is OK but we probably should state it if so.]; </span></div>
<div><span style="background-color:rgb(255,255,255);font-family:verdana,charcoal,helvetica,arial,sans-serif">(2) the update request MUST include all the values in (1), otherwise it may change the values; </span></div><div>
<span style="background-color:rgb(255,255,255);font-family:verdana,charcoal,helvetica,arial,sans-serif">(3) the update request creates new parameters if the server defaults were added between the registration and update; </span></div>
<div><span style="background-color:rgb(255,255,255);font-family:verdana,charcoal,helvetica,arial,sans-serif"><br></span></div><div><span style="font-family:verdana,charcoal,helvetica,arial,sans-serif;background-color:rgb(255,255,255)">Now, the question is, is this the intended behavior? </span></div>
<div><span style="font-family:verdana,charcoal,helvetica,arial,sans-serif;background-color:rgb(255,255,255)"><br></span></div><div><span style="font-family:verdana,charcoal,helvetica,arial,sans-serif;background-color:rgb(255,255,255)">Also, another question is that if the server changed the server default, would this affect the currently registered values? My read is "no", but just to make sure -- and we should clarify it in any case. </span></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><div class="im"><p class="MsoNormal" style="margin-left:.5in">
<span style="font-family:"Verdana","sans-serif""><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">Justin</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">, it would be good if you applied the changes made in this version
to the OAuth registration draft as well, because there were numerous bug fixes – especially in the examples. (BTW, you can’t put more than 70 characters in an <artwork> line or xml2rfc complains when producing the .txt version.)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">The .xml, .unpg (unpaginated text), and .html versions are attached.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I’ll send a few questions about the current text separately.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
</div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> -- Mike<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Nat Sakimura [<a href="mailto:sakimura@gmail.com" target="_blank">mailto:sakimura@gmail.com</a>]
<br></span></p><div class="im">
<b>Sent:</b> Monday, February 04, 2013 2:03 PM<br>
<b>To:</b> Mike Jones<br>
</div><b>Cc:</b> <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a> Group; Justin Richer<div class="im"><br>
<b>Subject:</b> Re: [Openid-specs-ab] Dynamic Client Registration<u></u><u></u></div><p></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">OK. Now I have uploaded the correct Discussion Draft 17. <br></p><div><div class="h5">
<br>
HTML: <a href="http://nat.sakimura.org/wp-content/uploads/2013/02/draft-openid-connect-registration-1_0.html" target="_blank">
http://nat.sakimura.org/wp-content/uploads/2013/02/draft-openid-connect-registration-1_0.html</a><br>
diff: <a href="http://nat.sakimura.org/wp-content/uploads/2013/02/openid-connect-registration-1_0-diff-16-17.txt" target="_blank">
http://nat.sakimura.org/wp-content/uploads/2013/02/openid-connect-registration-1_0-diff-16-17.txt</a><u></u><u></u></div></div><p></p><div><div class="h5">
<div>
<p class="MsoNormal">XML: <a href="http://nat.sakimura.org/wp-content/uploads/2013/02/openid-connect-registration-1_0.xml" target="_blank">http://nat.sakimura.org/wp-content/uploads/2013/02/openid-connect-registration-1_0.xml</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">TXT (d16): <a href="http://nat.sakimura.org/wp-content/uploads/2013/02/openid-connect-registration-1_0-d16.txt" target="_blank">http://nat.sakimura.org/wp-content/uploads/2013/02/openid-connect-registration-1_0-d16.txt</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">TXT (d17): <a href="http://nat.sakimura.org/wp-content/uploads/2013/02/openid-connect-registration-1_0-d17.txt" target="_blank">http://nat.sakimura.org/wp-content/uploads/2013/02/openid-connect-registration-1_0-d17.txt</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br>
[Changes] <u></u><u></u></p>
<p style="margin-right:24.0pt;margin-bottom:5.0pt;margin-left:24.0pt">
<span style="font-family:"Verdana","sans-serif"">-17 discussion version<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Moved Terminology section out of Introduction to form an independent section and added several terminology definitions<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Deleted the </span><tt><span style="font-size:10.0pt;color:#003366">operation</span></tt><span style="font-family:"Verdana","sans-serif""> parameter<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Deleted the </span><tt><span style="font-size:10.0pt;color:#003366">rotate_secret</span></tt><span style="font-family:"Verdana","sans-serif""><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added Client Read Request (GET)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added Client Delete Request (DELETE)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added "Self URL"<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added </span><tt><span style="font-size:10.0pt;color:#003366">_links</span></tt><span style="font-family:"Verdana","sans-serif""><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added Editor's Notes<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Changed the Japanese client name to make it sound more natural<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added issued_at<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Added client update example (that seems to be missing many parameters that were present in the registration request example)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:24.0pt;margin-left:60.0pt">
<u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-family:"Verdana","sans-serif"">Cleand up the indents<u></u><u></u></span></p>
<p class="MsoNormal">[Remarks] <u></u><u></u></p>
<div>
<ul type="disc">
<li class="MsoNormal">
The <tt><span style="font-size:10.0pt;color:#003366">operation</span></tt><span style="font-family:"Verdana","sans-serif""> parameter was removed but since the URL for the registration and other operations are different, there should be no problem in finding
out what action should be taken. </span><u></u><u></u></li><li class="MsoNormal">
The URL for update etc. (Self URL) are given in _links/self/href. For servers' backward compatibility with the current implementations, it could be set like
<span style="font-family:"Courier New""><a href="https://server.example.com/connect/register?operation=client_update" target="_blank">https://server.example.com/connect/register?operation=client_update</a></span> so that the existing code is likely not break (if the web application
framework is putting GET and POST parameters together into an object) or needs only minor change. Clients needs to read this value and store, so it is a bigger change. <u></u><u></u></li></ul>
<div>
<p class="MsoNormal">Unfortunately, I will be able to join the call only very briefly due to my flight schedule. <u></u><u></u></p>
</div>
<p class="MsoNormal">-- <br>
Nat Sakimura (=nat)<br>
Chairman, OpenID Foundation<br>
<a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en<u></u><u></u></p>
</div>
</div>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Nat Sakimura (=nat)<div>Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>@_nat_en</div>
</div>