<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:Cambria;
panose-1:2 4 5 3 5 4 6 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;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Cambria",serif;
color:#44546A;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.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:14.0pt;font-family:"Cambria",serif;color:#44546A">I need Eva to verify that what I am saying is correct, I am still coming up to speed on UMA … HL7 has/is developing FHIR consent(contract) standards and I believe
the oAuth and UMA profiles are in scope to support these and possibly others. <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Cambria",serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Cambria",serif;color:#44546A">To easily support interoperability, is it possible (or in scope) to develop profile standards or profile taxonomy that would be flexible and adaptable so that the
RS would be able to process FHIR consents even if they are modified by a specific implementation without special coding. This could be too idealistic, out of scope or just not supportable with oAuth and/or UMA profiles.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Cambria",serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Cambria",serif;color:#44546A">For example: A client could connect to any FHIR resource and process any Heart Profile that is provided, even if the client is another RS running in a “Client” role
to another RS .<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Cambria",serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Cambria",serif;color:#44546A">Bill<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Cambria",serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Eve Maler [mailto:eve.maler@forgerock.com]
<br>
<b>Sent:</b> Tuesday, July 07, 2015 10:00 PM<br>
<b>To:</b> Aaron Seib<br>
<b>Cc:</b> Kinsley, William; openid-specs-heart@lists.openid.net<br>
<b>Subject:</b> Re: [Openid-specs-heart] Flip the question of “Vanilla" OAuth vs. UMA<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Commenting on one of Aaron's bulleted items:<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Profiling "a standard way to label assets managed by the RS" is one of the tasks I was contemplating to be potentially in scope for our semantic UMA profile. This is because it is possible for resource set descriptions (these are things
that an UMA RS registers at an AS, to put resources under protection) to include resource types. As I understand it, the FHIR API conveys data structures that reflect quite a lot of HL7 standardization work already done, which amounts to "resource typing".<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">While a lot of companies with proprietary APIs might not want to standardize their resource assets, there's a lot of power in standardized resource labeling in open ecosystems like the one we're working on. For starters, there's a
<a href="https://docs.kantarainitiative.org/uma/rec-oauth-resource-reg-v1_0.html#rfc.section.4">
security consideration</a> that is mitigated by the use of "well-known and standardized" description elements. (See this <a href="https://github.com/xmlgrrl/UMA-Specifications/issues/151">UMA issue</a> for some background.) For another example, standard types
could drive automated policy workflows in interesting ways.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<p><b>Eve Maler<br>
</b>ForgeRock Office of the CTO | VP Innovation & Emerging Technology<br>
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl<br>
Join our <a href="http://forgerock.org/openuma/" target="_blank">ForgeRock.org OpenUMA</a> community!<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Jul 7, 2015 at 2:56 PM, Aaron Seib <<a href="mailto:aaron.seib@nate-trust.org" target="_blank">aaron.seib@nate-trust.org</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks for starting this new thread.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I am not expert in this space (yet) but let me see if I can repeat back what I think you are proposing.
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Are you suggesting that for Resource Server (RS) be able to accept a standard profile authorization
assertion (based on the UMA profile) from a standard (UMA-based) Authorization Server (AS)?
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I maybe out of date but I seem to remember reading that the UMA profile states that the Authorization
Policy service capabilities (as required to implement an AS) are out of scope for the UMA profile - as are the specific policies for how you label assets (network, applications, data) managed by the RS with access tokens that are registered with and managed
by the AS. </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">To echo back your language is your suggestion that
</span><span style="font-size:14.0pt;font-family:"Cambria",serif;background:yellow">it</span><span style="font-size:14.0pt;font-family:"Cambria",serif"> ^would^
<span style="background:yellow">be simpler to have consistent patterns (libraries) implemented</span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> that would address what the UMA profile has intentionally said is out
of scope? I.e., </span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">addressing the need for a standard way to label assets managed by the RS; and (?)
</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">a standard way to represent the inputs to an Authorization Policy Service</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">In my mind this would allow us to not only solve the simple cases but also enable us to develop libraries
that represent the applicable policy of a given Federal Reg or libraries of applicable state law that could be re-used by everyone. It might also enable the different associations to provide recommended policies to be adopted by their members and plugged
into the solution following a period of local policy tweaking by a given institution or Agency.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Am I getting this right?</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Aaron Seib, CEO</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">@CaptBlueButton
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> (o)
<a href="tel:301-540-2311" target="_blank">301-540-2311</a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">(m)
<a href="tel:301-326-6843" target="_blank">301-326-6843</a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="http://nate-trust.org" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;text-decoration:none"><img border="0" width="205" height="48" id="_x0000_i1025" src="cid:image001.jpg@01D0B96A.2D63C6D0"></span></a><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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:<a href="mailto:openid-specs-heart-bounces@lists.openid.net" target="_blank">openid-specs-heart-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>Kinsley, William<br>
<b>Sent:</b> Monday, July 06, 2015 8:45 PM<br>
<b>To:</b> <a href="mailto:openid-specs-heart@lists.openid.net" target="_blank">openid-specs-heart@lists.openid.net</a><br>
<b>Subject:</b> [Openid-specs-heart] Flip the question of “Vanilla" OAuth vs. UMA</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif">I am starting a new thread … I think we need to flip the question of “Vanilla" OAuth vs. UMA”. I feel confident that
we are going to discover use cases that cannot be supported by “Vanilla” OAuth or would be greatly simplified by using UMA.
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif">Maybe the real question to ask is: Are there any augments (use case, technology restriction, cost, etc.) that justifies
NOT using (requiring) UMA?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif">From a interoperability, quality, security and development perspective, would it be simpler to have consistent patterns
(libraries) implemented that are more likely to be “drop-in compatible” without source changes. While the standard itself would be considered rigid, it would be flexible by the use and implementation of the UMA profiles.
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif">The caveat here is the resource server (RS) would need to be able to accept/process a UMA profile without developing custom
code to interpret it. Would this require resource servers to adhere to a standard set of UMA profiles or a defined UMA profile taxonomy that could describe the healthcare consent models (if one exists)?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif">Bill</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div style="margin-top:6.7pt;margin-bottom:6.7pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<table class="MsoNormalTable" border="0" cellspacing="3" cellpadding="0" width="894" style="width:670.45pt;margin-left:5.4pt">
<tbody>
<tr style="height:26.25pt">
<td style="padding:.75pt .75pt .75pt .75pt;height:26.25pt">
<p class="MsoNormal" align="right" style="mso-margin-top-alt:auto;margin-bottom:6.7pt;text-align:right">
<span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt;height:26.25pt">
<p class="MsoNormal" align="right" style="mso-margin-top-alt:auto;margin-bottom:6.7pt;text-align:right">
<o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif"> </span><o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="3" cellpadding="0" width="894" style="width:670.45pt;margin-left:5.4pt">
<tbody>
<tr>
<td style="padding:.75pt 9.85pt .75pt 9.85pt"></td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:14.0pt;font-family:"Cambria",serif"> </span><o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="3" cellpadding="0" width="894" style="width:670.45pt;margin-left:5.4pt">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:6.7pt"><b><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">William Kinsley<br>
</span></b><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Enterprise Architect, Ambulatory</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:6.7pt"><b><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">NEXTGEN HEALTHCARE<br>
</span></b><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Solutions for: Ambulatory, Inpatient and Community Connectivity<br>
795 Horsham Road, Horsham, PA 19044<br>
<a href="tel:%28215%29%20657-7010%20x21128" target="_blank">(215) 657-7010 x21128</a> [o] <br>
<a href="mailto:BKinsley@nextgen.com" target="_blank">BKinsley@nextgen.com</a></span><o:p></o:p></p>
</div>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:6.7pt"><span style="font-family:"Arial",sans-serif;color:blue"><a href="http://www.oneugm.com" target="_blank"><span style="font-family:"Times New Roman",serif;color:windowtext;text-decoration:none"><o:p></o:p></span></a></span></p>
</td>
</tr>
</tbody>
</table>
<div style="margin-top:6.7pt;margin-bottom:6.7pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif"><a href="http://www.oneugm.com" target="_blank"><span style="color:windowtext;text-decoration:none"> </span><span style="font-family:"Times New Roman",serif;color:windowtext;text-decoration:none"><o:p></o:p></span></a></span></p>
</div>
<table class="MsoNormalTable" border="0" cellspacing="3" cellpadding="0" width="650" style="width:487.5pt;margin-left:5.4pt">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:6.7pt"><b><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#E46C0A"><a href="http://www.oneugm.com" target="_blank"><span style="color:#E46C0A;text-decoration:none">Be
ready for MU and ICD-10 in 2015. Start your EHR version 5.8 and KBM version 8.3 upgrade today. Get the resources you need at
</span><span style="color:#E46C0A;font-weight:normal;font-style:normal;text-decoration:none"><b><i><u><span style="color:#007CB9">www.nextgen.com/upgradecentral</span></u></i></b></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:windowtext;font-weight:normal;font-style:normal;text-decoration:none"><o:p></o:p></span></a></span></i></b></p>
</td>
</tr>
</tbody>
</table>
<div style="margin-top:6.7pt;margin-bottom:6.7pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif"><a href="http://www.oneugm.com" target="_blank"><span style="color:windowtext;text-decoration:none"> </span><span style="font-family:"Times New Roman",serif;color:windowtext;text-decoration:none"><o:p></o:p></span></a></span></p>
</div>
<table class="MsoNormalTable" border="0" cellspacing="3" cellpadding="0" width="656" style="width:492.0pt;margin-left:5.4pt">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:6.7pt"><span style="font-size:6.0pt;font-family:"Arial",sans-serif"><a href="http://www.oneugm.com" target="_blank"><span style="color:windowtext;text-decoration:none">This message, and any documents
attached hereto, may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering
it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete
the original message and any copies immediately thereafter. Thank you for your cooperation.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:windowtext;text-decoration:none"><o:p></o:p></span></a></span></p>
</td>
</tr>
</tbody>
</table>
<div style="margin-top:6.7pt;margin-bottom:6.7pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif"><a href="http://www.oneugm.com" target="_blank"><span style="color:windowtext;text-decoration:none"> </span><span style="font-family:"Times New Roman",serif;color:windowtext;text-decoration:none"><o:p></o:p></span></a></span></p>
</div>
<div style="margin-top:6.7pt;margin-bottom:6.7pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif"><a href="http://www.oneugm.com" target="_blank"><span style="color:windowtext;text-decoration:none"> </span><span style="font-family:"Times New Roman",serif;color:windowtext;text-decoration:none"><o:p></o:p></span></a></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><a href="http://www.oneugm.com" target="_blank"><span style="color:windowtext;text-decoration:none"><br>
_______________________________________________<br>
Openid-specs-heart mailing list<br>
<u><span style="color:blue">Openid-specs-heart@lists.openid.net</span></u><br>
<u><span style="color:blue">http://lists.openid.net/mailman/listinfo/openid-specs-heart</span></u><o:p></o:p></span></a></p>
</blockquote>
</div>
<p class="MsoNormal"><a href="http://www.oneugm.com" target="_blank"><span style="color:windowtext;text-decoration:none"><o:p> </o:p></span></a></p>
</div>
</div>
</body>
</html>