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 "R-Card vocabulary"
m (categorized) |
m (recategorized) |
||
Line 111: | Line 111: | ||
* [[Persona Data Model 2.0]] | * [[Persona Data Model 2.0]] | ||
− | [[Category:Higgins 2]] | + | [[Category:Higgins 2 Vocabularies]] |
Revision as of 17:36, 25 April 2011
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}Vocabulary to describe R-Cards (including App-Cards). Imported by Persona vocabulary.
Contents
Files
UML Overview
Classes
R-Card
A Higgins relationship card (R-Card), which is essentially a profile of an IMI managed or personal i-card.
- subClassOf
i-card:I-Card
AppCard
An App-Card is an r-card that supports a Javascript app.
- subClassOf: R-Card
- 1..1
description
AgentLink
An h:Agent that lives within an R-Card context, that is usually named _AgentLinkSingleton, and that has a resource-udr attribute that points to the "real" h:Agent of this R-Card
- subClassOf: h:Agent
- 1..1
resource-udr
DynamicAppCard
A kind of AppCard where its AppData context is dynamically created from the "recipe" of its "template" attribute:
- subClassOf: AppCard
- 0..1
template
(URL) - a link to an external "template" context (See TemplateContext class in Template vocabulary)
StaticAppCard
A kind of AppCard where its AppData context is specified by the value of its appDataContext attribute:
- subClassOf: AppCard
- 0..1
appDataContext
ContextID
Attributes
appDataContext
Context id of a pre-existing context
- domain:
StaticAppData
- value:
h:Context
- likely an AppData context instance
description
A string description of this AppCard
- domain:
AppCard
- value: string
resource-udr
Representation of the http://schemas.informationcard.net/@ics/resource-udr/2009-03 claim type.
- domain:
h:Agent
- the h:Agent node that represents the person this card is about - value: May be a UDI referent or an inline XRDS service endpoint description
template
URL of an RDF file in n3 notation containing a serialization of a TemplateContext. This template context describes the kind of AppData context that should be dynamically instantiated for this AppCard (see the section on the "template.owl" vocabulary)
- domain:
DynamicAppData
- value:
xsd:anyURI
Personal R-Card Example
From a structural point of view, the presence of the resource-udr claim on a P-Card or an M-Card makes it be considered an R-Card. Here is an example of a personal R-Card:
ERRATA: the above image is incorrect for PDM 2.0. As above the card is a context. The entity (in this case referenced by the value of the resource_udr claim) would be a free standing Person
entity (as above) and described in the PDM 1.1 model. Also icf: prefix should be removed along with ...2008... suffix. Also entityid of context object should be _ContextSingleton
Managed R-Card
The final type of card is the managed r-card. The presence of the resource-udr claim makes an ordinary M-Card into an R-Card. Here is an example of a managed R-Card:
ERRATA: The image above needs to be replaced. Card entityid should be _ContextSingleton
AppCard
Every AppCard context must contain a h:Person entity. More precisely, it should contain a p:Person entity. The p:Person entity is a node in the p:Person graph that is rooted at the RootMe p:Person node.
This p:Person node's purpose is to allow the context to be linked into the p:Person graph. It also serves as a cache of the value of the resource-udr claim (and other claims) returned in a token from the r-card's STS. This resource-udr is the link that points to main entity (probably a p:Person entity) in the card's associated AppData context.
NOTE: Since we don't yet support cards with proper STSes, a static resource-udr & value can be stored as a permanent attribute of the p:Person node.
Example
Notes
- Missing from the above diagram is the resource-udr attribute on the h:Person entity
- Missing from the above diagram is the list of supported claims. This list would include the ICF's resource-udr claim type.
Example #2
Here is an example showing an app-card and how it (a) would be linked to RootMe and (b) how the app-card points to a p:Person entity in its associated AppData context:
- The RootMe node (in the root context--not shown)
- An app-card instance in the "credit-bureau-app-card" context. The diagram shows both the card's "Person_1" entity as well as the "_ContextSingleton" entity.
- A Person_1 entity in the "cbdata" context. The surrounding AppDataContext entity and structure is not shown.
Notes:
- Missing from the above diagram is the list of supported claims. This list would include the ICF's resource-udr claim type.
- Not shown above are the Context entities for the root context at the top and the app data context at the bottom