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"
| Line 2: | Line 2: | ||
Examples of [[Context]]s that contain multiple [[Digital Subject]]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 Digital Subject are: driver's licenses, credit cards, business cards, and many other kinds of security devices. | Examples of [[Context]]s that contain multiple [[Digital Subject]]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 Digital Subject are: driver's licenses, credit cards, business cards, and many other kinds of security devices. | ||
| − | |||
| − | |||
Every [[Context]] has a schema that describes kinds of [[Digital Subject]]s and [[Identity Attribute]]s that an instance of this [[Context]] contains. | Every [[Context]] has a schema that describes kinds of [[Digital Subject]]s and [[Identity Attribute]]s that an instance of this [[Context]] contains. | ||
Every [[Context]] has its own security policy, consumers must be able to provide the required [[Digital Identity]] object 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]]. | Every [[Context]] has its own security policy, consumers must be able to provide the required [[Digital Identity]] object 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 [[Context]]s are abstract. An example of an abstract [[Context]] would be the internet mail [[Context]] associated with the internet mail [[ContextId]]. The [[Digital Subject]]s within this [[Context]] have a SubjectId that is an email address (e.g. "foo@boo.com") within the email namespace defined by internet mail. This [[ContextId]] 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 12:47, 31 January 2008
- Definition
- A Higgins Context is a set of one or more Digital Subjects identified by a ContextId. Each Context is an instance of a ContextType.
Examples of Contexts that contain multiple Digital Subjects 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 Digital Subject are: driver's licenses, credit cards, business cards, and many other kinds of security devices.
Every Context has a schema that describes kinds of Digital Subjects and Identity Attributes that an instance of this Context contains.
Every Context has its own security policy, consumers must be able to provide the required Digital Identity object 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 Digital Subjects within this Context have a SubjectId that is an email address (e.g. "foo@boo.com") within the email namespace defined by internet mail. This ContextId cannot be resolved to a physical Context because there is no globally defined set of all email addresses.