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 08:31, 11 April 2008 by Asafronkova.aquasoft.dp.ua (Talk | contribs) (Undo revision 91869 by Asafronkova.aquasoft.dp.ua (Talk))

{{#eclipseproject:technology.higgins}}

Higgins logo 76Wx100H.jpg

Introduction

This page describes the Context concept.

Definition

  • A Context is a set of one or more Nodes identified by a ContextId Data Range.
  • A Context may have zero or more Attributes.
  • A Context has a schema that describes kinds of Nodes and Attributes that an instance of this Context contains.
  • Each Context has its own security and access control policy

Examples

Examples of Contexts that contain multiple Nodes 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 Node are: driver's licenses, credit cards, business cards, and many other kinds of security devices.

HOWL


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 Data Range. The Nodes within this Context have a NodeId Data Range that is an email address (e.g. "foo@boo.com") within the email namespace defined by internet mail. This ContextId Data Range cannot be resolved to a physical Context because there is no globally defined set of all email addresses.

See Also

Back to the top