Merge main into v7.1 (#475)

* Update extracted files (#443)

Co-authored-by: Luther Tychonievich <[email protected]>

* decribe branches in README.md (#451)

* decribe branches in README.md

* Update README.md

Co-authored-by: Dave Thaler <[email protected]>

---------

Co-authored-by: Dave Thaler <[email protected]>

* Add contact info to auto-generated YAML files (#454)

Per discussion in steering committee meeting 2024-04-04, using <https://gedcom.io/community/> as the contact info because that page describes various means of contact and is expected to be updated from time to time as means of contact change.

* Add CI/CD workflow to validate YAML files (#457)

* Add CI/CD workflow to validate YAML files

Signed-off-by: Dave Thaler <[email protected]>

* Update YAML files to resolve yamllint errors

Signed-off-by: Dave Thaler <[email protected]>

* Update .github/workflows/validate-yaml.yml

* Update .github/workflows/validate-yaml.yml

---------

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>

* yamllint is recursive (#460)

Avoid validating the same file multiple times

https://github.com/FamilySearch/GEDCOM/actions/runs/8838156091/job/24268618756
under "Validate YAML" shows multiple occurences of files under
.github/workflow since .github and .github/workflow are both passed to
yamllint

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>

* Add Separation event (#459)

* Add Separation event

* Remove FS API reference

* Fix workflow (#462)

https://github.com/FamilySearch/GEDCOM/actions/runs/9044561163 failure
reports: "The workflow is not valid.
.github/workflows/propagate-main-to-v7.1.yml (Line: 18, Col: 3): The
identifier 'merge-to-v7.1' is invalid. IDs may only contain alphanumeric
characters, '_', and '-'. IDs must start with a letter or '_' and and
must be less than 100 characters."

This PR therefore removes the '.' that is causing the failure.

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>

* Track request for Separated as a future FAM attribute (#469)

Related to PR #459 which tracks the separation event

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>

* Fix reference to FilePath data type (#466)

Fixes #465

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>

* Typo in README.md (#472)

---------

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Luther Tychonievich <[email protected]>
Co-authored-by: Luther Tychonievich <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
Co-authored-by: Christopher Horn <[email protected]>
Co-authored-by: Dylan Stephano-Shachter <[email protected]>

README.md

@@ -13,7 +13,7 @@ If you are looking for FamilySearch's GEDCOM 5.5.1 Java parser, which previously
 - [`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 splint into several files (ordered by the integer in their names) to facilitate comparing files.
+	- `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.
 	- [`specification/terms/`](specification/terms/)
 		- YAML files to be served in the <https://gedcom.io/terms/v7/> namespace, augmenting those automatically extracted from the specification itself by [`build/uri-def.py`](build/uri-def.py).