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.
Difference between revisions of "Context"
(→See Also) |
|||
| Line 26: | Line 26: | ||
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 [[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 [[ContextId Data Range]] cannot be resolved to a physical [[Context]] because there is no globally defined set of all email addresses. | 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 [[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 [[ContextId Data Range]] cannot be resolved to a physical [[Context]] because there is no globally defined set of all email addresses. | ||
| − | + | ||
| − | + | ||
[[Category:Higgins Global Graph 1.1]] | [[Category:Higgins Global Graph 1.1]] | ||
Revision as of 14:10, 22 April 2008
{{#eclipseproject:technology.higgins}}
Contents
Version
This page describes the concept of Context used in the Higgins Global Graph 1.1
Definition
- Is a set of one or more Entities
- Is identified by a ContextId Data Range UDI
- Has one ContextId Attribute
- May have additional Attributes.
- Has a schema (ontology) that describes kinds of Nodes 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 Data Range. 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 ContextId Data Range cannot be resolved to a physical Context because there is no globally defined set of all email addresses.