Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Context vocabulary"

(New page: {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} right A vocabulary to describe events that happen at a specific date and time and that ...)
 
(→‎Links)
 
(48 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}}  
−
A vocabulary to describe events that happen at a specific date and time and that affect either a specific attribute of an entity or all attributes of that entity. Event types include CRUD operations, verification events and disclosure events. Imported by [[Persona vocabulary]].
+
 
 +
A vocabulary to describe contexts. Imported by [[Persona vocabulary]].
  
 
=== Files ===
 
=== Files ===
−
* Most recently [http://www.eclipse.org/higgins/ontologies/2010/6/event published].
+
* SVN source: [https://dev.eclipse.org/svnroot/technology/org.eclipse.higgins/trunk/H2/org.eclipse.higgins.ontology/context.owl context.owl]
−
* SVN source: [https://dev.eclipse.org/svnroot/technology/org.eclipse.higgins/trunk/H2/org.eclipse.higgins.ontology/event.owl event.owl]
+
  
 
==UML Overview==
 
==UML Overview==
−
[[Image:Event 2.0.107.png|center]]
+
[[Image:Context 2.0.108.png|center]]
  
 
==Classes==
 
==Classes==
−
=== <code>Event</code> ===
 
−
Change event. Abstract superclass. Subclasses describes changes to an attribute "attribute" of some entity "entity" that happened at dateTime "at"
 
−
* 1..1 at
 
−
* 1..N entity
 
  
−
=== <code>AttPolicy</code>===
+
===Context===
−
An association of an attribute of some entity with a disclosure policy
+
A context as used in the Persona data model. A container of a set of entities. Contexts are usually created using information from a special kind of context called a template:TemplateContext. The template:TemplateContext contains a ContextPrototype that describes the context to be created. Regular contexts have a ''template'' attribute that its the TemplateContext that originally defined it.
−
* 1..1 policy
+
* subClassOf: h:Context
−
* 1..1 attribute
+
* 0..1 h:control
−
* 1..1 entity
+
* 0..1 issuer
 +
* 0..1 template
 +
* 0..1 settings
 +
* 1..1 skos:prefLabel
  
−
=== <code>AttributeChanged</code> ===
+
===AppContext===
−
A class of events wherein a single attribute is changed
+
A context that provides storage for an add-on app to the portal, a built-in app-like functionality in the portal (e.g. the all-about-me editor app), or an HBX add-on (e.g. dynamically loaded JavaScript app).
−
* subClassOf Event
+
* subClassOf: h:Context
−
* 1..1 attribute
+
−
* 1..1 entity
+
  
−
=== <code>Add</code> ===
+
===InboxContext===
−
New value "value"(s) was/were added to attribute "attribute" of entity "entity" at dateTime "at"
+
Special "inbox" context that is used to receive notifications from other ADS user accounts. Only one inbox context per ADS user.
−
* subClassOf AttributeChanged
+
* subClassOf: h:Context
−
* 1..N value - "new" value(s)
+
  
−
=== <code>Delete</code> ===
+
=== RootContext===
−
One, more or all values of attribute "attribute" of entity "entity" was deleted at dateTime "at". Values to be deleted are specified by one or more "oldValue"(s). If all values of attribute "attribute" are to be deleted then the oldValue (attribute) is omitted.
+
A tagging subclass indicating that this context is the "root" context for this user. There should only be one instance of RootContext for each user.
−
* subClassOf AttributeChanged
+
* subClassOf: Context
−
* 1..N oldValue
+
  
−
=== <code>Get</code> ===
+
===Settings===
−
One or more values of attribute "attribute" of entity "entity" was read at dateTime "at"
+
A class to hold setting information for the containing context. Settings are the user's preferences for how to interact with the containing context, as opposed to pure data held by the context. It is expected that contexts that have specific settings will attach them as attributes to an instance of Settings (or some subclass thereof).
−
* subClassOf AttributeChanged
+
* subClassOf: owl:Thing
−
 
+
−
=== <code>Modify</code> ===
+
−
The attribute "attribute" of entity "entity" was modified at datetime "at". The value "oldValue" was replaced with value(s) "newValue"
+
−
* subClassOf AttributeChanged
+
−
* 1..1 oldValue
+
−
* 1..N value
+
−
 
+
−
=== <code>Disclosure</code> ===
+
−
A disclosure of attributes to an external party (e.g. an RP website). Each "entity" points to a context object (h:Context instance)
+
−
* subClassOf Event
+
−
* 1..1 relyingParty
+
−
* 1..N disclosed
+
−
 
+
−
=== <code>Verification</code> ===
+
−
Verification event performed by the p:issuer of this context. If event:attribute is not present then event:entity(ies) in their entirety have been verified. Else if event:attribute is present then just the attribute mentioned has been verified.
+
−
* subClassOf Event
+
−
* 1..1 entity
+
−
* 0..1 verificationResult
+
  
 
==Attributes==
 
==Attributes==
  
−
=== <code>at</code>  ===
+
=== issuer ===
−
When this event happened
+
The entity (e.g. a business) that defines this context: defines the schema used, defines the meaning of the attributes of the schema, defines the interaction context withing which these attributes gain values. The issuer is often, but not necessarily the entity that makes the attribute value assertions (claims). If the issuer is Equifax, then indeed Equifax is making the claim that the "bearer" of this context is, say, over 21 years of age. As a counter example, the issuer of a context might be Facebook. In this case the values are asserted by the Facebook user, yet Facebook is considered the issuer. This is a required attribute of all Contexts.
−
* domain: Event
+
* domain: Context
−
* value: dateTime
+
* value: URI. The URI is either the domain name that is the authority behind the attribute assertions or
−
 
+
**The value <code>http://!self</code> - the user has explicitly asserted entities &amp; attributes in this context
−
=== <code>attribute</code>  ===
+
** The value <code>http://!derived</code> - the active client has derived entities &amp; attributes in this context based on observed behavior and/or assertions made by the user in other contexts
−
* value: an attribute
+
−
 
+
−
=== <code>disclosed</code> ===
+
−
The attribute that has been disclosed/blocked
+
−
* domain: Disclosure
+
−
* value: AttPolicy
+
−
 
+
−
=== <code>entity</code> ===
+
−
The entity that has been verified
+
−
* domain: Event
+
−
* value: an entity
+
−
 
+
−
=== <code>event</code> ===
+
−
An event that happened. Used to associate event(s) with some object to which it relates (often an h:Context)
+
−
* value: Event
+
  
−
=== <code>oldValue</code>  ===
+
=== settings ===
−
Old value of an attribute
+
A singleton instance of the Settings class.
−
* domain: Delete, Modify
+
* domain: Context
−
* value: entity or literal
+
* value: Settings
  
−
=== <code>policy</code>  ===
+
=== template ===
−
* domain: AttPolicy
+
A link to a TemplateContext that acts as a template for this context.
−
* value: string value one of {"allow", "block"}
+
* domain: Context
 +
* value: template:TemplateContext
  
−
=== <code>relyingParty</code>  ===
+
==Attributes from higgins.owl ==
−
* domain: Disclosure
+
Repeated here for convenience.
−
* value: xsd:anyURI
+
  
−
=== <code>value</code>  ===
+
=== h:control ===
−
New value(s)
+
Inherited from h:Context. See [[Higgins Data Model 2.0]].
−
* domain: Add, Modify
+
* domain: Context
−
* value: entity or literal
+
* value: h:Context
  
−
=== <code>verificationResult</code>  ===
+
===h:vocabulary===
−
Result of verification
+
Inherited from h:Context. See [[Higgins Data Model 2.0]].
−
New value(s)
+
* domain: h:Context
−
* domain: Verification
+
* range: owl:Ontology
−
* value: one of {"false" , "indeterminate" , "true"}
+
  
 
== Links ==
 
== Links ==

Latest revision as of 20:50, 11 October 2011

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

A vocabulary to describe contexts. Imported by Persona vocabulary.

Files

UML Overview

Context 2.0.108.png

Classes

Context

A context as used in the Persona data model. A container of a set of entities. Contexts are usually created using information from a special kind of context called a template:TemplateContext. The template:TemplateContext contains a ContextPrototype that describes the context to be created. Regular contexts have a template attribute that its the TemplateContext that originally defined it.

  • subClassOf: h:Context
  • 0..1 h:control
  • 0..1 issuer
  • 0..1 template
  • 0..1 settings
  • 1..1 skos:prefLabel

AppContext

A context that provides storage for an add-on app to the portal, a built-in app-like functionality in the portal (e.g. the all-about-me editor app), or an HBX add-on (e.g. dynamically loaded JavaScript app).

  • subClassOf: h:Context

InboxContext

Special "inbox" context that is used to receive notifications from other ADS user accounts. Only one inbox context per ADS user.

  • subClassOf: h:Context

RootContext

A tagging subclass indicating that this context is the "root" context for this user. There should only be one instance of RootContext for each user.

  • subClassOf: Context

Settings

A class to hold setting information for the containing context. Settings are the user's preferences for how to interact with the containing context, as opposed to pure data held by the context. It is expected that contexts that have specific settings will attach them as attributes to an instance of Settings (or some subclass thereof).

  • subClassOf: owl:Thing

Attributes

issuer

The entity (e.g. a business) that defines this context: defines the schema used, defines the meaning of the attributes of the schema, defines the interaction context withing which these attributes gain values. The issuer is often, but not necessarily the entity that makes the attribute value assertions (claims). If the issuer is Equifax, then indeed Equifax is making the claim that the "bearer" of this context is, say, over 21 years of age. As a counter example, the issuer of a context might be Facebook. In this case the values are asserted by the Facebook user, yet Facebook is considered the issuer. This is a required attribute of all Contexts.

  • domain: Context
  • value: URI. The URI is either the domain name that is the authority behind the attribute assertions or
    • The value http://!self - the user has explicitly asserted entities & attributes in this context
    • The value http://!derived - the active client has derived entities & attributes in this context based on observed behavior and/or assertions made by the user in other contexts

settings

A singleton instance of the Settings class.

  • domain: Context
  • value: Settings

template

A link to a TemplateContext that acts as a template for this context.

  • domain: Context
  • value: template:TemplateContext

Attributes from higgins.owl

Repeated here for convenience.

h:control

Inherited from h:Context. See Higgins Data Model 2.0.

  • domain: Context
  • value: h:Context

h:vocabulary

Inherited from h:Context. See Higgins Data Model 2.0.

  • domain: h:Context
  • range: owl:Ontology

Links

Retrieved from "https://wiki.eclipse.org/index.php?title=Context_vocabulary&oldid=272051"

This page was last modified 20:50, 11 October 2011 by Paul Trevithick.

Back to the top