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 "Node"

(Definition)
(Redirecting to Entity)
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Introduction ==
+
#REDIRECT [[Entity]]
This page describes the Higgins concept of [[Node]].
+
 
+
It is similar to the [http://wiki.idcommons.net/index.php/Digital_Subject Identity Gang Lexicon's definition of Digital Subject]. The term was changed to eliminate any possible confusion with the term subject (or data subject) in international privacy law.
+
 
+
A Higgins [[Node]] is a representation of an [[Entity]] ''within a given context.'' [[Node]]s and [[Entity | Entities]] are not the same concept. The distinction is subtle but critical. In Higgins the same [[Entity]] is usually represented by multiple [[Node]]s in different [[Context]]s.
+
 
+
== Definition ==
+
* A digital representation of an [[Entity]]
+
* A [[Node]] has zero or more [[Attribute]]s
+
 
+
== Details ==
+
* Although not strictly required, almost all [[Node]]s have a single [[NodeId]] [[Attribute]] in addition to whatever other kinds of [[Attribute]]s they may have.
+
* Some of the [[Attribute]]s of an [[Node]] may be references to other [[Node]]s in the same or different [[Context]]s. These are called [[Node Relation]]s. For example, an [[Node]] representing the [[Entity]] Bob may have a "knows" [[Node Relation]] [[Attribute]] pointing to an [[Node]] representing Bob's friend Alice.
+
* A single person (thing or concept) may be represented as one (or more) [[Node]]s in one [[Context]] and (an)other [[Node]]s in other [[Context]]s. By linking or "federating" these disparate [[Node]]s one can gain a more unified view of a given person. [[Context]]s representing different systems, organizations and entire enterprises with widely varying storage and trust models are handled using this [[Node]] linking approach. For example the person "Bob Smith" could be represented as two [[Node]]s; the first having "bsmith" as an [[NodeId]] and the second having "bob" as a [[NodeId]]. These two [[Node]]s may be in the same or in different [[Context]]s. To express that the "bsmith" is the same person as "bob" an [[Node Correlation]] [[Attribute]] would be added to "bsmith" whose value points to "bob".
+
* [[Context]]s can be nested (e.g. enterprises have sub-organizations, and there are systems within an enterprise/org, etc.) or related through other means (employment/HR system vs. customer system where same person is a customer and an employee). Thus linking the [[Node]]s relevant to those contexts provides an overall view of a [[Node]](or at least a partial "overall" view to those [[Context]]s).
+
* The information contained in one [[Node]] is not necessarily a pure subset of the union of all of the information contained in all of the linked [[Node]]s representing a person taken together. There is no consistency constraint imposed between the [[Node]]s of an person. For example, a person could be represented such that their name was Joe in one [[Node]] in one [[Context]] and JoAnn in [[Node]].
+
 
+
== HOWL ==
+
<pre>
+
</pre>
+
== See Also ==
+
* [[ContextId]]
+
* [[NodeId]]
+
* [[Concepts]]
+
 
+
==Links==
+
* [http://eclipse.org/higgins Higgins Home]
+

Latest revision as of 13:32, 22 April 2008

Redirect to:

Back to the top