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

Possibly change URI of some FamilySearch EXID.TYPEs #106

Open
tychonievich opened this issue Dec 17, 2024 · 3 comments
Open

Possibly change URI of some FamilySearch EXID.TYPEs #106

tychonievich opened this issue Dec 17, 2024 · 3 comments

Comments

@tychonievich
Copy link
Collaborator

Copied from FamilySearch/GEDCOM#567

Standard recommends to have a EXID.TYPE paylod which by appending the EXID payload the full url to find the webpage in the refrenced extrenal system. I wonder why this is not done in the examples for FAmily Search systems, like the place system. In the defining exid-types.json we find:
https://gedcom.io/exid-type/FamilySearch-PlaceId

This cannot be expanded to an valid url. It should be:
https://www.familysearch.org/research/places/?focusedId=

??!!

@dthaler
Copy link
Collaborator

dthaler commented Jan 7, 2025

Discussion in GEDCOM Steering Committee 7 JAN 2025:

  • Will find out if FamilySearch can create stable ARK URLs for place records (both place-sets and place instance)

@dthaler
Copy link
Collaborator

dthaler commented Feb 25, 2025

@lynchrs3 any update?

@dthaler
Copy link
Collaborator

dthaler commented Feb 25, 2025

The GEDCOM file format can express URIs without needing any new extensions or changes to the file format. To store a persistent place ID or place set ID, we need to be able to express it as a persistent URI. Hence the request for ARK URIs for place id and place set id.

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

No branches or pull requests

2 participants