Sign in or 
| Version | User | Scope of changes |
|---|---|---|
| Apr 24 2009, 9:39 AM EDT | gcraigburton | 178 words added |
| Apr 24 2009, 9:37 AM EDT | gcraigburton |
Changes
Key: Additions Deletions
The Identity Metasystem is defined by the use of an identity selector to store, manage, generate and interface digital identity representations—information cards—to the user and to other applications.
Since the selector model is under the umbrella of the Identity Metasystem, the model must support multiple platforms, protocols, and identity mechanisms.
Currently, there are four groups providing selectors that meet the requirements for the selector based identity model:
The selector based model is not only cross site sensitive, but provides context across sites at the individual level.
The selector based model does not require a relying party to be aware of the presence of a selector or information card in order to derive benefits from cross site context sensitivity.
The selector model is not only accessible from the web browser, but from any application executing on the operating system platform.
Since the selector model is under the umbrella of the Identity Metasystem, the model must support multiple platforms, protocols, and identity mechanisms.
Currently, there are four groups providing selectors that meet the requirements for the selector based identity model:
- Microsoft CardSpace selector
- Higgins Project-based selectors
- The Azigo selector
- Novell’s Bandit Project DigitalMe selector
- openinformationcard selector
The selector based model is not only cross site sensitive, but provides context across sites at the individual level.
The selector based model does not require a relying party to be aware of the presence of a selector or information card in order to derive benefits from cross site context sensitivity.
The selector model is not only accessible from the web browser, but from any application executing on the operating system platform.
