It is common for submitters to include an INDI representing themselves, and common for applications to use that information to inform the user interface. Support for storing that relationship should be included in the spec.
The proposal in a comment in #191 was to have a pointer substructure of SUBM pointing to the relevant INDI. Presumably this would have cardinality {0:1} to support the common user-interface deisngs that use this information. Two tags have been proposed for this: SUBM.INDI and SUBM.ALIA; we could also create a new tag for this case.
Note: this could also create a "root individual" pointer for applications that want that: the HEAD.SUBM points to the default submitter and the new structure points to the individual of that default submitter
It is common for submitters to include an INDI representing themselves, and common for applications to use that information to inform the user interface. Support for storing that relationship should be included in the spec.
The proposal in a comment in #191 was to have a pointer substructure of SUBM pointing to the relevant INDI. Presumably this would have cardinality
{0:1}
to support the common user-interface deisngs that use this information. Two tags have been proposed for this:SUBM
.INDI
andSUBM
.ALIA
; we could also create a new tag for this case.Extracted from a post by @fisharebest in https://github.com/FamilySearch/GEDCOM/discussions/191#discussioncomment-4743752