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.

Sign up for GitHub

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

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

Merged
merged 1 commit into from
Dec 17, 2024
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
116 changes: 0 additions & 116 deletions exid-types.json
View file
Open in desktop

This file was deleted.

12 changes: 2 additions & 10 deletions specification/gedcom-3-structures-3-meaning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`

Expand Down
Loading