-
Notifications
You must be signed in to change notification settings - Fork 3
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
Extension that adds GEDCOM-X names to GEDCOM 7 #6
base: main
Are you sure you want to change the base?
Conversation
Need more explanations. I see a conflict to standard tags as GIVN, SURN, SPFX, NSFX, and to NAME.TYPE with several standardized and possible extended payloads. |
uri: https://tychonievich.github.io/gx-g7-names#hidden | ||
|
||
extension tags: | ||
- _NPQ_HIDDEN |
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.
So this is not part of GEDCOM-X? (not _GX_HIDDEN
)
If so, then perhaps the PR title isn't quite right.
|
||
type: enumeration set | ||
|
||
uri: https://tychonievich.github.io/gx-g7-names#qualifiers |
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.
Who should the contact
be for this YAML file? The GEDCOM X spec maintainers? Luther personally?
type: structure | ||
|
||
uri: https://tychonievich.github.io/gx-g7-names#name-part-qualifier | ||
|
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.
add contact
field
Co-authored-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
I wrote this extension as a proof of concept some time ago, but since then have started using in my ongoing work on extracting GEDCOM 7 files from the FamilySearch Family Tree API, and hence expect it to start appearing in files I create that other applications might encounter. Registering in the extension registries thus seems useful.