-
Notifications
You must be signed in to change notification settings - Fork 20
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
Clarify that BURI does not imply burial #311
Conversation
While defined to mean "the event of disposing of the mortal remains of a person who has died" since 3.0, the tag name "burial" led this to be mis-interproeted. I think this resolves #309
Clearer definition of cremation
Use "burial" not "under ground"
Discussion in 6/1 GEDCOM Steering Committee: Use of
A third possibility would be to add another enumeration, rather than using TYPE , where Cremation is an enumeration value. This would also solve the localization problem, but would require changes to add the enumset and a tag to put it in. |
| `DEAT` | 3.0 | [Death](#death) | | | ||
| `BURI` | 3.0 | [Depositing remains](#depositing-remains) | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do find it confusing to see BURI in both line 17 and line 23, with two different definitions, both saying since 3.0. Perhaps line 17 shouldn't be BURI, since there was no tag specifically for burial, as opposed to depositing remains in general?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to mirror what we did with NATI
Co-authored-by: Dave Thaler <dthaler@microsoft.com>
While defined to mean "the event of disposing of the mortal remains of a person who has died" since 3.0, the tag name "burial" led this to be mis-interpreted.
I think this resolves #309