Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Context"

m
 
(88 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Definition of the term "Context"==
+
[[Image:Higgins_logo_76Wx100H.jpg|right]]
A [[Context]] is a container of [[Digital Subject]]s and their network of relationships with other [[Digital Subject]]s and related objects. A [[Context]] provides these [[Digital Subject]]s with their surrounding environment and circumstances that in turn determines their meaning as well as the polices and protocols that govern their interactions. [[Context]]s are not an intrinsic part of the Higgins framework, they are provided by [[Context Provider]]s.
+
  
Examples of [[Context]]s include directories, informal groups, project teams, collaboration spaces, and communications systems and networks.
+
== Definition ==
 +
* A set of statements about one or more [[Entity | Entities]]
 +
* Have zero or more [[Attribute]]s.
 +
* Has a schema (ontology) that describes kinds of [[Entity | Entities]] and [[Attribute]]s that an instance of this [[Context]] contains.
 +
* Has its own security and access control policy
  
Every [[Context]] has an associated [[Digital Subject]] unique identifier namespace. Every [[Digital Subject]] within a [[Context]] has a unique identifier from this namespace.
+
== Examples ==
  
Every [[Context]] has a schema (or more correctly an ontology) that describes kinds of [[Digital Subject]]s and [[Identity Attribute]]s that an instance of this Context contains.
+
Examples of [[Context]]s that contain multiple [[Entity | Entities]] include: directories, informal groups, project teams, collaboration spaces, and communications systems and networks. Examples of [[Context]]s that, at least from the point of view of the authenticated consumer, typically contain only a single [[Entity]] are: driver's licenses, credit cards, business cards, and many other kinds of security devices.
  
<to-be-written: describe authN policies>
+
== In IdAS ==
 +
IdAS consumers must be able to provide the required authentication materials to "open" i.e. authenticate to a [[Context]]. Once opened, the contents of the [[Context]] can be searched, read and updated to varying extents based on the access control policy of the [[Context]].
  
<to-be-written: describe authZ policies>
+
==Footnote==
 +
Some [[Context]]s are abstract. An example of an abstract [[Context]] would be the internet mail [[Context]] associated with the internet mail [[ContextId]]. The [[Entity | Entities]]s within this [[Context]] have a [[EntityId]]s that are email addresses (e.g. "foo@boo.com") within the email namespace defined by internet mail. This cannot be resolved to a physical [[Context]] because there is no globally defined set of all email addresses.
  
[[Context]]s are implemented by [[Context Provider]]s.  
+
[[Category:Higgins Data Model 1.0]]
 
+
[[Category:Context Data Model 2.0]]
===[[Digital Subject]] Networks===
+
 
+
In a given [[Context]] an [[Entity]] is represented as one or more [[Digital Subject]]s engaged in interactions with other [[Digital Subject]]s. These interactions between [[Digital Subject]]s are represented by [Subject Relationship] objects. [[Digital Subject]]s are connected by these [Subject Relationships] into a directed graph structure. This graph is often referred to as the [[Network]] (as in social network). A [[Context]] with no inter-[[Digital Subject]]s links is effectively equivalent to a directory or a list.
+

Latest revision as of 11:34, 31 May 2021

Higgins logo 76Wx100H.jpg

Definition

  • A set of statements about one or more Entities
  • Have zero or more Attributes.
  • Has a schema (ontology) that describes kinds of Entities and Attributes that an instance of this Context contains.
  • Has its own security and access control policy

Examples

Examples of Contexts that contain multiple Entities include: directories, informal groups, project teams, collaboration spaces, and communications systems and networks. Examples of Contexts that, at least from the point of view of the authenticated consumer, typically contain only a single Entity are: driver's licenses, credit cards, business cards, and many other kinds of security devices.

In IdAS

IdAS consumers must be able to provide the required authentication materials to "open" i.e. authenticate to a Context. Once opened, the contents of the Context can be searched, read and updated to varying extents based on the access control policy of the Context.

Footnote

Some Contexts are abstract. An example of an abstract Context would be the internet mail Context associated with the internet mail ContextId. The Entitiess within this Context have a EntityIds that are email addresses (e.g. "foo@boo.com") within the email namespace defined by internet mail. This cannot be resolved to a physical Context because there is no globally defined set of all email addresses.

Back to the top