Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft recommendation on ASSO #587

Merged
merged 3 commits into from
Jan 21, 2025
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions specification/gedcom-3-structures-1-organization.md
Original file line number Diff line number Diff line change
Expand Up @@ -213,6 +213,7 @@ for example, by consistently displaying the `HUSB` on the same side of the `WIFE
Family structures with more than 2 partners
may either use several `FAM` records
or use `ASSOCIATION_STRUCTURE`s to indicate additional partners.
`ASSO` should not be used for relationships that can be expressed using `HUSB`, `WIFE`, and/or `CHIL` instead.
tychonievich marked this conversation as resolved.
Show resolved Hide resolved

:::note
The `FAM` record will be revised in a future version to more fully express the diversity of human family relationships.
Expand Down Expand Up @@ -279,6 +280,7 @@ Details about those links are stored as substructures of the pointers in the ind
Other associations or relationships are represented by the `ASSO` (association) tag.
The person's relation or associate is the person being pointed to.
The association or relationship is stated by the value on the subordinate `ROLE` line.
`ASSO` should not be used for relationships that can be expressed using `FAMS` or `FAMC` instead.

:::example
The following example refers to 2 individuals, `@I1@` and `@I2@`,
Expand Down
Loading