<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#002060;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#002060">The normative definition of “Claim” for JWTs is this one from the JWT spec at
<a href="https://tools.ietf.org/html/rfc7519#section-2">https://tools.ietf.org/html/rfc7519#section-2</a>:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Consolas;color:black;background:white"> Claim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Consolas;color:black;background:white"> A piece of information asserted about a subject. A claim is<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Consolas;color:black;background:white"> represented as a name/value pair consisting of a Claim Name and a<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Consolas;color:black;background:white"> Claim Value.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">It says nothing about doubt – just that the information was asserted. Therefore, I continue to agree that Torsten’s suggested identifier “verified_claim” is the right one.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Torsten Lodderstedt <torsten@lodderstedt.net> <br>
<b>Sent:</b> Saturday, June 15, 2019 12:52 AM<br>
<b>To:</b> Anthony Nadalin <tonynad@microsoft.com><br>
<b>Cc:</b> Mike Jones <Michael.Jones@microsoft.com>; Artifact Binding/Connect Working Group <openid-specs-ab@lists.openid.net><br>
<b>Subject:</b> Re: Review of openid-connect-4-identity-assurance-04<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Am 14.06.2019 um 18:48 schrieb Anthony Nadalin <<a href="mailto:tonynad@microsoft.com">tonynad@microsoft.com</a>>:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">It’s not a claim then, it’s a statement, it does not matter who has the claim, the issuer or the beholder, it’s still in doubt. I don’t understand enough of the “verified” statement since the language is vague in the specification, is it
the provenance of the data or the truth of the data ?<o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">I would say first of all truth but backed by data about the provenance<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Happy to incorporate your text proposals to improve the spec language <o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>>
<br>
<b>Sent:</b> Friday, June 14, 2019 9:45 AM<br>
<b>To:</b> Anthony Nadalin <<a href="mailto:tonynad@microsoft.com">tonynad@microsoft.com</a>>; Artifact Binding/Connect Working Group <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>>; Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>><br>
<b>Subject:</b> Re: Review of openid-connect-4-identity-assurance-04<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Arial",sans-serif;color:black">A claim is a statement made by the issuer. A verified claim is one with evidence backing it beyond the veracity of the issuer.
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Arial",sans-serif;color:black">Doubt or belief are both properties of the beholder - not the issuer.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black">-- Mike</span><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Anthony Nadalin<br>
<b>Sent:</b> Friday, June 14, 2019 6:44:29 PM<br>
<b>To:</b> Artifact Binding/Connect Working Group; Torsten Lodderstedt<br>
<b>Cc:</b> Mike Jones<br>
<b>Subject:</b> RE: Review of openid-connect-4-identity-assurance-04</span> <o:p>
</o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">A claim is something in doubt, how can you have a verified claim?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Openid-specs-ab <<a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>>
<b>On Behalf Of </b>Mike Jones via Openid-specs-ab<br>
<b>Sent:</b> Friday, June 14, 2019 8:42 AM<br>
<b>To:</b> Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>><br>
<b>Cc:</b> Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>>;
<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> Re: [Openid-specs-ab] Review of openid-connect-4-identity-assurance-04<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Arial",sans-serif;color:black">I agree with "verified_claims".</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black">Thanks!</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black">-- Mike</span><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="98%" align="center">
</div>
<div id="x_divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>><br>
<b>Sent:</b> Friday, June 14, 2019 5:47:17 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Daniel Fett; <a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> Re: Review of openid-connect-4-identity-assurance-04</span> <o:p>
</o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Mike,<br>
<br>
Thanks a lot for your substantial feedback.<br>
<br>
While I'm incorporating it, I would like to sort out one question:<br>
<br>
> On 1. Jun 2019, at 02:16, Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>> wrote:<br>
> <br>
> All Sections: Generalize kinds of verified claims. The most important issue is to generalize the goal of the document from defining how to use “verified person data” to defining how to use “verified data”. This work isn’t happening in a vacuum. There
are other efforts to define representations of verified claims in the industry, including
<a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fvc-data-model%2F&data=04%7C01%7Ctonynad%40microsoft.com%7C751b6b0b0ffb4842def908d6f0e7a856%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961275087950014%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=cV1XZpHoSMWZ%2BUNfp6jDGKyBRrKkly%2F4D8JQJ7eFov0%3D&reserved=0">
https://w3c.github.io/vc-data-model/</a>, that take this more general approach, but propose much more complicated data representations that are not based on JWTs. It would be highly beneficial to have a simple general JWT-based “verified data” representation
that is general-purpose. Indeed, that’s the possibility that excites me about this work. Don’t get me wrong – I believe that all the particulars for verified people data can and should remain. The main concrete change needed is to rename “verified_person_data”
to “verified_data”. <br>
<br>
I think “verified_claims” would fit even better. What do you think?<br>
<br>
best regards,<br>
Torsten. <br>
<br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>