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.
Difference between revisions of "Context"
(Undo revision 91869 by Asafronkova.aquasoft.dp.ua (Talk)) |
|||
| Line 5: | Line 5: | ||
== Definition == | == Definition == | ||
| − | * A [[Context]] is a set of one or more [[ | + | * A [[Context]] is a set of one or more [[Node]]s identified by a [[ContextId Data Range]]. |
* A [[Context]] may have zero or more [[Attribute]]s. | * A [[Context]] may have zero or more [[Attribute]]s. | ||
| − | * A [[Context]] has a schema that describes kinds of [[ | + | * A [[Context]] has a schema that describes kinds of [[Node]]s and [[Attribute]]s that an instance of this [[Context]] contains. |
* Each [[Context]] has its own security and access control policy | * Each [[Context]] has its own security and access control policy | ||
== Examples == | == Examples == | ||
| − | Examples of [[Context]]s that contain multiple [[ | + | Examples of [[Context]]s that contain multiple [[Node]]s 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 [[Node]] are: driver's licenses, credit cards, business cards, and many other kinds of security devices. |
== HOWL == | == HOWL == | ||
| Line 22: | Line 22: | ||
==Footnote== | ==Footnote== | ||
| − | Some [[Context]]s are abstract. An example of an abstract [[Context]] would be the internet mail [[Context]] associated with the internet mail [[ContextId Data Range]]. The [[ | + | Some [[Context]]s are abstract. An example of an abstract [[Context]] would be the internet mail [[Context]] associated with the internet mail [[ContextId Data Range]]. The [[Node]]s 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== | ==See Also== | ||
Revision as of 08:31, 11 April 2008
{{#eclipseproject:technology.higgins}}
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.