search

FamilySearch / GEDCOM.io

Files for the GEDCOM.io website
2 stars 5 forks source link

Extension YAML file location #95

Closed dthaler closed 6 months ago

dthaler commented 11 months ago

When an extension structure is being defined, should it be hosted on an external website or hosted in the gedcom.io repository or both? Currently I don't think there is any guidance and we should probably provide some guidance.

A documented extension tag needs a URI, and we say that URI should be a URL, ideally resolvable to the YAML description (see https://github.com/FamilySearch/GEDCOM/issues/330 and https://github.com/FamilySearch/GEDCOM/pull/350).

If the URI points to an external website, then the question of durability of the URL arises (what happens if the external website goes away in 10 years?)

tychonievich commented 11 months ago

We added the URL recommendation before we had the registry. I think we should change that recommendation to be the registry first, with URI-is-URL as a backup.

dthaler commented 11 months ago

Discussion 9/28/2023 in GEDCOM meeting: We want to recommend the registry be the place extensions are hosted, since they have more durability and discoverability across applications. This should be done in the GEDCOM, making the use of the registry be a recommendation, not just a "such as". @tychonievich will add an index of URI to YAML URL to the GEDCOM-registries/generated_files section

tychonievich commented 10 months ago

@tychonievich will add an index of URI to YAML URL to the GEDCOM-registries/generated_files section

Added in https://github.com/FamilySearch/GEDCOM-registries/commit/361ba5f95eaf99a0a29bdce0501c45b86368b75f