exid-types YAML file format issues

[dthaler]

https://github.com/FamilySearch/GEDCOM-registries/tree/main/uri/exid-types files have the following YAML fields today: lang, type, uri, specification, and (optionally) contact.

The main README file at https://github.com/FamilySearch/GEDCOM-registries says:

The repository is primarily made up of YAML files organized as documented at https://gedcom.io/terms/format. ... YAML files are placed in this repository in subdirectories type/subtype/name.yaml where ...

Issue: https://github.com/FamilySearch/GEDCOM/issues/569 proposes moving data out of exid-types.json. 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 -> documentation fragment -> ??? no current field

So should we add change-controller and fragment to https://gedcom.io/terms/format ?

[dthaler]

Discussion during GEDCOM Steering Committee meeting 19 NOV 2024:

• Fragment in the JSON contains a label for the fragment ID meaning
• We should add fragment and change-controller to the format file as optional fields