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 proposed changes to NAME structure #27

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tychonievich
Copy link

A draft of a replacement and extension to personal names based on FamilySearch/GEDCOM#473

A draft of a replacement and extension to personal names based on FamilySearch/GEDCOM#473
@tychonievich
Copy link
Author

I'm submitting this PR just to be hopefully helpful, and because PRs seem to be one of the easier ways for people to comment on and change parts of a document in github. I think this is a reasonable possiblity for moving forward, but am not trying to suggest that it is in any way perfect. Changes or even wholesale replacement with a different proposal are welcome.

@mother10
Copy link

mother10 commented Jul 4, 2024

I miss the fact you can combine TYPE's. Don't see a description for that.
Further, in Japan it seems titles can go behind a name.
https://en.wikipedia.org/wiki/Japanese_honorifics
https://www.familysearch.org/en/wiki/Japan_Naming_Customs

To denote a sequence TYPE could maybe have PARTFIRST, PARTLAST, PART1, PART2, PART3, PART4 etc.
So textual sequence like first and last, and numberd PART's for numbered sequence,
I used PARTFIRST, because maybe for other TYPE's there could also be a FIRST and LAST.
Because you can combine TYPEvalues, that could work.

CON: The TYPE list would be longer.

tychonievich added a commit to FamilySearch/GEDCOM that referenced this pull request Jul 31, 2024
This draft was created based on conversation with members of the names working group in fisharebest/gedcom-name#27 and #473. The text is mostly new, though, and may have failed to capture some elements of those conversations.

A separate v7.1 draft is anticipated once conversation on this draft stabilizes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants