<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 14 (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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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
{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:"Times New Roman","serif";}
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";}
span.EmailStyle18
{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";}
.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><!--[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='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I am getting foggy on my understanding of where things are heading. I follow the notion that magic will happen on the resource server side that will tag data using the confidentiality codes. What I don’t follow is who does the coding for that informs this magic on how it should work?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It may be a sin amongst this crowd but I am thinking of how DS4P is designed. There is a code set that gets populated by some “authority”” and the software says – oh this code is found in my table of HIV related codes and I tag it as HIV. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For me the entire DS4p scheme falls down because no one has the authority to say if you populate your Code sets with these values then you follow the clients preference you are in a safe harbor and no one can ding you for sharing when you shouldn’t.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>John – where you say this should include the patient UX am I to understand that for a given code set the every patient will have the opportunity to configure what is in that code set of things that get tagged with a confidentiality code?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I think that is an improvement over DS4P but it still hinges on the question – am I as the RS disclosing a patient’s data doing so in a safe harbor if I allow the patient to customize what they consider sensitive or not?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Or is that the bit of Harry Potter magic that takes place? Or should we be explicit and say that it is another assumption about the CEs in the role of discloser being compliant if they allow the patient to configure the LOV to aligg with their own sensitivities?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Aaron Seib, CEO<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>@CaptBlueButton <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> (o) 301-540-2311<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>(m) 301-326-6843<o:p></o:p></span></p><p class=MsoNormal><a href="nate-trust.org"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;text-decoration:none'><img border=0 width=205 height=48 id="Picture_x0020_1" src="cid:image002.jpg@01D1E763.24512010"></span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></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"'> Openid-specs-heart [mailto:openid-specs-heart-bounces@lists.openid.net] <b>On Behalf Of </b>John Moehrke<br><b>Sent:</b> Tuesday, July 26, 2016 4:36 PM<br><b>To:</b> Eve Maler<br><b>Cc:</b> HEART List<br><b>Subject:</b> Re: [Openid-specs-heart] Resources vs Resource sets<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p>So. I think best step forward is to say that some magic will happen on the resource server side that will tag data using the _confidentiality codes. This should include patient UX that aids with this setting. Yes it is known today this is poorly done. Default is N when it is not set. <o:p></o:p></p><p>But setting the tags on the RS is not in HEART scope. It is a precondition.<o:p></o:p></p><p>UMA will control authorization to the various _confidentiality levels. <o:p></o:p></p><p>UMA can also control resource types.<o:p></o:p></p><p>UMA can also control specific instances of a resource.<o:p></o:p></p><p>Nice clean separation.<o:p></o:p></p><p>John<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Jul 26, 2016 2:56 PM, "Eve Maler" <<a href="mailto:eve.maler@forgerock.com">eve.maler@forgerock.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>No, sorry, I meant UMA resource set types -- semantic types, not security labels. Yikes.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><a href="https://docs.kantarainitiative.org/uma/rec-oauth-resource-reg-v1_0_1.html#resource-set-desc" target="_blank"><span style='font-size:9.5pt'>https://docs.kantarainitiative.org/uma/rec-oauth-resource-reg-v1_0_1.html#resource-set-desc</span></a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>In other words, we should be defining a profile that literally standardizes UMA resource set types, because that's the only thing in UMA that makes sense to standardize.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I promise never to leave off a qualifying name again, cross my heart. (Uh, no pun intended.)<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><div><div><div><div><div><div><div><div><div><div><p><b>Eve Maler<br></b>ForgeRock Office of the CTO | VP Innovation & Emerging Technology<br>Cell <a href="tel:%2B1%20425.345.6756" target="_blank">+1 425.345.6756</a> | Skype: xmlgrrl | Twitter: @xmlgrrl<br><b>ForgeRock Summits and UnSummits</b> <a href="http://summits.forgerock.com/" target="_blank">are coming to</a> <b>Sydney, London, and Paris!</b><o:p></o:p></p></div></div></div></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Tue, Jul 26, 2016 at 12:26 PM, John Moehrke <<a href="mailto:johnmoehrke@gmail.com" target="_blank">johnmoehrke@gmail.com</a>> wrote:<o:p></o:p></p><p>You are reinventing the securityLabels solution that already exists and that I have recommended. It is frustrating that this committee can't focus in what UMA does and leverage the work others have already put in place.<o:p></o:p></p><p><span style='color:#888888'>John<o:p></o:p></span></p><div><div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Jul 26, 2016 12:06 PM, "Eve Maler" <<a href="mailto:eve.maler@forgerock.com" target="_blank">eve.maler@forgerock.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>If we have Alice check off the FHIR resources she wants to share individually and not share them as a prepackaged "first visit" bundle, then a number of things get a bit easier for the services involved (though the "HIV problem" doesn't get solved).<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We can next set about defining UMA resource sets and their attendant scopes for that list of FHIR resources. Note that the scopes <i>can</i> be unique per resource set, but need not be.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I recommend that we plan for these to be profiled UMA resource set <b>types</b>. Alice's instance of a medication list type would differ from Carol's, which would differ from David's, and so on.<o:p></o:p></p></div></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><div><div><div><div><div><div><div><div><div><div><p><b>Eve Maler<br></b>ForgeRock Office of the CTO | VP Innovation & Emerging Technology<br>Cell <a href="tel:%2B1%20425.345.6756" target="_blank">+1 425.345.6756</a> | Skype: xmlgrrl | Twitter: @xmlgrrl<br><b>ForgeRock Summits and UnSummits</b> <a href="http://summits.forgerock.com/" target="_blank">are coming to</a> <b>Sydney, London, and Paris!</b><o:p></o:p></p></div></div></div></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Mon, Jul 25, 2016 at 7:19 PM, Nancy Lush <<a href="mailto:nlush@lgisoftware.com" target="_blank">nlush@lgisoftware.com</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'>Hello all,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'>My sense is that we want to start with a simple example. Like, Alice can choose which resources she wants to share. Those can be from the list Debbie displayed today or the list I sent – or whatever the final list turns out to be. (The list can be changed later.) But that list is a list of ‘FHIR Resources’. Alice can choose to share either all, or she can specify which in the list she wishes to share. (I think this is consistent with Adrian’s most recent ‘b’ point.)</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'>While we can have resource sets, I don’t think we need to confuse the conversation with that yet.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'>Also, we have talked about confidentiality codes and the desire to have Alice share her conditions, but exclude her HIV condition. I think as a group we would like to be able to do that, but because it is confusing it takes us off track. Just temporarily, let’s skip that detail. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'>If we start with Alice’s ability to share the FHIR resources, we can work that through the more technical issues, and reach a point where we agree. We can then add additional detail on top of that.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'>As a group we all come from different places, often each of those very different places are technical in nature. As a result, one term can have different meanings to each individual. I think we are close. The next step would be to define the flow for this, then bring it back to the team for review.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'>-Nancy</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'> </span><o:p></o:p></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 style='border-collapse:collapse'><tr style='height:1.0pt'><td width=428 colspan=2 valign=top style='width:256.7pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt'><div style='border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%'><span style='font-size:8.0pt;line-height:115%;color:#1F4E79'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-line-height-alt:1.0pt'><span style='font-size:8.0pt;color:#1F4E79'> </span><o:p></o:p></p></td></tr><tr style='height:1.0pt'><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt;height:1.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-line-height-alt:1.0pt'><b><span style='font-size:10.0pt;color:#222A35'>Nancy Lush </span></b><o:p></o:p></p></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-line-height-alt:1.0pt'><span style='font-size:10.0pt;color:#1F4E79'><a href="mailto:nancy.lush@lgisoftware.com" target="_blank">nancy.lush@lgisoftware.com</a></span><o:p></o:p></p></td></tr><tr style='height:1.0pt'><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt;height:1.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-line-height-alt:1.0pt'><b><span style='font-size:10.0pt;color:#222A35'>Lush Group, Inc</span></b><o:p></o:p></p></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-line-height-alt:1.0pt'><span style='font-size:10.0pt;color:#1F4E79'>Office: <a href="tel:%28401%29%20423-9111" target="_blank">(401) 423-9111</a></span><o:p></o:p></p></td></tr><tr style='height:1.0pt'><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt;height:1.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%'><span style='font-size:10.0pt;line-height:115%;color:#1F4E79'>28 Narragansett Ave</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-line-height-alt:1.0pt'><span style='font-size:10.0pt;color:#1F4E79'>PO Box 651</span><o:p></o:p></p></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%'><span style='font-size:10.0pt;line-height:115%;color:#1F4E79'><a href="http://www.lgisoftware.com" target="_blank">www.lgisoftware.com</a> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-line-height-alt:1.0pt'><span style='font-size:10.0pt;color:#1F4E79'>Cell:<a href="tel:%28401%29%20965-9347" target="_blank">(401) 965-9347</a></span><o:p></o:p></p></td></tr><tr style='height:1.0pt'><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt;height:1.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-line-height-alt:1.0pt'><span style='font-size:10.0pt;color:#1F4E79'>Jamestown, RI 02835</span><o:p></o:p></p></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%'><span style='font-size:10.0pt;line-height:115%;color:#1F4E79'> </span><o:p></o:p></p></td></tr><tr><td width=428 colspan=2 valign=top style='width:256.7pt;padding:0in 5.75pt 0in 5.75pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:115%'><span style='font-size:10.0pt;line-height:115%;color:#1F4E79'><img border=0 width=153 height=50 id="_x0000_i1025" src="cid:image003.gif@01D1E763.24512010" alt="LGI_logo_small"></span><o:p></o:p></p></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=174 valign=top style='width:1.45in;padding:0in 5.75pt 0in 5.75pt'></td><td width=254 valign=top style='width:152.3pt;padding:0in 5.75pt 0in 5.75pt'></td></tr><tr><td width=428 colspan=2 valign=bottom style='width:256.7pt;padding:0in 5.75pt 0in 5.75pt'></td></tr></table><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F4E79'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>Openid-specs-heart mailing list<br><a href="mailto:Openid-specs-heart@lists.openid.net" target="_blank">Openid-specs-heart@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>Openid-specs-heart mailing list<br><a href="mailto:Openid-specs-heart@lists.openid.net" target="_blank">Openid-specs-heart@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a><o:p></o:p></p></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></body></html>