Skip to main content
Jump to: navigation, search

Difference between revisions of "Node"

(Definition)
m (Details)
Line 15: Line 15:
 
* 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".
 
* 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).
 
* [[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]].
+
* 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 another [[Node]] in another [[Context]].
  
 
== HOWL ==
 
== HOWL ==

Revision as of 02:17, 8 February 2008

Introduction

This page describes the Higgins concept of Node.

It is similar to the 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. Nodes and Entities are not the same concept. The distinction is subtle but critical. In Higgins the same Entity is usually represented by multiple Nodes in different Contexts.

Definition

Details

  • Although not strictly required, almost all Nodes have a single NodeId Attribute in addition to whatever other kinds of Attributes they may have.
  • Some of the Attributes of an Node may be references to other Nodes in the same or different Contexts. These are called Node Relations. 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) Nodes in one Context and (an)other Nodes in other Contexts. By linking or "federating" these disparate Nodes one can gain a more unified view of a given person. Contexts 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 Nodes; the first having "bsmith" as an NodeId and the second having "bob" as a NodeId. These two Nodes may be in the same or in different Contexts. 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".
  • Contexts 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 Nodes relevant to those contexts provides an overall view of a Node(or at least a partial "overall" view to those Contexts).
  • 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 Nodes representing a person taken together. There is no consistency constraint imposed between the Nodes 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 another Node in another Context.

HOWL


See Also

Links

Back to the top