=== Successes ===

==== [[I3 User-Centric Identity Interop through RSA 2008]] ====

RSA Conference, San Francisco CA, April 7-11 2008

During the third OSIS Interop (I3), participants worked from late 2007 through RSA in April 2008 to test their solutions against each other and to test features of their implementations, with the goal of demonstrating interoperability both between OpenID and Information Card Systems and helping implementers improve their implementations. The Interop testing was performed online via public endpoints on the Internet, most of which remain up for ongoing interop testing.

* [http://www.rsaconference.com/2008/US/ RSA Conference]
* [http://www.rsaconference.com/2008/US/Highlights_and_Events/Interoperability_Demonstrations.aspx RSA Conference page for the Interop]
* [http://web3id.org/files/RSA%202008%20Handout/I3-Handout.jpg Printable Handout] printable 8-1/2 x 11 version with logos of all participants

==== [[I3a User-Centric Identity Interop at the 2nd European Identity Conference 2008 in Munich]] ====

I3a took place at the [https://www.kuppingercole.de/events/eic2008 European Identity Conference 2008], April 22-25, 2008. This event brought the results obtained in the [[I3 User-Centric Identity Interop through RSA 2008]] to the conference attendees and built upon them.

==== Summary ====
* I3: Two large events held at RSA 2008 in San Francisco and at EIC 2008 in Munich.
* Information Card Interoperability between multiple selectors, identity providers, and relying party sites
* OpenID Interoperability between Open ID providers, issued Open IDs, and relying sites.
* I3 Interoperability Test matrix - Pamela Dingle created an automated table generator that accelerated recording results and creating multiple table views.
* I3 Feature test cases with success/failure metrics, exception handling, and user features
* I3 handouts and banners were created.
* [http://groups.google.com/group/user-centric-identity-interop/web/user-centric-identity-interoperability I3 Overview]
* RSA 2008: OSIS secured a large room at RSA, and held two days of interoperability tests. There were 33 companies and 24 projects represented with over 1200 interoperability tests completed. During the two days, RSA attendees were able to meet with developers 1:1, as well as get an overview of the state of user-centric identity management. An [http://www.youtube.com/watch?v=edrcv-xUFtM introductory video] was created for orientation.
* Tests covered both the key interoperability requirements from several sources including I1 and I2 Higgins Project tests and Microsoft ISIP tests.

=== Issues and Resolutions ===
* It was immediately obvious to Identity Specialists that there were multiple interoperability/workshops at RSA, which gave an overtone confusion from mixed messages. At a summit meeting held with Roger Sullivan of the Liberty Alliance, Bill Washburn of the OpenID Foundation, Paul Trevithick and Mary Ruddy of the Higgins Project, Dale Olds, Charles Andres, and Mike Jones representing OSIS, there was consensus that at future industry events, coordination between organizations ahead of time would help insure consistent unifying marketing messages for the established standards and emerging technologies.
* Funding for such a large complicated event required much coordination, but in the end, the following companies participated in sponsoring the event: Microsoft, IBM, Novell, Parity Communications, Versign, Sun Microsystems, Oracle, TrustBearer, Computer Associates, and ooTao.

=== Requests ===
* 2009 Interops to be held with advance communication and collaboration with Information Card Foundation, OpenID Foundation, Concordia, Liberty Alliance, and other groups concerned with data portabilty, open web, where identity management systems are an essential part of the underlying infrastructure.

=== Announcements ===
I4: The next interop event: [http://conference.digitalidworld.com/2008/ Digital ID World (DIDW) Conference], September 8-10, 2008, Anaheim, CA,

* over [http://osis.idcommons.net/wiki/Category:Participant 50 companies and projects] participated in testing over 80 [http://osis.idcommons.net/wiki/Category:I4_Solutions software solutions] with [http://osis.idcommons.net/wiki/Category:I4_Features hundreds of interoperability test cases].

* [[2008_Q3_Report_OSIS]]
* [[2008_Q1_Report_OSIS]]

2008 Q2 Report OSIS

2008-12-10T15:26:15Z

Candres: /* Announcements */

2008-11-05T15:42:22Z

Candres: /* TECHNOLOGY - STANDARDS, INTEROP and CODE */

== COMMUNITY ==

[[Identity_Gang|'''The Identity Gang''']] [[Identity_Gang_Charter|''Charter'']] - mailing list for the digital identity community. The gang, formed in 2004, also collaboratively developed a lexicon related to digital identity technologies and issues. The active mailing list has over 500 members - to avoid spam registration is required. [http://groups.google.com/group/idworkshop mailing list].

[http://iiw.idcommons.net/ '''Internet Identity Workshop'''] [[Internet_Identity_Workshop_Charter|''Charter'']] supports face to face conversation about internet-wide digital identity and it's implications. User-centric identity has been a topic of particular interest. This twice a year event aims to support the whole marketplace, especially individuals contributing their voice in open inclusive conversation. These events have a reputation of being incredibly effective for getting real work done and moving the industry forward.

[[Newbies4Newbies|'''Newbies 4 Newbies''']] [[Newbies4Newbies_Charter|''Charter'']] - This working group was formed at the Dec 2007 Internet Identity Workshop to support by a group of "newbies" to connect with their peers who were inspired by the community but wanted to make sure documentation and material about the topics in the community were more accessible. They have regular conference calls and are working on the development of the [[Starting Points]] page.

== BUSINESS ==
'''[http://projectvrm.org/ VRM (Vendor Relationship Management)]''' [[VRM_Charter|''Charter'']] This group grew out of Doc Searls original 'rental car use case' put forward at Digital Identity World 2004. VRM, or Vendor Relationship Management, is the reciprocal of CRM or Customer Relationship Management. It provides customers with tools for engaging with vendors in ways that work for both parties. Project VRM is currently under [http://cyber.law.harvard.edu/ Berkman Center for Internet and Society at Harvard Law]. Participants are working to create the ecosystem of tools, protocols, and services that help users manage vendor relationships. It has five committees, ,Vision, Standards, Organization, Usage and Compliance. There are several active mailing lists, [http://blogs.law.harvard.edu/vrm a blog], regular conference calls and an community of software vendors working on building standards based tools to make it real.

== TECHNOLOGY - STANDARDS, INTEROP and CODE ==

'''[http://www.informationcard.net Information Card Foundation]''' [[Information Card Foundation Charter|''Charter'']] Advance the use of the Information Card metaphor as a key component of an open, interoperable, royalty-free, user-centric identity layer spanning both the enterprise and the Internet. A 501c(6) trade association, ICF is open to any individual or organization. Community members comprise the majority of the Board of Directors. Current Community members are active participants in Identity Commons, Information Cards, Open ID, OSIS for interoperability, Concordia, The Higgins Project, Microsoft CardSpace, the Bandit Project, The Pamela Project, Identity Schemas, and XDI.

'''[http://www.openid.net/ OpenID]''' [[OpenID_Charter|''Charter'']] The purpose is to advance development, implemention, and adoption of the OpenID framework of specifications for user-centric identity. This working group is organized as a 501c3 non-profit corporation. The group is open to any individual or organization interested in the advancement of OpenID. Specifications and open source code are maintained by meritocracy.

'''[http://osis.idcommons.net/wiki/Main_Page OSIS (Open Source Identity Systems)]''' [[OsisCharter|''Charter'']] OSIS brings together many identity-related open-source projects, and synchronizes and harmonizes the construction of an interoperable identity layer for the internet from open-source parts. Its first deliverable is interoperability with Microsoft CardSpace, although OSIS also encompasses alternate technologies such as OpenID and SAML.

This is one of the most active groups in making the metasystem vision come alive and has participation from a range of [http://osis.idcommons.net/wiki/Category:Participant both big and little technology vendors]. They are having their third major [http://osis.idcommons.net/wiki/I3_User-Centric_Identity_Interop_through_RSA_2008 Interop Event with over 200 tests through to the RSA Conference in April 2008].

'''[[Identity Schemas]]''' [[Identity_Schemas_Charter|''Charter'']] To promote interoperability between identity systems by making it easier to find, understand, and reuse the semantics of identity attributes defined in existing schemas. They have clearly articulated the [http://wiki.idcommons.net/index.php/Problem_Space problem space] and [http://wiki.idcommons.net/index.php/Deliverables deliverables] to address it. There is an active mailing list and face to face meetings happen at events like the Internet Identity Workshop and Data Sharing Summit.

'''[http://eclipse.org/higgins Higgins Project]''' [[Higgins_Project_Charter|''Charter'']] Higgins is an open source identity framework. Higgins is a framework that enables users and applications to integrate identity, profile, and relationship information across multiple data sources and protocols. End-users can experience Higgins through the UI metaphor of Information Cards.

'''SAML Commons''' [[SAML_Commons_Charter|''Charter'']] The purpose of this working group is to advance development, implemention, and adoption of SAML, in particular by producing SAML profiles that enable its use with other technologies such as XRI, OpenID, etc.

'''XDI Commons''' [[XDI_Commons_Charter|''Charter'']] The purpose of this working group is to advance practical deployment, usage, and best practices for the [http://en.wikipedia.org/wiki/XDI XDI (XRI Data Interchange)] protocol under development by the [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee].

'''[http://www.pamelaproject.com/ Pamela Project]''' [[Pamela_Project_Charter|''Charter'']] The Pamela Project exists to information-card enable popular open source web frameworks, with the goal of allowing administrators to install rather than code information card support into their sites. It also is working to make it easier for people of all skill levels to understand and use this technology.

== SOCIAL / LEGAL / POLICY ==

'''[[ID-Legal]]''' [[ID-Legal_Charter|''Charter'']] This group was formed at the 2008a IIW - at a session wondering what it would be like to have a conference that was 1/3 lawyers and 1/3 techies in identity and 1/3 other people. It is working on organizing a conference for mid 2009. There is a mailing list you can join.

'''[[Kids Online]]''' [[Kids_Online_Charter|''Charter'']] is focused on developing best practices around kids safey online while not loosing sight of the fact that they are kids and want to have fun there too. The group primarily meets face to face and is having its first conference November 13, 2008.

'''[http://www.xdi.org/ XDI.org]''' [[XDI_Org_Charter|''Charter'']] - The purpose of this working group is to provide community governance of open public infrastructure based on the XRI & XDI standards.

'''[[Identity_Futures|ID Futures]]''' [[IdFutures_Charter|''Charter'']] The Purpose of the Identity Futures Group is to engage in interactive (shallower) and indepth consideration of potential future events and scenarios for an identity layer of the web. The first step in this was at Digital Identity World 2007 where we developed [[Identity_Futures|50 future identity related events]] and mapped them. More scenario development and planning is being coordinated.

'''[[IdMedia|ID Media Review Group]]''' [[IdMedia_Charter|''Charter'']] ''"The Book Club"'' is here to support the Identity Commons community engaging with books, movies and other media that cover identity related topics. We do this by [http://wiki.idcommons.net/index.php/Identity_Bibliography collecting a bibliography] and by reviewing and discussing these media. We use the issues raised by these works to inform our work innovating the identity layer of the web and help us understand and address the social, psychological, legal, privacy, security, regulatory and ethical issues. [[Identity_Bibliography|The bibliography is growing]] and further collaboration is planned to engage with these works.

'''[[Photo Group]]''' [[Photo_Group_Charter|''Charter'']] - The photo group aims to serve as a community hub for identerati with interests in photography, as a gallery in which identity community photographers can display their work, and as a resource for people looking for photographs which illustrate aspects of identity.

== IC Operations ==

Identity Commons has at its core a stewards council. Groups within the commons support the operations of the commons.

'''[[IC Evangelism & Marketing]]''' ''[[IC_Evangelism_%26_Marketing_Charter|Charter]]''
Provide content that will help Identity Commons, its member groups, and individuals more effectively communicate the goals, principles, and messages of Identity Commons. Assist in any evangelism efforts to bring appropriate working groups and individuals to become Identity Commons members.

Stewards Council Telecon: 2008 November 5

2008-11-02T23:58:40Z

Candres: /* Agenda */

2008 Q3 Report Information Card Foundation

2008-10-31T21:38:59Z

Candres: /* Requests */

=== Successes ===
* Information Card Foundation has grown to more than 50 members.
* The Board of Directors was expanded to include Deutsche Telekom and Intel
* In September 2 new Community Members were nominated by the Board and elected by the entire membership. The vote was done using Helios, a new electronic voting system that is verifiable and anonymous. The two new members are:
** Craig Burton
** Scott Loftesness

* The following working groups were formed, approved, and are now active:
** OASIS Coordination Working Group -- coordinates efforts between ICF and OASIS Technical Committees working on standards affecting information cards. This includes the SSTC and IMI TC
** RP Evangelists Working Group -- Promoting information card adoption to relying party sites
** Browser Integration Working Group --
** Website Best Practices Working Group -- focusing on getting a consistent ceremony for users at all sites regardless of the user's state (do they have a selector? have they been to the site before? Is the site issuing a card? asking for claims? etc.)
** Schemas Working Group -- defining a lightweight human and machine-readable claim and data type to ensure that like claims are treated the same by the entire information card ecosystem.

* Information Card Foundation was prominent at DIDW by:
** sponsoring the OSIS Interop
** having a booth on the floor of the show
** participating in 11 sessions, either run by, staffed by, or participated in by ICF members

* Information Card Foundation is promoting a discussion with Identity Commons for a common unified marketing message to minimize marketplace confusion between various identity systems and methods.

=== Breakdowns ===

=== Requests ===
* Identity Commons is the place for a common unified marketing message to be agreed upon. see [[Unified_Messaging_Charter]]
Please feel free to contribute to [[Unified_Messaging_Wiki]]

=== Announcements ===

2008 Q3 Report Information Card Foundation

2008-10-31T21:37:52Z

Candres: /* Requests */

2008 Q3 Report Information Card Foundation

2008-10-31T21:37:27Z

Candres: /* Requests */

2008-10-11T06:12:14Z

Candres:

Why Identity Commons:
- company neutral
- wisdom of the crowd
- too important not to get this right
- systems that control personal data (identity information) is the stickiest of all software.

----

'''How do we get to a Common Message?'''

Best Practices: Emulate Abraham Lincoln. ref. "Team of Rivals" (Doris Kearns Goodwin)
Before making a decision, Lincoln insisted on vigorous debate and discussion. His abiity
to tolerate dissent was an enormous asset. Any individual expert is likely to be wrong.
The average of the experts' predictions often outperforms the individuals from whom the
average is derived. See: "The Wisdom of Crowds" (James Surowiecki)."If you have impressive
academic credentials and/or an impressive amount of experience, you should be alert to the
possibility that you could still be profoundly wrong." Foxes approach problems from
multiple viewpoints. Hedgehogs are more ideological, draw conclusions from a single
overarching theory, and make more mistakes. "The fox knows many things, but the hedgehog
knows one big thing" Isaiah Berlin. Overspecialization leads to a community of hedgehogs.

[[PROBLEMS - USE CASES]]

'''General Principles'''
* vast diverse ecosystem:
** needs are highly varied,
** no business or government agency can be trusted with a centralized system
* too much concentration of power leads to,
** a non-competitive environment,
** stratified system,
** unable to cope with various new electronic communications mechanisms,

'''The fundamental importance of personal data to control citizens, customers, users.'''
* Social interactions, politics, economics, and business depend on trust.
* data protection is necessary for accountability; and accountability is necessary for trust.

'''Unless law and technology are crafted to respect certain “Properties of Identity”,

''there is no data protection; and if there is no data protection,
''
''there is no accountability; and if there is no accountability,
''
''there is no trust.''

''Balancing two different notions:''
- Identity is personal and cannot be centralized
- Centralized systems cannot keep up with change
- Walled gardens and data silos are necessary for proprietary companies

- digital media is profoundly different from physical media -- it is infinitely malleable, divisible
- identity data must be taken within a greater context.

Identity ecosystem (metasystem) is not a system, but a way of ensuring authorization, accountability, and trust in the digital ecosystem.
* the identity ecosystem needs to handle a broad range of security requirements (from light to heavy)
* each person (user) has to be involved in decisions within the ecosystem, although they are not always the only decision maker (example of unconscious in a foreign hospital) risk assessment for hospital to protect itself -- all claims are made by a user.
* ecosystem includes all business databases (controlled by a business, assigned to a transactor)
* legal contracts -- liability transfer, deals made between parties, setting up relationship between business entities, between businesses and customers, between government service organizations and citizens.
* ease of use -- both for consistent ceremonies (to both set expectations and minimize phishing/pharming) is part of the ecosystem
** security (data protection) is part of the ecosystem:
** setting appropriate security and authorization levels for transaction types
** encompassing both high and low (security) levels appropriate for the transaction (blogging to money transfer)
** enough to make verifying claims made to dynamically assess risk

Digital communication and media trends
- - cheaper (move from human-intensive operations to heuristic software, business process routines migrate to automated services -- need to get the automation right -- scheduling, exception handling has to be part of this.
- - ubiquitous
- - improving heuristics, automated condition and exception handling
- - moving toward mutually beneficial relationships between transactors -- B2B (heavy, expensive relationships) moving toward B2C (B2B services priced low enough to provide with all customers)

Market Positioning statements
- education for customers making buying, deployment, workflow design along with state of the art as the ecosystem matures
- For 2009, positioning statements on each type of element in the identity metasystem.
-- What they are (link)
-- Their current status
-- State of the art for:
- security
- biometrics
- interoperable exchange mechanisms
- applicable standards and those in process
-

=== Target Audience: ===

** Decision makers. (Advice for making good decisions)
What they need to know:

-- What are they trying to solve

-- Their current state of the business

-- What the technical, social, legal, trends are,
''and the factors that govern the rate of change in each
''

'''So they can assess:'''
* What does their business look like in the future
* What should they do now, what should be done later (and why wait/act now)
* What products can address their requirements now and the associated architectural decisions for:
* IT infrastructure
* Business Processes
* Integration with legacy systems
* What to adopt and when to adopt it
* Specific requirements for any system

'''RISK ASSESSMENT'''
* risk assessment ratio at all points in a transaction
** who: is asking for access, am I dealing with?
* how accountable am I to ensure I know?
** difficulty to crack
** track record
** probability factors
** good data
** timeliness

'''Business'''
- type
- scale

'''per communication media type'''
- skype
- cell
- internet
-- amount right / errors

'''Products - what is interoperable and how they fit together'''''Italic text''

== Philosophy ==
- Magna Carta
- U.S. Constitution
- Seven Laws of Identity
- OECD international Principles of Identity

= Technology =

------------------------Best uses:

* User-centric

* Federated

* Enterprise Role Management

* Identity Management Systems

* Access Manager

Where data should live (and where it shouldn't)

Objective statements on the following:
relative to strengths/weakenesses
ability to interoperate
degree of security spectrum coverage
ease of use
maturity
development environment (tools, etc.)
certification
legal maturity
platform coverage
- operating systems
- browsers
- mobile devices
- PCs
- Enterprise systems

Problems addressable

Problems addressed

Check off sheet for specific features, relative issues, state of the art

Areas of research and development

= Open ID =
- primary uses
- position on security scale
- major movers
- issues
- number of users
- number of sites
-

= SAML =
- primary uses
- position on security scale
- major movers
- issues
- number of users
- number of sites
-
= LDAP

= OpenSSO =

= information card =
infocard
I-card

Selector
Cardspace
Bandit
Higgins

= Data Portability =

What works with what

Interoperability levels

== Claims ==
- the first 14
- the universe of 2500
- level of common agreement
- work on definitions and schemas

=== Security ===
- types
-
[[Glossary, Tautology, Ontology]]

Low risk, high probability of being correct
credit score

Unified Messaging Wiki

2008-10-11T06:11:14Z

Candres:

Why Identity Commons:
- company neutral
- wisdom of the crowd
- too important not to get this right
- systems that control personal data (identity information) is the stickiest of all software.

----

'''How do we get to a Common Message?'''

Best Practices: Emulate Abraham Lincoln. ref. "Team of Rivals" (Doris Kearns Goodwin)
Before making a decision, Lincoln insisted on vigorous debate and discussion. His abiity
to tolerate dissent was an enormous asset. Any individual expert is likely to be wrong.
The average of the experts' predictions often outperforms the individuals from whom the
average is derived. See: "The Wisdom of Crowds" (James Surowiecki)."If you have impressive
academic credentials and/or an impressive amount of experience, you should be alert to the
possibility that you could still be profoundly wrong." Foxes approach problems from
multiple viewpoints. Hedgehogs are more ideological, draw conclusions from a single
overarching theory, and make more mistakes. "The fox knows many things, but the hedgehog
knows one big thing" Isaiah Berlin. Overspecialization leads to a community of hedgehogs.

[[PROBLEMS - USE CASES]]

'''General Principles'''
* vast diverse ecosystem:
** needs are highly varied,
** no business or government agency can be trusted with a centralized system
* too much concentration of power leads to,
** a non-competitive environment,
** stratified system,
** unable to cope with various new electronic communications mechanisms,

'''The fundamental importance of personal data to control citizens, customers, users.'''
* Social interactions, politics, economics, and business depend on trust.
* data protection is necessary for accountability; and accountability is necessary for trust.

'''Unless law and technology are crafted to respect certain “Properties of Identity”,

''there is no data protection; and if there is no data protection,
''
''there is no accountability; and if there is no accountability,
''
''there is no trust.''

''Balancing two different notions:''
- Identity is personal and cannot be centralized
- Centralized systems cannot keep up with change
- Walled gardens and data silos are necessary for proprietary companies

- digital media is profoundly different from physical media -- it is infinitely malleable, divisible
- identity data must be taken within a greater context.

Identity ecosystem (metasystem) is not a system, but a way of ensuring authorization, accountability, and trust in the digital ecosystem.
* the identity ecosystem needs to handle a broad range of security requirements (from light to heavy)
* each person (user) has to be involved in decisions within the ecosystem, although they are not always the only decision maker (example of unconscious in a foreign hospital) risk assessment for hospital to protect itself -- all claims are made by a user. User is defined as anyone to whom personal data (attributes, claims made) are either attributed to (i.e. birthdate, name, location) or privileges granted (HR manager, access to databases, business transactor, authorized member)
* ecosystem includes all business databases (controlled by a business, assigned to a transactor)
* legal contracts -- liability transfer, deals made between parties, setting up relationship between business entities, between businesses and customers, between government service organizations and citizens.
* ease of use -- both for consistent ceremonies (to both set expectations and minimize phishing/pharming) is part of the ecosystem
** security (data protection) is part of the ecosystem:
** setting appropriate security and authorization levels for transaction types
** encompassing both high and low (security) levels appropriate for the transaction (blogging to money transfer)
** enough to make verifying claims made to dynamically assess risk

Digital communication and media trends
- - cheaper (move from human-intensive operations to heuristic software, business process routines migrate to automated services -- need to get the automation right -- scheduling, exception handling has to be part of this.
- - ubiquitous
- - improving heuristics, automated condition and exception handling
- - moving toward mutually beneficial relationships between transactors -- B2B (heavy, expensive relationships) moving toward B2C (B2B services priced low enough to provide with all customers)

Market Positioning statements
- education for customers making buying, deployment, workflow design along with state of the art as the ecosystem matures
- For 2009, positioning statements on each type of element in the identity metasystem.
-- What they are (link)
-- Their current status
-- State of the art for:
- security
- biometrics
- interoperable exchange mechanisms
- applicable standards and those in process
-

=== Target Audience: ===

** Decision makers. (Advice for making good decisions)
What they need to know:

-- What are they trying to solve

-- Their current state of the business

-- What the technical, social, legal, trends are,
''and the factors that govern the rate of change in each
''

'''So they can assess:'''
* What does their business look like in the future
* What should they do now, what should be done later (and why wait/act now)
* What products can address their requirements now and the associated architectural decisions for:
* IT infrastructure
* Business Processes
* Integration with legacy systems
* What to adopt and when to adopt it
* Specific requirements for any system

'''RISK ASSESSMENT'''
* risk assessment ratio at all points in a transaction
** who: is asking for access, am I dealing with?
* how accountable am I to ensure I know?
** difficulty to crack
** track record
** probability factors
** good data
** timeliness

'''Business'''
- type
- scale

'''per communication media type'''
- skype
- cell
- internet
-- amount right / errors

'''Products - what is interoperable and how they fit together'''''Italic text''

== Philosophy ==
- Magna Carta
- U.S. Constitution
- Seven Laws of Identity
- OECD international Principles of Identity

= Technology =

------------------------Best uses:

* User-centric

* Federated

* Enterprise Role Management

* Identity Management Systems

* Access Manager

Where data should live (and where it shouldn't)

Objective statements on the following:
relative to strengths/weakenesses
ability to interoperate
degree of security spectrum coverage
ease of use
maturity
development environment (tools, etc.)
certification
legal maturity
platform coverage
- operating systems
- browsers
- mobile devices
- PCs
- Enterprise systems

Problems addressable

Problems addressed

Check off sheet for specific features, relative issues, state of the art

Areas of research and development

= Open ID =
- primary uses
- position on security scale
- major movers
- issues
- number of users
- number of sites
-

= SAML =
- primary uses
- position on security scale
- major movers
- issues
- number of users
- number of sites
-
= LDAP

= OpenSSO =

= information card =
infocard
I-card

Selector
Cardspace
Bandit
Higgins

= Data Portability =

What works with what

Interoperability levels

== Claims ==
- the first 14
- the universe of 2500
- level of common agreement
- work on definitions and schemas

=== Security ===
- types
-
[[Glossary, Tautology, Ontology]]

Low risk, high probability of being correct
credit score