Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Data Models 1.X"

(Overview)
Line 4: Line 4:
 
; The upper layer: Provides end-user applications called "Identity Selectors" that manage [[I-Card]]s and present end-users with a visual metaphor for the [[Digital Identity | Digital Identities]] and their component [[Claim]]s.
 
; The upper layer: Provides end-user applications called "Identity Selectors" that manage [[I-Card]]s and present end-users with a visual metaphor for the [[Digital Identity | Digital Identities]] and their component [[Claim]]s.
 
; The middle layer: Provides web services for Identity Providers and Relying Parties
 
; The middle layer: Provides web services for Identity Providers and Relying Parties
; The lower (data) layer: This layer is based on a data model abstraction includes data stores called [[Context]]s, the [[Digital Subject]]s within them, the [[Identity Attribute]]s on each [[Digital Subject]], and the links (called [[Relation]]s) between them. This is the "pure" data layer. The abstract data model is realized as concrete data by the [[Identity Attribute Service]] (IdAS) and supporting [[Context Provider]]s.  
+
; The lower (data) layer: This layer is based on a data model abstraction includes data stores called [[Context]]s, the [[Entity | Entities]]s within them, the [[Attribute]]s on each [[Entity]], and the links (called [[Relation]]s) between them. This is the "pure" data layer. The abstract data model is realized as concrete data by the [[Identity Attribute Service]] (IdAS) and supporting [[Context Provider]]s.  
  
 
The [[Higgins Data Model]] is described in two sections:
 
The [[Higgins Data Model]] is described in two sections:

Revision as of 18:24, 31 January 2008

The Higgins data model provides a common representation for identity, profile and relationship data to enable interoperability and data portability across heterogeneous sites and systems.

The Higgins framework is has three layers:

The upper layer
Provides end-user applications called "Identity Selectors" that manage I-Cards and present end-users with a visual metaphor for the Digital Identities and their component Claims.
The middle layer
Provides web services for Identity Providers and Relying Parties
The lower (data) layer
This layer is based on a data model abstraction includes data stores called Contexts, the Entitiess within them, the Attributes on each Entity, and the links (called Relations) between them. This is the "pure" data layer. The abstract data model is realized as concrete data by the Identity Attribute Service (IdAS) and supporting Context Providers.

The Higgins Data Model is described in two sections:

  1. Higgins Global Graph Describes the part of the model used by the "lower" layer.
  2. Tokens, Claims and I-Cards describes additional concepts used in the upper and middle layers including Digital Identity, Claim, I-Card and others.

See Data Model Background for more information about the motivations for and design goals behind the model.

Links

Back to the top