|
|
| (7 intermediate revisions by the same user 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).
| + | 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/H2/org.eclipse.higgins.ontology/rcard.owl rcard.owl]. See also [[R-Card]].
| + | |
| − | | + | |
| − | == UML Overview ==
| + | |
| − | | + | |
| − | [[Image:Rcard 2.0.109.png|center]]
| + | |
| − | | + | |
| − | == 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 a card that supports a Javascript app.
| + | |
| − | * subClassOf: proxy:Card
| + | |
| − | * 1..1 descriptio
| + | |
| − | | + | |
| − | ===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 ==
| + | |
| − | | + | |
| − | ===<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>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==
| + | |
| − | | + | |
| − | A proxy:Card that supports a Javascript app. It's proxy:resource is a reference to a target entity in a context that (among perhaps other things) is based on the AppData vocabulary (see app-data.owl)
| + | |
| − | | + | |
| − | ===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 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.
| + | |
| − | | + | |
| − | [[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.
| + | |
| − | # Not shown above are the Context entities for the root context at the top and the app data context at the bottom
| + | |
| − | | + | |
| − | == Links ==
| + | |
| − | * [[App-data vocabulary]]
| + | |
| − | * [[Persona vocabulary]]
| + | |
| − | * [[Template vocabulary]]
| + | |
| − | * [[Persona Data Model 2.0]]
| + | |
| − | | + | |
| − | [[Category:Higgins 2 Vocabularies]]
| + | |
