[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[higgins-dev] Higgins and OSIS
|
These are just some notes related to my section of the Ear-to-Ear developer meeting today. It's not very usable on it's own, but may help in conjunction with the discussion.
1. Status of OSIS.
For history and current state see:
http://mailman.netmesh.us/pipermail/osis-general/2006-September/000162.html
http://mailman.netmesh.us/pipermail/osis-general/
http://osis.netmesh.org/wiki/Main_Page
OSIS is a working group of the reconstituted identity commons:
http://wiki.idcommons.net/moin.cgi/OsisCharter
http://wiki.idcommons.net
2. OSIS next steps:
focus on infocard interop of various endpoint implementations
work with idcommons as it evolves
3. OSIS attempting to coordinate interop with multiple STS's, selectors, IdPs, etc.. Known implementations Higgins, Heraldry (stated direction), whobar, openSSO, ping's STS, MS's stuff
4. Role of Higgins:
Legal - projects must handle their own legal agreements since they actually distribute IP, but would be helpful to work with OSIS for combined response to MS. Mary is providing bulk of input here.
OSIS agreements designates Higgins as main project for the selector -- what about others? (xmldap, and safari derivative...)
5. Possible overlap? Deployment diagram and use cases for milestone 6, ISS interop with Mike's STS, etc., and interactions with OSIS
--Dale
