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.
Vocabulary to describe Information cards. See also I-Card.
Information Card (aka i-card) technology is defined by the OASIS IMI TC. It is a standard way to represent a person's digital identities using a card metaphor, XML card formats, and associated SOAP and HTTP network protocols. See also I-Card.
Note: in CDM multiple inheritance is allowed: any single entity may be a member of multiple classes simultaneously.
- Now I-Card is a subclass of CardContext (not h:Context)
- Need to delete backgroundColor, image, imageType attributes. These have been moved to CardContext.
cardId (xsd:string)- a unique identifier for the card
image- an image bitmap for the background of the card when it is displayed
- ... others.
An OASIS IMI Personal card
An OASIS IMI Managed card
The attributes that define a personal card are taken directly from the OASIS IMI specification.
An example p-card
Shown below is an example of an instance of an m-card. For simplicity this m-card has only a single supported claim, "LastName". The entity shown in the center of the card is a cache of what is returned by the STS in response to a request for a display token.
Note: There is an error in the above diagram the DisplayTokenEntity should have been modeled in the Persona data model (thus identity:surname would have been transformed into its equivalent in PDM.
- For any M-Card: The value of any of the above "supported" claims attributes is considered to be a cache of the most recent value of these claims as fetched from the m-card's STS