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"
m |
|||
| (75 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Image:Higgins_logo_76Wx100H.jpg|right]] | |
| − | + | == 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 | ||
| − | + | == Examples == | |
| − | Examples of | + | 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. |
| − | + | == 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 [[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. | ||
| − | + | [[Category:Higgins Data Model 1.0]] | |
| − | + | [[Category:Context Data Model 2.0]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 11:34, 31 May 2021
Contents
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.