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

Context

Revision as of 22:51, 11 February 2009 by Ptrevithick.gmail.com (Talk | contribs)

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

Higgins logo 76Wx100H.jpg

Version

This page describes the concept of Context used in the Context Data Model 1.1

Definition

  • Is a set of one or more Entities
  • Is identified by a ContextId
  • Have zero or more Attributes.
  • Has a schema (ontology) that describes kinds of Entitiess 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 authorization 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 Context UDI cannot be resolved to a physical Context because there is no globally defined set of all email addresses.

Back to the top