Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Node"
(→Definition) |
|||
| Line 3: | Line 3: | ||
== Definition == | == Definition == | ||
* A digital representation of a person, thing or concept. | * A digital representation of a person, thing or concept. | ||
| − | * A [[Entity]] has zero or more [[ | + | * A [[Entity]] has zero or more [[Attribute]]s |
===As Used In Higgins=== | ===As Used In Higgins=== | ||
| − | * Most [[Entity]]s have one [[SubjectId]] [[ | + | * Most [[Entity]]s have one [[SubjectId]] [[Attribute]] |
| − | * Some of these [[ | + | * Some of these [[Attribute]]s may be [[Relation]]s that are references to other [[Digital Subject]]s in the same or different [[Context]]s |
| − | * Relationship to an [[Entity]]: Although any given [[ | + | * Relationship to an [[Entity]]: Although any given [[Entity]] is relevant to, and exists within a given [[Context]], a single [[Entity]] may be represented as one (or more) [[Digital Subject]](s) in one [[Context]] and yet other [[Digital Subject]]s in another [[Context]]s. By linking or "federating" these disparate [[Digital Subject]]s one can gain a more unified view of a given [[Entity]]. [[Context]]s representing different systems, organizations and entire enterprises with widely varying storage and trust models are handled using this [[Digital Subject]] linking approach. For example the [[Entity]] "Bob Smith" could be represented as two [[Digital Subject|Digital Subjects]]; the first having "bsmith" as an identifier and the second having "bob" as an identifier. These two [[Digital Subject]]s may be in the same or in different [[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 [[Digital Subject]]s relevant to those contexts provides an overall view of a [[Digital Subject]] (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 [[Digital Subject]]s relevant to those contexts provides an overall view of a [[Digital Subject]] (or at least a partial "overall" view to those [[Context]]s). | ||
* The information contained in a [[Digital Subject]] is not necessarily a pure subset of the union of all of the information contained in all of the [[Digital Subject]]s of an [[Entity]] taken together. There is no consistency constraint imposed between the [[Digital Subject]]s of an [[Entity]]. For example, a person could claim that their name was Joe in one [[Digital Subject]] and JoAnn in another. | * The information contained in a [[Digital Subject]] is not necessarily a pure subset of the union of all of the information contained in all of the [[Digital Subject]]s of an [[Entity]] taken together. There is no consistency constraint imposed between the [[Digital Subject]]s of an [[Entity]]. For example, a person could claim that their name was Joe in one [[Digital Subject]] and JoAnn in another. | ||
Revision as of 17:35, 31 January 2008
Introduction
Definition
- A digital representation of a person, thing or concept.
- A Entity has zero or more Attributes
As Used In Higgins
- Most Entitys have one SubjectId Attribute
- Some of these Attributes may be Relations that are references to other Digital Subjects in the same or different Contexts
- Relationship to an Entity: Although any given Entity is relevant to, and exists within a given Context, a single Entity may be represented as one (or more) Digital Subject(s) in one Context and yet other Digital Subjects in another Contexts. By linking or "federating" these disparate Digital Subjects one can gain a more unified view of a given Entity. Contexts representing different systems, organizations and entire enterprises with widely varying storage and trust models are handled using this Digital Subject linking approach. For example the Entity "Bob Smith" could be represented as two Digital Subjects; the first having "bsmith" as an identifier and the second having "bob" as an identifier. These two Digital Subjects may be in the same or in different Contexts.
- 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 Digital Subjects relevant to those contexts provides an overall view of a Digital Subject (or at least a partial "overall" view to those Contexts).
- The information contained in a Digital Subject is not necessarily a pure subset of the union of all of the information contained in all of the Digital Subjects of an Entity taken together. There is no consistency constraint imposed between the Digital Subjects of an Entity. For example, a person could claim that their name was Joe in one Digital Subject and JoAnn in another.