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.
Persona Data Model 2.0
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Within the I-Card Service's RPPS Package are many different components that persist data objects on behalf of the user. These include user account data, the users set of cards, and other data. Some components use IdAS to persist their data. Others manage their own local data stores "above" IdAS. An attempt to document all of these different kinds of objects and stores would be a major project. Instead of looking backward, this page describes a new, updated data model that we call ICS Data Model 2.0.
Version
During the Higgins 1.1 development project we will be working on defining the ICS Data Model 2.0. We will not be able to implement the new model in time for Higgins 1.1, but work will continue thereafter.
Approach
The ICS Data Model 2.0 defines the patterns and kinds of objects that exist in a running instance of the I-Card Service. The ICS Data Model 2.0 can be expressed in the still more general Context Data Model 1.1 and that is exactly what this document does. It describes one model in terms of the other. It is assumed here that the reader is familiar with CDM 1.1.
Implementation
Since this document is about design, not implementation we make a short implementation note here before we move on. We expect that when it comes time to implement the new ICS Data Model 2.0 (ICSDM) that a decision will be made that the I-Card Service, the RPPS Package components, etc. store all data objects in IdAS. IdAS would thus become the "data layer" in the traditional tiered model.
Key Concepts
Account
The I-Card Service is used by
Cards
Four classes of cards are defined:
- p-card (as in CardSpace)
- m-card (as in CardSpace)
- relationship p-card
- relationship m-card