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

Difference between revisions of "Context"

(Digital Subject Relationships)
Line 1: Line 1:
A [[Context]] is a container of one or more [[Digital Subject]]s. [[Context]]s are provided by [[Context Provider]]s.
+
A Higgins [[Context]] is a container of one or more [[Digital Subject]]s. [[Context]]s data objects instantiated and managed by [[Context Provider]] plug-ins.
  
Examples of multiple-subject [[Context]]s include: directories, informal groups, project teams, collaboration spaces, and communications systems and networks.
+
Examples of [[Context]]s that contain multiple [[Digital Subject]]s include: directories, informal groups, project teams, collaboration spaces, and communications systems and networks.  
  
Every [[Context]] defines its own identifier namespace. Every [[Digital Subject]] within a [[Context]] has a unique identifier from this namespace called "CUID" --a Contextually Unique Identifier [[Identity Attribute]].
+
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 (or more correctly, ontology) that describes kinds of [[Digital Subject]]s and [[Identity Attribute]]s that an instance of this Context contains.
+
Every [[Context]] has its own identifier namespace. Every [[Digital Subject]] within a [[Context]] has a unique identifier from this namespace called "CUID" --a Contextually Unique Identifier [[Identity Attribute]].
  
[[Context]]s are instantiated and managed by [[Context Provider]]s.
+
Every [[Context]] has a schema that describes kinds of [[Digital Subject]]s and [[Identity Attribute]]s that an instance of this [[Context]] contains.
 
+
<to-be-written: describe authN policies>
+
 
+
<to-be-written: describe authZ policies>
+
 
+
+
 
+
===[[Digital Subject]] Relationships===
+
 
+
Within a given [[Context]] an [[Entity]] is represented as one or more [[Digital Subject]]s that may have relationships with other [[Digital Subject]]s in the same [[Context]]. These relationships are directed edges called [[Subject Relationship]]s. [[Digital Subject]]s are connected by these edges into a directed graph structure. A [[Context]] with no inter-[[Digital Subject]]s relationships is equivalent to a traditional directory or a list.
+
 
+
[[Digital Subject]]s may also have directed [[Subject Relationship]]s edges that point to [[Digital Subject]]s in other [[Context]]s.
+
  
 
==See Also==
 
==See Also==

Revision as of 17:50, 22 December 2006

A Higgins Context is a container of one or more Digital Subjects. Contexts data objects instantiated and managed by Context Provider plug-ins.

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 its own identifier namespace. Every Digital Subject within a Context has a unique identifier from this namespace called "CUID" --a Contextually Unique Identifier Identity Attribute.

Every Context has a schema that describes kinds of Digital Subjects and Identity Attributes that an instance of this Context contains.

See Also

Back to the top