|
|
| (24 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} [[Image:Higgins logo 76Wx100H.jpg|right]] | | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} [[Image:Higgins logo 76Wx100H.jpg|right]] |
| | | | |
| − | Vocabulary to describe [[R-Card]]s (including [[App-Card]]s). Imported by [[Persona vocabulary]].
| + | Obsolete |
| − | | + | |
| − | === Files ===
| + | |
| − | * Most recently [http://www.eclipse.org/higgins/ontologies/2010/6/rcard published]
| + | |
| − | * SVN source: [https://dev.eclipse.org/svnroot/technology/org.eclipse.higgins/trunk/ontology/org.eclipse.higgins.ontology/rcard.owl rcard.owl]. See also [[R-Card]].
| + | |
| − | | + | |
| − | == UML Overview ==
| + | |
| − | | + | |
| − | [[Image:Rcard 2.0.104.png|center]]
| + | |
| − | | + | |
| − | == Classes ==
| + | |
| − | | + | |
| − | ===<code>R-Card</code>===
| + | |
| − | A Higgins relationship card ([[R-Card]]), which is essentially a profile of an IMI managed or personal i-card.
| + | |
| − | * subClassOf <code>i-card:I-Card</code>
| + | |
| − | * 1..1 <code>resource-udr</code>
| + | |
| − | | + | |
| − | ===<code>AppCard</code>===
| + | |
| − | An [[App-Card]] is an r-card that supports a Javascript app. It's resource-udr is a reference to a target entity in an AppData context (see app-data.owl). This resource-udr's target entity and its surrounding context are described by the app-data ontology.
| + | |
| − | * subClassOf: R-Card
| + | |
| − | * 1..1 <code>description</code>
| + | |
| − | | + | |
| − | ===<code>DynamicAppData</code>===
| + | |
| − | A kind of AppCard where its AppData context is dynamically created from the "recipe" of its "template" attribute:
| + | |
| − | * subClassOf: AppCard
| + | |
| − | * 0..1 <code>template</code> (URL) - a link to an external "template" context (See TemplateContext class in [[Template vocabulary]])
| + | |
| − | | + | |
| − | ===<code>StaticAppData</code>===
| + | |
| − | A kind of AppCard where its AppData context is specified by the value of its appDataContext attribute:
| + | |
| − | * subClassOf: AppCard
| + | |
| − | * 0..1 <code>appDataContext</code> ContextID
| + | |
| − | | + | |
| − | == Attributes ==
| + | |
| − | | + | |
| − | ===<code>appDataContext</code>===
| + | |
| − | Context id of a pre-existing context
| + | |
| − | * domain: <code>StaticAppData</code>
| + | |
| − | * value: <code>h:Context</code> - likely an AppData context instance
| + | |
| − | | + | |
| − | ===<code>description</code>===
| + | |
| − | A string description of this AppCard
| + | |
| − | * domain: <code>AppCard</code>
| + | |
| − | * value: string
| + | |
| − | | + | |
| − | ===<code>resource-udr</code>===
| + | |
| − | Representation of the http://schemas.informationcard.net/@ics/resource-udr/2009-03 claim type.
| + | |
| − | * domain: <code>h:Person</code> - the h:Person node that represents the person this card is about
| + | |
| − | * value: <code>xsd:anyURI</code> - [http://www.azigo.com/company/dev/udi/ UDI] resource reference
| + | |
| − | | + | |
| − | ===<code>template</code>===
| + | |
| − | 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: <code>DynamicAppData</code>
| + | |
| − | * value: <code>xsd:anyURI</code>
| + | |
| − | | + | |
| − | == 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]]:
| + | |
| − | | + | |
| − | [[Image:Example-r-pcard-v2.png|center]]
| + | |
| − | | + | |
| − | 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 <code>Person</code> 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]]:
| + | |
| − | | + | |
| − | [[Image:Managed-r-card.png|center]]
| + | |
| − | | + | |
| − | 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===
| + | |
| − | [[Image:App-card-example-v7.png|center]]
| + | |
| − | | + | |
| − | 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 three contexts:
| + | |
| − | # 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.
| + | |
| − | | + | |
| − | [[Image:Root-appcard-appdata-example.png|center]]
| + | |
| − | | + | |
| − | Notes:
| + | |
| − | # Missing from the above diagram is the list of supported claims. This list would include the ICF's resource-udr claim type.
| + | |
| − | | + | |
| − | == Links ==
| + | |
| − | * [[App-data vocabulary]]
| + | |
| − | * [[Persona vocabulary]]
| + | |
| − | * [[Template vocabulary]]
| + | |
| − | * [[Persona Data Model 2.0]]
| + | |
