Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "I-Card vocabulary"
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} | + | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} |
| − | Information card | + | 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. | ||
| + | |||
| + | === Errata === | ||
| + | * Now I-Card is a subclass of CardContext (not h:Context) | ||
| + | * Need to delete backgroundColor, image, imageType attributes. These have been moved to CardContext. | ||
=== Files === | === Files === | ||
* Most recently [http://www.eclipse.org/higgins/ontologies/2010/6/icard published] | * Most recently [http://www.eclipse.org/higgins/ontologies/2010/6/icard published] | ||
| − | * SVN source: [https://dev.eclipse.org/svnroot/technology/org.eclipse.higgins/trunk/ | + | * SVN source: [https://dev.eclipse.org/svnroot/technology/org.eclipse.higgins/trunk/H2/org.eclipse.higgins.ontology/icard.owl icard.owl]. |
| + | |||
| + | == UML Overview == | ||
| + | |||
| + | [[Image:Icard 2.0.104.png|center]] | ||
| + | |||
| + | == Classes == | ||
| + | |||
| + | === <code>I-Card</code>=== | ||
| + | Abstract class | ||
| + | * subclassOf: <code>h:Context</code>. | ||
| + | *1..1 <code>cardId (xsd:string)</code> - a unique identifier for the card | ||
| + | *1..1 <code>image</code> - an image bitmap for the background of the card when it is displayed | ||
| + | *... others. | ||
| + | |||
| + | ===<code>P-Card</code>=== | ||
| + | An OASIS IMI Personal card | ||
| + | * subclassOf: <code>I-Card</code> | ||
| + | |||
| + | ===<code>M-Card</code> === | ||
| + | An OASIS IMI Managed card | ||
| + | * subclassOf: <code>I-Card</code> | ||
| + | |||
| + | == P-Card Attributes == | ||
| + | |||
| + | The attributes that define a personal card are taken directly from the OASIS IMI specification. | ||
| + | |||
| + | === An example p-card === | ||
| + | |||
| + | [[Image:Personal-i-card-example.png|center]] | ||
| + | |||
| + | == M-Card Attributes == | ||
| + | |||
| + | 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. | ||
| + | |||
| + | === Example m-card === | ||
| + | |||
| + | [[Image:M-card-explained.png|center]] | ||
| + | |||
| + | 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. | ||
| + | |||
| + | == Card Axioms == | ||
| + | |||
| + | #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 | ||
| + | |||
== Links == | == Links == | ||
* [[Persona Data Model 2.0]] | * [[Persona Data Model 2.0]] | ||
Latest revision as of 09:37, 5 May 2012
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
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.
Contents
Errata
- Now I-Card is a subclass of CardContext (not h:Context)
- Need to delete backgroundColor, image, imageType attributes. These have been moved to CardContext.
Files
UML Overview
Classes
I-Card
Abstract class
- subclassOf:
h:Context. - 1..1
cardId (xsd:string)- a unique identifier for the card - 1..1
image- an image bitmap for the background of the card when it is displayed - ... others.
P-Card
An OASIS IMI Personal card
- subclassOf:
I-Card
M-Card
An OASIS IMI Managed card
- subclassOf:
I-Card
P-Card Attributes
The attributes that define a personal card are taken directly from the OASIS IMI specification.
An example p-card
M-Card Attributes
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.
Example m-card
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.
Card Axioms
- 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