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"
(→As Used In Higgins) |
(→As Used In Higgins) |
||
| Line 6: | Line 6: | ||
===As Used In Higgins=== | ===As Used In Higgins=== | ||
| − | * Most Entities have one [[LocalId]] [[Attribute]] | + | * Most [[Entity | Entities]] have one [[LocalId]] [[Attribute]] |
| − | * Some of these [[Attribute]]s may be [[ | + | * Some of these [[Attribute]]s may be [[EntityId]]s that are references to other [[Entity | Entities]] in the same or different [[Context]]s |
| − | * Modeling a person, thing or concept. Although any given person (or thing or concept, etc.) is relevant to, and exists within a given [[Context]], a single person may be represented as one (or more) [[Entity | Entities]] in one [[Context]] and (an)other [[Entity | Entity(ies) | + | * Modeling a person, thing or concept. Although any given person (or thing or concept, etc.) is relevant to, and exists within a given [[Context]], a single person may be represented as one (or more) [[Entity | Entities]] in one [[Context]] and (an)other [[Entity | Entity(ies)]] in other [[Context]]s. By linking or "federating" these disparate [[Entity | Entities]] 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 [[Entity]] linking approach. For example the person "Bob Smith" could be represented as two [[Entity | Entities]]; the first having "bsmith" as an [[LocalId]] and the second having "bob" as a [[LocalId]]. These two [[Entity | Entities]] 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 [[Entity | Entities]] relevant to those contexts provides an overall view of an Entity (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 [[Entity | Entities]] relevant to those contexts provides an overall view of an Entity (or at least a partial "overall" view to those [[Context]]s). | ||
* The information contained in one [[Entity]] is not necessarily a pure subset of the union of all of the information contained in all of the linked [[Entity | Entities]] representing a person taken together. There is no consistency constraint imposed between the [[Entity | Entities]] of an person. For example, a person could be represented such that their name was Joe in one [[Entity]] in one [[Context]] and JoAnn in [[Entity]]. | * The information contained in one [[Entity]] is not necessarily a pure subset of the union of all of the information contained in all of the linked [[Entity | Entities]] representing a person taken together. There is no consistency constraint imposed between the [[Entity | Entities]] of an person. For example, a person could be represented such that their name was Joe in one [[Entity]] in one [[Context]] and JoAnn in [[Entity]]. | ||
Revision as of 20:03, 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 Entities have one LocalId Attribute
- Some of these Attributes may be EntityIds that are references to other Entities in the same or different Contexts
- Modeling a person, thing or concept. Although any given person (or thing or concept, etc.) is relevant to, and exists within a given Context, a single person may be represented as one (or more) Entities in one Context and (an)other Entity(ies) in other Contexts. By linking or "federating" these disparate Entities 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 Entity linking approach. For example the person "Bob Smith" could be represented as two Entities; the first having "bsmith" as an LocalId and the second having "bob" as a LocalId. These two Entities 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 Entities relevant to those contexts provides an overall view of an Entity (or at least a partial "overall" view to those Contexts).
- The information contained in one Entity is not necessarily a pure subset of the union of all of the information contained in all of the linked Entities representing a person taken together. There is no consistency constraint imposed between the Entities of an person. For example, a person could be represented such that their name was Joe in one Entity in one Context and JoAnn in Entity.