Identity is an m:n map of an operational entity as a human being; because after you narrow all of humanity over time to a single individual (m:1) making a decision that has consequential effects in any theory or model, there are also issues of alias identities associated with roles and relationships (1:m) which still must be understood and mapped for effective utility. This trace requirement, falls into a typical patterns formed when many x values map with some consistent relationship to many y values it defines the surface of a hyperbolic paraboloid.
The hyperbolic paraboloid can be defined as the ruled surface generated by the straight lines
- meeting two lines that are non coplanar and remaining parallel to a fixed plane (secant to these two lines) called directrix plane of the paraboloid
- meeting three lines that are two by two non coplanar, but parallel to a given plane (when it is not the case, we get the one-sheeted hyperboloid).
Identity is who and how you demonstrate and authenticate who you are as authentication to do something, to be authorized to act. Person is simply who you are. One person can have multiple identities, and one identity can be used by multiple persons to perform some related set of acts.
Complex X*Y mapping is a fundamental method in EATSv5. Encoding and decoding roles and relationships through relational maps and dynamic keys is a factor in helping secure privacy.
Initial maps, until the system is more sufficiently enabled to be audited by routine, cogent humans, uses names for people. There is no current edits or automated assist on whether human recognizable labels on content, or names of files, match the concepts modeled by defined concepts and relationships. Currently, that is a manual, data munging operation. Mixing it up confuses other humans, but over time, with better indexing of the codex some automation can assist is the assurance of similarity, if not congruity.
All internal data is managed by internally generated unique identifiers. All data occurs within some known “pool” of information classified by type of data, which is the key for internal data management.
People is a metadata Class. It is an open collection container set of all individually identified people, humans. It has no size limits. All people references elsewhere within the content of the system implicitly should be identified here as members of this class. The class is used as a primary distinction mechanism in models developed using the AF architecture in terms of how design rules are implemented, and how the architectural algorithms operate.
- People are authorities of their own self. Their statement of intent is what the model follows for things for which they are the steward. This is the basis for content ownership and privacy rights; which are in immediate conflict as soon as one person maintains information about another person.
- To the extent the second person is a historical figure, the information about the second person is public data, the second person is deceased, etc., this can lack social concern and be functionally inconsequential.
- To the extent the data is of a purely personal nature and might cause undue personal harm if exposed, this is a major concern related to human rights and the right of privacy in each individual human person’s private thoughts and actions.
- The point of the model is to force this concern to the fore; and to prove a mechanism for architecting on the basis of people as distinct and special types of “things” in architectural models of a general nature.