From 0c70d5f0f053379c17391ec1c74c58ca94fa83d1 Mon Sep 17 00:00:00 2001 From: Dave Thaler Date: Tue, 3 Dec 2024 12:20:16 -0800 Subject: [PATCH] Replace exid-types.json with gedcom-registries Fixes #569 Signed-off-by: Dave Thaler --- README.md | 1 - exid-types.json | 116 ------------------ .../gedcom-3-structures-3-meaning.md | 12 +- 3 files changed, 2 insertions(+), 127 deletions(-) delete mode 100644 exid-types.json diff --git a/README.md b/README.md index 45e8eaa9..f6893b50 100644 --- 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 deleted file mode 100644 index 267ce7e4..00000000 --- a/exid-types.json +++ /dev/null @@ -1,116 +0,0 @@ -[ - { - "label": "AFN", - "type": "https://gedcom.io/terms/v7/AFN", - "description": "Ancestral File Number", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FamilySearch", - "reference": "https://gedcom.io/migrate/#afn-rfn-rin" - }, - { - "label": "RIN", - "type": "https://gedcom.io/terms/v7/RIN", - "description": "Automated Record ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FamilySearch", - "fragment": "Source System", - "reference": "https://gedcom.io/migrate/#afn-rfn-rin" - }, - { - "label": "RFN", - "type": "https://gedcom.io/terms/v7/RFN", - "description": "Permanent Record ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FamilySearch", - "fragment": "Resource ID", - "reference": "https://gedcom.io/migrate/#afn-rfn-rin" - }, - { - "label": "FamilySearch Memory ID", - "type": "https://gedcom.io/exid-type/FamilySearch-MemoryId", - "description": "FamilySearch Memory ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FamilySearch", - "reference": "https://gedcom.io/exid-type/FamilySearch-MemoryId" - }, - { - "label": "FamilySearch Person ID", - "type": "https://gedcom.io/exid-type/FamilySearch-PersonId", - "description": "FamilySearch Person ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FamilySearch", - "reference": "https://gedcom.io/exid-type/FamilySearch-PersonId" - }, - { - "label": "FamilySearch Place ID", - "type": "https://gedcom.io/exid-type/FamilySearch-PlaceId", - "description": "FamilySearch Place ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FamilySearch", - "reference": "https://gedcom.io/exid-type/FamilySearch-PlaceId" - }, - { - "label": "FamilySearch Source Description ID", - "type": "https://gedcom.io/exid-type/FamilySearch-SourceDescriptionId", - "description": "FamilySearch Source Description ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FamilySearch", - "reference": "https://gedcom.io/exid-type/FamilySearch-SourceDescriptionId" - }, - { - "label": "FamilySearch User ID", - "type": "https://gedcom.io/exid-type/FamilySearch-UserId", - "description": "FamilySearch User ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FamilySearch", - "reference": "https://gedcom.io/exid-type/FamilySearch-UserId" - }, - { - "label": "FindAGrave Memorial ID", - "type": "https://www.findagrave.com/memorial", - "description": "FindAGrave Memorial ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FindAGrave.com", - "reference": "https://support.findagrave.com/s/article/Memorial-Search" - }, - { - "label": "FindAGrave Cemetery ID", - "type": "https://www.findagrave.com/cemetery", - "description": "FindAGrave Cemetery ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "FindAGrave.com", - "reference": "https://support.findagrave.com/s/article/Cemetery-Search" - }, - { - "label": "BillionGraves Grave ID", - "type": "https://www.billiongraves.com/grave/name/", - "description": "BillionGraves Grave ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "BillionGraves.com", - "reference": "https://billiongraves.com/search" - }, - { - "label": "BillionGraves Cemetery ID", - "type": "https://www.billiongraves.com/cemetery/name/", - "description": "BillionGraves Cemetery ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "BillionGraves.com", - "reference": "https://billiongraves.com/search/cemetery" - }, - { - "label": "WikiTree Person ID", - "type": "https://www.wikitree.com/wiki/", - "description": "WikiTree Person ID", - "contact": "GEDCOM@familysearch.org", - "change-controller": "wikitree.com", - "reference": "https://www.wikitree.com/wiki/Help:WikiTree_ID" - }, - { - "label": "GOV Historic Gazeteer ID", - "type": "http://gov.genealogy.net/", - "description": "Historic Gazeteer place ID", - "contact": "gov-support@genealogy.net", - "change-controller": "CompGen", - "reference": "https://wiki.genealogy.net/GOV" - } -] diff --git a/specification/gedcom-3-structures-3-meaning.md b/specification/gedcom-3-structures-3-meaning.md index 8e00f23c..e9a3bba6 100644 --- 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`