Replace exid-types.json with gedcom-registries (#576)

Fixes #569 Signed-off-by: Dave Thaler <[email protected]> Co-authored-by: Dave Thaler <[email protected]>
FamilySearch · Dec 17, 2024 · 5c2eb60 · 5c2eb60
1 parent 10a53c4
commit 5c2eb60
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 127 deletions.
diff --git a/README.md b/README.md
@@ -11,7 +11,6 @@ If you are looking for FamilySearch's GEDCOM 5.5.1 Java parser, which previously
 ## Repository structure
 
 - [`changelog.md`](changelog.md) is a running log of major changes made to the specification.
-- [`exid-types.json`](exid-types.json) is a JSON file containing registered EXID-TYPE values.
 - [`specification/`](specification/) contains the FamilySearch GEDCOM specification:
 	- `specification/gedcom-`number`-`title`.md` files are the source documents used to define the FamilySearch GEDCOM specification. It is written in pandoc-flavor markdown and is intended to be more easily written than read. It is split into several files (ordered by the integer in their names) to facilitate comparing files.
 	- In a local check-out, this is also where the build scripts place rendered files `gedcom.html` and `gedcom.pdf`; see [releases](releases/latest) for a pre-rendered copy of these.

diff --git a/exid-types.json b/exid-types.json
diff --git a/specification/gedcom-3-structures-3-meaning.md b/specification/gedcom-3-structures-3-meaning.md
@@ -1585,18 +1585,10 @@ If the authority maintains stable URLs for each identifier it issues,
 it is recommended that the `TYPE` payload be selected such that appending the `EXID` payload to it yields that URL.
 However, this is not required and a different URI for the set of issued identifiers may be used instead.
 
-Registered URIs are listed in [exid-types.json](https://github.com/FamilySearch/GEDCOM/blob/main/exid-types.json), where fields include:
-
-* "label": a short string suitable for display in a user interface.
-* "type": The URI representing the authority issuing the `EXID`.
-* "description": A description of the meaning of the `EXID`.
-* "contact": A contact email address for the person or organization registering the URI.
-* "change-controller": The name or contact information for the person or organization authorized to update the registration.
-* "fragment": If present, indicates a short string that can be used as a label for a fragment identifier appended to the URI.  If absent, indicates that fragment identifiers are not used with the URI.
-* "reference": A URL with more information about the meaning of the `EXID`. Such information should explain the uniqueness and expected durability of the identifier.
+Registered URIs are listed in the [exid-types registry](https://github.com/FamilySearch/GEDCOM-registries/tree/main/uri/exid-types), where fields are defined using the [YAML file format](https://gedcom.io/terms/format).
 
 Additional type URIs can be registered by filing a
-[GitHub pull request](https://github.com/FamilySearch/GEDCOM/pulls).
+[GitHub pull request](https://github.com/FamilySearch/GEDCOM-registries/pulls).
 
 #### `UID` (Unique Identifier) `g7:UID`