<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Probably an official readers guide type of thing would do. </div><div><br></div><div>For now, I just wanted to be ready to answer when I was asked. </div>
<div><br>=nat via iPhone</div><div><br>Jun 3, 2013 8:30$B!"(BMike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>> $B$N%a%C%;!<%8(B:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=iso-2022-jp">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"MS PGothic";
panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
{font-family:"\@MS PGothic";
panose-1:2 11 6 0 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"MS PGothic","sans-serif";
mso-fareast-language:JA;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"MS PGothic","sans-serif";
mso-fareast-language:JA;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:JA;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
mso-fareast-language:JA;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">We already cover the rationale for using the “request_uri” in
<a href="http://openid.net/specs/openid-connect-messages-1_0.html#RequestUriRationale">
http://openid.net/specs/openid-connect-messages-1_0.html#RequestUriRationale</a>. We could add similar rationale for when to use the “request” parameter, but I’d submit that adding this isn’t essential to completing the Implementer’s Drafts. We could write
that and review it in a leisurely fashion, after publishing the Implementer’s Drafts, should the working group decide to do so.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> -- Mike</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </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">mailto:sakimura@gmail.com</a>]
<br>
<b>Sent:</b> Sunday, June 02, 2013 4:26 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Michael Jones; <a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> Re: [Openid-specs-ab] [Bitbucket] Issue #835: Clarify the expected JSON type(s) of "value" and "values" in the claims request JSON object (openid/connect)</span></p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Actually, I am asking the guidance between the use of 'claims' top-level parameter and 'request' parameter. </p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">'claims' parameter was added by #748 to ease the writing of MTI and request parameter processing rules. From spec writing point of view, that is more elegant and fine. I just thought that developers who reads this spec may wonder when they
should pick one or the other. </p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> </p>
<div>
<p class="MsoNormal">2013/6/3 Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>></p>
<div>
<div>
<p class="MsoNormal" style><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">The “claims” parameter is always what is used to request individual claims. Independent of that,
the “claims” parameter is one of the parameters that can either occur as a query parameter value, or within a request object passed either as a query parameter value using the “request” parameter or by reference using the “request_uri” parameter.</span></p>
<p class="MsoNormal" style><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal" style><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I think you’re really asking the question “what is the guidance between using request parameters
passed as query parameters and using request parameters passed by reference or by value using a Request Object”. The question is independent of whether the “claims” parameter is used.</span></p>
<p class="MsoNormal" style><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal" style><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> -- Mike</span></p>
<p class="MsoNormal" style><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal" style><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"">
<a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a> [mailto:<a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>Nat Sakimura<br>
<b>Sent:</b> Sunday, June 02, 2013 3:55 PM<br>
<b>To:</b> Michael Jones; <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">
openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> Re: [Openid-specs-ab] [Bitbucket] Issue #835: Clarify the expected JSON type(s) of "value" and "values" in the claims request JSON object (openid/connect)</span></p>
<div>
<p class="MsoNormal" style> </p>
<div>
<p class="MsoNormal" style>A naive question. </p>
<div>
<p class="MsoNormal" style> </p>
</div>
<div>
<p class="MsoNormal" style>What is the guidance between the requesting claims in 'claims' request parameter and the request object? </p>
</div>
<div>
<p class="MsoNormal" style> </p>
</div>
<div>
<p class="MsoNormal" style>From what I see, 'claims' request parameter features are completely covered by request object. Main differences are that request object can specify other parameter such as response_types
as well as other security parameters and can be signed (it is a compact serialized JWS), while 'claims' parameter is form encoded. </p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> </p>
<div>
<p class="MsoNormal" style>2013/5/30 Michael Jones <<a href="mailto:issues-reply@bitbucket.org" target="_blank">issues-reply@bitbucket.org</a>></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td style="background:whitesmoke;padding:7.5pt 7.5pt 0in 7.5pt">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td style="padding:0in 0in 0in 0in">
<div style="border:solid #cccccc 1.0pt;padding:15.0pt 15.0pt 15.0pt 15.0pt;border-radius:5px">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td style="padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td width="40" valign="top" style="width:24.0pt;padding:0in 0in 0in 0in"></td>
<td style="padding:0in 0in 0in 7.5pt">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td colspan="2" style="padding:0in 0in 0in 0in">
<p class="MsoNormal" style><strong><span style="font-size:10.5pt;font-family:"Arial","sans-serif"">Michael Jones</span></strong><span style="font-size:10.5pt;font-family:"Arial","sans-serif""> commented on
issue #835: </span></p>
</td>
</tr>
<tr>
<td colspan="2" style="padding:3.75pt 0in 0in 0in">
<p class="MsoNormal" style><b><span style="font-size:10.5pt;font-family:"Arial","sans-serif""><a href="https://bitbucket.org/openid/connect/issue/835/clarify-the-expected-json-type-s-of-value" target="_blank"><span style="color:#3b73af;text-decoration:none">Clarify
the expected JSON type(s) of "value" and "values" in the claims request JSON object</span></a>
</span></b></p>
</td>
</tr>
<tr>
<td colspan="2" style="padding:7.5pt 0in 11.25pt 0in">
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.5pt;font-family:"Arial","sans-serif"">Fixed
<a href="https://bitbucket.org/openid/connect/issue/835/clarify-the-expected-json-type-s-of-value" target="_blank">
<s><span style="color:#3b73af">#835</span></s></a> - Clarified requirements on using "value" and "values" qualifiers when requesting specific values for individual claims.</span></p>
<p style="margin-bottom:0in;margin-bottom:.0001pt"><span style="font-size:10.5pt;font-family:"Arial","sans-serif"">$B"*(B <<cset
<a href="https://bitbucket.org/openid/connect/commits/6af1216a68a0" target="_blank">
<span style="color:#3b73af;text-decoration:none">6af1216a68a0</span></a>>></span></p>
</td>
</tr>
<tr>
<td nowrap valign="top" style="padding:0in 7.5pt 0in 0in">
<p class="MsoNormal" style><span style="font-size:10.5pt;font-family:"Arial","sans-serif";color:#707070">Status:</span></p>
</td>
<td width="100%" style="width:100.0%;padding:0in 0in 0in 0in">
<p class="MsoNormal" style><s><span style="font-size:10.5pt;font-family:"Arial","sans-serif";background:#ffdddd">new</span></s><span style="font-size:10.5pt;font-family:"Arial","sans-serif"">
<span style="background:#ccffcc">resolved</span> </span></p>
</td>
</tr>
<tr>
<td style="padding:7.5pt 0in 0in 0in"></td>
<td style="padding:7.5pt 0in 0in 0in"></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td style="border:none;border-top:solid #cccccc 1.0pt;padding:7.5pt 0in 0in 0in">
<p class="MsoNormal" style><span style="font-size:10.5pt;font-family:"Arial","sans-serif""><a href="https://bitbucket.org/openid/connect/issue/835/clarify-the-expected-json-type-s-of-value" target="_blank"><span style="color:#3b73af;text-decoration:none">View
this issue</span></a> or add a comment by replying to this email. </span></p>
</td>
</tr>
</tbody>
</table>
</div>
</td>
</tr>
<tr>
<td style="padding:15.0pt 0in 15.0pt 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal" style><a href="https://bitbucket.org/openid/connect/issue/835/unsubscribe/Nat/6c4f45461cac10ce372f1f81a7903130e0898f5c/" target="_blank"><span style="color:#3b73af;text-decoration:none">Unsubscribe
from issue emails</span></a> for this repository. </p>
</td>
<td style="padding:0in 0in 0in 0in"></td>
<td width="125" style="width:75.0pt;padding:0in 0in 0in 0in"></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<p class="MsoNormal" style><a href="https://bitbucket.org" target="_blank"><span style="color:windowtext;text-decoration:none"><br>
<br clear="all">
</span></a></p>
<div>
<p class="MsoNormal" style><a href="https://bitbucket.org" target="_blank"><span style="color:windowtext;text-decoration:none"> </span></a></p>
</div>
</div>
<p class="MsoNormal" style><span style="color:#888888"><a href="https://bitbucket.org" target="_blank"><span style="color:windowtext;text-decoration:none">--
<br>
Nat Sakimura (=nat)</span></a></span></p>
<div>
<div>
<p class="MsoNormal" style><a href="https://bitbucket.org" target="_blank"><span style="color:windowtext;text-decoration:none">Chairman, OpenID Foundation<br>
</span>http://nat.sakimura.org/<span style="color:windowtext;text-decoration:none"><br>
@_nat_en</span></a></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
</p>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">-- <br>
Nat Sakimura (=nat)</p>
<div>
<p class="MsoNormal">Chairman, OpenID Foundation<br>
<a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en</p>
</div>
</div>
</div>
</div></blockquote></body></html>