<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Steven,<div><br></div><div><blockquote type="cite"><span class="Apple-style-span" style="color: rgb(31, 73, 125); font-family: Calibri; font-size: 15px; ">Be interesting if anyone is looking into an online library to find this kind of stuff for OpenID? We don’t need 50 versions of “Role” or “FavouriteBook”. If no one has such a library yet I may do something on it.</span></blockquote><div><font class="Apple-style-span" color="#1F497D" face="Calibri" size="4"><span class="Apple-style-span" style="font-size: 15px;"><br></span></font></div></div><div>There were various half-hearted attempts at creating such a library for LDAP -- we called it a "schema registry" -- but it was never very successful. I think it'd be good to get a base list for the most common attributes, though. It might be useful for you to check out the way TERENA did some reconciliation for European Universities.</div><div><br></div><div><a href="http://www.terena.org/activities/tf-emc2/schac.html">http://www.terena.org/activities/tf-emc2/schac.html</a></div><div><br></div><div>SREG does this, but maybe not completely, and it's a separate spec as well. I think it should be revisited at some point.</div><div><br></div><div><blockquote type="cite"><span class="Apple-style-span" style="color: rgb(0, 0, 0); "><div style="margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span class="Apple-style-span" style="color: rgb(0, 0, 221); font-size: 12px; -webkit-text-stroke-width: -1; ">They were interested in how you could manage roles in that scenario too – after I explained to them to more user centric nature of openid, w.r.t to Athens.</span></div></span></blockquote></div><div><br></div><div>I'm of the opinion that universities will not manage many identifiers in the future once commercial/governmental services *that do good identity proofing* arise. I'm also of the opinion that universities will always manage attributes about their users for which they must remain authoritative and in control of the data: class enrollment, degrees, licensed under contract XYZ for content provider ABC, etc.</div><div><br></div><div>To reach these two goals, we need protocol fluency in our systems, and to solve attribute aggregation issues soon so we can express the union of "<a href="mailto:ndk@outsourcedID.org">ndk@outsourcedID.org</a>" + "is licensed through Double U. to download all your movies for free." That's a very real use case too, and a secret reason for my starting the other thread.</div><div><br></div><div>Thanks,</div><div>Nate.</div><div><div><br></div></div></body></html>