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"

Line 7: Line 7:
  
 
The [[Higgins Data Model]] is described in two sections:
 
The [[Higgins Data Model]] is described in two sections:
# [[Higgins Global Graph]] Describes the part of the model includes concepts related to 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.  
+
# [[Higgins Global Graph]] Describes the part of the model used in the '''bottom''' layer. It includes concepts related to 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.  
# [[Tokens, Claims and I-Cards]] describes additional concepts used in the upper and middle layers including  [[Digital Identity]], [[Claim]], [[I-Card]] and others.
+
# [[Tokens, Claims and I-Cards]] describes additional concepts used in the '''middle''' and '''top''' 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.
 
See [[Data Model Background]] for more information about the motivations for and design goals behind the model.

Revision as of 18:29, 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:

  • Top: End-user applications (e.g. Identity Selector)
  • Middle: Web services for Identity Providers and Relying Parties
  • Bottom: Higgins Global Graph data abstraction layer

The Higgins Data Model is described in two sections:

  1. Higgins Global Graph Describes the part of the model used in the bottom layer. It includes concepts related to 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.
  2. Tokens, Claims and I-Cards describes additional concepts used in the middle and top 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