The table below identifies some of the main event-types and event-subtypes of interest. The default in both instances is ‘Unknown’. The table also indicates typical associations of roles with event-type.
The predefined event-types are ones for which direct evidence is likely to be available. STEMMA deliberately makes it easy to define new event-types and subtypes, partly so that custom higher-level entities can be defined for creating hierarchical events. The Persons associated with an Event are ones mentioned in the evidence, and that usually means they were present but not always. The Status Property can be used for implied/absent/deceased persons (e.g. in marriage).
The values for event-subtype are subordinate to an event-type. In software terms, the event-subtype may be represented as a child of the event-type, e.g. Union.Marriage. The reason this was not carried through to the event-role (e.g. Union.Marriage.Bride) was due to the number of combinations.
The group of roles listed below that identify family relationships are usually relative to, and hence subordinate to, another role. For instance, Bride.Mother and Groom.Father. If there is no prefix, and the context doesn’t make it obvious (see table below), then they are assumed to be relative to Head or Subject – one of which must be present and unique.
A description of how custom event-types and roles are accommodated may be found at Extended Vocabularies. Note that Unions involving more than two people, or people of the same sex, can be determined by looking at the Roles involved. They are not given a specific event-type.
Q: Do we need a recognised event-type for a gender reassignment procedure? The <Sex> element describes the “birth sex” (however indeterminate) but we still need to be able to such a procedure.
Q: Should we handle change of slave ownership under the event-type ‘Responsibility’?