This entity type represents some state of the research into an individual person.
When a person is first entered into a BetterGEDCOM (BG) file, using the data from a single source, the person entity will clearly contain just the information extracted from that single source. When a second source, apparently for the same person, is obtained and entered to the BG file, the user can then proceed in one of two ways:
- Add the new information to the existing PERSON entity, so that the single PERSON entity always contains the current working hypothesis about an individual;
- Create a second PERSON entity, using only the data from the second source. The first and second entities can be referred to as "evidence" entities. Then, assuming analysis justifies this, create a third PERSON entity containing the complete working hypothesis for this individual, manually selecting those accepted pieces of information from the first two "evidence" entities to put into the third PERSON, which we can refer to as a "hypothesis" person (or "conclusion" person providing we understand that these conclusions will probably be updated later).
The first method is employed by most users of GEDCOM today, and so must be present in BG to allow ease of conversion from GEDCOM to BG.
The second method can be referred to as the "evidence and conclusion model" (or "evidence and working hypothesis model"). It allows the separation of evidence and conclusions / hypotheses for better examination of that process.
It is clear that it will be possible
to stack persons in a tree so that a hypothesis person on one layer, later becomes an evidence person for a later hypothesis person.
The intention of the model is that (probably) all historical knowledge about a person be held against related entities and that this entity type should simply point to them.
To follow (this could be the appropriate place to save flags that control security of the IT application(s))
A PERSON may take evidence from 1 or more PERSONs
A PERSON may provide evidence for 1 PERSON
A PERSON may be characterised by 1 or more CHARACTERISTICs
A PERSON may be involved in 1 or more EVENTs
- This relationship (PERSON - EVENT) needs an optional attribute to define the role of that PERSON in that EVENT - e.g. a role of biological mother in a birth event)
A PERSON may belong to 1 or more GROUPs
- This relationship (PERSON - GROUP) needs an optional attribute to define the role of that PERSON in that GROUP)
More to follow re sources, citations, etc.