Merge main into v7.1 (#507)

* 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)

* Add the meaning of WWW (#480)

* Add the meaning of WWW

Previously (in both 5.5.1 and 7.0.0–7.0.14) `WWW` was defined only by the type of is payload. This is an attempt to fix that without invalidating any existing files.

Resolves #476

* Update specification/gedcom-3-structures-3-meaning.md

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

---------

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

* Remove substructure-specific extension wording (#481)

Resolves #478

* Add some possible additional family events for consideration (#479)

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

* Clarify no-FORM PLACs (#487)

Resolves #486

* Define "principle date" (#492)

* Define "principle date"

As pointed out in #488 and #490, the definition of DATE includes the vague phrase "principle date" which could use some clarification. This is my effort to provide that clarification.

Note, if competing definitions of the principle date in these contexts exists then this suggestion could be seen as backwards-incompatible and may need to be reworded as a non-normative recommendation or note. That said, I'm not aware of any conflicting definitions.

Resolves #490

* typos

* typo

* Update extracted files (#485)

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

* Clarify nickname (#482)

* Clarify nickname

Add additional clarification to nickname, explaining the word's meaning in English which is not shared by several European countries. See [this comment](#473 (comment)) and the rest of issue #473 for more on why this clarification is needed.

Although #473's discussion covers many more topics, if we go back to the title and first question in the issue I think this resolves #473.

* Update specification/gedcom-3-structures-3-meaning.md

* Change recommendation

* Update specification/gedcom-3-structures-3-meaning.md

* Update specification/gedcom-3-structures-3-meaning.md

---------

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

* Update extracted files (#501)

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

* Restore 3.0's definition of jurisdiction (#506)

* Restore 3.0's definition of jurisdiction

Restored the definition of "jurisdiction" that was present in version 3.0.

Resolved #496

* Update specification/gedcom-3-structures-3-meaning.md

Additional examples and less proscriptive text

---------

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]>

specification/gedcom-3-structures-3-meaning.md

@@ -1120,7 +1120,9 @@ A name given to a foundling orphan might be
 #### `PLAC` (Place) `g7:PLAC`
 
 The principal place in which the superstructure's subject occurred,
-represented as a [List] of jurisdictional entities in a sequence from the lowest to the highest jurisdiction.
+represented as a [List] of jurisdictional entities in a sequence from the lowest to the highest jurisdiction,
+where "jurisdiction" includes units in a political, ecclesiastical, and geographical hierarchies
+and may include units as large as a nation or as specific as a building, farm, or cemetery.
 As with other lists, the jurisdictions are separated by commas.
 Any jurisdiction's name that is missing is still accounted for by an empty string in the list.