2004 Previous << History of Digital Identity 2005 >> Next....

TYPE: [MEMBERSHIP ORGANIZATION] idCommons
DESCRIPTION: A member-owned international federation that empowers individuals and organizations to own, control and share their online identity and profile information in an environment of mutual trust and peer governance.
PARTICIPANTS: Andrew Nelson Drummond Reed Joel Getzendanner Michael Wolff Nikolaj Nyholm Owen Davis Sridhar Rao
SUPPORTED STANDARDS: OASIS XRI, XDI, and SAML 2.0

TYPE: [IDENTITY LAWS] The Laws of Identity
DESCRIPTION: People who work on or with identity systems need to obey the Laws of Identity.  When we don't, we leave behind us a wake of reinforcing side-effects that eventually undermine all resulting technology.  The result is similar to what would happen if civil engineers were to flaunt the law of gravity. The Laws of Identity are not about the "philosophy of identity" - which is a compelling but entirely orthogonal pursuit. Instead, they define the set of "objective" dynamics that constrain the definition of an identity system capable of being widely enough accepted that can serve as a backplane for distributed computing on a universal scale.  Our goal is to change the identity conversation enough that its laws are no longer argued as "moral imperatives", but rather as explanations of dynamics which must be mastered to craft such a universal system. 
PARTICIPANTS: Kim Cameron
SUPPORTED STANDARDS: N/A

TYPE: [SOFTWARE] Light-Weight Identity™ (LID™)DESCRIPTION: A very simple protocol that gives users control over their digital ID by enabling them to host their digital identities on a site/sites of their choosing. Uses standard URLs to identify users. Fully decentralized system, no central entity required beyond DNS. No web services stack required, very REST-ful. Supports single-sign-on (SSO), controlled information sharing (e.g. VCARDs), authenticated messaging, authenticated blog comments and more. Extensible vocabularies and protocol. Example implementation based on Perl, GPG, VCARDs and FOAF.
PARTICIPANTS: Johannes Ernst
SUPPORTED STANDARDS: Based on Perl Scripts

TYPE: [SOFTWARE] Platform for Privacy Preferences 1.1 (P3P1.1) Specification
DESCRIPTION: The Platform for Privacy Preferences Project (P3P) enables Web sites to state their privacy practices in a standard automatically retrievable format that can be interpreted easily by user agents. P3P agents will allow users to be alerted as to site practices (in both machine- and human-readable formats) and to automate decision-making based on these practices when appropriate.  P3P complements laws and self-regulatory programs that can provide enforcement mechanisms. In addition, P3P does not include mechanisms for transferring data or for securing personal data in transit or storage. P3P may be built into tools designed to facilitate data transfer. These tools should include appropriate security safeguards.
PARTICIPANTS: Lorrie Cranor, CMU (P3P 1.0 & P3P 1.1), Brooks Dobbs, bdobbs at doubleclick.net, Doubleclick Inc. (P3P 1.1), Serge Egelman, CMU (P3P 1.1), serge at guanotronic.com, Giles Hogben, Joint Research Center of the European Commission (P3P 1.1), Jack Humphrey, JHumphrey at coremetrics.com, Coremetrics, Marc Langheinrich, ETH Zurich (P3P 1.0),Massimo Marchiori, W3C / MIT / University of Venice (P3P 1.0), Martin Presler-Marshall, IBM (P3P 1.0), Joseph Reagle, W3C/MIT(P3P 1.0),Matthias Schunter, IBM (P3P 1.1), David A. Stampley, David_Stampley at reyrey.com, Invited Expert, Rigo Wenning, W3C
SUPPORTED STANDARDS: P3P1?.1

TYPE: [STANDARD] Security Assertion Markup Language 2.0 (SAML 2.0)
DESCRIPTION: A framework for the exchange of security-related information
PARTICIPANTS: OASIS
SUPPORTED STANDARDS: OASIS SAML 2.0

---

NOTE: This page is being assembled in connection with an analysis of Open Standards in Identity Management Systems. If you have questions or comments please see the contact information here.

This work is licensed under a Creative Commons License. Aldo F. Castañeda