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

Merge exid-types.json with gedcom-registries #569

Open
tychonievich opened this issue Nov 12, 2024 · 4 comments · May be fixed by #576
Open

Merge exid-types.json with gedcom-registries #569

tychonievich opened this issue Nov 12, 2024 · 4 comments · May be fixed by #576

Comments

@tychonievich
Copy link
Collaborator

exid-types.json predates gedcom-registries, and has some overlap with it (in particular, it duplicates the semantic purpose of https://github.com/FamilySearch/GEDCOM-registries/tree/main/uri/exid-types). We should merge these two to avoid duplicate information, probably keeping the registries because it is more versatile.

@dthaler
Copy link
Collaborator

dthaler commented Nov 18, 2024

exid-types has: label, type, description, contact, change-controller, and reference.

These can be mapped to https://gedcom.io/terms/format fields as follows:

  • label -> label
  • type -> uri
  • description -> specification
  • contact -> contact
  • change-controller ("FamilySearch" for AFN/RIN/RFN) ->??? no current field
  • reference -> ??? no current field

@dthaler
Copy link
Collaborator

dthaler commented Nov 19, 2024

Filed FamilySearch/GEDCOM.io#220 in GEDCOM.io regarding change-controller and reference.

@tychonievich
Copy link
Collaborator Author

Adding one entry:

  • reference -> documentation

(see https://gedcom.io/terms/format)

@dthaler
Copy link
Collaborator

dthaler commented Dec 3, 2024

FamilySearch/GEDCOM-registries#102 added the data from exid-types.json to gedcom-registries. exid-types.json can now be deleted.

dthaler pushed a commit to dthaler/GEDCOM that referenced this issue Dec 3, 2024
dthaler pushed a commit to dthaler/GEDCOM that referenced this issue Dec 3, 2024
@dthaler dthaler linked a pull request Dec 3, 2024 that will close this issue
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 a pull request may close this issue.

2 participants