<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">Hi James<DIV><BR class="khtml-block-placeholder"></DIV><DIV>As Phillip states, SAML can be used to represent the assertion.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Interesting that you mention a Doctor example. A use case that we are working on uses a Surgeon (Sally) who needs to prove:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>- Tthe College of Physicians and Surgeons says she is a surgeon</DIV><DIV>- A particular hospital says she is part of their team</DIV><DIV>- The university says she is part of their faculty</DIV><DIV>- the government says she is the business owner of her surgical practice</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>With OpenID, each of these authorities could make a claim about Sally's OpenID. This could be expressed as a SAML assertion.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>When accessing a resource that requires one of Sally's verified attributes, Sally (using her OP) proves she is a specific OpenID Idenitifier and also provides the SAML assertion(s) that prove that identifier has been verified to belong to a surgeon, team member, faculty member, business owner.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>We have created an example for something anyone on the net can have verified, their email address. I'll post separately about that.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>-- Dick</DIV><DIV><BR><DIV><DIV>On 18-Jan-07, at 8:51 AM, McGovern, James F ((HTSC, IT)) wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P><FONT size="2" face="Arial">I would love to see folks hear that also blog not only continue to discuss federated identity but also consider of the course of several additional postings also talk about the need for federated authorization. Consider an example where a Doctor in a hospital is having an electronic interaction with a healthcare insurance provider. The hospital should be the identity provider while the entity that licensed the Doctor for given sets of practices should be responsible for certain forms of authorization.</FONT></P><P><FONT size="2" face="Arial">If we only talk about identity without authorization, the conversation will result in lots of great software where folks who create them won't make any money since consumer-centric interactions have volume without corresponding revenue. </FONT></P> <FONT size="3"><BR> <BR> *************************************************************************<BR> This communication, including attachments, is<BR> for the exclusive use of addressee and may contain proprietary,<BR> confidential and/or privileged information. If you are not the intended<BR> recipient, any use, copying, disclosure, dissemination or distribution is<BR> strictly prohibited. If you are not the intended recipient, please notify<BR> the sender immediately by return e-mail, delete this communication and<BR> destroy all copies.<BR> *************************************************************************<BR> </FONT><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">specs mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:specs@openid.net">specs@openid.net</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="http://openid.net/mailman/listinfo/specs">http://openid.net/mailman/listinfo/specs</A></DIV> </BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>