FAMILY_EVENT_DETAIL, AGE cardinality confusion

[Norwegian-Sardines]

I confused a little by the requirement of the AGE payload in the following FAMILY_EVENT_DETAIL:

n HUSB                                     {0:1}  g7:HUSB
  +1 AGE <Age>                             {1:1}  g7:AGE
     +2 PHRASE <Text>                      {0:1}  g7:PHRASE
n WIFE                                     {0:1}  g7:WIFE
  +1 AGE <Age>                             {1:1}  g7:AGE
     +2 PHRASE <Text>                      {0:1}  g7:PHRASE
n <<EVENT_DETAIL>>                         {0:1}

I see other places where the AGE is not required such as INDIVIDUAL_EVENT_DETAIL:

n <<EVENT_DETAIL>>                         {1:1}
n AGE <Age>                                {0:1}  g7:AGE
  +1 PHRASE <Text>                         {0:1}  g7:PHRASE

[WGroleau]

AGE should not be required in any kind of event because it may not be known—otherwise, to be compliant, we would have to put something silly like AGE < 999y

[tychonievich]

INDI.(event).AGE indicates the age of the individual at the time of the event. This is optional.

FAM.(event).HUSB.AGE indicates the age of the individual pointed to by FAM.HUSB at the time of the event, and similarly for FAM.(event).WIFE.AGE. These are also optional, but the optionality is indicated a level above the AGE. In both cases, the only purpose for the (event).HUSB/(event).WIFE structure is to indicate which partner has an age indicated; to omit the age of a partner at the time of the event, we omit the AGE and the HUSB/WIFE substructure of the event.

I agree that this is not very well described in the specification, and should be clarified.

[tychonievich]

Discussed in steering committee 18 MAR 2025

• The reason that HUSB.AGE/WIFE.AGE are {1:1} is because we cannot have structures with neither payloads nor substructures.
• Both of these cases (family and individual) are common in many kinds of sources, but the current spec requires interpretation to understand the comments listed in the previous comment.
• We should add clarifying information about the use of AGE to the 7.0 specification.