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.

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

Describe and link to YAML registry #104

Merged
merged 3 commits into from
Oct 19, 2023
Merged
Changes from all commits
Commits
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
10 changes: 10 additions & 0 deletions _pages/tools.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,16 @@ The following files are provided for testing.
| [spaces.ged](/testfiles/gedcom70/spaces.ged) | This file contains empty DATE and EVEN payloads, with and without spaces. |
| [voidptr.ged](/testfiles/gedcom70/voidptr.ged) | This file contains several @VOID@ references. |

## Extension Registry

As part of publishing each version of the [FamilySearch GEDCOM 7 specification](https://gedcom.io/specs/#familysearch-gedcom-version-7), a set of YAML files are generated describing each structure type, enumeration set, enumeration value, calendar, and month.
The format is [documented](/terms/format)
and served at the URIs documented in the specification (e.g., <https://gedcom.io/terms/v7/HEAD>).

The full set of YAML files, together with some synthesis information such as parsing metadata and lists of all structure types, can be found in the [GEDCOM-registries github repository](https://github.com/familysearch/gedcom-registries).
The GEDCOM-registries repository also hosts YAML files for extensions to the specification,
facilitating interoperability beyond the official specification.

## Other Development Tools

Other development, conversions tools and sample files will be posted here as they become available.
Expand Down