From 9a5cf85166223595154ab2452a17650a5eb7c918 Mon Sep 17 00:00:00 2001 From: Luther Tychonievich Date: Tue, 20 Aug 2024 11:52:14 -0500 Subject: [PATCH] version 7.0.15 release --- _pages/changelog.md | 52 +++- _pages/tag-def/ABBR.md | 2 + _pages/tag-def/ADDR.md | 41 +-- _pages/tag-def/ADOP-FAMC.md | 12 +- _pages/tag-def/ADOP.md | 8 +- _pages/tag-def/ADR1.md | 15 +- _pages/tag-def/ADR2.md | 15 +- _pages/tag-def/ADR3.md | 15 +- _pages/tag-def/AGE.md | 6 +- _pages/tag-def/AGNC.md | 11 +- _pages/tag-def/ALIA.md | 20 +- _pages/tag-def/ANCI.md | 6 +- _pages/tag-def/ANUL.md | 4 +- _pages/tag-def/ASSO.md | 41 +-- _pages/tag-def/AUTH.md | 8 +- _pages/tag-def/BAPL.md | 8 +- _pages/tag-def/BAPM.md | 6 +- _pages/tag-def/BARM.md | 4 +- _pages/tag-def/BASM.md | 8 +- _pages/tag-def/BIRT.md | 4 +- _pages/tag-def/BLES.md | 4 +- _pages/tag-def/BURI.md | 16 +- _pages/tag-def/CALN.md | 8 +- _pages/tag-def/CAST.md | 10 +- _pages/tag-def/CAUS.md | 2 + _pages/tag-def/CHAN.md | 13 +- _pages/tag-def/CHIL.md | 6 +- _pages/tag-def/CHR.md | 4 +- _pages/tag-def/CHRA.md | 4 +- _pages/tag-def/CITY.md | 5 +- _pages/tag-def/CONF.md | 4 +- _pages/tag-def/CONL.md | 6 +- _pages/tag-def/CONT.md | 8 +- _pages/tag-def/COPR.md | 6 +- _pages/tag-def/CORP.md | 6 +- _pages/tag-def/CREA.md | 10 +- _pages/tag-def/CREM.md | 4 +- _pages/tag-def/CROP.md | 30 ++- _pages/tag-def/CTRY.md | 4 +- _pages/tag-def/DATA-EVEN-DATE.md | 4 +- _pages/tag-def/DATA-EVEN.md | 10 +- _pages/tag-def/DATA.md | 9 +- _pages/tag-def/DATE-exact.md | 4 +- _pages/tag-def/DATE.md | 29 ++- _pages/tag-def/DEAT.md | 4 +- _pages/tag-def/DESI.md | 6 +- _pages/tag-def/DEST.md | 4 +- _pages/tag-def/DIV.md | 4 +- _pages/tag-def/DIVF.md | 4 +- _pages/tag-def/DSCR.md | 4 +- _pages/tag-def/EDUC.md | 4 +- _pages/tag-def/EMAIL.md | 16 +- _pages/tag-def/EMIG.md | 6 +- _pages/tag-def/ENDL.md | 10 +- _pages/tag-def/ENGA.md | 4 +- _pages/tag-def/EXID-TYPE.md | 42 +-- _pages/tag-def/EXID.md | 14 +- _pages/tag-def/FAM-CENS.md | 10 +- _pages/tag-def/FAM-EVEN.md | 5 +- _pages/tag-def/FAM-FACT.md | 5 +- _pages/tag-def/FAM-HUSB.md | 4 +- _pages/tag-def/FAM-NCHI.md | 5 +- _pages/tag-def/FAM-RESI.md | 9 +- _pages/tag-def/FAM-WIFE.md | 4 +- _pages/tag-def/FAMC-ADOP.md | 4 +- _pages/tag-def/FAMC-STAT.md | 6 +- _pages/tag-def/FAMC.md | 2 + _pages/tag-def/FAMS.md | 5 +- _pages/tag-def/FAX.md | 6 +- _pages/tag-def/FCOM.md | 6 +- _pages/tag-def/FILE-TRAN.md | 60 +++-- _pages/tag-def/FILE.md | 48 +--- _pages/tag-def/FORM.md | 4 +- _pages/tag-def/GEDC-VERS.md | 9 +- _pages/tag-def/GEDC.md | 6 +- _pages/tag-def/GIVN.md | 2 + _pages/tag-def/GRAD.md | 4 +- _pages/tag-def/HEAD-DATE.md | 4 +- _pages/tag-def/HEAD-LANG.md | 33 ++- _pages/tag-def/HEAD-PLAC-FORM.md | 4 +- _pages/tag-def/HEAD-PLAC.md | 4 +- _pages/tag-def/HEAD-SOUR-DATA.md | 8 +- _pages/tag-def/HEAD-SOUR.md | 10 +- _pages/tag-def/HEAD.md | 27 +- _pages/tag-def/HEIGHT.md | 23 +- _pages/tag-def/HUSB.md | 4 +- _pages/tag-def/IDNO.md | 10 +- _pages/tag-def/IMMI.md | 4 +- _pages/tag-def/INDI-CENS.md | 10 +- _pages/tag-def/INDI-EVEN.md | 29 ++- _pages/tag-def/INDI-FACT.md | 27 +- _pages/tag-def/INDI-FAMC.md | 8 +- _pages/tag-def/INDI-NAME.md | 47 ++-- _pages/tag-def/INDI-NCHI.md | 5 +- _pages/tag-def/INDI-RELI.md | 4 +- _pages/tag-def/INDI-RESI.md | 31 ++- _pages/tag-def/INDI-TITL.md | 4 +- _pages/tag-def/INIL.md | 16 +- _pages/tag-def/LANG.md | 67 +++-- _pages/tag-def/LATI.md | 12 +- _pages/tag-def/LEFT.md | 6 +- _pages/tag-def/LONG.md | 16 +- _pages/tag-def/MAP.md | 13 +- _pages/tag-def/MARB.md | 4 +- _pages/tag-def/MARC.md | 10 +- _pages/tag-def/MARL.md | 4 +- _pages/tag-def/MARR.md | 8 +- _pages/tag-def/MARS.md | 10 +- _pages/tag-def/MEDI.md | 30 ++- _pages/tag-def/MIME.md | 77 +++--- _pages/tag-def/NAME-TRAN.md | 52 ++-- _pages/tag-def/NAME-TYPE.md | 4 +- _pages/tag-def/NAME.md | 4 +- _pages/tag-def/NATI.md | 6 +- _pages/tag-def/NATU.md | 4 +- _pages/tag-def/NICK.md | 20 +- _pages/tag-def/NMR.md | 4 +- _pages/tag-def/NO-DATE.md | 6 +- _pages/tag-def/NO.md | 39 ++- _pages/tag-def/NOTE-TRAN.md | 71 ++--- _pages/tag-def/NOTE.md | 13 +- _pages/tag-def/NPFX.md | 5 +- _pages/tag-def/NSFX.md | 6 +- _pages/tag-def/OBJE.md | 12 +- _pages/tag-def/OCCU.md | 4 +- _pages/tag-def/ORDN.md | 4 +- _pages/tag-def/PAGE.md | 47 ++-- _pages/tag-def/PEDI.md | 4 +- _pages/tag-def/PHON.md | 14 +- _pages/tag-def/PHRASE.md | 86 ++++-- _pages/tag-def/PLAC-FORM.md | 16 +- _pages/tag-def/PLAC-TRAN.md | 56 ++-- _pages/tag-def/PLAC.md | 80 +++--- _pages/tag-def/POST.md | 4 +- _pages/tag-def/PROB.md | 4 +- _pages/tag-def/PROP.md | 7 +- _pages/tag-def/PUBL.md | 14 +- _pages/tag-def/QUAY.md | 13 +- _pages/tag-def/REFN.md | 12 +- _pages/tag-def/RELI.md | 10 +- _pages/tag-def/REPO.md | 16 +- _pages/tag-def/RESN.md | 16 +- _pages/tag-def/RETI.md | 8 +- _pages/tag-def/ROLE.md | 48 ++-- _pages/tag-def/SCHMA.md | 6 +- _pages/tag-def/SDATE.md | 18 +- _pages/tag-def/SEX.md | 4 +- _pages/tag-def/SLGC.md | 9 +- _pages/tag-def/SLGS.md | 13 +- _pages/tag-def/SNOTE.md | 6 +- _pages/tag-def/SOUR-DATA.md | 4 +- _pages/tag-def/SOUR-EVEN.md | 13 +- _pages/tag-def/SOUR.md | 40 +-- _pages/tag-def/SPFX.md | 2 + _pages/tag-def/SSN.md | 8 +- _pages/tag-def/STAE.md | 6 +- _pages/tag-def/SUBM-LANG.md | 5 +- _pages/tag-def/SUBM.md | 6 +- _pages/tag-def/SURN.md | 2 + _pages/tag-def/TAG.md | 6 +- _pages/tag-def/TEMP.md | 8 +- _pages/tag-def/TEXT.md | 12 +- _pages/tag-def/TIME.md | 4 +- _pages/tag-def/TITL.md | 32 ++- _pages/tag-def/TOP.md | 6 +- _pages/tag-def/TRLR.md | 6 +- _pages/tag-def/TYPE.md | 42 +-- _pages/tag-def/UID.md | 38 +-- _pages/tag-def/VERS.md | 2 + _pages/tag-def/WIDTH.md | 5 +- _pages/tag-def/WIFE.md | 4 +- _pages/tag-def/WILL.md | 10 +- _pages/tag-def/WWW.md | 16 +- _pages/tag-def/cal-FRENCH_R.md | 43 +-- _pages/tag-def/cal-GREGORIAN.md | 42 +-- _pages/tag-def/cal-HEBREW.md | 78 +++--- _pages/tag-def/cal-JULIAN.md | 25 +- _pages/tag-def/enum-0.md | 2 + _pages/tag-def/enum-1.md | 6 +- _pages/tag-def/enum-2.md | 2 + _pages/tag-def/enum-3.md | 2 + _pages/tag-def/enum-ADOP-HUSB.md | 4 +- _pages/tag-def/enum-ADOP-WIFE.md | 4 +- _pages/tag-def/enum-ADOPTED.md | 2 + _pages/tag-def/enum-AKA.md | 2 + _pages/tag-def/enum-AUDIO.md | 2 + _pages/tag-def/enum-BIC.md | 4 +- _pages/tag-def/enum-BIRTH.md | 2 + _pages/tag-def/enum-BOOK.md | 2 + _pages/tag-def/enum-BOTH.md | 4 +- _pages/tag-def/enum-CANCELED.md | 4 +- _pages/tag-def/enum-CARD.md | 2 + _pages/tag-def/enum-CHALLENGED.md | 6 +- _pages/tag-def/enum-CHIL.md | 2 + _pages/tag-def/enum-CHILD.md | 8 +- _pages/tag-def/enum-CLERGY.md | 4 +- _pages/tag-def/enum-COMPLETED.md | 6 +- _pages/tag-def/enum-CONFIDENTIAL.md | 2 + _pages/tag-def/enum-DISPROVEN.md | 6 +- _pages/tag-def/enum-DNS.md | 4 +- _pages/tag-def/enum-DNS_CAN.md | 4 +- _pages/tag-def/enum-ELECTRONIC.md | 2 + _pages/tag-def/enum-EXCLUDED.md | 6 +- _pages/tag-def/enum-F.md | 2 + _pages/tag-def/enum-FATH.md | 4 +- _pages/tag-def/enum-FICHE.md | 2 + _pages/tag-def/enum-FILM.md | 2 + _pages/tag-def/enum-FOSTER.md | 2 + _pages/tag-def/enum-FRIEND.md | 2 + _pages/tag-def/enum-GODP.md | 2 + _pages/tag-def/enum-HUSB.md | 4 +- _pages/tag-def/enum-IMMIGRANT.md | 2 + _pages/tag-def/enum-INFANT.md | 6 +- _pages/tag-def/enum-LOCKED.md | 2 + _pages/tag-def/enum-M.md | 2 + _pages/tag-def/enum-MAGAZINE.md | 2 + _pages/tag-def/enum-MAIDEN.md | 2 + _pages/tag-def/enum-MANUSCRIPT.md | 2 + _pages/tag-def/enum-MAP.md | 2 + _pages/tag-def/enum-MARRIED.md | 2 + _pages/tag-def/enum-MOTH.md | 4 +- _pages/tag-def/enum-MULTIPLE.md | 4 +- _pages/tag-def/enum-NEWSPAPER.md | 2 + _pages/tag-def/enum-NGHBR.md | 2 + _pages/tag-def/enum-OFFICIATOR.md | 2 + _pages/tag-def/enum-OTHER.md | 4 +- _pages/tag-def/enum-PARENT.md | 2 + _pages/tag-def/enum-PHOTO.md | 2 + _pages/tag-def/enum-PRE_1970.md | 4 +- _pages/tag-def/enum-PRIVACY.md | 10 +- _pages/tag-def/enum-PROFESSIONAL.md | 2 + _pages/tag-def/enum-PROVEN.md | 2 + _pages/tag-def/enum-SEALING.md | 2 + _pages/tag-def/enum-SPOU.md | 2 + _pages/tag-def/enum-STILLBORN.md | 2 + _pages/tag-def/enum-SUBMITTED.md | 6 +- _pages/tag-def/enum-TOMBSTONE.md | 2 + _pages/tag-def/enum-U.md | 2 + _pages/tag-def/enum-UNCLEARED.md | 6 +- _pages/tag-def/enum-VIDEO.md | 2 + _pages/tag-def/enum-WIFE.md | 4 +- _pages/tag-def/enum-WITN.md | 2 + _pages/tag-def/enum-X.md | 2 + _pages/tag-def/enumset-ADOP.md | 2 + _pages/tag-def/enumset-EVEN.md | 5 +- _pages/tag-def/enumset-EVENATTR.md | 17 +- _pages/tag-def/enumset-FAMC-STAT.md | 2 + _pages/tag-def/enumset-MEDI.md | 2 + _pages/tag-def/enumset-NAME-TYPE.md | 2 + _pages/tag-def/enumset-PEDI.md | 2 + _pages/tag-def/enumset-QUAY.md | 2 + _pages/tag-def/enumset-RESN.md | 2 + _pages/tag-def/enumset-ROLE.md | 2 + _pages/tag-def/enumset-SEX.md | 2 + _pages/tag-def/enumset-ord-STAT.md | 2 + _pages/tag-def/month-AAV.md | 2 + _pages/tag-def/month-ADR.md | 2 + _pages/tag-def/month-ADS.md | 2 + _pages/tag-def/month-APR.md | 2 + _pages/tag-def/month-AUG.md | 2 + _pages/tag-def/month-BRUM.md | 2 + _pages/tag-def/month-COMP.md | 2 + _pages/tag-def/month-CSH.md | 2 + _pages/tag-def/month-DEC.md | 2 + _pages/tag-def/month-ELL.md | 2 + _pages/tag-def/month-FEB.md | 2 + _pages/tag-def/month-FLOR.md | 2 + _pages/tag-def/month-FRIM.md | 2 + _pages/tag-def/month-FRUC.md | 2 + _pages/tag-def/month-GERM.md | 2 + _pages/tag-def/month-IYR.md | 2 + _pages/tag-def/month-JAN.md | 2 + _pages/tag-def/month-JUL.md | 2 + _pages/tag-def/month-JUN.md | 2 + _pages/tag-def/month-KSL.md | 2 + _pages/tag-def/month-MAR.md | 2 + _pages/tag-def/month-MAY.md | 2 + _pages/tag-def/month-MESS.md | 2 + _pages/tag-def/month-NIVO.md | 2 + _pages/tag-def/month-NOV.md | 2 + _pages/tag-def/month-NSN.md | 2 + _pages/tag-def/month-OCT.md | 2 + _pages/tag-def/month-PLUV.md | 2 + _pages/tag-def/month-PRAI.md | 2 + _pages/tag-def/month-SEP.md | 2 + _pages/tag-def/month-SHV.md | 2 + _pages/tag-def/month-SVN.md | 2 + _pages/tag-def/month-THER.md | 2 + _pages/tag-def/month-TMZ.md | 2 + _pages/tag-def/month-TSH.md | 2 + _pages/tag-def/month-TVT.md | 2 + _pages/tag-def/month-VEND.md | 2 + _pages/tag-def/month-VENT.md | 2 + _pages/tag-def/ord-STAT.md | 4 +- _pages/tag-def/record-FAM.md | 86 +++--- _pages/tag-def/record-INDI.md | 58 +++-- _pages/tag-def/record-OBJE.md | 16 +- _pages/tag-def/record-REPO.md | 18 +- _pages/tag-def/record-SNOTE.md | 58 +++-- _pages/tag-def/record-SOUR.md | 29 ++- _pages/tag-def/record-SUBM.md | 13 +- _pages/tag-def/type-Age.md | 80 +++--- _pages/tag-def/type-Date.md | 162 ++++++------ _pages/tag-def/type-Enum.md | 51 ++-- _pages/tag-def/type-List.md | 51 ++-- _pages/tag-def/type-Name.md | 33 +-- _pages/tag-def/type-Time.md | 36 ++- specifications/FamilySearchGEDCOMv7.html | 316 +++++++++++++++-------- specifications/FamilySearchGEDCOMv7.pdf | Bin 1964510 -> 2007647 bytes 309 files changed, 2478 insertions(+), 1476 deletions(-) diff --git a/_pages/changelog.md b/_pages/changelog.md index ad68639d..22001c8a 100644 --- a/_pages/changelog.md +++ b/_pages/changelog.md @@ -4,6 +4,46 @@ permalink: /changelog/ sidebar: nav: "changelog" --- +# Version 7.0.15 + +- Clarified that `FORM`.`MEDI` describe the original medium, not the derived medium, when used with derived files. + +- Clarified the meaning of the `WWW` structure, which previously only mentioned its payload datatype. + +- Clarified `PLAC` to both define "jurisdiction" and document its meaning in the absence of a `PLAC`.`FORM`. + +- Clarified what the term "principal date" means in different contexts in the definition of `g7:DATE`. + +- Updated `NICK` to no longer suggest that some names are "improper" and to document the diversity of views in what a "nickname" is. + +- Removed confusing reference to superstructures in the meaning of a documented extension tag. + +- Added ABNF for more datatypes and updated DIGIT's capitalization for compatibility with more ABNF toolchains. + +- Various typo corrections. + + +# Version 7.0.14 + +- Recommend that `NO XYZ` only be used where `XYZ` is permitted (its meaning is undefined elsewhere). + +- Recommend that a given `INDI` have at most one `FAMC` pointing to a given `FAM` (having more than one has unclear meaning); and likewise that a given `FAM` have at most one `CHIL` pointing to a given `INDI` (having more than one indicates nonsensical birth order). + +- Refactor presentation of local files to better match related RFCs and only make implementable constraints, and to use its own `` datatype instead of ``. This does not change `FILE` payloads, only how they are specified to better support automated tooling. + +- Refactor the enumeration tags `CENS`, `EVEN`, `FACT`, `NCHI`, and `RESI` to have different URIs, removing a previous parsing ambiguity. This changes neither the set of tags permitted in any enumeration set nor those tags' meaning, only how they are specified to better support automated tooling. + +- Deprecate extension-defined substructures using `stdTag` in a way incompatible with any standard definition of that tag. The now-deprecated use was common in 5.5.1 and is permitted in 7.0, but can prevent extension structures from being adopted as-is as new standard structures in future versions of the specification. + +- Clarify that the "applies to" and "status" columns of `g7:enumset-ord-STAT` are recommendations, not restrictions. + +- Clarify that AGE values may be larger than any calendar supports. This was always permitted; that fact is now called out more clearly. + +- Clarify that records cannot be relocated standard structures. This was always incompatible with the definition of relocated standard structures; that fact is now called out more clearly. + +- Various typo corrections. + + # Version 7.0.13 - Deprecated `ADR1`, `ADR2`, and `ADR3` which convey no information not already in `ADDR`. @@ -79,7 +119,7 @@ nav: "changelog" - Changes anticipating a coming extension registry: - - Add URIs for sets of enumeration values. This has changes some fragment identifiers in the HTML version of the spec and could cause hotlinks to the specific sections discussing enumeration sets to change. + - Add URIs for sets of enumeration values. This changed some fragment identifiers in the HTML version of the spec and could cause hotlinks to the specific sections discussing enumeration sets to change. - Many updates to the YAML format served at and at the other URIs in the specification. @@ -145,7 +185,7 @@ nav: "changelog" - `mul` can be used if there is no single primary language, but is unlikely to provide practical functionality beyond `und`. - `zxx` can be used for ASCII art and other non-language text, and can improve accessibility for screen readers. -- Clarify that empty *payloads* are encoded as missing `LineVal`s and empty `LineVal`s are not been permitted; this has been true since 7.0.0 but was easily overlooked in the previous text. +- Clarify that empty *payloads* are encoded as missing `LineVal`s and empty `LineVal`s are not permitted; this has been true since 7.0.0 but was easily overlooked in the previous text. - Note cases where the same couple might be the partners in multiple `FAM` records. @@ -226,7 +266,7 @@ nav: "changelog" # Version 7.0.0 -As a major release and the first update to the specification in 20 years, there a many changes in this version. +As a major release and the first update to the specification in 20 years, there are many changes in this version. This version is the first version to use [semantic versioning](https://semver.org/). 7 was chosen as the new major version number because 1 through 6 were each used previously, some for released standards and others for abandoned drafts. @@ -308,7 +348,7 @@ Earlier versions of GEDCOM predated language tags, media types, and Unicode beca ## New Extensibility -- Every standard tag now has a single "default" meaning, even if it also has additional meanings in other contexts. Tags conforming to this default meaning can now be used by extensions as substructures of structures with extention tags. +- Every standard tag now has a single "default" meaning, even if it also has additional meanings in other contexts. Tags conforming to this default meaning can now be used by extensions as substructures of structures with extension tags. - Extension tags remain in a backwards-compatible way, but should additionally be paired with a URI to avoid name collisions and provide documentation. @@ -332,7 +372,7 @@ Earlier versions of GEDCOM predated language tags, media types, and Unicode beca - Age phrases are now only phrases, not long-hand terms for specific age ranges -- Previously registered values (APPROVED_SYSTEM_ID, RECEIVING_SYSTEM_NAME, etc) are kept as-is if present; new ones are URIs instead of having a separate registration process +- Previously registered values (APPROVED_SYSTEM_ID, RECEIVING_SYSTEM_NAME, etc.) are kept as-is if present; new ones are URIs instead of having a separate registration process - `RESI` may have a payload, just as all other attributes may @@ -350,7 +390,7 @@ Various ambiguities were identified in version 5.5.1: some due to poor wording, - Dual-year dates were used with widely different semantics and have been replaced by more flexibility in date phrases. -- `SEX` is now unambiguously biological sex at birth; all other related concepts (gender identity, sexual preference, sex reassignment, etc) are time-varying attributes and to be stored in an individual attribute instead +- `SEX` is now unambiguously biological sex at birth; all other related concepts (gender identity, sexual preference, sex reassignment, etc.) are time-varying attributes and to be stored in an individual attribute instead Note that new tags were not introduced for gender-related attributes. It is not yet clear what the correct set of attribute types should be given the evolving and regionally-specific understanding of these concepts. The generic `FACT` is recommended for these concepts instead. diff --git a/_pages/tag-def/ABBR.md b/_pages/tag-def/ABBR.md index 67397eea..1fb9e925 100644 --- a/_pages/tag-def/ABBR.md +++ b/_pages/tag-def/ABBR.md @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/record-SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ADDR.md b/_pages/tag-def/ADDR.md index e2c68e37..598ffce7 100644 --- a/_pages/tag-def/ADDR.md +++ b/_pages/tag-def/ADDR.md @@ -20,31 +20,36 @@ standard tag: ADDR specification: - Address - - The location of, or most relevant to, the subject of the superstructure. - See ADDRESS_STRUCTURE for more. + - The location of, or most relevant to, the subject of the superstructure. See + `ADDRESS_STRUCTURE` for more details. - | A specific building, plot, or location. The payload is the full formatted address as it would appear on a mailing label, including appropriate line - breaks (encoded using CONT tags). The expected order of address components - varies by region; the address should be organized as expected by the - addressed region. + breaks (encoded using `CONT` tags). The expected order of address components + varies by region; the address should be organized as expected by the addressed + region. - Optionally, additional substructures such as STAE and CTRY are provided to + Optionally, additional substructures such as `STAE` and `CTRY` are provided to be used by systems that have structured their addresses for indexing and - sorting. If the substructures and ADDR payload disagree, the ADDR payload - shall be taken as correct. Because the regionally-correct order and - formatting of address components cannot be determined from the - substructures alone, the ADDR payload is required, even if its content - appears to be redundant with the substructures. + sorting. If the substructures and `ADDR` payload disagree, the `ADDR` payload + shall be taken as correct. Because the regionally-correct order and formatting + of address components cannot be determined from the substructures alone, the + `ADDR` payload is required, even if its content appears to be redundant with + the substructures. - ADR1 and ADR2 were introduced in version 5.5 (1996) and ADR3 in version - 5.5.1 (1999), defined as “The first/second/third line of an address.” Some - applications interpreted ADR1 as “the first line of the street address”, - but most took the spec as-written and treated it as a straight copy of a - line of text already available in the ADDR payload. +
+ + `ADR1` and `ADR2` were introduced in version 5.5 (1996) and `ADR3` in version + 5.5.1 (1999), defined as "The first/second/third line of an address." Some + applications interpreted ADR1 as "the first line of the *street* address", but + most took the spec as-written and treated it as a straight copy of a line of + text already available in the `ADDR` payload. Duplicating information bloats files and introduces the potential for - self-contradiction. ADR1, ADR2, and ADR3 should not be added to new files. + self-contradiction. `ADR1`, `ADR2`, and `ADR3` should not be added to new + files. + +
label: 'Address' @@ -114,6 +119,8 @@ superstructures: "https://gedcom.io/terms/v7/WILL": "{0:1}" "https://gedcom.io/terms/v7/record-REPO": "{0:1}" "https://gedcom.io/terms/v7/record-SUBM": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ADOP-FAMC.md b/_pages/tag-def/ADOP-FAMC.md index 9a81098c..3aa51aac 100644 --- a/_pages/tag-def/ADOP-FAMC.md +++ b/_pages/tag-def/ADOP-FAMC.md @@ -23,11 +23,11 @@ specification: - | The individual or couple that adopted this individual. - Adoption by an individual, rather than a couple, may be represented either - by pointing to a FAM where that individual is a HUSB or WIFE and using a - https://gedcom.io/terms/v7/FAMC-ADOP substructure to indicate which 1 - performed the adoption; or by using a FAM where the adopting individual is - the only HUSB/WIFE. + Adoption by an individual, rather than a couple, may be represented either by + pointing to a `FAM` where that individual is a `HUSB` or `WIFE` and using a + `https://gedcom.io/terms/v7/FAMC-ADOP` substructure to indicate which 1 + performed the adoption; or by using a `FAM` where the adopting individual is + the only `HUSB`/`WIFE`. label: 'Family child' @@ -38,6 +38,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/ADOP": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ADOP.md b/_pages/tag-def/ADOP.md index 71bcc247..6999772e 100644 --- a/_pages/tag-def/ADOP.md +++ b/_pages/tag-def/ADOP.md @@ -20,10 +20,10 @@ standard tag: ADOP specification: - Adoption - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - adoption - - Creation of a legally approved child-parent relationship that does not - exist biologically. + - Creation of a legally approved child-parent relationship that does not exist + biologically. label: 'Adoption' @@ -58,6 +58,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ADR1.md b/_pages/tag-def/ADR1.md index 168d0961..7c2f45a6 100644 --- a/_pages/tag-def/ADR1.md +++ b/_pages/tag-def/ADR1.md @@ -21,11 +21,16 @@ standard tag: ADR1 specification: - Address Line 1 - | - The first line of the address, used for indexing. This structure’s payload - should be a single line of text equal to the first line of the - corresponding ADDR. See ADDRESS_STRUCTURE for more. + The first line of the address, used for indexing. This structure's payload + should be a single line of text equal to the first line of the corresponding + `ADDR`. See `ADDRESS_STRUCTURE` for more details. - ADR1 should not be added to new files; see ADDRESS_STRUCTURE for more. +
+ + `ADR1` should not be added to new files; see `ADDRESS_STRUCTURE` for more + details. + +
label: 'Address Line 1' @@ -35,6 +40,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/ADDR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ADR2.md b/_pages/tag-def/ADR2.md index 11d18f96..061d9d8f 100644 --- a/_pages/tag-def/ADR2.md +++ b/_pages/tag-def/ADR2.md @@ -21,11 +21,16 @@ standard tag: ADR2 specification: - Address Line 2 - | - The second line of the address, used for indexing. This structure’s payload - should be a single line of text equal to the second line of the - corresponding ADDR. See ADDRESS_STRUCTURE for more. + The second line of the address, used for indexing. This structure's payload + should be a single line of text equal to the second line of the corresponding + `ADDR`. See `ADDRESS_STRUCTURE` for more details. - ADR2 should not be added to new files; see ADDRESS_STRUCTURE for more. +
+ + `ADR2` should not be added to new files; see `ADDRESS_STRUCTURE` for more + details. + +
label: 'Address Line 2' @@ -35,6 +40,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/ADDR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ADR3.md b/_pages/tag-def/ADR3.md index 2ab2fdb9..ecbdc77a 100644 --- a/_pages/tag-def/ADR3.md +++ b/_pages/tag-def/ADR3.md @@ -21,11 +21,16 @@ standard tag: ADR3 specification: - Address Line 3 - | - The third line of the address, used for indexing. This structure’s payload - should be a single line of text equal to the third line of the - corresponding ADDR. See ADDRESS_STRUCTURE for more. + The third line of the address, used for indexing. This structure's payload + should be a single line of text equal to the third line of the corresponding + `ADDR`. See `ADDRESS_STRUCTURE` for more details. - ADR3 should not be added to new files; see ADDRESS_STRUCTURE for more. +
+ + `ADR3` should not be added to new files; see `ADDRESS_STRUCTURE` for more + details. + +
label: 'Address Line 3' @@ -35,6 +40,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/ADDR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/AGE.md b/_pages/tag-def/AGE.md index 3493d9b1..94aee7f5 100644 --- a/_pages/tag-def/AGE.md +++ b/_pages/tag-def/AGE.md @@ -20,8 +20,8 @@ standard tag: AGE specification: - Age at event - - The age of the individual at the time an event occurred, or the age listed - in the document. + - The age of the individual at the time an event occurred, or the age listed in + the document. label: 'Age at event' @@ -70,6 +70,8 @@ superstructures: "https://gedcom.io/terms/v7/SSN": "{0:1}" "https://gedcom.io/terms/v7/WIFE": "{1:1}" "https://gedcom.io/terms/v7/WILL": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/AGNC.md b/_pages/tag-def/AGNC.md index 8c076e82..6ad88d2f 100644 --- a/_pages/tag-def/AGNC.md +++ b/_pages/tag-def/AGNC.md @@ -20,11 +20,10 @@ standard tag: AGNC specification: - Responsible agency - - The organization, institution, corporation, person, or other entity that - has responsibility for the associated context. Examples are an employer of - a person of an associated occupation, or a church that administered rites - or events, or an organization responsible for creating or archiving - records. + - The organization, institution, corporation, person, or other entity that has + responsibility for the associated context. Examples are an employer of a person + of an associated occupation, or a church that administered rites or events, or + an organization responsible for creating or archiving records. label: 'Responsible agency' @@ -85,6 +84,8 @@ superstructures: "https://gedcom.io/terms/v7/RETI": "{0:1}" "https://gedcom.io/terms/v7/SSN": "{0:1}" "https://gedcom.io/terms/v7/WILL": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ALIA.md b/_pages/tag-def/ALIA.md index 84107e8a..209d796a 100644 --- a/_pages/tag-def/ALIA.md +++ b/_pages/tag-def/ALIA.md @@ -22,15 +22,19 @@ specification: - Alias - | A single individual may have facts distributed across multiple individual - records, connected by ALIA pointers (named after “alias” in the computing + records, connected by `ALIA` pointers (named after "alias" in the computing sense, not the pseudonym sense). - This specification does not define how to connect INDI records with ALIA. - Some systems organize ALIA pointers to create a tree structure, with the - root INDI record containing the composite view of all facts in the leaf - INDI records. Others distribute events and attributes between INDI records - mutually linked by symmetric pairs of ALIA pointers. A future version of - this specification may adjust the definition of ALIA. +
+ + This specification does not define how to connect `INDI` records with `ALIA`. + Some systems organize `ALIA` pointers to create a tree structure, with the root + `INDI` record containing the composite view of all facts in the leaf `INDI` + records. Others distribute events and attributes between `INDI` records + mutually linked by symmetric pairs of `ALIA` pointers. A future version of this + specification may adjust the definition of `ALIA`. + +
label: 'Alias' @@ -41,6 +45,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ANCI.md b/_pages/tag-def/ANCI.md index 741260d7..c3e1317a 100644 --- a/_pages/tag-def/ANCI.md +++ b/_pages/tag-def/ANCI.md @@ -20,8 +20,8 @@ standard tag: ANCI specification: - Ancestor interest - - Indicates an interest in additional research for ancestors of this - individual. (See also DESI). + - Indicates an interest in additional research for ancestors of this individual. + (See also `DESI`). label: 'Ancestor interest' @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ANUL.md b/_pages/tag-def/ANUL.md index 4050053a..9b6b009f 100644 --- a/_pages/tag-def/ANUL.md +++ b/_pages/tag-def/ANUL.md @@ -20,7 +20,7 @@ standard tag: ANUL specification: - Annulment - - A Family Event. See also FAMILY_EVENT_STRUCTURE. + - A [Family Event]. See also `FAMILY_EVENT_STRUCTURE`. - annulment - Declaring a marriage void from the beginning (never existed). @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ASSO.md b/_pages/tag-def/ASSO.md index d5d650ab..bd8e16f6 100644 --- a/_pages/tag-def/ASSO.md +++ b/_pages/tag-def/ASSO.md @@ -20,26 +20,33 @@ standard tag: ASSO specification: - Associates - - A pointer to an associated individual. See ASSOCIATION_STRUCTURE for more. + - A pointer to an associated individual. See `ASSOCIATION_STRUCTURE` for more + details. - | - An individual associated with the subject of the superstructure. The nature - of the association is indicated in the ROLE substructure. + An individual associated with the subject of the superstructure. The nature of + the association is indicated in the `ROLE` substructure. - A voidPtr and PHRASE can be used to describe associations to people not - referenced by any INDI record. + A `voidPtr` and `PHRASE` can be used to describe associations to people not + referenced by any `INDI` record. - The following indicates that “Mr Stockdale” was the individual’s teacher - and that individual @I2@ was the clergy officiating at their baptism. +
- 0 @I1@ INDI - 1 ASSO @VOID@ - 2 PHRASE Mr Stockdale - 2 ROLE OTHER - 3 PHRASE Teacher - 1 BAPM - 2 DATE 1930 - 2 ASSO @I2@ - 3 ROLE CLERGY + The following indicates that "Mr Stockdale" was the individual's teacher and + that individual `@I2@` was the clergy officiating at their baptism. + + ```gedcom + 0 @I1@ INDI + 1 ASSO @VOID@ + 2 PHRASE Mr Stockdale + 2 ROLE OTHER + 3 PHRASE Teacher + 1 BAPM + 2 DATE 1930 + 2 ASSO @I2@ + 3 ROLE CLERGY + ``` + +
label: 'Associates' @@ -106,6 +113,8 @@ superstructures: "https://gedcom.io/terms/v7/WILL": "{0:M}" "https://gedcom.io/terms/v7/record-FAM": "{0:M}" "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/AUTH.md b/_pages/tag-def/AUTH.md index 02adc237..80d64d4e 100644 --- a/_pages/tag-def/AUTH.md +++ b/_pages/tag-def/AUTH.md @@ -21,9 +21,9 @@ standard tag: AUTH specification: - Author - The person, agency, or entity who created the record. For a published work, - this could be the author, compiler, transcriber, abstractor, or editor. For - an unpublished source, this may be an individual, a government agency, - church organization, or private organization. + this could be the author, compiler, transcriber, abstractor, or editor. For an + unpublished source, this may be an individual, a government agency, church + organization, or private organization. label: 'Author' @@ -33,6 +33,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/record-SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/BAPL.md b/_pages/tag-def/BAPL.md index 7cefcad4..cd067515 100644 --- a/_pages/tag-def/BAPL.md +++ b/_pages/tag-def/BAPL.md @@ -20,10 +20,10 @@ standard tag: BAPL specification: - Baptism, Latter-Day Saint - - A Latter-Day Saint Ordinance. See also LDS_INDIVIDUAL_ORDINANCE. + - A [Latter-Day Saint Ordinance]. See also `LDS_INDIVIDUAL_ORDINANCE`. - baptism - - The event of baptism performed at age 8 or later by priesthood authority of - The Church of Jesus Christ of Latter-day Saints. (See also BAPM) + - The event of baptism performed at age 8 or later by priesthood authority of The + Church of Jesus Christ of Latter-day Saints. (See also [`BAPM`]) label: 'Baptism, Latter-Day Saint' @@ -40,6 +40,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/BAPM.md b/_pages/tag-def/BAPM.md index 72d1484c..a357b54f 100644 --- a/_pages/tag-def/BAPM.md +++ b/_pages/tag-def/BAPM.md @@ -20,9 +20,9 @@ standard tag: BAPM specification: - Baptism - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - baptism - - Baptism, performed in infancy or later. (See also BAPL and CHR.) + - Baptism, performed in infancy or later. (See also [`BAPL`] and `CHR`.) label: 'Baptism' @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/BARM.md b/_pages/tag-def/BARM.md index 8fc7d0fd..9471e833 100644 --- a/_pages/tag-def/BARM.md +++ b/_pages/tag-def/BARM.md @@ -20,7 +20,7 @@ standard tag: BARM specification: - Bar Mitzvah - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - Bar Mitzvah - The ceremonial event held when a Jewish boy reaches age 13. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/BASM.md b/_pages/tag-def/BASM.md index 8197841d..7b482464 100644 --- a/_pages/tag-def/BASM.md +++ b/_pages/tag-def/BASM.md @@ -20,10 +20,10 @@ standard tag: BASM specification: - Bas Mitzvah - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - Bas Mitzvah - - The ceremonial event held when a Jewish girl reaches age 13, also known as - “Bat Mitzvah.” + - The ceremonial event held when a Jewish girl reaches age 13, also known as "Bat + Mitzvah." label: 'Bas Mitzvah' @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/BIRT.md b/_pages/tag-def/BIRT.md index 9fcdd608..c4cfa96b 100644 --- a/_pages/tag-def/BIRT.md +++ b/_pages/tag-def/BIRT.md @@ -20,7 +20,7 @@ standard tag: BIRT specification: - Birth - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - birth - Entering into life. @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/BLES.md b/_pages/tag-def/BLES.md index f7272e38..5dbfba52 100644 --- a/_pages/tag-def/BLES.md +++ b/_pages/tag-def/BLES.md @@ -20,7 +20,7 @@ standard tag: BLES specification: - Blessing - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - blessing - Bestowing divine care or intercession. Sometimes given in connection with a naming ceremony. @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/BURI.md b/_pages/tag-def/BURI.md index 4af3bb6e..25b4168e 100644 --- a/_pages/tag-def/BURI.md +++ b/_pages/tag-def/BURI.md @@ -21,14 +21,14 @@ standard tag: BURI specification: - Depositing remains - | - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - Although defined as any depositing of remains since it was introduced in - the first version of GEDCOM, this tag is a shortened form of the English - word “burial” and has been interpreted to mean “depositing of remains by - burial” by some applications and users. In the absence of a clarifying TYPE - substructure it is likely, but not guaranteed, that a BURI structure refers - to a burial rather than another form of depositing remains. + Although defined as any depositing of remains since it was introduced in the + first version of GEDCOM, this tag is a shortened form of the English word + "burial" and has been interpreted to mean "depositing of remains by burial" by + some applications and users. In the absence of a clarifying `TYPE` substructure + it is likely, but not guaranteed, that a `BURI` structure refers to a burial + rather than another form of depositing remains. - depositing remains - Depositing the mortal remains of a deceased person. @@ -64,6 +64,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CALN.md b/_pages/tag-def/CALN.md index 47305313..fc4e80f5 100644 --- a/_pages/tag-def/CALN.md +++ b/_pages/tag-def/CALN.md @@ -20,9 +20,9 @@ standard tag: CALN specification: - Call number - - An identification or reference description used to file and retrieve items - from the holdings of a repository. Despite the word “number” in the name, - may contain any character, not just digits. + - An identification or reference description used to file and retrieve items from + the holdings of a repository. Despite the word "number" in the name, may + contain any character, not just digits. label: 'Call number' @@ -33,6 +33,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/REPO": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CAST.md b/_pages/tag-def/CAST.md index f4ad052c..2f94d3ce 100644 --- a/_pages/tag-def/CAST.md +++ b/_pages/tag-def/CAST.md @@ -20,11 +20,11 @@ standard tag: CAST specification: - Caste - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - caste - - The name of an individual’s rank or status in society which is sometimes - based on racial or religious differences, or differences in wealth, - inherited rank, profession, or occupation. + - The name of an individual's rank or status in society which is sometimes based + on racial or religious differences, or differences in wealth, inherited rank, + profession, or occupation. label: 'Caste' @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CAUS.md b/_pages/tag-def/CAUS.md index 11593ed6..574d4987 100644 --- a/_pages/tag-def/CAUS.md +++ b/_pages/tag-def/CAUS.md @@ -82,6 +82,8 @@ superstructures: "https://gedcom.io/terms/v7/RETI": "{0:1}" "https://gedcom.io/terms/v7/SSN": "{0:1}" "https://gedcom.io/terms/v7/WILL": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CHAN.md b/_pages/tag-def/CHAN.md index cd720d71..93a673f6 100644 --- a/_pages/tag-def/CHAN.md +++ b/_pages/tag-def/CHAN.md @@ -21,13 +21,14 @@ standard tag: CHAN specification: - Change - The most recent change to the superstructure. This is metadata about the - structure itself, not data about its subject. See CHANGE_DATE for more. + structure itself, not data about its subject. See `CHANGE_DATE` for more + details. - | - The date of the most recent modification of the superstructure, optionally - with notes about that modification. + The date of the most recent modification of the superstructure, optionally with + notes about that modification. - The NOTE substructure may describe previous changes as well as the most - recent, although only the most recent change is described by the DATE + The `NOTE` substructure may describe previous changes as well as the most + recent, although only the most recent change is described by the `DATE` substructure. label: 'Change' @@ -47,6 +48,8 @@ superstructures: "https://gedcom.io/terms/v7/record-SNOTE": "{0:1}" "https://gedcom.io/terms/v7/record-SOUR": "{0:1}" "https://gedcom.io/terms/v7/record-SUBM": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CHIL.md b/_pages/tag-def/CHIL.md index 8acf8eed..bfd4ab2e 100644 --- a/_pages/tag-def/CHIL.md +++ b/_pages/tag-def/CHIL.md @@ -20,8 +20,8 @@ standard tag: CHIL specification: - Child - - The child in a family, whether biological, adopted, foster, sealed, or - other relationship. + - The child in a family, whether biological, adopted, foster, sealed, or other + relationship. label: 'Child' @@ -32,6 +32,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CHR.md b/_pages/tag-def/CHR.md index bb4a886b..17fbce73 100644 --- a/_pages/tag-def/CHR.md +++ b/_pages/tag-def/CHR.md @@ -20,7 +20,7 @@ standard tag: CHR specification: - Christening - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - christening - Baptism or naming events for a child. @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CHRA.md b/_pages/tag-def/CHRA.md index fc1d21b0..7a437611 100644 --- a/_pages/tag-def/CHRA.md +++ b/_pages/tag-def/CHRA.md @@ -20,7 +20,7 @@ standard tag: CHRA specification: - Christening, adult - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - adult christening - Baptism or naming events for an adult person. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CITY.md b/_pages/tag-def/CITY.md index b7100006..5614872f 100644 --- a/_pages/tag-def/CITY.md +++ b/_pages/tag-def/CITY.md @@ -20,7 +20,8 @@ standard tag: CITY specification: - City - - The name of the city used in the address. See ADDRESS_STRUCTURE for more. + - The name of the city used in the address. See `ADDRESS_STRUCTURE` for more + details. label: 'City' @@ -30,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/ADDR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CONF.md b/_pages/tag-def/CONF.md index d4c10df5..ad11572c 100644 --- a/_pages/tag-def/CONF.md +++ b/_pages/tag-def/CONF.md @@ -20,7 +20,7 @@ standard tag: CONF specification: - Confirmation - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - confirmation - Conferring full church membership. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CONL.md b/_pages/tag-def/CONL.md index ce530eec..188e63bd 100644 --- a/_pages/tag-def/CONL.md +++ b/_pages/tag-def/CONL.md @@ -20,10 +20,10 @@ standard tag: CONL specification: - Confirmation, Latter-Day Saint - - A Latter-Day Saint Ordinance. See also LDS_INDIVIDUAL_ORDINANCE. + - A [Latter-Day Saint Ordinance]. See also `LDS_INDIVIDUAL_ORDINANCE`. - confirmation - The religious event by which a person receives membership in The Church of - Jesus Christ of Latter-day Saints. (See also CONF) + Jesus Christ of Latter-day Saints. (See also [`CONF`]) label: 'Confirmation, Latter-Day Saint' @@ -40,6 +40,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CONT.md b/_pages/tag-def/CONT.md index e7590d57..c01d8030 100644 --- a/_pages/tag-def/CONT.md +++ b/_pages/tag-def/CONT.md @@ -20,9 +20,9 @@ standard tag: CONT specification: - Continued - - A pseudo-structure to indicate a line break. The CONT tag is generated - during serialization and is never present in parsed datasets. See Lines for - more. + - A pseudo-structure to indicate a line break. The `CONT` tag is generated during + serialization and is never present in parsed datasets. See [Lines] for more + details. label: 'Continued' @@ -31,6 +31,8 @@ payload: null substructures: {} superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/COPR.md b/_pages/tag-def/COPR.md index 968bc400..def2a566 100644 --- a/_pages/tag-def/COPR.md +++ b/_pages/tag-def/COPR.md @@ -20,8 +20,8 @@ standard tag: COPR specification: - Copyright - - A copyright statement, as appropriate for the copyright laws applicable to - this data. + - A copyright statement, as appropriate for the copyright laws applicable to this + data. label: 'Copyright' @@ -32,6 +32,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/HEAD": "{0:1}" "https://gedcom.io/terms/v7/HEAD-SOUR-DATA": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CORP.md b/_pages/tag-def/CORP.md index fb693882..d5c84d91 100644 --- a/_pages/tag-def/CORP.md +++ b/_pages/tag-def/CORP.md @@ -20,8 +20,8 @@ standard tag: CORP specification: - Corporate name - - The name of the business, corporation, or person that produced or - commissioned the product. + - The name of the business, corporation, or person that produced or commissioned + the product. label: 'Corporate name' @@ -36,6 +36,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/HEAD-SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CREA.md b/_pages/tag-def/CREA.md index 8a94b381..9810d833 100644 --- a/_pages/tag-def/CREA.md +++ b/_pages/tag-def/CREA.md @@ -21,10 +21,10 @@ standard tag: CREA specification: - Creation - The initial creation of the superstructure. This is metadata about the - structure itself, not data about its subject. See CREATION_DATE for more. - - The date of the initial creation of the superstructure. Because this refers - to the initial creation, it should not be modified after the structure is - created. + structure itself, not data about its subject. See `CREATION_DATE` for more + details. + - The date of the initial creation of the superstructure. Because this refers to + the initial creation, it should not be modified after the structure is created. label: 'Creation' @@ -41,6 +41,8 @@ superstructures: "https://gedcom.io/terms/v7/record-SNOTE": "{0:1}" "https://gedcom.io/terms/v7/record-SOUR": "{0:1}" "https://gedcom.io/terms/v7/record-SUBM": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CREM.md b/_pages/tag-def/CREM.md index 1ec5e543..25e9825d 100644 --- a/_pages/tag-def/CREM.md +++ b/_pages/tag-def/CREM.md @@ -20,7 +20,7 @@ standard tag: CREM specification: - Cremation - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - cremation - The act of reducing a dead body to ashes by fire. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CROP.md b/_pages/tag-def/CROP.md index 880176e6..d730c7eb 100644 --- a/_pages/tag-def/CROP.md +++ b/_pages/tag-def/CROP.md @@ -21,27 +21,27 @@ standard tag: CROP specification: - Crop - | - A subregion of an image to display. It is only valid when the - superstructure links to a MULTIMEDIA_RECORD with at least 1 FILE - substructure that refers to an external file with a defined pixel unit. + A subregion of an image to display. It is only valid when the superstructure + links to a `MULTIMEDIA_RECORD` with at least 1 `FILE` substructure that refers + to an external file with a defined pixel unit. - LEFT and TOP indicate the top-left corner of the region to display. WIDTH - and HEIGHT indicate how many pixels wide and tall the region to display is. - If omitted, LEFT and TOP each default to 0; WIDTH defaults to the image - width minus LEFT; and HEIGHT defaults to the image height minus TOP. + `LEFT` and `TOP` indicate the top-left corner of the region to display. `WIDTH` + and `HEIGHT` indicate how many pixels wide and tall the region to display is. + If omitted, `LEFT` and `TOP` each default to 0; `WIDTH` defaults to the image + width minus `LEFT`; and `HEIGHT` defaults to the image height minus `TOP`. - If the superstructure links to a MULTIMEDIA_RECORD that includes multiple - FILE substructures, the CROP applies to the first FILE to which it can + If the superstructure links to a `MULTIMEDIA_RECORD` that includes multiple + `FILE` substructures, the `CROP` applies to the first `FILE` to which it can apply, namely the first external file with a defined pixel unit. - It is recommended that CROP be used only with a single-FILE - MULTIMEDIA_RECORD. + It is recommended that `CROP` be used only with a single-FILE + `MULTIMEDIA_RECORD`. The following are errors: - - LEFT or LEFT + WIDTH exceed the image width. - - TOP or TOP + HEIGHT exceed the image height. - - CROP applied to a non-image or image without a defined pixel unit. + - `LEFT` or `LEFT` + `WIDTH` exceed the image width. + - `TOP` or `TOP` + `HEIGHT` exceed the image height. + - `CROP` applied to a non-image or image without a defined pixel unit. label: 'Crop' @@ -55,6 +55,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/OBJE": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/CTRY.md b/_pages/tag-def/CTRY.md index a2bdee01..34423dd0 100644 --- a/_pages/tag-def/CTRY.md +++ b/_pages/tag-def/CTRY.md @@ -21,7 +21,7 @@ standard tag: CTRY specification: - Country - The name of the country that pertains to the associated address. See - ADDRESS_STRUCTURE for more. + `ADDRESS_STRUCTURE` for more details. label: 'Country' @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/ADDR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DATA-EVEN-DATE.md b/_pages/tag-def/DATA-EVEN-DATE.md index b764c812..b838968d 100644 --- a/_pages/tag-def/DATA-EVEN-DATE.md +++ b/_pages/tag-def/DATA-EVEN-DATE.md @@ -20,7 +20,7 @@ standard tag: DATE specification: - Date - - The DatePeriod covered by the entire source; the period during which this + - The `DatePeriod` covered by the entire source; the period during which this source recorded events. label: 'Date' @@ -32,6 +32,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/DATA-EVEN": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DATA-EVEN.md b/_pages/tag-def/DATA-EVEN.md index 2dc612e9..29e2d21a 100644 --- a/_pages/tag-def/DATA-EVEN.md +++ b/_pages/tag-def/DATA-EVEN.md @@ -21,10 +21,10 @@ standard tag: EVEN specification: - Event - A list of enumerated values from set - https://gedcom.io/terms/v7/enumset-EVENATTR indicating the types of events - that were recorded in a particular source. Each event type is separated by - a comma and space. For example, a parish register of births, deaths, and - marriages would be BIRT, DEAT, MARR. + `https://gedcom.io/terms/v7/enumset-EVENATTR` indicating the types of events + that were recorded in a particular source. Each event type is separated by a + comma and space. For example, a parish register of births, deaths, and + marriages would be `BIRT, DEAT, MARR`. label: 'Event' @@ -38,6 +38,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/DATA": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DATA.md b/_pages/tag-def/DATA.md index d0dbdc66..7693cee3 100644 --- a/_pages/tag-def/DATA.md +++ b/_pages/tag-def/DATA.md @@ -20,10 +20,9 @@ standard tag: DATA specification: - Data - - A structure with no payload used to distinguish a description of something - from metadata about it. For example, SOUR and its other substructures - describe a source itself, while SOUR.DATA describes the content of the - source. + - A structure with no payload used to distinguish a description of something from + metadata about it. For example, `SOUR` and its other substructures describe a + source itself, while `SOUR`.`DATA` describes the content of the source. label: 'Data' @@ -37,6 +36,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DATE-exact.md b/_pages/tag-def/DATE-exact.md index 87fb323d..c83544d1 100644 --- a/_pages/tag-def/DATE-exact.md +++ b/_pages/tag-def/DATE-exact.md @@ -21,7 +21,7 @@ standard tag: DATE specification: - Date - The principal date of the subject of the superstructure. The payload is a - DateExact. + `DateExact`. label: 'Date' @@ -35,6 +35,8 @@ superstructures: "https://gedcom.io/terms/v7/CREA": "{1:1}" "https://gedcom.io/terms/v7/HEAD-SOUR-DATA": "{0:1}" "https://gedcom.io/terms/v7/ord-STAT": "{1:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DATE.md b/_pages/tag-def/DATE.md index d006d8d2..55dfe86c 100644 --- a/_pages/tag-def/DATE.md +++ b/_pages/tag-def/DATE.md @@ -22,16 +22,33 @@ specification: - Date - | The principal date of the subject of the superstructure. The payload is a - DateValue. + `DateValue`. - See DATE_VALUE for more. + When the superstructure is an event, the principal date indicates when the + event took place. + + When the superstructure is an attribute, the principal date indicates when the + attribute was observed, asserted, or applied. A date period might put bounds on + the attributes applicability, but other date forms assume that the attribute + may have also applied on other dates too. + + When the superstructure is a `https://gedcom.io/terms/v7/SOUR-DATA`, the + principal date indicates when the data was entered into the source; or, for a + source like a website that changes over time, a date on which the source + contained the data. + + See `DATE_VALUE` for more details. - | - A date, optionally with a time and/or a phrase. If there is a TIME, it - asserts that the event happened at a specific time on a single day. TIME - should not be used with DatePeriod but may be used with other date types. + A date, optionally with a time and/or a phrase. If there is a `TIME`, it + asserts that the event happened at a specific time on a single day. `TIME` + should not be used with `DatePeriod` but may be used with other date types. + +
There is currently no provision for approximate times or time phrases. Time phrases are expected to be added in version 7.1. + +
label: 'Date' @@ -100,6 +117,8 @@ superstructures: "https://gedcom.io/terms/v7/SOUR-DATA": "{0:1}" "https://gedcom.io/terms/v7/SSN": "{0:1}" "https://gedcom.io/terms/v7/WILL": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DEAT.md b/_pages/tag-def/DEAT.md index 79a0ae3f..69e529d1 100644 --- a/_pages/tag-def/DEAT.md +++ b/_pages/tag-def/DEAT.md @@ -20,7 +20,7 @@ standard tag: DEAT specification: - Death - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - death - Mortal life terminates. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DESI.md b/_pages/tag-def/DESI.md index 28585d36..da98cf44 100644 --- a/_pages/tag-def/DESI.md +++ b/_pages/tag-def/DESI.md @@ -20,8 +20,8 @@ standard tag: DESI specification: - Descendant Interest - - Indicates an interest in research to identify additional descendants of - this individual. See also ANCI. + - Indicates an interest in research to identify additional descendants of this + individual. See also `ANCI`. label: 'Descendant Interest' @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DEST.md b/_pages/tag-def/DEST.md index 9c3f6fc3..eab8cfe5 100644 --- a/_pages/tag-def/DEST.md +++ b/_pages/tag-def/DEST.md @@ -21,7 +21,7 @@ standard tag: DEST specification: - Destination - An identifier for the system expected to receive this document. See - HEAD.SOUR for guidance on choosing identifiers. + `HEAD`.`SOUR` for guidance on choosing identifiers. label: 'Destination' @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/HEAD": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DIV.md b/_pages/tag-def/DIV.md index cdf4ba42..4cc9371f 100644 --- a/_pages/tag-def/DIV.md +++ b/_pages/tag-def/DIV.md @@ -20,7 +20,7 @@ standard tag: DIV specification: - Divorce - - A Family Event. See also FAMILY_EVENT_STRUCTURE. + - A [Family Event]. See also `FAMILY_EVENT_STRUCTURE`. - divorce - Dissolving a marriage through civil action. @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DIVF.md b/_pages/tag-def/DIVF.md index d724534f..5ac297c2 100644 --- a/_pages/tag-def/DIVF.md +++ b/_pages/tag-def/DIVF.md @@ -20,7 +20,7 @@ standard tag: DIVF specification: - Divorce filing - - A Family Event. See also FAMILY_EVENT_STRUCTURE. + - A [Family Event]. See also `FAMILY_EVENT_STRUCTURE`. - divorce filed - Filing for a divorce by a spouse. @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/DSCR.md b/_pages/tag-def/DSCR.md index 9de543ec..caa9c281 100644 --- a/_pages/tag-def/DSCR.md +++ b/_pages/tag-def/DSCR.md @@ -20,7 +20,7 @@ standard tag: DSCR specification: - Description - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - physical description - The physical characteristics of a person. @@ -55,6 +55,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/EDUC.md b/_pages/tag-def/EDUC.md index 0a2212e6..b6be04e9 100644 --- a/_pages/tag-def/EDUC.md +++ b/_pages/tag-def/EDUC.md @@ -20,7 +20,7 @@ standard tag: EDUC specification: - Education - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - education - Indicator of a level of education attained. @@ -55,6 +55,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/EMAIL.md b/_pages/tag-def/EMAIL.md index d498c2cd..4f537842 100644 --- a/_pages/tag-def/EMAIL.md +++ b/_pages/tag-def/EMAIL.md @@ -21,15 +21,19 @@ standard tag: EMAIL specification: - Email - | - An electronic mail address, as defined by any relevant standard such as RFC - 3696, RFC 5321, or RFC 5322. + An electronic mail address, as defined by any relevant standard such as [RFC + 3696], [RFC 5321], or [RFC 5322]. If an invalid email address is present upon import, it should be preserved as-is on export. - The version 5.5.1 specification contained a typo where this tag was - sometimes written EMAI and sometimes written EMAIL. EMAIL should be used in - version 7.0 and later. +
+ + The version 5.5.1 specification contained a typo where this tag was sometimes + written `EMAI` and sometimes written `EMAIL`. `EMAIL` should be used in version + 7.0 and later. + +
label: 'Email' @@ -92,6 +96,8 @@ superstructures: "https://gedcom.io/terms/v7/WILL": "{0:M}" "https://gedcom.io/terms/v7/record-REPO": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/EMIG.md b/_pages/tag-def/EMIG.md index 37457ffd..d230d1cb 100644 --- a/_pages/tag-def/EMIG.md +++ b/_pages/tag-def/EMIG.md @@ -20,9 +20,9 @@ standard tag: EMIG specification: - Emigration - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - emigration - - Leaving one’s homeland with the intent of residing elsewhere. + - Leaving one's homeland with the intent of residing elsewhere. label: 'Emigration' @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ENDL.md b/_pages/tag-def/ENDL.md index 0fc297c4..773bbf46 100644 --- a/_pages/tag-def/ENDL.md +++ b/_pages/tag-def/ENDL.md @@ -20,11 +20,11 @@ standard tag: ENDL specification: - Endowment, Latter-Day Saint - - A Latter-Day Saint Ordinance. See also LDS_INDIVIDUAL_ORDINANCE. + - A [Latter-Day Saint Ordinance]. See also `LDS_INDIVIDUAL_ORDINANCE`. - endowment - - A religious event where an endowment ordinance for an individual was - performed by priesthood authority in a temple of The Church of Jesus Christ - of Latter-day Saints. + - A religious event where an endowment ordinance for an individual was performed + by priesthood authority in a temple of The Church of Jesus Christ of Latter-day + Saints. label: 'Endowment, Latter-Day Saint' @@ -41,6 +41,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ENGA.md b/_pages/tag-def/ENGA.md index a80582ac..d9dacc9a 100644 --- a/_pages/tag-def/ENGA.md +++ b/_pages/tag-def/ENGA.md @@ -20,7 +20,7 @@ standard tag: ENGA specification: - Engagement - - A Family Event. See also FAMILY_EVENT_STRUCTURE. + - A [Family Event]. See also `FAMILY_EVENT_STRUCTURE`. - engagement - Recording or announcing an agreement between 2 people to become married. @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/EXID-TYPE.md b/_pages/tag-def/EXID-TYPE.md index 3bfda977..843df121 100644 --- a/_pages/tag-def/EXID-TYPE.md +++ b/_pages/tag-def/EXID-TYPE.md @@ -21,31 +21,31 @@ standard tag: TYPE specification: - Type - | - The authority issuing the EXID, represented as a URI. It is recommended - that this be a URL. + The authority issuing the `EXID`, represented as a URI. It is recommended that + this be a URL. 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. + 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, where fields include: + Registered URIs are listed in [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. + - "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. - Additional type URIs can be registered by filing a GitHub pull request. + Additional type URIs can be registered by filing a [GitHub pull request]. label: 'Type' @@ -55,6 +55,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/EXID": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/EXID.md b/_pages/tag-def/EXID.md index 39057319..dd5c55d9 100644 --- a/_pages/tag-def/EXID.md +++ b/_pages/tag-def/EXID.md @@ -22,17 +22,17 @@ specification: - External Identifier - | An identifier for the subject of the superstructure. The identifier is - maintained by some external authority; the authority owning the identifier - is provided in the TYPE substructure; see EXID.TYPE for more. + maintained by some external authority; the authority owning the identifier is + provided in the TYPE substructure; see `EXID`.`TYPE` for more details. - Depending on the maintaining authority, an EXID may be a unique identifier + Depending on the maintaining authority, an `EXID` may be a unique identifier for the subject, an identifier for 1 of several views of the subject, or an identifier for the externally-maintained copy of the same information as is - contained in this structure. However, unlike UID and REFN, EXID does not - identify a structure; structures with the same EXID may have originated + contained in this structure. However, unlike `UID` and `REFN`, `EXID` does not + identify a structure; structures with the same `EXID` may have originated independently rather than by edits from the same starting point. - EXID identifiers are expected to be unique. Once assigned, an EXID + `EXID` identifiers are expected to be unique. Once assigned, an `EXID` identifier should never be re-used for any other purpose. label: 'External Identifier' @@ -51,6 +51,8 @@ superstructures: "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}" "https://gedcom.io/terms/v7/record-SOUR": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAM-CENS.md b/_pages/tag-def/FAM-CENS.md index 251338dc..cdb95c98 100644 --- a/_pages/tag-def/FAM-CENS.md +++ b/_pages/tag-def/FAM-CENS.md @@ -20,10 +20,10 @@ standard tag: CENS specification: - Census - - An Family Event. + - An [Family Event]. - census - - Periodic count of the population for a designated locality, such as a - national or state census. + - Periodic count of the population for a designated locality, such as a national + or state census. label: 'Census' @@ -55,9 +55,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVEN" - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAM-EVEN.md b/_pages/tag-def/FAM-EVEN.md index 808f6678..ce137a3d 100644 --- a/_pages/tag-def/FAM-EVEN.md +++ b/_pages/tag-def/FAM-EVEN.md @@ -20,7 +20,7 @@ standard tag: EVEN specification: - Event - - See https://gedcom.io/terms/v7/INDI-EVEN. + - See `https://gedcom.io/terms/v7/INDI-EVEN`. label: 'Event' @@ -52,8 +52,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAM-FACT.md b/_pages/tag-def/FAM-FACT.md index 94f0dae1..8a4db39d 100644 --- a/_pages/tag-def/FAM-FACT.md +++ b/_pages/tag-def/FAM-FACT.md @@ -20,7 +20,7 @@ standard tag: FACT specification: - Fact - - See https://gedcom.io/terms/v7/INDI-FACT. + - See `https://gedcom.io/terms/v7/INDI-FACT`. label: 'Fact' @@ -52,8 +52,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAM-HUSB.md b/_pages/tag-def/FAM-HUSB.md index 30809596..2c9b6d6c 100644 --- a/_pages/tag-def/FAM-HUSB.md +++ b/_pages/tag-def/FAM-HUSB.md @@ -20,7 +20,7 @@ standard tag: HUSB specification: - Husband - - This is a partner in a FAM record. See FAMILY_RECORD for more. + - This is a partner in a `FAM` record. See `FAMILY_RECORD` for more details. label: 'Husband' @@ -31,6 +31,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAM-NCHI.md b/_pages/tag-def/FAM-NCHI.md index c445e5ab..be67576b 100644 --- a/_pages/tag-def/FAM-NCHI.md +++ b/_pages/tag-def/FAM-NCHI.md @@ -20,7 +20,7 @@ standard tag: NCHI specification: - Number of children - - A Family Attribute. See also FAMILY_ATTRIBUTE_STRUCTURE. + - A [Family Attribute]. See also `FAMILY_ATTRIBUTE_STRUCTURE`. - number of children - The number of children that belong to this family. @@ -54,8 +54,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAM-RESI.md b/_pages/tag-def/FAM-RESI.md index b338c8a3..8ed988b8 100644 --- a/_pages/tag-def/FAM-RESI.md +++ b/_pages/tag-def/FAM-RESI.md @@ -21,10 +21,10 @@ standard tag: RESI specification: - Residence - | - A Family Attribute. See also FAMILY_ATTRIBUTE_STRUCTURE. + A [Family Attribute]. See also `FAMILY_ATTRIBUTE_STRUCTURE`. - See https://gedcom.io/terms/v7/INDI-RESI for comments on the use of payload - strings in RESI structures. + See `https://gedcom.io/terms/v7/INDI-RESI` for comments on the use of payload + strings in `RESI` structures. - residence - An address or place of residence where a family resided. @@ -58,8 +58,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAM-WIFE.md b/_pages/tag-def/FAM-WIFE.md index 1bb8e60d..05507c6e 100644 --- a/_pages/tag-def/FAM-WIFE.md +++ b/_pages/tag-def/FAM-WIFE.md @@ -20,7 +20,7 @@ standard tag: WIFE specification: - Wife - - A partner in a FAM record. See FAMILY_RECORD for more. + - A partner in a `FAM` record. See `FAMILY_RECORD` for more details. label: 'Wife' @@ -31,6 +31,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAMC-ADOP.md b/_pages/tag-def/FAMC-ADOP.md index f275c1bc..7e21a262 100644 --- a/_pages/tag-def/FAMC-ADOP.md +++ b/_pages/tag-def/FAMC-ADOP.md @@ -20,7 +20,7 @@ standard tag: ADOP specification: - Adoption - - An enumerated value from set https://gedcom.io/terms/v7/enumset-ADOP + - An enumerated value from set `https://gedcom.io/terms/v7/enumset-ADOP` indicating which parent(s) in the family adopted this individual. label: 'Adoption' @@ -34,6 +34,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/ADOP-FAMC": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAMC-STAT.md b/_pages/tag-def/FAMC-STAT.md index e08b31b6..5e3b5fae 100644 --- a/_pages/tag-def/FAMC-STAT.md +++ b/_pages/tag-def/FAMC-STAT.md @@ -20,8 +20,8 @@ standard tag: STAT specification: - Status - - An enumerated value from set https://gedcom.io/terms/v7/enumset-FAMC-STAT - assessing of the state or condition of a researcher’s belief in a family + - An enumerated value from set `https://gedcom.io/terms/v7/enumset-FAMC-STAT` + assessing of the state or condition of a researcher's belief in a family connection. label: 'Status' @@ -35,6 +35,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/INDI-FAMC": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAMC.md b/_pages/tag-def/FAMC.md index 8ae0271a..ae64f466 100644 --- a/_pages/tag-def/FAMC.md +++ b/_pages/tag-def/FAMC.md @@ -32,6 +32,8 @@ superstructures: "https://gedcom.io/terms/v7/BIRT": "{0:1}" "https://gedcom.io/terms/v7/CHR": "{0:1}" "https://gedcom.io/terms/v7/SLGC": "{1:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAMS.md b/_pages/tag-def/FAMS.md index 4d4eefce..4d43d835 100644 --- a/_pages/tag-def/FAMS.md +++ b/_pages/tag-def/FAMS.md @@ -20,7 +20,8 @@ standard tag: FAMS specification: - Family spouse - - The family in which an individual appears as a partner. See FAM for more. + - The family in which an individual appears as a partner. See `FAMILY_RECORD` for + more details. label: 'Family spouse' @@ -32,6 +33,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FAX.md b/_pages/tag-def/FAX.md index 37f30a68..9c7ac3f0 100644 --- a/_pages/tag-def/FAX.md +++ b/_pages/tag-def/FAX.md @@ -20,8 +20,8 @@ standard tag: FAX specification: - Facsimile - - A fax telephone number appropriate for sending data facsimiles. See PHON - for more. + - A fax telephone number appropriate for sending data facsimiles. See `PHON` for + additional comments on telephone numbers. label: 'Facsimile' @@ -84,6 +84,8 @@ superstructures: "https://gedcom.io/terms/v7/WILL": "{0:M}" "https://gedcom.io/terms/v7/record-REPO": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FCOM.md b/_pages/tag-def/FCOM.md index 85b73979..2b95e57f 100644 --- a/_pages/tag-def/FCOM.md +++ b/_pages/tag-def/FCOM.md @@ -20,9 +20,9 @@ standard tag: FCOM specification: - First communion - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - first communion - - The first act of sharing in the Lord’s supper as part of church worship. + - The first act of sharing in the Lord's supper as part of church worship. label: 'First communion' @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FILE-TRAN.md b/_pages/tag-def/FILE-TRAN.md index 492a09b5..1e0e493e 100644 --- a/_pages/tag-def/FILE-TRAN.md +++ b/_pages/tag-def/FILE-TRAN.md @@ -21,54 +21,62 @@ standard tag: TRAN specification: - Translation - | - A type of TRAN for external media files. Each - https://gedcom.io/terms/v7/NOTE-TRAN must have a FORM substructure. See - also FILE. + A type of `TRAN` for external media files. Each + `https://gedcom.io/terms/v7/NOTE-TRAN` must have a `FORM` substructure. See + also `FILE` and the [File Path datatype]. + +
If an mp3 audio file has been transcoded as an ogg file and a timestamped transcript has been extracted as a WebVTT file, the resulting set of files might be presented as follows: - 0 @EX@ OBJE - 1 FILE media/original.mp3 - 2 FORM audio/mp3 - 2 TRAN media/derived.oga - 3 FORM audio/ogg - 2 TRAN media/transcript.vtt - 3 FORM text/vtt + ```gedcom + 0 @EX@ OBJE + 1 FILE media/original.mp3 + 2 FORM audio/mp3 + 2 TRAN media/derived.oga + 3 FORM audio/ogg + 2 TRAN media/transcript.vtt + 3 FORM text/vtt + ``` + +
- Note that FILE.TRAN refers to translation to a different digital format, + Note that `FILE`.`TRAN` refers to translation to a different digital format, not to translation to a different human language. Files that differ in the - human language of their content should each be given their own FILE + human language of their content should each be given their own `FILE` structure. - | - A representation of the superstructure’s data in a different format. + A representation of the superstructure's data in a different format. In some situations it is desirable to provide the same semantic content in - multiple formats. Where this is desirable, a TRAN substructure is used, - where the specific format is given in its language tag substructure, media - type substructure, or both. + multiple formats. Where this is desirable, a `TRAN` substructure is used, where + the specific format is given in its language tag substructure, media type + substructure, or both. - Different TRAN structures are used in different contexts to fully capture - the structure of the information being presented in multiple formats. In - all cases, a TRAN structure’s payload and substructures should provide only - information also contained in the TRAN structures’ superstructure, but - provide it in a new language, script, or media type. + Different `TRAN` structures are used in different contexts to fully capture the + structure of the information being presented in multiple formats. In all cases, + a `TRAN` structure's payload and substructures should provide only information + also contained in the `TRAN` structures' superstructure, but provide it in a + new language, script, or media type. - Each TRAN substructure must have either a language tag or a media type or - both. Each TRAN structure must differ from its superstructure and from - every other TRAN substructure of its superstructure in either its language - tag or its media type or both. + Each `TRAN` substructure must have either a language tag or a media type or + both. Each `TRAN` structure must differ from its superstructure and from every + other `TRAN` substructure of its superstructure in either its language tag or + its media type or both. label: 'Translation' -payload: http://www.w3.org/2001/XMLSchema#string +payload: https://gedcom.io/terms/v7/type-FilePath substructures: "https://gedcom.io/terms/v7/FORM": "{1:1}" superstructures: "https://gedcom.io/terms/v7/FILE": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FILE.md b/_pages/tag-def/FILE.md index ca95cadb..db3b2736 100644 --- a/_pages/tag-def/FILE.md +++ b/_pages/tag-def/FILE.md @@ -20,52 +20,12 @@ standard tag: FILE specification: - File reference - - | - A reference to an external file. Syntactically, the payload is a URI - reference as defined by RFC 3986, or a valid URL string as defined by the - WHATWG URL specification. That is, it can be an absolute or relative URL, - optionally with a fragment string. However, only the following URL types - are used: - - - A URL with scheme ftp, http, or https refers to a web-accessible file. - - - A URL with scheme file refers to a machine-local file as defined by RFC - 8089. Machine-local files must not be used in FamilySearch GEDZIP nor - when sharing datasets on the web or with unknown parties, but may be - used for close collaboration between parties with known similar file - structures. - - - A URI reference with all of the following: - - - no scheme - - not beginning with / (U+002F) - - not containing any path segments equal to .. (U+002E U+002E) - - not containing a reverse solidus character (U+005C \) or banned - character, either directly or in escaped form - - no query or fragment - - refers to a local file. If the dataset is part of a GEDZIP file, the - URL of the local file is a zip archive filename; otherwise, the URL of - a local file is resolved with base equal to the directory containing - the dataset. - - It is recommended that local files use the directory prefix media/, but - doing so is not required. - - For compatibility with GEDZIP and related formats, it is recommended - that the following FILE payloads not be used: - - - gedcom.ged - - MANIFEST.MF - - any URL beginning META-INF/ - - The meaning of a FILE payload with any format not listed above is not - defined by this version of the specification, but may be defined in a - subsequent version. + - A reference to an external file. See the [File Path datatype] for more + details. label: 'File reference' -payload: http://www.w3.org/2001/XMLSchema#string +payload: https://gedcom.io/terms/v7/type-FilePath substructures: "https://gedcom.io/terms/v7/FILE-TRAN": "{0:M}" @@ -74,6 +34,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-OBJE": "{1:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/FORM.md b/_pages/tag-def/FORM.md index fad0a954..a3433119 100644 --- a/_pages/tag-def/FORM.md +++ b/_pages/tag-def/FORM.md @@ -20,7 +20,7 @@ standard tag: FORM specification: - Format - - The media type of the file referenced by the superstructure. + - The [media type] of the file referenced by the superstructure. label: 'Format' @@ -32,6 +32,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/FILE": "{1:1}" "https://gedcom.io/terms/v7/FILE-TRAN": "{1:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/GEDC-VERS.md b/_pages/tag-def/GEDC-VERS.md index a86273c0..eaa414b8 100644 --- a/_pages/tag-def/GEDC-VERS.md +++ b/_pages/tag-def/GEDC-VERS.md @@ -20,10 +20,11 @@ standard tag: VERS specification: - Version - - The version number of the official specification that this document’s data + - The version number of the official specification that this document's data conforms to. This must include the major and minor version (for example, - “7.0”); it may include the patch as well (for example, “7.0.1”), but doing - so is not required. See [A Guide to Version Numbers] for more. + "`7.0`"); it may include the patch as well (for example, "`7.0.1`"), but doing + so is not required. See [A Guide to Version Numbers] for more details about + version numbers. label: 'Version' @@ -33,6 +34,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/GEDC": "{1:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/GEDC.md b/_pages/tag-def/GEDC.md index 415ba594..b8e8969f 100644 --- a/_pages/tag-def/GEDC.md +++ b/_pages/tag-def/GEDC.md @@ -23,8 +23,8 @@ specification: - | A container for information about the entire document. - It is recommended that applications write GEDC with its required subrecord - VERS as the first substructure of HEAD. + It is recommended that applications write `GEDC` with its required substructure + `https://gedcom.io/terms/v7/GEDC-VERS` as the first substructure of `HEAD`. label: 'GEDCOM' @@ -35,6 +35,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/HEAD": "{1:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/GIVN.md b/_pages/tag-def/GIVN.md index e14d839c..f351ba48 100644 --- a/_pages/tag-def/GIVN.md +++ b/_pages/tag-def/GIVN.md @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}" "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/GRAD.md b/_pages/tag-def/GRAD.md index bc11ff90..7f756a66 100644 --- a/_pages/tag-def/GRAD.md +++ b/_pages/tag-def/GRAD.md @@ -20,7 +20,7 @@ standard tag: GRAD specification: - Graduation - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - graduation - Awarding educational diplomas or degrees to individuals. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/HEAD-DATE.md b/_pages/tag-def/HEAD-DATE.md index 1c1d1aad..605039ea 100644 --- a/_pages/tag-def/HEAD-DATE.md +++ b/_pages/tag-def/HEAD-DATE.md @@ -20,7 +20,7 @@ standard tag: DATE specification: - Date - - The DateExact that this document was created. + - The `DateExact` that this document was created. label: 'Date' @@ -31,6 +31,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/HEAD": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/HEAD-LANG.md b/_pages/tag-def/HEAD-LANG.md index 2c98b32b..a9007259 100644 --- a/_pages/tag-def/HEAD-LANG.md +++ b/_pages/tag-def/HEAD-LANG.md @@ -21,25 +21,30 @@ standard tag: LANG specification: - Language - | - A default language which may be used to interpret any Text-typed payloads - that lack a specific language tag from a https://gedcom.io/terms/v7/LANG - structure. An application may choose to use a different default based on - its knowledge of the language preferences of the user. + A default language which may be used to interpret any `Text`-typed payloads + that lack a specific language tag from a `https://gedcom.io/terms/v7/LANG` + structure. An application may choose to use a different default based on its + knowledge of the language preferences of the user. - The payload of the LANG structure is a language tag, as defined by BCP 47. + The payload of the `LANG` structure is a language tag, as defined by [BCP + 47]. + +
Some algorithms on text are language-specific. Examples include sorting sequences, name comparison and phonetic name matching algorithms, spell-checking, computer-synthesized speech, Braille transcription, and language translation. When the language of the text is given through a - https://gedcom.io/terms/v7/LANG, that should be used. When - https://gedcom.io/terms/v7/LANG is not available, - https://gedcom.io/terms/v7/HEAD-LANG provides the file creator’s suggested - default language. For some language-specific algorithms, the user’s - preferred language may be a more appropriate default than the file’s - default language. User language preferences can be found in a variety of - platform-specific places, such as the default language from operating - system settings, user locales, Input Method Editors (IMEs), etc. + `https://gedcom.io/terms/v7/LANG`, that should be used. When + `https://gedcom.io/terms/v7/LANG` is not available, + `https://gedcom.io/terms/v7/HEAD-LANG` provides the file creator's suggested + default language. For some language-specific algorithms, the user's preferred + language may be a more appropriate default than the file's default language. + User language preferences can be found in a variety of platform-specific + places, such as the default language from operating system settings, user + locales, Input Method Editors (IMEs), etc. + +
label: 'Language' @@ -49,6 +54,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/HEAD": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/HEAD-PLAC-FORM.md b/_pages/tag-def/HEAD-PLAC-FORM.md index c7b42b17..04f42598 100644 --- a/_pages/tag-def/HEAD-PLAC-FORM.md +++ b/_pages/tag-def/HEAD-PLAC-FORM.md @@ -20,7 +20,7 @@ standard tag: FORM specification: - Format - - Any PLAC with no FORM shall be treated as if it has this FORM. + - Any `PLAC` with no [`FORM`] shall be treated as if it has this [`FORM`]. label: 'Format' @@ -30,6 +30,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/HEAD-PLAC": "{1:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/HEAD-PLAC.md b/_pages/tag-def/HEAD-PLAC.md index 09d64308..94b21ee6 100644 --- a/_pages/tag-def/HEAD-PLAC.md +++ b/_pages/tag-def/HEAD-PLAC.md @@ -20,7 +20,7 @@ standard tag: PLAC specification: - Place - - This is a placeholder for providing a default PLAC.FORM, and must not have + - This is a placeholder for providing a default `PLAC`.`FORM`, and must not have a payload. label: 'Place' @@ -32,6 +32,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/HEAD": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/HEAD-SOUR-DATA.md b/_pages/tag-def/HEAD-SOUR-DATA.md index c076e1a8..cf92d921 100644 --- a/_pages/tag-def/HEAD-SOUR-DATA.md +++ b/_pages/tag-def/HEAD-SOUR-DATA.md @@ -20,9 +20,9 @@ standard tag: DATA specification: - Data - - The electronic data source or digital repository from which this dataset - was exported. The payload is the name of that source, with substructures - providing additional details about the source (not the export). + - The electronic data source or digital repository from which this dataset was + exported. The payload is the name of that source, with substructures providing + additional details about the source (not the export). label: 'Data' @@ -34,6 +34,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/HEAD-SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/HEAD-SOUR.md b/_pages/tag-def/HEAD-SOUR.md index 916e84c7..c7c8ba8e 100644 --- a/_pages/tag-def/HEAD-SOUR.md +++ b/_pages/tag-def/HEAD-SOUR.md @@ -20,10 +20,10 @@ standard tag: SOUR specification: - Source - - An identifier for the product producing this dataset. A registration - process for these identifiers existed for a time, but no longer does. If an - existing identifier is known, it should be used. Otherwise, a URI owned by - the product should be used instead. + - An identifier for the product producing this dataset. A registration process + for these identifiers existed for a time, but no longer does. If an existing + identifier is known, it should be used. Otherwise, a URI owned by the product + should be used instead. label: 'Source' @@ -37,6 +37,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/HEAD": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/HEAD.md b/_pages/tag-def/HEAD.md index 5e0c71ac..cd2f5a61 100644 --- a/_pages/tag-def/HEAD.md +++ b/_pages/tag-def/HEAD.md @@ -20,20 +20,21 @@ standard tag: HEAD specification: - Header - - A pseudo-structure for storing metadata about the document. See The Header - and Trailer for more. + - A pseudo-structure for storing metadata about the document. See [The Header + and Trailer] for more details. - | - The header pseudo-structure provides metadata about the entire dataset. A - few substructures of note: + The header pseudo-structure provides metadata about the entire dataset. A few + substructures of note: - - GEDC identifies the specification that this document conforms to. It is - recommended that GEDC be the first substructure of the header. - - SCHMA gives the meaning of extension tags; see Extensions for more. - - SOUR describes the originating software. - - CORP describes the corporation creating the software. - - HEAD.SOUR.DATA describes a larger database this data is extracted - from. - - LANG and PLAC give a default value for the rest of the document. + - `GEDC` identifies the specification that this document conforms to. It is + recommended that `GEDC` be the first substructure of the header. + - `SCHMA` gives the meaning of extension tags; see [Extensions] for more + details. + - `SOUR` describes the originating software. + - `CORP` describes the corporation creating the software. + - `HEAD`.`SOUR`.`DATA` describes a larger database this data is extracted + from. + - `LANG` and `PLAC` give a default value for the rest of the document. label: 'Header' @@ -53,6 +54,8 @@ substructures: "https://gedcom.io/terms/v7/SUBM": "{0:1}" superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/HEIGHT.md b/_pages/tag-def/HEIGHT.md index 45289b92..c572859a 100644 --- a/_pages/tag-def/HEIGHT.md +++ b/_pages/tag-def/HEIGHT.md @@ -21,13 +21,24 @@ standard tag: HEIGHT specification: - Height in pixels - | - How many pixels to display vertically for the image. See CROP for more. + How many pixels to display vertically for the image. See `CROP` for more + details. - HEIGHT is a number of pixels. The correct tag for the height of an - individual is the DSCR attribute. +
- 0 @I45@ INDI - 1 DSCR brown eyes, 5ft 10in, 198 pounds + `HEIGHT` is a number of pixels. The correct tag for the height of an individual + is the `DSCR` attribute. + +
+ + ```gedcom + 0 @I45@ INDI + 1 DSCR brown eyes, 5ft 10in, 198 pounds + ``` + +
+ +
label: 'Height in pixels' @@ -37,6 +48,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/CROP": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/HUSB.md b/_pages/tag-def/HUSB.md index 419c8d5a..f5fb5f3c 100644 --- a/_pages/tag-def/HUSB.md +++ b/_pages/tag-def/HUSB.md @@ -21,7 +21,7 @@ standard tag: HUSB specification: - Husband - A container for information relevant to the subject of the superstructure - specific to the individual described by the associated FAM’s HUSB + specific to the individual described by the associated `FAM`'s `HUSB` substructure. label: 'Husband' @@ -46,6 +46,8 @@ superstructures: "https://gedcom.io/terms/v7/MARL": "{0:1}" "https://gedcom.io/terms/v7/MARR": "{0:1}" "https://gedcom.io/terms/v7/MARS": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/IDNO.md b/_pages/tag-def/IDNO.md index 84b4bf8a..a237b6d9 100644 --- a/_pages/tag-def/IDNO.md +++ b/_pages/tag-def/IDNO.md @@ -20,11 +20,11 @@ standard tag: IDNO specification: - Identification number - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - identifying number - - A number or other string assigned to identify a person within some - significant external system. It must have a TYPE substructure to define - what kind of identification number is being provided. + - A number or other string assigned to identify a person within some significant + external system. It must have a `TYPE` substructure to define what kind of + identification number is being provided. label: 'Identification number' @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/IMMI.md b/_pages/tag-def/IMMI.md index 5858d14b..8e6894e5 100644 --- a/_pages/tag-def/IMMI.md +++ b/_pages/tag-def/IMMI.md @@ -20,7 +20,7 @@ standard tag: IMMI specification: - Immigration - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - immigration - Entering into a new locality with the intent of residing there. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INDI-CENS.md b/_pages/tag-def/INDI-CENS.md index b32de160..bb8ae6e5 100644 --- a/_pages/tag-def/INDI-CENS.md +++ b/_pages/tag-def/INDI-CENS.md @@ -20,10 +20,10 @@ standard tag: CENS specification: - Census - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - census - - Periodic count of the population for a designated locality, such as a - national or state census. + - Periodic count of the population for a designated locality, such as a national + or state census. label: 'Census' @@ -54,9 +54,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVEN" - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INDI-EVEN.md b/_pages/tag-def/INDI-EVEN.md index 5855a5b3..2b5f3e27 100644 --- a/_pages/tag-def/INDI-EVEN.md +++ b/_pages/tag-def/INDI-EVEN.md @@ -22,20 +22,26 @@ specification: - Event - | An event: a noteworthy happening related to an individual or family. If a - specific event type exists, it should be used instead of a generic EVEN - structure. Each EVEN must be classified by a subordinate use of the TYPE - tag and may be further described in the structure’s payload. + specific event type exists, it should be used instead of a generic `EVEN` + structure. Each `EVEN` must be classified by a subordinate use of the `TYPE` + tag and may be further described in the structure's payload. + +
A person that signed a lease for land dated October 2, 1837 and a lease for mining equipment dated November 4, 1837 would be written as: - 0 @I1@ INDI - 1 EVEN - 2 TYPE Land Lease - 2 DATE 2 OCT 1837 - 1 EVEN Mining equipment - 2 TYPE Equipment Lease - 2 DATE 4 NOV 1837 + ```gedcom + 0 @I1@ INDI + 1 EVEN + 2 TYPE Land Lease + 2 DATE 2 OCT 1837 + 1 EVEN Mining equipment + 2 TYPE Equipment Lease + 2 DATE 4 NOV 1837 + ``` + +
label: 'Event' @@ -66,8 +72,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INDI-FACT.md b/_pages/tag-def/INDI-FACT.md index e969ae86..0f3a2e79 100644 --- a/_pages/tag-def/INDI-FACT.md +++ b/_pages/tag-def/INDI-FACT.md @@ -22,17 +22,23 @@ specification: - Fact - | A noteworthy attribute or fact concerning an individual or family. If a - specific attribute type exists, it should be used instead of a generic FACT - structure. Each FACT must be classified by a subordinate use of the TYPE - tag and may be further described in the structure’s payload. + specific attribute type exists, it should be used instead of a generic `FACT` + structure. Each `FACT` must be classified by a subordinate use of the `TYPE` + tag and may be further described in the structure's payload. - If the attribute being defined was 1 of the person’s skills, such as - woodworking, the FACT tag would have the value of “Woodworking”, followed - by a subordinate TYPE tag with the value “Skills”. +
- 0 @I1@ INDI - 1 FACT Woodworking - 2 TYPE Skills + If the attribute being defined was 1 of the person's skills, such as + woodworking, the `FACT` tag would have the value of "Woodworking", followed by + a subordinate `TYPE` tag with the value "Skills". + + ```gedcom + 0 @I1@ INDI + 1 FACT Woodworking + 2 TYPE Skills + ``` + +
label: 'Fact' @@ -63,8 +69,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INDI-FAMC.md b/_pages/tag-def/INDI-FAMC.md index 165f820d..a65deb0f 100644 --- a/_pages/tag-def/INDI-FAMC.md +++ b/_pages/tag-def/INDI-FAMC.md @@ -20,9 +20,9 @@ standard tag: FAMC specification: - Family child - - The family in which an individual appears as a child. It is also used with - a STAT substructure to show individuals who are not children of the family. - See FAM and FAMC.STAT for more. + - The family in which an individual appears as a child. It is also used with a + `https://gedcom.io/terms/v7/FAMC-STAT` substructure to show individuals who are + not children of the family. See `FAMILY_RECORD` for more details. label: 'Family child' @@ -36,6 +36,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INDI-NAME.md b/_pages/tag-def/INDI-NAME.md index 804441f3..1cb4132d 100644 --- a/_pages/tag-def/INDI-NAME.md +++ b/_pages/tag-def/INDI-NAME.md @@ -20,34 +20,37 @@ standard tag: NAME specification: - Name - - A PERSONAL_NAME_STRUCTURE with parts, translations, sources, and so forth. + - A `PERSONAL_NAME_STRUCTURE` with parts, translations, sources, and so forth. - | - Names of individuals are represented in the manner the name is normally - spoken, with the family name, surname, or nearest cultural parallel - thereunto separated by slashes (U+002F /). Based on the dynamic nature or - unknown compositions of naming conventions, it is difficult to provide a - more detailed name piece structure to handle every case. The - PERSONAL_NAME_PIECES are provided optionally for systems that cannot - operate effectively with less structured information. The Personal Name - payload shall be seen as the primary name representation, with name pieces - as optional auxiliary information; in particular it is recommended that all - name parts in PERSONAL_NAME_PIECES appear within the PersonalName payload - in some form, possibly adjusted for gender-specific suffixes or the like. - It is permitted for the payload to contain information not present in any - name piece substructure. + Names of individuals are represented in the manner the name is normally spoken, + with the family name, surname, or nearest cultural parallel thereunto separated + by slashes (U+002F `/`). Based on the dynamic nature or unknown compositions of + naming conventions, it is difficult to provide a more detailed name piece + structure to handle every case. The `PERSONAL_NAME_PIECES` are provided + optionally for systems that cannot operate effectively with less structured + information. The Personal Name payload shall be seen as the primary name + representation, with name pieces as optional auxiliary information; in + particular it is recommended that all name parts in `PERSONAL_NAME_PIECES` + appear within the `PersonalName` payload in some form, possibly adjusted for + gender-specific suffixes or the like. It is permitted for the payload to + contain information not present in any name piece substructure. The name may be translated or transliterated into different languages or - scripts using the TRAN substructure. It is recommended, but not required, - that if the name pieces are used, the same pieces are used in each - translation and transliteration. + scripts using the `TRAN` substructure. It is recommended, but not required, + that if the name pieces are used, the same pieces are used in each translation + and transliteration. - A TYPE is used to specify the particular variation that this name is. For + A `TYPE` is used to specify the particular variation that this name is. For example; it could indicate that this name is a name taken at immigration or that it could be an ‘also known as’ name. See - https://gedcom.io/terms/v7/enumset-NAME-TYPE for more. + `https://gedcom.io/terms/v7/enumset-NAME-TYPE` for more details. - Alternative approaches to representing names are being considered for - future versions of this specification. +
+ + Alternative approaches to representing names are being considered for future + versions of this specification. + +
label: 'Name' @@ -68,6 +71,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INDI-NCHI.md b/_pages/tag-def/INDI-NCHI.md index 2f9617ba..2393ac52 100644 --- a/_pages/tag-def/INDI-NCHI.md +++ b/_pages/tag-def/INDI-NCHI.md @@ -20,7 +20,7 @@ standard tag: NCHI specification: - Number of children - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - number of children - The number of children that this person is known to be the parent of (all marriages). @@ -54,8 +54,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INDI-RELI.md b/_pages/tag-def/INDI-RELI.md index 906421e4..21c3d04b 100644 --- a/_pages/tag-def/INDI-RELI.md +++ b/_pages/tag-def/INDI-RELI.md @@ -20,7 +20,7 @@ standard tag: RELI specification: - Religion - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. label: 'Religion' @@ -50,6 +50,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INDI-RESI.md b/_pages/tag-def/INDI-RESI.md index cd633eeb..692b261b 100644 --- a/_pages/tag-def/INDI-RESI.md +++ b/_pages/tag-def/INDI-RESI.md @@ -21,22 +21,30 @@ standard tag: RESI specification: - Residence - | - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - Where possible, the residence should be identified in PLAC and/or ADDR - substructures of the RESI structure. The payload text should not duplicate - PLAC or ADDR information, but may be used for residence information that + Where possible, the residence should be identified in `PLAC` and/or `ADDR` + substructures of the `RESI` structure. The payload text should not duplicate + `PLAC` or `ADDR` information, but may be used for residence information that cannot be expressed by those structures. - The following two examples show situations where a RESI payload may be +
+ + The following two examples show situations where a `RESI` payload may be appropriate: - 1 RESI living with an aunt - 2 DATE ABT MAR 1894 + ```gedcom + 1 RESI living with an aunt + 2 DATE ABT MAR 1894 + ``` + + ```gedcom + 1 RESI in a mobile caravan + 2 PLAC , , Austro-Hungarian Empire + 3 FORM City, County, Country + ``` - 1 RESI in a mobile caravan - 2 PLAC , , Austro-Hungarian Empire - 3 FORM City, County, Country +
- residence - An address or place of residence where an individual resided. @@ -69,8 +77,7 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" -value of: - - "https://gedcom.io/terms/v7/enumset-EVENATTR" +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INDI-TITL.md b/_pages/tag-def/INDI-TITL.md index a4cd1fa4..86d9858c 100644 --- a/_pages/tag-def/INDI-TITL.md +++ b/_pages/tag-def/INDI-TITL.md @@ -20,7 +20,7 @@ standard tag: TITL specification: - Title - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. label: 'Title' @@ -50,6 +50,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/INIL.md b/_pages/tag-def/INIL.md index 896bbdc4..7303b2f5 100644 --- a/_pages/tag-def/INIL.md +++ b/_pages/tag-def/INIL.md @@ -20,14 +20,14 @@ standard tag: INIL specification: - Initiatory, Latter-Day Saint - - A Latter-Day Saint Ordinance. See also LDS_INDIVIDUAL_ORDINANCE. - Previously, GEDCOM versions 3.0 through 5.3 called this WAC; it was not - part of 5.4 through 5.5.1. FamilySearch GEDCOM 7.0 reintroduced it with the - name INIL for consistency with BAPL, CONL, and ENDL. + - A [Latter-Day Saint Ordinance]. See also `LDS_INDIVIDUAL_ORDINANCE`. + Previously, GEDCOM versions 3.0 through 5.3 called this `WAC`; it was not part + of 5.4 through 5.5.1. FamilySearch GEDCOM 7.0 reintroduced it with the name + `INIL` for consistency with `BAPL`, `CONL`, and `ENDL`. - initiatory - - A religious event where an initiatory ordinance for an individual was - performed by priesthood authority in a temple of The Church of Jesus Christ - of Latter-day Saints. + - A religious event where an initiatory ordinance for an individual was performed + by priesthood authority in a temple of The Church of Jesus Christ of Latter-day + Saints. label: 'Initiatory, Latter-Day Saint' @@ -44,6 +44,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/LANG.md b/_pages/tag-def/LANG.md index c9691357..2c322bea 100644 --- a/_pages/tag-def/LANG.md +++ b/_pages/tag-def/LANG.md @@ -21,48 +21,59 @@ standard tag: LANG specification: - Language - | - The primary human language of the superstructure. The primary language in - which the Text-typed payloads of the superstructure and its substructures - appear. + The primary human language of the superstructure. The primary language in which + the `Text`-typed payloads of the superstructure and its substructures appear. - The payload of the LANG structure is a language tag, as defined by BCP 47. - A registry of component subtags is maintained publicly by the IANA. + The payload of the `LANG` structure is a language tag, as defined by [BCP + 47]. A [registry of component subtags] is maintained publicly by the IANA. - In the absence of a LANG structure, the language is assumed to be - unspecified; that may also be recorded explicitly with language tag und - (meaning “undetermined”). See https://gedcom.io/terms/v7/HEAD-LANG for + In the absence of a `LANG` structure, the language is assumed to be + unspecified; that may also be recorded explicitly with language tag `und` + (meaning "undetermined"). See `https://gedcom.io/terms/v7/HEAD-LANG` for information about applying language-specific algorithms to text in an unspecified language. If the text is primarily in one language with a few parts in a different language, it is recommended that a language tag identifying the primary - language be used. If no one language is primary, the language tag mul - (meaning “multiple”) may be used, but most language-specific algorithms - will treat mul the same way they do und. + language be used. If no one language is primary, the language tag `mul` + (meaning "multiple") may be used, but most language-specific algorithms will + treat `mul` the same way they do `und`. - Conversations are ongoing about adding part-of-payload language tagging in - a future version of the specification to provide more fidelity for - multilingual text. +
- If the text is not in any human language and should not be treated as - lingual content, the language tag zxx (meaning “no linguistic content” or - “not applicable”) may be used. An example of zxx text might be a diagram + Conversations are ongoing about adding part-of-payload language tagging in a + future version of the specification to provide more fidelity for multilingual + text. + +
+ + If the text is not in any human language and should not be treated as lingual + content, the language tag `zxx` (meaning "no linguistic content" or "not + applicable") may be used. An example of `zxx` text might be a diagram approximated using characters for their shape, not their meaning. - This specification does not permit LANG in every place where human language - text might appear. Conversations are ongoing about adding it in more places - in a future version of the specification. Using the current specification, - additional language tagging can be accomplished using a documented - extension tag by including the following in the header: +
+ + This specification does not permit `LANG` in every place where human language + text might appear. Conversations are ongoing about adding it in more places in + a future version of the specification. Using the current specification, + additional language tagging can be accomplished using a [documented extension + tag] by including the following in the header: - 1 SCHEMA - 2 TAG _LANG https://gedcom.io/terms/v7/LANG + ```gedcom + 1 SCHEMA + 2 TAG _LANG https://gedcom.io/terms/v7/LANG + ``` and using the extension tag like so: - 2 DATE 31 AUG 2018 - 3 PHRASE 2018年8月31日 - 4 _LANG cmn + ```gedcom + 2 DATE 31 AUG 2018 + 3 PHRASE 2018年8月31日 + 4 _LANG cmn + ``` + +
label: 'Language' @@ -78,6 +89,8 @@ superstructures: "https://gedcom.io/terms/v7/PLAC-TRAN": "{1:1}" "https://gedcom.io/terms/v7/TEXT": "{0:1}" "https://gedcom.io/terms/v7/record-SNOTE": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/LATI.md b/_pages/tag-def/LATI.md index 04b7e249..fb1f5ab0 100644 --- a/_pages/tag-def/LATI.md +++ b/_pages/tag-def/LATI.md @@ -21,13 +21,17 @@ standard tag: LATI specification: - Latitude - | - A latitudinal coordinate. The payload is either N (for a coordinate north - of the equator) or S (for a coordinate south of the equator) followed by a + A latitudinal coordinate. The payload is either `N` (for a coordinate north of + the equator) or `S` (for a coordinate south of the equator) followed by a decimal number of degrees. Minutes and seconds are not used and should be converted to fractional degrees prior to encoding. +
+ 18 degrees, 9 minutes, and 3.4 seconds North would be formatted as - N18.150944. + `N18.150944`. + +
label: 'Latitude' @@ -37,6 +41,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/MAP": "{1:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/LEFT.md b/_pages/tag-def/LEFT.md index 82e65b69..8675ce38 100644 --- a/_pages/tag-def/LEFT.md +++ b/_pages/tag-def/LEFT.md @@ -20,8 +20,8 @@ standard tag: LEFT specification: - Left crop width - - Left is a number of pixels to not display from the left side of the image. - See CROP for more. + - Left is a number of pixels to not display from the left side of the image. See + `CROP` for more details. label: 'Left crop width' @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/CROP": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/LONG.md b/_pages/tag-def/LONG.md index 5e3789ec..09a5dcf9 100644 --- a/_pages/tag-def/LONG.md +++ b/_pages/tag-def/LONG.md @@ -21,13 +21,17 @@ standard tag: LONG specification: - Longitude - | - A longitudinal coordinate. The payload is either E (for a coordinate east - of the prime meridian) or W (for a coordinate west of the prime meridian) - followed by a decimal number of degrees. Minutes and seconds are not used - and should be converted to fractional degrees prior to encoding. + A longitudinal coordinate. The payload is either `E` (for a coordinate east of + the prime meridian) or `W` (for a coordinate west of the prime meridian) + followed by a decimal number of degrees. Minutes and seconds are not used and + should be converted to fractional degrees prior to encoding. + +
168 degrees, 9 minutes, and 3.4 seconds East would be formatted as - E168.150944. + `E168.150944`. + +
label: 'Longitude' @@ -37,6 +41,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/MAP": "{1:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/MAP.md b/_pages/tag-def/MAP.md index d6d284eb..be96dc8d 100644 --- a/_pages/tag-def/MAP.md +++ b/_pages/tag-def/MAP.md @@ -21,14 +21,13 @@ standard tag: MAP specification: - Map - | - A representative point for a location, as defined by LATI and LONG + A representative point for a location, as defined by `LATI` and `LONG` substructures. - Note that MAP provides neither a notion of accuracy (for example, the MAP - for a birth event may be some distance from the point where the birth - occurred) nor a notion of region size (for example, the MAP for a place - “Belarus” may be anywhere within that nation’s 200,000 square kilometer - area). + Note that `MAP` provides neither a notion of accuracy (for example, the `MAP` + for a birth event may be some distance from the point where the birth occurred) + nor a notion of region size (for example, the `MAP` for a place "Belarus" may + be anywhere within that nation's 200,000 square kilometer area). label: 'Map' @@ -40,6 +39,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/PLAC": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/MARB.md b/_pages/tag-def/MARB.md index 259c73b8..126f70ea 100644 --- a/_pages/tag-def/MARB.md +++ b/_pages/tag-def/MARB.md @@ -20,7 +20,7 @@ standard tag: MARB specification: - Marriage banns - - A Family Event. See also FAMILY_EVENT_STRUCTURE. + - A [Family Event]. See also `FAMILY_EVENT_STRUCTURE`. - marriage bann - Official public notice given that 2 people intend to marry. @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/MARC.md b/_pages/tag-def/MARC.md index 5755300e..989e8716 100644 --- a/_pages/tag-def/MARC.md +++ b/_pages/tag-def/MARC.md @@ -20,11 +20,11 @@ standard tag: MARC specification: - Marriage contract - - A Family Event. See also FAMILY_EVENT_STRUCTURE. + - A [Family Event]. See also `FAMILY_EVENT_STRUCTURE`. - marriage contract - - Recording a formal agreement of marriage, including the prenuptial - agreement in which marriage partners reach agreement about the property - rights of 1 or both, securing property to their children. + - Recording a formal agreement of marriage, including the prenuptial agreement in + which marriage partners reach agreement about the property rights of 1 or both, + securing property to their children. label: 'Marriage contract' @@ -59,6 +59,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/MARL.md b/_pages/tag-def/MARL.md index d0f3274c..01500d7f 100644 --- a/_pages/tag-def/MARL.md +++ b/_pages/tag-def/MARL.md @@ -20,7 +20,7 @@ standard tag: MARL specification: - Marriage license - - A Family Event. See also FAMILY_EVENT_STRUCTURE. + - A [Family Event]. See also `FAMILY_EVENT_STRUCTURE`. - marriage license - Obtaining a legal license to marry. @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/MARR.md b/_pages/tag-def/MARR.md index ba7ca247..43eb3af0 100644 --- a/_pages/tag-def/MARR.md +++ b/_pages/tag-def/MARR.md @@ -20,10 +20,10 @@ standard tag: MARR specification: - Marriage - - A Family Event. See also FAMILY_EVENT_STRUCTURE. + - A [Family Event]. See also `FAMILY_EVENT_STRUCTURE`. - marriage - - A legal, common-law, or customary event such as a wedding or marriage - ceremony that joins 2 partners to create or extend a family unit. + - A legal, common-law, or customary event such as a wedding or marriage ceremony + that joins 2 partners to create or extend a family unit. label: 'Marriage' @@ -58,6 +58,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/MARS.md b/_pages/tag-def/MARS.md index 38282c2a..ee5e9122 100644 --- a/_pages/tag-def/MARS.md +++ b/_pages/tag-def/MARS.md @@ -20,11 +20,11 @@ standard tag: MARS specification: - Marriage settlement - - A Family Event. See also FAMILY_EVENT_STRUCTURE. + - A [Family Event]. See also `FAMILY_EVENT_STRUCTURE`. - marriage settlement - - Creating an agreement between 2 people contemplating marriage, at which - time they agree to release or modify property rights that would otherwise - arise from the marriage. + - Creating an agreement between 2 people contemplating marriage, at which time + they agree to release or modify property rights that would otherwise arise from + the marriage. label: 'Marriage settlement' @@ -59,6 +59,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/MEDI.md b/_pages/tag-def/MEDI.md index 59244e18..c97b565b 100644 --- a/_pages/tag-def/MEDI.md +++ b/_pages/tag-def/MEDI.md @@ -21,17 +21,31 @@ standard tag: MEDI specification: - Medium - | - An enumerated value from set https://gedcom.io/terms/v7/enumset-MEDI + An enumerated value from set `https://gedcom.io/terms/v7/enumset-MEDI` providing information about the media or the medium in which information is stored. - When MEDI is a substructure of a https://gedcom.io/terms/v7/CALN, it is - recommended that its payload describes the medium directly found at that - call number rather than a medium from which it was derived. + When `MEDI` is a substructure of a `https://gedcom.io/terms/v7/CALN`, it is + recommended that its payload describes the medium directly found at that call + number rather than a medium from which it was derived. - Consider an asset in a repository that is a digital scan of a book of - compiled newspapers; for this asset, the CALN.MEDI is recommended to be - ELECTRONIC rather than BOOK or NEWSPAPER. +
+ + Consider an asset in a repository that is a digital scan of a book of compiled + newspapers; for this asset, the `CALN`.`MEDI` is recommended to be `ELECTRONIC` + rather than `BOOK` or `NEWSPAPER`. + +
+ + When `MEDI` is a substructure of a `https://gedcom.io/terms/v7/FORM`, it is + recommended that its payload describes the medium from which it was derived. + +
+ + Consider a digital photo in a multimedia record; for this asset, the + `FORM`.`MEDI` is recommended to be `PHOTO` rather than `ELECTRONIC`. + +
label: 'Medium' @@ -45,6 +59,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/CALN": "{0:1}" "https://gedcom.io/terms/v7/FORM": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/MIME.md b/_pages/tag-def/MIME.md index 55b4683d..92f64c49 100644 --- a/_pages/tag-def/MIME.md +++ b/_pages/tag-def/MIME.md @@ -21,51 +21,62 @@ standard tag: MIME specification: - Media type - | - Indicates the media type of the payload of the superstructure. + Indicates the [media type] of the payload of the superstructure. As of version 7.0, only 2 media types are supported by this structure: - - text/plain shall be presented to the user as-is, preserving all - spacing, line breaks, and so forth. + - `text/plain` shall be presented to the user as-is, preserving all spacing, + line breaks, and so forth. - - text/html uses HTML tags to provide presentation information. - Applications should support at least the following: + - `text/html` uses HTML tags to provide presentation information. Applications + should support at least the following: - - p and br elements for paragraphing and line breaks. - - b, i, u, and s elements for bold, italic, underlined, and - strike-through text (or corresponding display in other locales; see - HTML §4.5 for more). - - sup and sub elements for super- and sub-script. - - The 3 XML entities that appear in text: &, < >. Note that - "e; and ' are only needed in attributes. Other entities - should be represented as their respective Unicode characters - instead. + - `p` and `br` elements for paragraphing and line breaks. + - `b`, `i`, `u`, and `s` elements for bold, italic, underlined, and + strike-through text (or corresponding display in other locales; see [HTML + §4.5] for more). + - `sup` and `sub` elements for super- and sub-script. + - The 3 XML entities that appear in text: `&`, `<` `>`. Note that + `"e;` and `'` are only needed in attributes. Other entities should + be represented as their respective Unicode characters instead. - Supporting more of HTML is encouraged. Unsupported elements should be - ignored during display. + Supporting more of HTML is encouraged. Unsupported elements should be ignored + during display. + +
Applications are welcome to support more XML entities or HTML character - references in their user interface. However, exporting must only use the - core XML entities, translating any other entities into their corresponding - Unicode characters. + references in their user interface. However, exporting must only use the core + XML entities, translating any other entities into their corresponding Unicode + characters. + +
+ +
+ + Applications are welcome to support additional HTML elements, but they should + ensure that content is meaningful if those extra elements are ignored and only + their content text is displayed. - Applications are welcome to support additional HTML elements, but they - should ensure that content is meaningful if those extra elements are - ignored and only their content text is displayed. +
- Media types are also used by external files, as described under FORM. - External file media types are not limited to text/plain and text/html. +
- If needed, text/html can be converted to text/plain using the following + Media types are also used by external files, as described under `FORM`. + External file media types are not limited to `text/plain` and `text/html`. + +
+ + If needed, `text/html` can be converted to `text/plain` using the following steps: - 1. Replace any sequence of 1 or more spaces, tabs, and line breaks with a - single space - 2. Case-insensitively replace each , , and with a line - break - 3. Remove all other <…> tags - 4. Replace each < with < and > with > - 5. Replace each & with & + 1. Replace any sequence of 1 or more spaces, tabs, and line breaks with a + single space + 2. Case-insensitively replace each ``, ``, and `` + with a line break + 3. Remove all other `<`...`>` tags + 4. Replace each `<` with `<` and `>` with `>` + 5. Replace each `&` with `&` label: 'Media type' @@ -78,6 +89,8 @@ superstructures: "https://gedcom.io/terms/v7/NOTE-TRAN": "{0:1}" "https://gedcom.io/terms/v7/TEXT": "{0:1}" "https://gedcom.io/terms/v7/record-SNOTE": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NAME-TRAN.md b/_pages/tag-def/NAME-TRAN.md index ad7f5be7..929968f6 100644 --- a/_pages/tag-def/NAME-TRAN.md +++ b/_pages/tag-def/NAME-TRAN.md @@ -21,36 +21,42 @@ standard tag: TRAN specification: - Translation - | - A type of TRAN substructure specific to Personal Names. Each NAME.TRAN must - have a LANG substructure. See also INDI.NAME. + A type of `TRAN` substructure specific to [Personal Names]. Each + `NAME`.`TRAN` must have a `LANG` substructure. See also `INDI`.`NAME`. + +
The following presents a name in Mandarin, transliterated using Pinyin - 1 NAME /孔/德庸 - 2 GIVN 德庸 - 2 SURN 孔 - 2 TRAN /Kǒng/ Déyōng - 3 GIVN Déyōng - 3 SURN Kǒng - 3 LANG zh-pinyin + ```gedcom + 1 NAME /孔/德庸 + 2 GIVN 德庸 + 2 SURN 孔 + 2 TRAN /Kǒng/ Déyōng + 3 GIVN Déyōng + 3 SURN Kǒng + 3 LANG zh-pinyin + ``` + +
- | - A representation of the superstructure’s data in a different format. + A representation of the superstructure's data in a different format. In some situations it is desirable to provide the same semantic content in - multiple formats. Where this is desirable, a TRAN substructure is used, - where the specific format is given in its language tag substructure, media - type substructure, or both. + multiple formats. Where this is desirable, a `TRAN` substructure is used, where + the specific format is given in its language tag substructure, media type + substructure, or both. - Different TRAN structures are used in different contexts to fully capture - the structure of the information being presented in multiple formats. In - all cases, a TRAN structure’s payload and substructures should provide only - information also contained in the TRAN structures’ superstructure, but - provide it in a new language, script, or media type. + Different `TRAN` structures are used in different contexts to fully capture the + structure of the information being presented in multiple formats. In all cases, + a `TRAN` structure's payload and substructures should provide only information + also contained in the `TRAN` structures' superstructure, but provide it in a + new language, script, or media type. - Each TRAN substructure must have either a language tag or a media type or - both. Each TRAN structure must differ from its superstructure and from - every other TRAN substructure of its superstructure in either its language - tag or its media type or both. + Each `TRAN` substructure must have either a language tag or a media type or + both. Each `TRAN` structure must differ from its superstructure and from every + other `TRAN` substructure of its superstructure in either its language tag or + its media type or both. label: 'Translation' @@ -67,6 +73,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NAME-TYPE.md b/_pages/tag-def/NAME-TYPE.md index 3cc2b9d1..39b5f9a1 100644 --- a/_pages/tag-def/NAME-TYPE.md +++ b/_pages/tag-def/NAME-TYPE.md @@ -20,7 +20,7 @@ standard tag: TYPE specification: - Type - - An enumerated value from set https://gedcom.io/terms/v7/enumset-NAME-TYPE + - An enumerated value from set `https://gedcom.io/terms/v7/enumset-NAME-TYPE` indicating the type of the name. label: 'Type' @@ -34,6 +34,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/INDI-NAME": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NAME.md b/_pages/tag-def/NAME.md index fe619c28..f45ec039 100644 --- a/_pages/tag-def/NAME.md +++ b/_pages/tag-def/NAME.md @@ -20,7 +20,7 @@ standard tag: NAME specification: - Name - - The name of the superstructure’s subject, represented as a simple string. + - The name of the superstructure's subject, represented as a simple string. label: 'Name' @@ -32,6 +32,8 @@ superstructures: "https://gedcom.io/terms/v7/HEAD-SOUR": "{0:1}" "https://gedcom.io/terms/v7/record-REPO": "{1:1}" "https://gedcom.io/terms/v7/record-SUBM": "{1:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NATI.md b/_pages/tag-def/NATI.md index ff2a479f..e316e4c4 100644 --- a/_pages/tag-def/NATI.md +++ b/_pages/tag-def/NATI.md @@ -20,9 +20,9 @@ standard tag: NATI specification: - Nationality - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - nationality - - An individual’s national heritage or origin, or other folk, house, kindred, + - An individual's national heritage or origin, or other folk, house, kindred, lineage, or tribal interest. label: 'Nationality' @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NATU.md b/_pages/tag-def/NATU.md index 99438235..9228e3d2 100644 --- a/_pages/tag-def/NATU.md +++ b/_pages/tag-def/NATU.md @@ -20,7 +20,7 @@ standard tag: NATU specification: - Naturalization - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - naturalization - Obtaining citizenship. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NICK.md b/_pages/tag-def/NICK.md index 3f31c69c..b9f69718 100644 --- a/_pages/tag-def/NICK.md +++ b/_pages/tag-def/NICK.md @@ -20,8 +20,22 @@ standard tag: NICK specification: - Nickname - - A descriptive or familiar name that is used instead of, or in addition to, - one’s proper name. + - | + A descriptive or familiar name that is used instead of, or in addition to, + one’s official or legal name. + +
+ + The label "nickname" and description text of this structure were introduced + with version 5.5 in 1996, but are understood differently by different users. + Some use `NICK` only for names that would be inappropriate in formal settings. + Some use it for pseudonyms regardless of where they are used. Some use it for + any variant of a name that is not the one used on legal documents. Because all + of these uses, and likely others as well, are common in existing data, no + further clarification of the meaning of the `NICK` structure is possible + without contradicting some existing data. + +
label: 'Nickname' @@ -32,6 +46,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}" "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NMR.md b/_pages/tag-def/NMR.md index 98f047e7..2c3ad148 100644 --- a/_pages/tag-def/NMR.md +++ b/_pages/tag-def/NMR.md @@ -20,7 +20,7 @@ standard tag: NMR specification: - Number of marriages - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - number of marriages - The number of times this person has participated in a family as a spouse or parent. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NO-DATE.md b/_pages/tag-def/NO-DATE.md index 6027e71e..4a8658fb 100644 --- a/_pages/tag-def/NO-DATE.md +++ b/_pages/tag-def/NO-DATE.md @@ -20,8 +20,8 @@ standard tag: DATE specification: - Date - - The DatePeriod during which the event did not occur or the attribute did - not apply. + - The `DatePeriod` during which the event did not occur or the attribute did not + apply. label: 'Date' @@ -32,6 +32,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/NO": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NO.md b/_pages/tag-def/NO.md index f3005cfa..c790097a 100644 --- a/_pages/tag-def/NO.md +++ b/_pages/tag-def/NO.md @@ -20,24 +20,37 @@ standard tag: 'NO' specification: - Did not happen - - An enumerated value from set https://gedcom.io/terms/v7/enumset-EVEN - identifying an event type which did not occur to the superstructure’s - subject. See NON_EVENT_STRUCTURE for more. - | - Indicates that a specific type of event, given in the payload, did not - happen within a given date period (or never happened if there is no DATE + An enumerated value from set `https://gedcom.io/terms/v7/enumset-EVEN` + identifying an event type which did not occur to the superstructure's subject. + A specific payload `NO XYZ` should only appear where `XYZ` would be legal. + + See `NON_EVENT_STRUCTURE` for more details. + - | + Indicates that a specific type of event, given in the payload, did not happen + within a given date period (or never happened if there is no `DATE` substructure). - Substructures may provide discussion about the non-occurrence of the event - but must not limit the meaning of what did not occur. No substructure other - than DATE may restrict the breadth of that negative assertion. + Substructures may provide discussion about the non-occurrence of the event but + must not limit the meaning of what did not occur. No substructure other than + `DATE` may restrict the breadth of that negative assertion. + +
+ + `1 NO MARR` means "no marriage occurred" - 1 NO MARR means “no marriage occurred” +
- 1 NO MARR - 2 DATE TO 24 MAR 1880 +
- means “no marriage had occurred as of March 24^(th), 1880” + ```gedcom + 1 NO MARR + 2 DATE TO 24 MAR 1880 + ``` + + means "no marriage had occurred as of March 24^th^, 1880" + +
label: 'Did not happen' @@ -54,6 +67,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:M}" "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NOTE-TRAN.md b/_pages/tag-def/NOTE-TRAN.md index 112677bb..03cf4a5e 100644 --- a/_pages/tag-def/NOTE-TRAN.md +++ b/_pages/tag-def/NOTE-TRAN.md @@ -21,47 +21,52 @@ standard tag: TRAN specification: - Translation - | - A type of TRAN for unstructured human-readable text, such as is found in - NOTE and SNOTE payloads. Each https://gedcom.io/terms/v7/NOTE-TRAN must - have either a LANG substructure or a MIME substructure or both. If either + A type of `TRAN` for unstructured human-readable text, such as is found in + `NOTE` and `SNOTE` payloads. Each `https://gedcom.io/terms/v7/NOTE-TRAN` must + have either a `LANG` substructure or a `MIME` substructure or both. If either is missing, it is assumed to have the same value as the superstructure. See - also NOTE and SNOTE. + also `NOTE` and `SNOTE`. - The following presents the same note in HTML-format English; in plain-text - with the same language as the superstructure (English); and in Spanish with - the same media type as the superstructure (HTML). +
- 1 NAME Arete /Hernandez/ - 2 NOTE Named after Arete from The Odyssey - 3 LANG en - 3 MIME text/html - 3 TRAN Named after Arete from "The Odyssey" - 4 MIME text/plain - 3 TRAN Nombrada en honor a Arete de La Odisea - 4 LANG es + The following presents the same note in HTML-format English; in plain-text with + the same language as the superstructure (English); and in Spanish with the same + media type as the superstructure (HTML). - It is recommended that text given in text/html should only be translated - into text/plain if the resulting text is different from the text created by - the HTML-to-text conversion process defined in - https://gedcom.io/terms/v7/MIME. + ```gedcom + 1 NAME Arete /Hernandez/ + 2 NOTE Named after Arete from The Odyssey + 3 LANG en + 3 MIME text/html + 3 TRAN Named after Arete from "The Odyssey" + 4 MIME text/plain + 3 TRAN Nombrada en honor a Arete de La Odisea + 4 LANG es + ``` + +
+ + It is recommended that text given in `text/html` should only be translated into + `text/plain` if the resulting text is different from the text created by the + HTML-to-text conversion process defined in `https://gedcom.io/terms/v7/MIME`. - | - A representation of the superstructure’s data in a different format. + A representation of the superstructure's data in a different format. In some situations it is desirable to provide the same semantic content in - multiple formats. Where this is desirable, a TRAN substructure is used, - where the specific format is given in its language tag substructure, media - type substructure, or both. + multiple formats. Where this is desirable, a `TRAN` substructure is used, where + the specific format is given in its language tag substructure, media type + substructure, or both. - Different TRAN structures are used in different contexts to fully capture - the structure of the information being presented in multiple formats. In - all cases, a TRAN structure’s payload and substructures should provide only - information also contained in the TRAN structures’ superstructure, but - provide it in a new language, script, or media type. + Different `TRAN` structures are used in different contexts to fully capture the + structure of the information being presented in multiple formats. In all cases, + a `TRAN` structure's payload and substructures should provide only information + also contained in the `TRAN` structures' superstructure, but provide it in a + new language, script, or media type. - Each TRAN substructure must have either a language tag or a media type or - both. Each TRAN structure must differ from its superstructure and from - every other TRAN substructure of its superstructure in either its language - tag or its media type or both. + Each `TRAN` substructure must have either a language tag or a media type or + both. Each `TRAN` structure must differ from its superstructure and from every + other `TRAN` substructure of its superstructure in either its language tag or + its media type or both. label: 'Translation' @@ -74,6 +79,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/NOTE": "{0:M}" "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NOTE.md b/_pages/tag-def/NOTE.md index d25c0732..d56b4031 100644 --- a/_pages/tag-def/NOTE.md +++ b/_pages/tag-def/NOTE.md @@ -21,13 +21,12 @@ standard tag: NOTE specification: - Note - | - A NOTE_STRUCTURE, containing additional information provided by the - submitter for understanding the enclosing data. + A `NOTE_STRUCTURE`, containing additional information provided by the submitter + for understanding the enclosing data. - When a substructure of HEAD, it should describe the contents of the - document in terms of “ancestors or descendants of” so that the person - receiving the data knows what genealogical information the document - contains. + When a substructure of `HEAD`, it should describe the contents of the document + in terms of "ancestors or descendants of" so that the person receiving the data + knows what genealogical information the document contains. label: 'Note' @@ -114,6 +113,8 @@ superstructures: "https://gedcom.io/terms/v7/record-REPO": "{0:M}" "https://gedcom.io/terms/v7/record-SOUR": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NPFX.md b/_pages/tag-def/NPFX.md index 2d21786a..c65b71ff 100644 --- a/_pages/tag-def/NPFX.md +++ b/_pages/tag-def/NPFX.md @@ -20,8 +20,7 @@ standard tag: NPFX specification: - Name prefix - - Text that appears on a name line before the given and surname parts of a - name. + - Text that appears on a name line before the given and surname parts of a name. label: 'Name prefix' @@ -32,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}" "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/NSFX.md b/_pages/tag-def/NSFX.md index 60ff0cc6..77b6a91f 100644 --- a/_pages/tag-def/NSFX.md +++ b/_pages/tag-def/NSFX.md @@ -20,8 +20,8 @@ standard tag: NSFX specification: - Name suffix - - Text which appears on a name line after or behind the given and surname - parts of a name. + - Text which appears on a name line after or behind the given and surname parts + of a name. label: 'Name suffix' @@ -32,6 +32,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}" "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/OBJE.md b/_pages/tag-def/OBJE.md index 782a605f..072f7b99 100644 --- a/_pages/tag-def/OBJE.md +++ b/_pages/tag-def/OBJE.md @@ -20,15 +20,15 @@ standard tag: OBJE specification: - Object - - See MULTIMEDIA_LINK. + - See `MULTIMEDIA_LINK`. - | - Links the superstructure to the MULTIMEDIA_RECORD with the given pointer. + Links the superstructure to the `MULTIMEDIA_RECORD` with the given pointer. - The optional CROP substructure indicates that a subregion of an image + The optional `CROP` substructure indicates that a subregion of an image represents or applies to the superstructure. - The optional TITL substructure supersedes any OBJE.FILE.TITL substructures - included in the MULTIMEDIA_RECORD. + The optional `TITL` substructure supersedes any `OBJE.FILE.TITL` substructures + included in the `MULTIMEDIA_RECORD`. label: 'Object' @@ -95,6 +95,8 @@ superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" "https://gedcom.io/terms/v7/record-SOUR": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/OCCU.md b/_pages/tag-def/OCCU.md index 3726f612..6e4082e3 100644 --- a/_pages/tag-def/OCCU.md +++ b/_pages/tag-def/OCCU.md @@ -20,7 +20,7 @@ standard tag: OCCU specification: - Occupation - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - occupation - The type of work or profession of an individual. @@ -55,6 +55,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ORDN.md b/_pages/tag-def/ORDN.md index 4d290b9a..0e815ad1 100644 --- a/_pages/tag-def/ORDN.md +++ b/_pages/tag-def/ORDN.md @@ -20,7 +20,7 @@ standard tag: ORDN specification: - Ordination - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - ordination - Receiving authority to act in religious matters. @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PAGE.md b/_pages/tag-def/PAGE.md index 98241063..6d1db82a 100644 --- a/_pages/tag-def/PAGE.md +++ b/_pages/tag-def/PAGE.md @@ -21,27 +21,38 @@ standard tag: PAGE specification: - Page - | - A specific location within the information referenced. For a published - work, this could include the volume of a multi-volume work and the page - number or numbers. For a periodical, it could include volume, issue, and - page numbers. For a newspaper, it could include a date, page number, and - column number. For an unpublished source or microfilmed works, this could - be a film or sheet number, page number, or frame number. A census record - might have an enumerating district, page number, line number, dwelling - number, and family number. + A specific location within the information referenced. For a published work, + this could include the volume of a multi-volume work and the page number or + numbers. For a periodical, it could include volume, issue, and page numbers. + For a newspaper, it could include a date, page number, and column number. For + an unpublished source or microfilmed works, this could be a film or sheet + number, page number, or frame number. A census record might have an enumerating + district, page number, line number, dwelling number, and family number. - It is recommended that the data in this field be formatted comma-separated - with label: value pairs + It is recommended that the data in this field be formatted comma-separated with + label: value pairs - 2 SOUR @S1@ - 3 PAGE Film: 1234567, Frame: 344, Line: 28 +
- If the superstructure’s pointer is @VOID@ then there is no information - referenced and the PAGE may describe the entire source. + ```gedcom + 2 SOUR @S1@ + 3 PAGE Film: 1234567, Frame: 344, Line: 28 + ``` - 1 DSCR Tall enough his head touched the ceiling - 2 SOUR @VOID@ - 3 PAGE His grand-daughter Lydia told me this in 1980 +
+ + If the superstructure's pointer is `@VOID@` then there is no information + referenced and the `PAGE` may describe the entire source. + +
+ + ```gedcom + 1 DSCR Tall enough his head touched the ceiling + 2 SOUR @VOID@ + 3 PAGE His grand-daughter Lydia told me this in 1980 + ``` + +
label: 'Page' @@ -51,6 +62,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PEDI.md b/_pages/tag-def/PEDI.md index 308a9899..60caed71 100644 --- a/_pages/tag-def/PEDI.md +++ b/_pages/tag-def/PEDI.md @@ -20,7 +20,7 @@ standard tag: PEDI specification: - Pedigree - - An enumerated value from set https://gedcom.io/terms/v7/enumset-PEDI + - An enumerated value from set `https://gedcom.io/terms/v7/enumset-PEDI` indicating the type of child-to-family relationship represented by the superstructure. @@ -35,6 +35,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/INDI-FAMC": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PHON.md b/_pages/tag-def/PHON.md index d2b3f635..9313e050 100644 --- a/_pages/tag-def/PHON.md +++ b/_pages/tag-def/PHON.md @@ -23,13 +23,13 @@ specification: - | A telephone number. Telephone numbers have many regional variations and can contain non-digit characters. Users should be encouraged to use - internationalized telephone numbers rather than local versions. As a - starting point for this recommendation, there are international standards - that use a “‘+’” shorthand for the international prefix (for example, in - place of “011” in the US or “00” in the UK). Examples are +1 (555) 555-1234 - (US) or +44 20 1234 1234 (UK). + internationalized telephone numbers rather than local versions. As a starting + point for this recommendation, there are international standards that use a + "'+'" shorthand for the international prefix (for example, in place of "011" in + the US or "00" in the UK). Examples are `+1 (555) 555-1234` (US) or + `+44 20 1234 1234` (UK). - See ITU standards E.123 and E.164 for more information. + See ITU standards [E.123] and [E.164] for more information. label: 'Phone' @@ -92,6 +92,8 @@ superstructures: "https://gedcom.io/terms/v7/WILL": "{0:M}" "https://gedcom.io/terms/v7/record-REPO": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PHRASE.md b/_pages/tag-def/PHRASE.md index 2ea5b82a..fcb39f0a 100644 --- a/_pages/tag-def/PHRASE.md +++ b/_pages/tag-def/PHRASE.md @@ -21,45 +21,81 @@ standard tag: PHRASE specification: - Phrase - | - Textual information that cannot be expressed in the superstructure due to - the limitations of its data type. A PHRASE may restate information - contained in the superstructure, but doing so is not recommended unless it - is needed for clarity. + Textual information that cannot be expressed in the superstructure due to the + limitations of its data type. A `PHRASE` may restate information contained in + the superstructure, but doing so is not recommended unless it is needed for + clarity. - A date interpreted from the phrase “The Feast of St John” might be +
- 2 DATE 24 JUN 1852 - 3 PHRASE During the feast of St John + A date interpreted from the phrase "The Feast of St John" might be - A record using 1648/9 to indicate a change in new year might become + ```gedcom + 2 DATE 24 JUN 1852 + 3 PHRASE During the feast of St John + ``` - 2 DATE 30 JAN 1649 - 3 PHRASE 30th of January, 1648/9 +
- A record using 1648/9 to indicate uncertainty in the year might become +
- 2 DATE BET 1648 AND 1649 - 3 PHRASE 1648/9 + A record using `1648/9` to indicate a change in new year might become - A record using Q1 1867 to indicate an event occurred sometime within the + ```gedcom + 2 DATE 30 JAN 1649 + 3 PHRASE 30th of January, 1648/9 + ``` + +
+ +
+ + A record using `1648/9` to indicate uncertainty in the year might become + + ```gedcom + 2 DATE BET 1648 AND 1649 + 3 PHRASE 1648/9 + ``` + +
+ +
+ + A record using `Q1 1867` to indicate an event occurred sometime within the first quarter of 1867 might become - 2 DATE BET 1 JAN 1867 AND 31 MAR 1867 - 3 PHRASE Q1 1867 + ```gedcom + 2 DATE BET 1 JAN 1867 AND 31 MAR 1867 + 3 PHRASE Q1 1867 + ``` + +
+ +
A record defining the Maid of Honor in a marriage might become - 1 MARR - 2 ASSO @I2@ - 3 ROLE OTHER - 4 PHRASE Maid of Honor + ```gedcom + 1 MARR + 2 ASSO @I2@ + 3 ROLE OTHER + 4 PHRASE Maid of Honor + ``` + +
+ +
A name given to a foundling orphan might be - 1 NAME Mary // - 2 GIVN Mary - 2 TYPE OTHER - 3 PHRASE given by orphanage + ```gedcom + 1 NAME Mary // + 2 GIVN Mary + 2 TYPE OTHER + 3 PHRASE given by orphanage + ``` + +
label: 'Phrase' @@ -85,6 +121,8 @@ superstructures: "https://gedcom.io/terms/v7/ROLE": "{0:1}" "https://gedcom.io/terms/v7/SDATE": "{0:1}" "https://gedcom.io/terms/v7/SOUR-EVEN": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PLAC-FORM.md b/_pages/tag-def/PLAC-FORM.md index 9f44b145..080fcdd2 100644 --- a/_pages/tag-def/PLAC-FORM.md +++ b/_pages/tag-def/PLAC-FORM.md @@ -21,14 +21,20 @@ standard tag: FORM specification: - Format - | - A comma-separated list of jurisdictional titles, which has the same number - of elements and in the same order as the PLAC structure. As with PLAC, this + A comma-separated list of jurisdictional titles, which has the same number of + elements and in the same order as the `PLAC` structure. As with `PLAC`, this shall be ordered from lowest to highest jurisdiction. +
+ The following represents Baltimore, a city that is not within a county. - 2 PLAC Baltimore, , Maryland, USA - 3 FORM City, County, State, Country + ```gedcom + 2 PLAC Baltimore, , Maryland, USA + 3 FORM City, County, State, Country + ``` + +
label: 'Format' @@ -38,6 +44,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/PLAC": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PLAC-TRAN.md b/_pages/tag-def/PLAC-TRAN.md index d663a50f..1df507d2 100644 --- a/_pages/tag-def/PLAC-TRAN.md +++ b/_pages/tag-def/PLAC-TRAN.md @@ -21,37 +21,43 @@ standard tag: TRAN specification: - Translation - | - A type of TRAN substructure specific to places. Each PLAC.TRAN must have a - LANG substructure. See also PLAC. + A type of `TRAN` substructure specific to places. Each `PLAC`.`TRAN` must have + a `LANG` substructure. See also `PLAC`. - The following presents a place in Japanese with a romaji transliteration - and English translation +
- 2 PLAC 千代田, 東京, 日本 - 3 FORM 区, 都, 国 - 3 LANG ja - 3 TRAN Chiyoda, Tokyo, Nihon - 4 LANG ja-Latn - 3 TRAN Chiyoda, Tokyo, Japan - 4 LANG en + The following presents a place in Japanese with a romaji transliteration and + English translation + + ```gedcom + 2 PLAC 千代田, 東京, 日本 + 3 FORM 区, 都, 国 + 3 LANG ja + 3 TRAN Chiyoda, Tokyo, Nihon + 4 LANG ja-Latn + 3 TRAN Chiyoda, Tokyo, Japan + 4 LANG en + ``` + +
- | - A representation of the superstructure’s data in a different format. + A representation of the superstructure's data in a different format. In some situations it is desirable to provide the same semantic content in - multiple formats. Where this is desirable, a TRAN substructure is used, - where the specific format is given in its language tag substructure, media - type substructure, or both. + multiple formats. Where this is desirable, a `TRAN` substructure is used, where + the specific format is given in its language tag substructure, media type + substructure, or both. - Different TRAN structures are used in different contexts to fully capture - the structure of the information being presented in multiple formats. In - all cases, a TRAN structure’s payload and substructures should provide only - information also contained in the TRAN structures’ superstructure, but - provide it in a new language, script, or media type. + Different `TRAN` structures are used in different contexts to fully capture the + structure of the information being presented in multiple formats. In all cases, + a `TRAN` structure's payload and substructures should provide only information + also contained in the `TRAN` structures' superstructure, but provide it in a + new language, script, or media type. - Each TRAN substructure must have either a language tag or a media type or - both. Each TRAN structure must differ from its superstructure and from - every other TRAN substructure of its superstructure in either its language - tag or its media type or both. + Each `TRAN` substructure must have either a language tag or a media type or + both. Each `TRAN` structure must differ from its superstructure and from every + other `TRAN` substructure of its superstructure in either its language tag or + its media type or both. label: 'Translation' @@ -62,6 +68,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/PLAC": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PLAC.md b/_pages/tag-def/PLAC.md index ada5f5d2..9d067327 100644 --- a/_pages/tag-def/PLAC.md +++ b/_pages/tag-def/PLAC.md @@ -21,47 +21,65 @@ standard tag: PLAC specification: - Place - | - 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. 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. + 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, where "jurisdiction" includes units in a political, + ecclesiastical, and geographical hierarchies and may include units of any size, + such as a continent, "at sea", or a specific 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. - The type of each jurisdiction is given in the PLAC.FORM substructure, if - present, or in the HEAD.PLAC.FORM structure. If neither is present, the - jurisdictional types are unspecified beyond the lowest-to-highest order - noted above. + The type of each jurisdiction is given in the `PLAC`.`FORM` substructure, if + present, or in the `HEAD`.`PLAC`.`FORM` structure. If neither is present, the + jurisdictional types are unspecified beyond the lowest-to-highest order noted + above. - | - Having an EXID without an EXID.TYPE substructure is deprecated. The meaning - of an EXID depends on its EXID.TYPE. The cardinality of EXID.TYPE will be - changed to {1:1} in version 8.0. +
+ + Having an `EXID` without an `EXID`.`TYPE` substructure is deprecated. The + meaning of an `EXID` depends on its `EXID`.`TYPE`. The cardinality of + `EXID`.`TYPE` will be changed to `{1:1}` in version 8.0. + +
A place, which can be represented in several ways: - - The payload contains a comma-separated list of region names, ordered - from smallest to largest. The specific meaning of each element is given - by the FORM substructure, or in the HEAD.PLAC.FORM if there is no FORM - substructure. Elements should be left blank if they are unknown, do not - apply to the location, or are too specific for the region in question. + - The payload contains a comma-separated list of region names, ordered from + smallest to largest. The specific meaning of each element is given by the + `FORM` substructure, or in the `HEAD`.`PLAC`.`FORM` if there is no `FORM` + substructure. If neither `FORM` exists, the meaning of the elements are not + defined in this specification beyond being names of jurisdictions of some + kind, ordered from smallest to largest. + + Elements should be left blank if they are unknown, do not apply to the + location, or are too specific for the region in question. + +
+ A record describing births throughout Oneida county could be recorded as - A record describing births throughout Oneida county could be recorded - as + ```gedcom + 0 @S1@ SOUR + 1 DATA + 2 EVEN BIRT + 3 PLAC , Oneida, Idaho, USA + 4 FORM City, County, State, Country + ``` - 0 @S1@ SOUR - 1 DATA - 2 EVEN BIRT - 3 PLAC , Oneida, Idaho, USA - 4 FORM City, County, State, Country +
- - The payload may be translated or transliterated into different - languages or scripts using the TRAN substructure. It should use the - same FORM as the payload. + - The payload may be translated or transliterated into different languages or + scripts using the `TRAN` substructure. It should use the same `FORM` as the + payload. - - Global coordinates may be presented in the MAP substructure + - Global coordinates may be presented in the `MAP` substructure + +
This specification does not support places where a region name contains a - comma. An alternative system for representing locations is likely to be - added in a later version. + comma. An alternative system for representing locations is likely to be added + in a later version. + +
label: 'Place' @@ -135,6 +153,8 @@ superstructures: "https://gedcom.io/terms/v7/SLGS": "{0:1}" "https://gedcom.io/terms/v7/SSN": "{0:1}" "https://gedcom.io/terms/v7/WILL": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/POST.md b/_pages/tag-def/POST.md index b7933794..0502a470 100644 --- a/_pages/tag-def/POST.md +++ b/_pages/tag-def/POST.md @@ -21,7 +21,7 @@ standard tag: POST specification: - Postal code - A code used by a postal service to identify an area to facilitate mail - handling. See ADDRESS_STRUCTURE for more. + handling. See `ADDRESS_STRUCTURE` for more details. label: 'Postal code' @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/ADDR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PROB.md b/_pages/tag-def/PROB.md index 4d4c4b3f..695a39a3 100644 --- a/_pages/tag-def/PROB.md +++ b/_pages/tag-def/PROB.md @@ -20,7 +20,7 @@ standard tag: PROB specification: - Probate - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - probate - Judicial determination of the validity of a will. It may indicate several related court activities over several dates. @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PROP.md b/_pages/tag-def/PROP.md index 0e1cc5ad..88b7a59d 100644 --- a/_pages/tag-def/PROP.md +++ b/_pages/tag-def/PROP.md @@ -20,10 +20,9 @@ standard tag: PROP specification: - Property - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - property - - Pertaining to possessions such as real estate or other property of - interest. + - Pertaining to possessions such as real estate or other property of interest. label: 'Property' @@ -56,6 +55,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/PUBL.md b/_pages/tag-def/PUBL.md index 69e2062f..a4730b10 100644 --- a/_pages/tag-def/PUBL.md +++ b/_pages/tag-def/PUBL.md @@ -22,13 +22,13 @@ specification: - Publication - | When and where the record was created. For published works, this includes - information such as the city of publication, name of the publisher, and - year of publication. + information such as the city of publication, name of the publisher, and year of + publication. - For an unpublished work, it includes the date the record was created and - the place where it was created, such as the county and state of residence - of a person making a declaration for a pension or the city and state of - residence of the writer of a letter. + For an unpublished work, it includes the date the record was created and the + place where it was created, such as the county and state of residence of a + person making a declaration for a pension or the city and state of residence of + the writer of a letter. label: 'Publication' @@ -38,6 +38,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/record-SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/QUAY.md b/_pages/tag-def/QUAY.md index 4af31d3f..df8dffdd 100644 --- a/_pages/tag-def/QUAY.md +++ b/_pages/tag-def/QUAY.md @@ -20,12 +20,11 @@ standard tag: QUAY specification: - Quality of data - - An enumerated value from set https://gedcom.io/terms/v7/enumset-QUAY - indicating the credibility of a piece of information, based on its - supporting evidence. Some systems use this feature to rank multiple - conflicting opinions for display of most likely information first. It is - not intended to eliminate the receivers’ need to evaluate the evidence for - themselves. + - An enumerated value from set `https://gedcom.io/terms/v7/enumset-QUAY` + indicating the credibility of a piece of information, based on its supporting + evidence. Some systems use this feature to rank multiple conflicting opinions + for display of most likely information first. It is not intended to eliminate + the receivers' need to evaluate the evidence for themselves. label: 'Quality of data' @@ -37,6 +36,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/REFN.md b/_pages/tag-def/REFN.md index 60bf55d0..a46f8d81 100644 --- a/_pages/tag-def/REFN.md +++ b/_pages/tag-def/REFN.md @@ -22,13 +22,13 @@ specification: - Reference - | A user-defined number or text that the submitter uses to identify the - superstructure. For instance, it may be a record number within the - submitter’s automated or manual system, or it may be a page and position - number on a pedigree chart. + superstructure. For instance, it may be a record number within the submitter's + automated or manual system, or it may be a page and position number on a + pedigree chart. This is metadata about the structure itself, not data about its subject. - Multiple structures describing different aspects of the same subject must - not have the same REFN value. + Multiple structures describing different aspects of the same subject must not + have the same `REFN` value. label: 'Reference' @@ -45,6 +45,8 @@ superstructures: "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}" "https://gedcom.io/terms/v7/record-SOUR": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/RELI.md b/_pages/tag-def/RELI.md index ab598355..e7c0c396 100644 --- a/_pages/tag-def/RELI.md +++ b/_pages/tag-def/RELI.md @@ -20,11 +20,11 @@ standard tag: RELI specification: - Religion - - A religious denomination associated with the event or attribute described - by the superstructure. + - A religious denomination associated with the event or attribute described by + the superstructure. - religion - - A religious denomination to which a person is affiliated or for which a - record applies. + - A religious denomination to which a person is affiliated or for which a record + applies. label: 'Religion' @@ -87,6 +87,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/REPO.md b/_pages/tag-def/REPO.md index 05945d53..7e0965c0 100644 --- a/_pages/tag-def/REPO.md +++ b/_pages/tag-def/REPO.md @@ -20,13 +20,13 @@ standard tag: REPO specification: - Repository - - See SOURCE_REPOSITORY_CITATION. - - This structure is used within a source record to point to a name and - address record of the holder of the source document. Formal and informal - repository name and addresses are stored in the REPOSITORY_RECORD. More - formal repositories, such as the Family History Library, should show a call - number of the source at that repository. The call number of that source - should be recorded using a CALN substructure. + - See `SOURCE_REPOSITORY_CITATION`. + - This structure is used within a source record to point to a name and address + record of the holder of the source document. Formal and informal repository + name and addresses are stored in the `REPOSITORY_RECORD`. More formal + repositories, such as the Family History Library, should show a call number of + the source at that repository. The call number of that source should be + recorded using a `CALN` substructure. label: 'Repository' @@ -39,6 +39,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-SOUR": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/RESN.md b/_pages/tag-def/RESN.md index ed9a36c6..c8b3de4a 100644 --- a/_pages/tag-def/RESN.md +++ b/_pages/tag-def/RESN.md @@ -22,15 +22,15 @@ specification: - Restriction - | A [List] of enumerated values from set - https://gedcom.io/terms/v7/enumset-RESN signifying access to information - may be denied or otherwise restricted. + `https://gedcom.io/terms/v7/enumset-RESN` signifying access to information may + be denied or otherwise restricted. - The RESN structure is provided to assist software in filtering data that + The `RESN` structure is provided to assist software in filtering data that should not be exported or otherwise used in a particular context. It is - recommended that tools provide an interface to allow users to filter data - on export such that certain RESN structure payload entries result in the - RESN structure and its superstructure being removed from the export. Such - removal must abide by some constraints: see Removing data for more. + recommended that tools provide an interface to allow users to filter data on + export such that certain `RESN` structure payload entries result in the `RESN` + structure and its superstructure being removed from the export. Such removal + must abide by some constraints: see [Removing data] for more details. This is metadata about the structure itself, not data about its subject. @@ -97,6 +97,8 @@ superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:1}" "https://gedcom.io/terms/v7/record-INDI": "{0:1}" "https://gedcom.io/terms/v7/record-OBJE": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/RETI.md b/_pages/tag-def/RETI.md index c538f263..1af5f0d0 100644 --- a/_pages/tag-def/RETI.md +++ b/_pages/tag-def/RETI.md @@ -20,10 +20,10 @@ standard tag: RETI specification: - Retirement - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - retirement - - Exiting an occupational relationship with an employer after a qualifying - time period. + - Exiting an occupational relationship with an employer after a qualifying time + period. label: 'Retirement' @@ -57,6 +57,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ROLE.md b/_pages/tag-def/ROLE.md index 7b495bf8..fe1b7b96 100644 --- a/_pages/tag-def/ROLE.md +++ b/_pages/tag-def/ROLE.md @@ -21,28 +21,40 @@ standard tag: ROLE specification: - Role - | - An enumerated value from set https://gedcom.io/terms/v7/enumset-ROLE - indicating what role this person played in an event or person’s life. + An enumerated value from set `https://gedcom.io/terms/v7/enumset-ROLE` + indicating what role this person played in an event or person's life. - The following indicates a child’s birth record as the source of the - mother’s name: +
- 0 @I1@ INDI - 1 NAME Mary // - 2 SOUR @S1@ - 3 EVEN BIRT - 4 ROLE MOTH + The following indicates a child's birth record as the source of the mother's + name: - The following indicates that a person’s best friend was a witness at their + ```gedcom + 0 @I1@ INDI + 1 NAME Mary // + 2 SOUR @S1@ + 3 EVEN BIRT + 4 ROLE MOTH + ``` + +
+ +
+ + The following indicates that a person's best friend was a witness at their baptism: - 0 @I2@ INDI - 1 ASSO @I3@ - 2 ROLE FRIEND - 3 PHRASE best friend - 1 BAPM - 2 ASSO @I3@ - 3 ROLE WITN + ```gedcom + 0 @I2@ INDI + 1 ASSO @I3@ + 2 ROLE FRIEND + 3 PHRASE best friend + 1 BAPM + 2 ASSO @I3@ + 3 ROLE WITN + ``` + +
label: 'Role' @@ -56,6 +68,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/ASSO": "{1:1}" "https://gedcom.io/terms/v7/SOUR-EVEN": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SCHMA.md b/_pages/tag-def/SCHMA.md index ff63bcd5..5e2a9657 100644 --- a/_pages/tag-def/SCHMA.md +++ b/_pages/tag-def/SCHMA.md @@ -20,8 +20,8 @@ standard tag: SCHMA specification: - Extension schema - - A container for storing meta-information about the extension tags used in - this document. See Extensions for more. + - A container for storing meta-information about the extension tags used in this + document. See [Extensions] for more details. label: 'Extension schema' @@ -32,6 +32,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/HEAD": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SDATE.md b/_pages/tag-def/SDATE.md index c0f7504e..fcab2c2e 100644 --- a/_pages/tag-def/SDATE.md +++ b/_pages/tag-def/SDATE.md @@ -24,19 +24,19 @@ specification: A date to be used as a sorting hint. It is intended for use when the actual date is unknown, but the display order may be dependent on date. - If both a DATE and SDATE are present in the same structure, the SDATE - should be used for sorting and positioning while the DATE should be - displayed as the date of the structure. + If both a `DATE` and `SDATE` are present in the same structure, the `SDATE` + should be used for sorting and positioning while the `DATE` should be displayed + as the date of the structure. - SDATE and its substructures (including PHRASE, TIME, and any extension + `SDATE` and its substructures (including `PHRASE`, `TIME`, and any extension structures) should be used only as sorting hints, not to convey historical meaning. It is recommended to use a payload that matches - [[day D] month D] year [D epoch]. Other DateValue forms may have unreliable - effects on sorting. Including a month and day is encouraged to help - different applications sort dates the same way, as the relative ordering of - dates with different levels of precision is not well defined. + `[[day D] month D] year [D epoch]`. Other DateValue forms may have unreliable + effects on sorting. Including a month and day is encouraged to help different + applications sort dates the same way, as the relative ordering of dates with + different levels of precision is not well defined. label: 'Sort date' @@ -98,6 +98,8 @@ superstructures: "https://gedcom.io/terms/v7/RETI": "{0:1}" "https://gedcom.io/terms/v7/SSN": "{0:1}" "https://gedcom.io/terms/v7/WILL": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SEX.md b/_pages/tag-def/SEX.md index 2ab4f7f3..a3c0197c 100644 --- a/_pages/tag-def/SEX.md +++ b/_pages/tag-def/SEX.md @@ -20,7 +20,7 @@ standard tag: SEX specification: - Sex - - An enumerated value from set https://gedcom.io/terms/v7/enumset-SEX that + - An enumerated value from set `https://gedcom.io/terms/v7/enumset-SEX` that indicates the sex of the individual at birth. label: 'Sex' @@ -33,6 +33,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SLGC.md b/_pages/tag-def/SLGC.md index 45bc92cb..aa0ce16d 100644 --- a/_pages/tag-def/SLGC.md +++ b/_pages/tag-def/SLGC.md @@ -20,11 +20,10 @@ standard tag: SLGC specification: - Sealing, child - - A Latter-Day Saint Ordinance. See also LDS_INDIVIDUAL_ORDINANCE. + - A [Latter-Day Saint Ordinance]. See also `LDS_INDIVIDUAL_ORDINANCE`. - sealing child - - A religious event pertaining to the sealing of a child to his or her - parents in a temple ceremony of The Church of Jesus Christ of Latter-day - Saints. + - A religious event pertaining to the sealing of a child to his or her parents in + a temple ceremony of The Church of Jesus Christ of Latter-day Saints. label: 'Sealing, child' @@ -42,6 +41,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SLGS.md b/_pages/tag-def/SLGS.md index 290f477b..129a40f9 100644 --- a/_pages/tag-def/SLGS.md +++ b/_pages/tag-def/SLGS.md @@ -20,13 +20,14 @@ standard tag: SLGS specification: - Sealing, spouse - - A Latter-Day Saint Ordinance. See also LDS_SPOUSE_SEALING. + - A [Latter-Day Saint Ordinance]. See also `LDS_SPOUSE_SEALING`. - Ordinances performed by members of The Church of Jesus Christ of Latter-day - Saints; see [Latter-day Saint Ordinances] for more. + Saints; see [Latter-day Saint Ordinances] for descriptions of each ordinance + type. - sealing spouse - - A religious event pertaining to the sealing of a husband and wife in a - temple ceremony of The Church of Jesus Christ of Latter-day Saints. (See - also MARR) + - A religious event pertaining to the sealing of a husband and wife in a temple + ceremony of The Church of Jesus Christ of Latter-day Saints. (See also + [`MARR`]) label: 'Sealing, spouse' @@ -43,6 +44,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/record-FAM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SNOTE.md b/_pages/tag-def/SNOTE.md index e1e4058e..af70f317 100644 --- a/_pages/tag-def/SNOTE.md +++ b/_pages/tag-def/SNOTE.md @@ -20,8 +20,8 @@ standard tag: SNOTE specification: - Shared note - - A pointer to a note that is shared by multiple structures. See - NOTE_STRUCTURE for more. + - A pointer to a note that is shared by multiple structures. See `NOTE_STRUCTURE` + for more details. label: 'Shared note' @@ -104,6 +104,8 @@ superstructures: "https://gedcom.io/terms/v7/record-REPO": "{0:M}" "https://gedcom.io/terms/v7/record-SOUR": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SOUR-DATA.md b/_pages/tag-def/SOUR-DATA.md index 750ee0f3..f06c0e01 100644 --- a/_pages/tag-def/SOUR-DATA.md +++ b/_pages/tag-def/SOUR-DATA.md @@ -20,7 +20,7 @@ standard tag: DATA specification: - Data - - See https://gedcom.io/terms/v7/DATA. + - See `https://gedcom.io/terms/v7/DATA`. label: 'Data' @@ -32,6 +32,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SOUR-EVEN.md b/_pages/tag-def/SOUR-EVEN.md index d442ef54..02b6bd52 100644 --- a/_pages/tag-def/SOUR-EVEN.md +++ b/_pages/tag-def/SOUR-EVEN.md @@ -20,12 +20,11 @@ standard tag: EVEN specification: - Event - - An enumerated value from set https://gedcom.io/terms/v7/enumset-EVENATTR - indicating the type of event or attribute which was responsible for the - source entry being recorded. For example, if the entry was created to - record a birth of a child, then the type would be BIRT regardless of the - assertions made from that record, such as the mother’s name or mother’s - birth date. + - An enumerated value from set `https://gedcom.io/terms/v7/enumset-EVENATTR` + indicating the type of event or attribute which was responsible for the source + entry being recorded. For example, if the entry was created to record a birth + of a child, then the type would be `BIRT` regardless of the assertions made + from that record, such as the mother's name or mother's birth date. label: 'Event' @@ -39,6 +38,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SOUR.md b/_pages/tag-def/SOUR.md index 10aabd1e..eb3d1f8f 100644 --- a/_pages/tag-def/SOUR.md +++ b/_pages/tag-def/SOUR.md @@ -20,31 +20,29 @@ standard tag: SOUR specification: - Source - - A description of the relevant part of a source to support the - superstructure’s data. See SOURCE_CITATION for more. + - A description of the relevant part of a source to support the superstructure's + data. See `SOURCE_CITATION` for more details. - | A citation indicating that the pointed-to source record supports the claims - made in the superstructure. Substructures provide additional information - about how that source applies to the subject of the citation’s - superstructure: + made in the superstructure. Substructures provide additional information about + how that source applies to the subject of the citation's superstructure: - - PAGE: where in the source the relevant material can be found. - - DATA: the relevant data from the source. - - EVEN: what event the relevant material was recording. - - QUAY: an estimation of the reliability of the source in regard to these - claims. - - MULTIMEDIA_LINK: digital copies of the cited part of the source + - `PAGE`: where in the source the relevant material can be found. + - `DATA`: the relevant data from the source. + - `EVEN`: what event the relevant material was recording. + - `QUAY`: an estimation of the reliability of the source in regard to these + claims. + - `MULTIMEDIA_LINK`: digital copies of the cited part of the source - It is recommended that every SOURCE_CITATION point to a SOURCE_RECORD. - However, a voidPtr can be used with the citation text in a PAGE - substructure. The PAGE is defined to express a “specific location within - the information referenced;” with a voidPtr there is no information - referenced, so the PAGE may describe the entire source. + It is recommended that every `SOURCE_CITATION` point to a `SOURCE_RECORD`. + However, a `voidPtr` can be used with the citation text in a `PAGE` + substructure. The `PAGE` is defined to express a "specific location within the + information referenced;" with a `voidPtr` there is no information referenced, + so the `PAGE` may describe the entire source. - A SOURCE_CITATION can contain a NOTE_STRUCTURE, which in turn can contain a - SOURCE_CITATION, allowing potentially unbounded nesting of structures. - Because each dataset is finite, this nesting is also guaranteed to be - finite. + A `SOURCE_CITATION` can contain a `NOTE_STRUCTURE`, which in turn can contain a + `SOURCE_CITATION`, allowing potentially unbounded nesting of structures. + Because each dataset is finite, this nesting is also guaranteed to be finite. label: 'Source' @@ -125,6 +123,8 @@ superstructures: "https://gedcom.io/terms/v7/record-INDI": "{0:M}" "https://gedcom.io/terms/v7/record-OBJE": "{0:M}" "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SPFX.md b/_pages/tag-def/SPFX.md index 7687f120..416fe5e4 100644 --- a/_pages/tag-def/SPFX.md +++ b/_pages/tag-def/SPFX.md @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}" "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SSN.md b/_pages/tag-def/SSN.md index 627e90ca..cb4bd2e5 100644 --- a/_pages/tag-def/SSN.md +++ b/_pages/tag-def/SSN.md @@ -20,10 +20,10 @@ standard tag: SSN specification: - Social security number - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. - social security number - - A number assigned by the United States Social Security Administration, used - for tax identification purposes. It is a type of IDNO. + - A number assigned by the United States Social Security Administration, used for + tax identification purposes. It is a type of `IDNO`. label: 'Social security number' @@ -56,6 +56,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/STAE.md b/_pages/tag-def/STAE.md index 348d3e02..c0648a09 100644 --- a/_pages/tag-def/STAE.md +++ b/_pages/tag-def/STAE.md @@ -20,8 +20,8 @@ standard tag: STAE specification: - State - - A geographical division of a larger jurisdictional area, such as a state - within the United States of America. See ADDRESS_STRUCTURE for more. + - A geographical division of a larger jurisdictional area, such as a state within + the United States of America. See `ADDRESS_STRUCTURE` for more details. label: 'State' @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/ADDR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SUBM-LANG.md b/_pages/tag-def/SUBM-LANG.md index a5f1b005..fdd2fa15 100644 --- a/_pages/tag-def/SUBM-LANG.md +++ b/_pages/tag-def/SUBM-LANG.md @@ -23,7 +23,8 @@ specification: - | A language the subject of that record understands. - The payload of the LANG structure is a language tag, as defined by BCP 47. + The payload of the `LANG` structure is a language tag, as defined by [BCP + 47]. label: 'Language' @@ -33,6 +34,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SUBM.md b/_pages/tag-def/SUBM.md index c06608df..a76da75b 100644 --- a/_pages/tag-def/SUBM.md +++ b/_pages/tag-def/SUBM.md @@ -20,8 +20,8 @@ standard tag: SUBM specification: - Submitter - - A contributor of information in the substructure. This is metadata about - the structure itself, not data about its subject. + - A contributor of information in the substructure. This is metadata about the + structure itself, not data about its subject. label: 'Submitter' @@ -33,6 +33,8 @@ superstructures: "https://gedcom.io/terms/v7/HEAD": "{0:1}" "https://gedcom.io/terms/v7/record-FAM": "{0:M}" "https://gedcom.io/terms/v7/record-INDI": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/SURN.md b/_pages/tag-def/SURN.md index d660c66e..371891ce 100644 --- a/_pages/tag-def/SURN.md +++ b/_pages/tag-def/SURN.md @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}" "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/TAG.md b/_pages/tag-def/TAG.md index 48a2f47d..580ef323 100644 --- a/_pages/tag-def/TAG.md +++ b/_pages/tag-def/TAG.md @@ -20,8 +20,8 @@ standard tag: TAG specification: - Extension tag - - Information relating to a single extension tag as used in this document. - See Extensions for more. + - Information relating to a single extension tag as used in this document. See + [Extensions] for more details. label: 'Extension tag' @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/SCHMA": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/TEMP.md b/_pages/tag-def/TEMP.md index 416fa184..63d05c45 100644 --- a/_pages/tag-def/TEMP.md +++ b/_pages/tag-def/TEMP.md @@ -21,9 +21,9 @@ standard tag: TEMP specification: - Temple - The name of a temple of The Church of Jesus Christ of Latter-day Saints. - Previous versions recommended using a set of abbreviations for temple - names, but the list of abbreviations is no longer published by the Church - and using abbreviations is no longer recommended. + Previous versions recommended using a set of abbreviations for temple names, + but the list of abbreviations is no longer published by the Church and using + abbreviations is no longer recommended. label: 'Temple' @@ -38,6 +38,8 @@ superstructures: "https://gedcom.io/terms/v7/INIL": "{0:1}" "https://gedcom.io/terms/v7/SLGC": "{0:1}" "https://gedcom.io/terms/v7/SLGS": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/TEXT.md b/_pages/tag-def/TEXT.md index 2fd998ba..ab7524fb 100644 --- a/_pages/tag-def/TEXT.md +++ b/_pages/tag-def/TEXT.md @@ -20,11 +20,11 @@ standard tag: TEXT specification: - Text from Source - - A verbatim copy of any description contained within the source. This - indicates notes or text that are actually contained in the source document, - not the submitter’s opinion about the source. This should be, from the - evidence point of view, “what the original record keeper said” as opposed - to the researcher’s interpretation. + - A verbatim copy of any description contained within the source. This indicates + notes or text that are actually contained in the source document, not the + submitter's opinion about the source. This should be, from the evidence point + of view, "what the original record keeper said" as opposed to the researcher's + interpretation. label: 'Text from Source' @@ -37,6 +37,8 @@ substructures: superstructures: "https://gedcom.io/terms/v7/SOUR-DATA": "{0:M}" "https://gedcom.io/terms/v7/record-SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/TIME.md b/_pages/tag-def/TIME.md index ccf18097..18792d53 100644 --- a/_pages/tag-def/TIME.md +++ b/_pages/tag-def/TIME.md @@ -20,7 +20,7 @@ standard tag: TIME specification: - Time - - A Time value in a 24-hour clock format. + - A `Time` value in a 24-hour clock format. label: 'Time' @@ -33,6 +33,8 @@ superstructures: "https://gedcom.io/terms/v7/DATE-exact": "{0:1}" "https://gedcom.io/terms/v7/HEAD-DATE": "{0:1}" "https://gedcom.io/terms/v7/SDATE": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/TITL.md b/_pages/tag-def/TITL.md index 17112b06..77b722d5 100644 --- a/_pages/tag-def/TITL.md +++ b/_pages/tag-def/TITL.md @@ -24,25 +24,29 @@ specification: The title, formal or informal, of the superstructure. A published work, such as a book, might have a title plus the title of the - series of which the book is a part. A magazine article would have a title - plus the title of the magazine that published the article. + series of which the book is a part. A magazine article would have a title plus + the title of the magazine that published the article. For an unpublished work, including most digital files, titles should be descriptive and appropriate to the work. - - The TITL of a letter might include the date, the sender, and the - receiver. - - The TITL of a transaction between a buyer and seller might have their - names and the transaction date. - - The TITL of a family Bible containing genealogical information might - have past and present owners and a physical description of the book. - - The TITL of a personal interview would cite the informant and - interviewer. +
- Some sources may have a citation text that cannot readily be represented - using the SOURCE_RECORD substructures AUTH, PUBL, REPO, and so on. In such +

+ + - The `TITL` of a letter might include the date, the sender, and the receiver. + - The `TITL` of a transaction between a buyer and seller might have their names + and the transaction date. + - The `TITL` of a family Bible containing genealogical information might have + past and present owners and a physical description of the book. + - The `TITL` of a personal interview would cite the informant and interviewer. + +
+ + Some sources may have a citation text that cannot readily be represented using + the `SOURCE_RECORD` substructures `AUTH`, `PUBL`, `REPO`, and so on. In such cases, the entire citation text may be presented as the payload of the - SOUR.TITL. + `SOUR`.`TITL`. - title - A formal designation used by an individual in connection with positions of royalty or other social status, such as Grand Duke. @@ -60,6 +64,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/TOP.md b/_pages/tag-def/TOP.md index e3ae456b..e21c524e 100644 --- a/_pages/tag-def/TOP.md +++ b/_pages/tag-def/TOP.md @@ -20,8 +20,8 @@ standard tag: TOP specification: - Top crop width - - A number of pixels to not display from the top side of the image. See CROP - for more. + - A number of pixels to not display from the top side of the image. See `CROP` + for more details. label: 'Top crop width' @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/CROP": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/TRLR.md b/_pages/tag-def/TRLR.md index 02b0219d..c933ef7f 100644 --- a/_pages/tag-def/TRLR.md +++ b/_pages/tag-def/TRLR.md @@ -20,8 +20,8 @@ standard tag: TRLR specification: - Trailer - - A pseudo-structure marking the end of a dataset. See The Header and Trailer - for more. + - A pseudo-structure marking the end of a dataset. See [The Header and Trailer] + for more details. label: 'Trailer' @@ -30,6 +30,8 @@ payload: null substructures: {} superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/TYPE.md b/_pages/tag-def/TYPE.md index a792e59a..65515035 100644 --- a/_pages/tag-def/TYPE.md +++ b/_pages/tag-def/TYPE.md @@ -23,35 +23,41 @@ specification: - | A descriptive word or phrase used to further classify the superstructure. - When both a NOTE and free-text TYPE are permitted as substructures of the - same structure, the displaying systems should always display the TYPE value - when they display the data from the associated structure; NOTE will - typically be visible only in a detailed view. + When both a `NOTE` and free-text `TYPE` are permitted as substructures of the + same structure, the displaying systems should always display the `TYPE` value + when they display the data from the associated structure; `NOTE` will typically + be visible only in a detailed view. - TYPE must be used whenever the generic EVEN, FACT and IDNO tags are used. - It may also be used for any other event or attribute. + `TYPE` must be used whenever the generic `EVEN`, `FACT` and `IDNO` tags are + used. It may also be used for any other event or attribute. - Using the subordinate TYPE classification method provides a further + Using the subordinate `TYPE` classification method provides a further classification of the superstructure but does not change its basic meaning. - A ORDN with a TYPE could clarify what kind of ordination was performed: +
- 0 @I1@ INDI - 1 ORDN - 2 TYPE Bishop + A `ORDN` with a `TYPE` could clarify what kind of ordination was performed: + + ```gedcom + 0 @I1@ INDI + 1 ORDN + 2 TYPE Bishop + ``` This classifies the entry as an ordination as a bishop, which is still a - ordination event. The event could be further clarified with RELI, DATE, and + ordination event. The event could be further clarified with `RELI`, `DATE`, and other substructures. Other descriptor values might include, for example, - - “Stillborn” as a qualifier to BIRT (birth) - - “Civil” as a qualifier to MARR (marriage) - - “College” as a qualifier to GRAD (graduation) - - “Oral” as a qualifier to WILL + - "Stillborn" as a qualifier to `BIRT` (birth) + - "Civil" as a qualifier to `MARR` (marriage) + - "College" as a qualifier to `GRAD` (graduation) + - "Oral" as a qualifier to `WILL` + + See also `FACT` and `EVEN` for additional examples. - See also FACT and EVEN for additional examples. +
label: 'Type' @@ -112,6 +118,8 @@ superstructures: "https://gedcom.io/terms/v7/RETI": "{0:1}" "https://gedcom.io/terms/v7/SSN": "{0:1}" "https://gedcom.io/terms/v7/WILL": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/UID.md b/_pages/tag-def/UID.md index b0480012..d5ebd717 100644 --- a/_pages/tag-def/UID.md +++ b/_pages/tag-def/UID.md @@ -22,32 +22,36 @@ specification: - Unique Identifier - | A globally-unique identifier of the superstructure, to be preserved across - edits. If a globally-unique identifier for the record already exists, it - should be used without modification, not even whitespace or letter case - normalization. New globally unique identifiers should be created and - formatted as described in RFC 4122. + edits. If a globally-unique identifier for the record already exists, it should + be used without modification, not even whitespace or letter case normalization. + New globally unique identifiers should be created and formatted as described in + [RFC 4122]. This is metadata about the structure itself, not data about its subject. - Multiple structures describing different aspects of the same subject would - have different UID values. + Multiple structures describing different aspects of the same subject would have + different `UID` values. - Because the UID identifies a structure, it can facilitate inter-tool + Because the `UID` identifies a structure, it can facilitate inter-tool collaboration by distinguishing between a structure being edited and a new - structure being created. If an application allows structures to be edited - in a way that completely changes their meaning (e.g., changing all the - contents of an INDI record to have it describe a completely different - person) then any UIDs should also be changed. + structure being created. If an application allows structures to be edited in a + way that completely changes their meaning (e.g., changing all the contents of + an `INDI` record to have it describe a completely different person) then any + `UID`s should also be changed. - Some systems used a 16-byte UUID with a custom 2-byte checksum for a total - of 18 bytes: +
- - checksum byte 1 = (sum of (byte_(i)) for i 1 through 16) mod 256 - - checksum byte 2 = (sum of ((16 − i) × (byte_(i))) for i 1 through 16) - mod 256 + Some systems used a 16-byte UUID with a custom 2-byte checksum for a total of + 18 bytes: + + - checksum byte 1 = (sum of (byte~*i*~) for *i* 1 through 16) mod 256 + - checksum byte 2 = (sum of ((16 − *i*) × (byte~*i*~)) for *i* 1 through 16) + mod 256 Use of checksums for UIDs is discouraged except in cases where error-prone input is expected and an appropriate action to take in case of an error is known. + +
label: 'Unique Identifier' @@ -114,6 +118,8 @@ superstructures: "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}" "https://gedcom.io/terms/v7/record-SOUR": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/VERS.md b/_pages/tag-def/VERS.md index b8a10306..d653bba3 100644 --- a/_pages/tag-def/VERS.md +++ b/_pages/tag-def/VERS.md @@ -31,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/HEAD-SOUR": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/WIDTH.md b/_pages/tag-def/WIDTH.md index 7d209074..e838df07 100644 --- a/_pages/tag-def/WIDTH.md +++ b/_pages/tag-def/WIDTH.md @@ -20,7 +20,8 @@ standard tag: WIDTH specification: - Width in pixels - - How many pixels to display horizontally for the image. See CROP for more. + - How many pixels to display horizontally for the image. See `CROP` for more + details. label: 'Width in pixels' @@ -30,6 +31,8 @@ substructures: {} superstructures: "https://gedcom.io/terms/v7/CROP": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/WIFE.md b/_pages/tag-def/WIFE.md index 7740d8f4..827adaa0 100644 --- a/_pages/tag-def/WIFE.md +++ b/_pages/tag-def/WIFE.md @@ -21,7 +21,7 @@ standard tag: WIFE specification: - Wife - A container for information relevant to the subject of the superstructure - specific to the individual described by the associated FAM’s WIFE + specific to the individual described by the associated `FAM`'s `WIFE` substructure. label: 'Wife' @@ -46,6 +46,8 @@ superstructures: "https://gedcom.io/terms/v7/MARL": "{0:1}" "https://gedcom.io/terms/v7/MARR": "{0:1}" "https://gedcom.io/terms/v7/MARS": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/WILL.md b/_pages/tag-def/WILL.md index d5b66058..115d903a 100644 --- a/_pages/tag-def/WILL.md +++ b/_pages/tag-def/WILL.md @@ -20,11 +20,11 @@ standard tag: WILL specification: - Will - - An Individual Event. See also INDIVIDUAL_EVENT_STRUCTURE. + - An [Individual Event]. See also `INDIVIDUAL_EVENT_STRUCTURE`. - will - - A legal document treated as an event, by which a person disposes of his or - her estate. It takes effect after death. The event date is the date the - will was signed while the person was alive. (See also PROB) + - A legal document treated as an event, by which a person disposes of his or her + estate. It takes effect after death. The event date is the date the will was + signed while the person was alive. (See also `PROB`) label: 'Will' @@ -58,6 +58,8 @@ superstructures: value of: - "https://gedcom.io/terms/v7/enumset-EVEN" - "https://gedcom.io/terms/v7/enumset-EVENATTR" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/WWW.md b/_pages/tag-def/WWW.md index c0a87734..106397c5 100644 --- a/_pages/tag-def/WWW.md +++ b/_pages/tag-def/WWW.md @@ -21,8 +21,18 @@ standard tag: WWW specification: - Web address - | - A URL or other locator for a World Wide Web page, as defined by any - relevant standard such as whatwg/url, RFC 3986, RFC 3987, and so forth. + A URL or other locator for a World Wide Web page of the subject of the + superstructure, as defined by any relevant standard such as [whatwg/url], + [RFC 3986], [RFC 3987], and so forth. + + Like other substructures, the `WWW` structure provides details about the + subject of its superstructure. For example, a `MARR`.`WWW` is a world wide web + page of the marriage event, not the personal website of the couple or an entry + in an online database serving as a source documenting the marriage. However, + the meaning of `WWW` was only implicit when it was introduced in version 5.5.1 + and many files were created that use `WWW` to store a more tangentially-related + web address, so applications are recommended to interpret the `WWW` structure's + meaning cautiously. If an invalid or no longer existing web address is present upon import, it should be preserved as-is on export. @@ -88,6 +98,8 @@ superstructures: "https://gedcom.io/terms/v7/WILL": "{0:M}" "https://gedcom.io/terms/v7/record-REPO": "{0:M}" "https://gedcom.io/terms/v7/record-SUBM": "{0:M}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/cal-FRENCH_R.md b/_pages/tag-def/cal-FRENCH_R.md index 25eb3d38..65a170b0 100644 --- a/_pages/tag-def/cal-FRENCH_R.md +++ b/_pages/tag-def/cal-FRENCH_R.md @@ -20,33 +20,32 @@ standard tag: FRENCH_R specification: - | - The French Republican calendar or French Revolutionary calendar are the - names given to the new calendar adopted in 1794 by the French National - Convention. This calendar was adopted on Gregorian day 22 September 1792, - which was 1 Vendémiaire 1 in this calendar. It was abandoned 18 years - later. + The French Republican calendar or French Revolutionary calendar are the names + given to the new calendar adopted in 1794 by the French National Convention. + This calendar was adopted on Gregorian day 22 September 1792, which was 1 + Vendémiaire 1 in this calendar. It was abandoned 18 years later. Permitted months are - Code Name - ------ ---------------------- - VEND Vendémiaire - BRUM Brumaire - FRIM Frimaire - NIVO Nivôse - PLUV Pluviôse - VENT Ventôse - GERM Germinal - FLOR Floréal - PRAI Prairial - MESS Messidor - THER Thermidor - FRUC Fructidor - COMP Jour Complémentaires + | Code | Name | + | :----- | :------------------- | + | `VEND` | Vendémiaire | + | `BRUM` | Brumaire | + | `FRIM` | Frimaire | + | `NIVO` | Nivôse | + | `PLUV` | Pluviôse | + | `VENT` | Ventôse | + | `GERM` | Germinal | + | `FLOR` | Floréal | + | `PRAI` | Prairial | + | `MESS` | Messidor | + | `THER` | Thermidor | + | `FRUC` | Fructidor | + | `COMP` | Jour Complémentaires | No epoch marker is permitted in this calendar. - The URI for this calendar is https://gedcom.io/terms/v7/cal-FRENCH_R + The URI for this calendar is `https://gedcom.io/terms/v7/cal-FRENCH_R` label: 'French Republican' @@ -66,6 +65,8 @@ months: - "https://gedcom.io/terms/v7/month-COMP" epochs: [] + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/cal-GREGORIAN.md b/_pages/tag-def/cal-GREGORIAN.md index 24ddc1c7..1e94f32a 100644 --- a/_pages/tag-def/cal-GREGORIAN.md +++ b/_pages/tag-def/cal-GREGORIAN.md @@ -21,31 +21,31 @@ standard tag: GREGORIAN specification: - | The Gregorian calendar is the now-ubiquitous calendar introduced by Pope - Gregory XIII in 1582 to correct the Julian calendar which was slowly - drifting relative to the seasons. + Gregory XIII in 1582 to correct the Julian calendar which was slowly drifting + relative to the seasons. Permitted months are - Code Name - ------ ----------- - JAN January - FEB February - MAR March - APR April - MAY May - JUN June - JUL July - AUG August - SEP September - OCT October - NOV November - DEC December + | Code | Name | + | :---- | :-------- | + | `JAN` | January | + | `FEB` | February | + | `MAR` | March | + | `APR` | April | + | `MAY` | May | + | `JUN` | June | + | `JUL` | July | + | `AUG` | August | + | `SEP` | September | + | `OCT` | October | + | `NOV` | November | + | `DEC` | December | - The epoch marker BCE is permitted in this calendar; year y BCE indicates a - year y years before year 1. Thus, there is no year 0; year 1 BCE was - followed by year 1. + The epoch marker `BCE` is permitted in this calendar; year *y* BCE indicates a + year *y* years before year 1. Thus, there is no year 0; year 1 BCE was followed + by year 1. - The URI for this calendar is https://gedcom.io/terms/v7/cal-GREGORIAN + The URI for this calendar is `https://gedcom.io/terms/v7/cal-GREGORIAN` label: 'Gregorian' @@ -65,6 +65,8 @@ months: epochs: - BCE + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/cal-HEBREW.md b/_pages/tag-def/cal-HEBREW.md index a09726f1..c9fc9ed0 100644 --- a/_pages/tag-def/cal-HEBREW.md +++ b/_pages/tag-def/cal-HEBREW.md @@ -20,55 +20,39 @@ standard tag: HEBREW specification: - | - The Hebrew calendar is the name given to the calendar used by Jewish - peoples around the world which developed into its current form in the early - ninth century. It traditionally marks new days at sunset, not midnight. Its - first day (1 Tishrei 1) primarily overlapped with Gregorian 7 September - 3761 BCE and Julian 7 October 3761 BCE (starting at sunset on the 6th day - of those months). - - -------------------------------------------------------------------------- - Code Name - ------ ------------------------------------------------------------------- - TSH Tishrei (תִּשְׁרֵי) - - CSH Marcheshvan (מַרְחֶשְׁוָן) or Cheshvan (חֶשְׁוָן) - - KSL Kislev (כִּסְלֵו) - - TVT Tevet (טֵבֵת) - - SHV Shevat (שְׁבָט) - - ADR Adar I, Adar Rishon, First Adar, or Adar Aleph (אדר א׳) - - ADS Adar (אֲדָר); or Adar II, Adar Sheni, Second Adar, or - Adar Bet (אדר ב׳) - - NSN Nisan (נִיסָן) - - IYR Iyar (אִייָר) - - SVN Sivan (סִיוָן) - - TMZ Tammuz (תַּמּוּז) - - AAV Av (אָב) - - ELL Elul (אֱלוּל) - -------------------------------------------------------------------------- - - To keep the lunar-based months synchronized with the solar-based years, - some years have Adar I and others do not, instead proceeding from Shevat - directly to Adar II. However, in common (non-leap) years, it is common to - simply write “Adar” not “Adar II”, which users not aware of the distinction - might incorrectly encode as ADR instead of ADS. It is recommended that - systems knowing which years had Adar I and which did not replace ADR in - common years with ADS. + The Hebrew calendar is the name given to the calendar used by Jewish peoples + around the world which developed into its current form in the early ninth + century. It traditionally marks new days at sunset, not midnight. Its first day + (1 Tishrei 1) primarily overlapped with Gregorian 7 September 3761 BCE and + Julian 7 October 3761 BCE (starting at sunset on the 6th day of those months). + + | Code | Name | + | :---- | :---------------------------------------------------------------------- | + | `TSH` | Tishrei (תִּשְׁרֵי) | + | `CSH` | Marcheshvan (מַרְחֶשְׁוָן) or Cheshvan (חֶשְׁוָן) | + | `KSL` | Kislev (כִּסְלֵו) | + | `TVT` | Tevet (טֵבֵת) | + | `SHV` | Shevat (שְׁבָט) | + | `ADR` | Adar I, Adar Rishon, First Adar, or Adar Aleph (אדר א׳) | + | `ADS` | Adar (אֲדָר); or Adar II, Adar Sheni, Second Adar, or Adar Bet (אדר ב׳) | + | `NSN` | Nisan (נִיסָן) | + | `IYR` | Iyar (אִייָר) | + | `SVN` | Sivan (סִיוָן) | + | `TMZ` | Tammuz (תַּמּוּז) | + | `AAV` | Av (אָב) | + | `ELL` | Elul (אֱלוּל) | + + To keep the lunar-based months synchronized with the solar-based years, some + years have Adar I and others do not, instead proceeding from Shevat directly to + Adar II. However, in common (non-leap) years, it is common to simply write + "Adar" not "Adar II", which users not aware of the distinction might + incorrectly encode as `ADR` instead of `ADS`. It is recommended that systems + knowing which years had Adar I and which did not replace `ADR` in common years + with `ADS`. No epoch marker is permitted in this calendar. - The URI for this calendar is https://gedcom.io/terms/v7/cal-HEBREW + The URI for this calendar is `https://gedcom.io/terms/v7/cal-HEBREW` label: 'Hebrew' @@ -88,6 +72,8 @@ months: - "https://gedcom.io/terms/v7/month-ELL" epochs: [] + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/cal-JULIAN.md b/_pages/tag-def/cal-JULIAN.md index e3981792..64a1b74d 100644 --- a/_pages/tag-def/cal-JULIAN.md +++ b/_pages/tag-def/cal-JULIAN.md @@ -20,21 +20,20 @@ standard tag: JULIAN specification: - | - The Julian calendar was introduced by Julius Caesar in 45 BC and - subsequently amended by Augustus in about 8 BC to correct an error in the - application of its leap year rule during its first 3 decades. Years had - been counted from various starting epochs during the Julian calendar’s use; - the version specified by this specification uses the same starting epoch as - the Gregorian calendar. + The Julian calendar was introduced by Julius Caesar in 45 BC and subsequently + amended by Augustus in about 8 BC to correct an error in the application of its + leap year rule during its first 3 decades. Years had been counted from various + starting epochs during the Julian calendar's use; the version specified by this + specification uses the same starting epoch as the Gregorian calendar. - This calendar uses the same months as the Gregorian calendar, differing - only in which years February has 29 days. + This calendar uses the same months as the Gregorian calendar, differing only in + which years February has 29 days. - The epoch marker BCE is permitted in this calendar; year y BCE indicates a - year y years before year 1. Thus, there is no year 0; year 1 BCE was - followed by year 1. + The epoch marker `BCE` is permitted in this calendar; year *y* BCE indicates a + year *y* years before year 1. Thus, there is no year 0; year 1 BCE was followed + by year 1. - The URI for this calendar is https://gedcom.io/terms/v7/cal-JULIAN + The URI for this calendar is `https://gedcom.io/terms/v7/cal-JULIAN` label: 'Julian' @@ -54,6 +53,8 @@ months: epochs: - BCE + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-0.md b/_pages/tag-def/enum-0.md index 64c84d5e..5e39b2c6 100644 --- a/_pages/tag-def/enum-0.md +++ b/_pages/tag-def/enum-0.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-QUAY" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-1.md b/_pages/tag-def/enum-1.md index d56e8ea2..fbb40a75 100644 --- a/_pages/tag-def/enum-1.md +++ b/_pages/tag-def/enum-1.md @@ -19,11 +19,13 @@ uri: https://gedcom.io/terms/v7/enum-1 standard tag: '1' specification: - - Questionable reliability of evidence (interviews, census, oral genealogies, - or potential for bias, such as an autobiography) + - Questionable reliability of evidence (interviews, census, oral genealogies, or + potential for bias, such as an autobiography) value of: - "https://gedcom.io/terms/v7/enumset-QUAY" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-2.md b/_pages/tag-def/enum-2.md index a61cfa91..80d8dcf8 100644 --- a/_pages/tag-def/enum-2.md +++ b/_pages/tag-def/enum-2.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-QUAY" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-3.md b/_pages/tag-def/enum-3.md index 27b2dbe7..f2c4a985 100644 --- a/_pages/tag-def/enum-3.md +++ b/_pages/tag-def/enum-3.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-QUAY" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-ADOP-HUSB.md b/_pages/tag-def/enum-ADOP-HUSB.md index 6f06c177..ac49d8af 100644 --- a/_pages/tag-def/enum-ADOP-HUSB.md +++ b/_pages/tag-def/enum-ADOP-HUSB.md @@ -19,10 +19,12 @@ uri: https://gedcom.io/terms/v7/enum-ADOP-HUSB standard tag: HUSB specification: - - Adopted by the HUSB of the FAM pointed to by FAMC. + - Adopted by the `HUSB` of the `FAM` pointed to by `FAMC`. value of: - "https://gedcom.io/terms/v7/enumset-ADOP" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-ADOP-WIFE.md b/_pages/tag-def/enum-ADOP-WIFE.md index 16927cd2..ba0b51b3 100644 --- a/_pages/tag-def/enum-ADOP-WIFE.md +++ b/_pages/tag-def/enum-ADOP-WIFE.md @@ -19,10 +19,12 @@ uri: https://gedcom.io/terms/v7/enum-ADOP-WIFE standard tag: WIFE specification: - - Adopted by the WIFE of the FAM pointed to by FAMC. + - Adopted by the `WIFE` of the `FAM` pointed to by `FAMC`. value of: - "https://gedcom.io/terms/v7/enumset-ADOP" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-ADOPTED.md b/_pages/tag-def/enum-ADOPTED.md index 0480ea18..6c0f1dab 100644 --- a/_pages/tag-def/enum-ADOPTED.md +++ b/_pages/tag-def/enum-ADOPTED.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-PEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-AKA.md b/_pages/tag-def/enum-AKA.md index d5d820dd..f3ec594e 100644 --- a/_pages/tag-def/enum-AKA.md +++ b/_pages/tag-def/enum-AKA.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-NAME-TYPE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-AUDIO.md b/_pages/tag-def/enum-AUDIO.md index f3554d9a..9d33859f 100644 --- a/_pages/tag-def/enum-AUDIO.md +++ b/_pages/tag-def/enum-AUDIO.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-BIC.md b/_pages/tag-def/enum-BIC.md index ae9c438c..63b43e04 100644 --- a/_pages/tag-def/enum-BIC.md +++ b/_pages/tag-def/enum-BIC.md @@ -19,12 +19,14 @@ uri: https://gedcom.io/terms/v7/enum-BIC standard tag: BIC specification: - - "Applies to: SLGC" + - "Applies to: `SLGC`" - Born in the covenant, so child to parent sealing ordinance is not required. - "Status: Current" value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-BIRTH.md b/_pages/tag-def/enum-BIRTH.md index 3349a017..fc5d897e 100644 --- a/_pages/tag-def/enum-BIRTH.md +++ b/_pages/tag-def/enum-BIRTH.md @@ -24,6 +24,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-NAME-TYPE" - "https://gedcom.io/terms/v7/enumset-PEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-BOOK.md b/_pages/tag-def/enum-BOOK.md index 5ab905ac..31f32c20 100644 --- a/_pages/tag-def/enum-BOOK.md +++ b/_pages/tag-def/enum-BOOK.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-BOTH.md b/_pages/tag-def/enum-BOTH.md index cfa39fa0..ca9da80e 100644 --- a/_pages/tag-def/enum-BOTH.md +++ b/_pages/tag-def/enum-BOTH.md @@ -19,10 +19,12 @@ uri: https://gedcom.io/terms/v7/enum-BOTH standard tag: BOTH specification: - - Adopted by both HUSB and WIFE of the FAM pointed to by FAMC + - Adopted by both `HUSB` and `WIFE` of the `FAM` pointed to by `FAMC` value of: - "https://gedcom.io/terms/v7/enumset-ADOP" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-CANCELED.md b/_pages/tag-def/enum-CANCELED.md index 6f044afc..bec0ce2b 100644 --- a/_pages/tag-def/enum-CANCELED.md +++ b/_pages/tag-def/enum-CANCELED.md @@ -19,12 +19,14 @@ uri: https://gedcom.io/terms/v7/enum-CANCELED standard tag: CANCELED specification: - - "Applies to: SLGS" + - "Applies to: `SLGS`" - Canceled and considered invalid. - "Status: Current" value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-CARD.md b/_pages/tag-def/enum-CARD.md index d804a05f..24050199 100644 --- a/_pages/tag-def/enum-CARD.md +++ b/_pages/tag-def/enum-CARD.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-CHALLENGED.md b/_pages/tag-def/enum-CHALLENGED.md index 8a91143a..802d63f6 100644 --- a/_pages/tag-def/enum-CHALLENGED.md +++ b/_pages/tag-def/enum-CHALLENGED.md @@ -19,11 +19,13 @@ uri: https://gedcom.io/terms/v7/enum-CHALLENGED standard tag: CHALLENGED specification: - - Linking this child to this family is suspect, but the linkage has been - neither proven nor disproven. + - Linking this child to this family is suspect, but the linkage has been neither + proven nor disproven. value of: - "https://gedcom.io/terms/v7/enumset-FAMC-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-CHIL.md b/_pages/tag-def/enum-CHIL.md index 9b29fa87..d557218d 100644 --- a/_pages/tag-def/enum-CHIL.md +++ b/_pages/tag-def/enum-CHIL.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-CHILD.md b/_pages/tag-def/enum-CHILD.md index 1a799dbc..b086dd9d 100644 --- a/_pages/tag-def/enum-CHILD.md +++ b/_pages/tag-def/enum-CHILD.md @@ -19,13 +19,15 @@ uri: https://gedcom.io/terms/v7/enum-CHILD standard tag: CHILD specification: - - "Applies to: All but SLGC" - - Died before 8 years old, so ordinances other than child to parent sealing - are not required. + - "Applies to: All but `SLGC`" + - Died before 8 years old, so ordinances other than child to parent sealing are + not required. - "Status: Current" value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-CLERGY.md b/_pages/tag-def/enum-CLERGY.md index a4778b76..24a3eff5 100644 --- a/_pages/tag-def/enum-CLERGY.md +++ b/_pages/tag-def/enum-CLERGY.md @@ -19,10 +19,12 @@ uri: https://gedcom.io/terms/v7/enum-CLERGY standard tag: CLERGY specification: - - Religious official in event; implies OFFICIATOR + - Religious official in event; implies `OFFICIATOR` value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-COMPLETED.md b/_pages/tag-def/enum-COMPLETED.md index 1608273c..eb725ac3 100644 --- a/_pages/tag-def/enum-COMPLETED.md +++ b/_pages/tag-def/enum-COMPLETED.md @@ -21,11 +21,13 @@ standard tag: COMPLETED specification: - "Applies to: All" - Completed, but the date is not known. - - "Status: Deprecated, use DATE BEF date instead. This status was defined for - use with TempleReady which is no longer in use." + - "Status: Deprecated, use `DATE BEF date` instead. This status was defined for + use with [TempleReady] which is no longer in use." value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-CONFIDENTIAL.md b/_pages/tag-def/enum-CONFIDENTIAL.md index 398939a3..eed6d4b6 100644 --- a/_pages/tag-def/enum-CONFIDENTIAL.md +++ b/_pages/tag-def/enum-CONFIDENTIAL.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-RESN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-DISPROVEN.md b/_pages/tag-def/enum-DISPROVEN.md index f295450d..8d2406cc 100644 --- a/_pages/tag-def/enum-DISPROVEN.md +++ b/_pages/tag-def/enum-DISPROVEN.md @@ -19,11 +19,13 @@ uri: https://gedcom.io/terms/v7/enum-DISPROVEN standard tag: DISPROVEN specification: - - There has been a claim by some that this child belongs to this family, but - the linkage has been disproven. + - There has been a claim by some that this child belongs to this family, but the + linkage has been disproven. value of: - "https://gedcom.io/terms/v7/enumset-FAMC-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-DNS.md b/_pages/tag-def/enum-DNS.md index 8a9b7add..a3d52207 100644 --- a/_pages/tag-def/enum-DNS.md +++ b/_pages/tag-def/enum-DNS.md @@ -19,12 +19,14 @@ uri: https://gedcom.io/terms/v7/enum-DNS standard tag: DNS specification: - - "Applies to: SLGC, SLGS" + - "Applies to: `SLGC`, `SLGS`" - This ordinance is not authorized. - "Status: Current" value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-DNS_CAN.md b/_pages/tag-def/enum-DNS_CAN.md index a49038ff..f4797050 100644 --- a/_pages/tag-def/enum-DNS_CAN.md +++ b/_pages/tag-def/enum-DNS_CAN.md @@ -19,12 +19,14 @@ uri: https://gedcom.io/terms/v7/enum-DNS_CAN standard tag: DNS_CAN specification: - - "Applies to: SLGS" + - "Applies to: `SLGS`" - This ordinance is not authorized, and the previous ordinance is cancelled. - "Status: Current" value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-ELECTRONIC.md b/_pages/tag-def/enum-ELECTRONIC.md index 09a55803..67de625b 100644 --- a/_pages/tag-def/enum-ELECTRONIC.md +++ b/_pages/tag-def/enum-ELECTRONIC.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-EXCLUDED.md b/_pages/tag-def/enum-EXCLUDED.md index fb5d701f..6afbbb84 100644 --- a/_pages/tag-def/enum-EXCLUDED.md +++ b/_pages/tag-def/enum-EXCLUDED.md @@ -21,11 +21,13 @@ standard tag: EXCLUDED specification: - "Applies to: All" - Patron excluded this ordinance from being cleared in this submission. - - "Status: Deprecated. This status was defined for use with TempleReady which - is no longer in use." + - "Status: Deprecated. This status was defined for use with TempleReady which is + no longer in use." value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-F.md b/_pages/tag-def/enum-F.md index 14b5cc38..b1cb36c6 100644 --- a/_pages/tag-def/enum-F.md +++ b/_pages/tag-def/enum-F.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-SEX" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-FATH.md b/_pages/tag-def/enum-FATH.md index 32bb667d..a10c40e9 100644 --- a/_pages/tag-def/enum-FATH.md +++ b/_pages/tag-def/enum-FATH.md @@ -19,10 +19,12 @@ uri: https://gedcom.io/terms/v7/enum-FATH standard tag: FATH specification: - - Father; implies PARENT + - Father; implies `PARENT` value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-FICHE.md b/_pages/tag-def/enum-FICHE.md index 1029c280..5a1cfd1d 100644 --- a/_pages/tag-def/enum-FICHE.md +++ b/_pages/tag-def/enum-FICHE.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-FILM.md b/_pages/tag-def/enum-FILM.md index bce15a7f..c2da35ea 100644 --- a/_pages/tag-def/enum-FILM.md +++ b/_pages/tag-def/enum-FILM.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-FOSTER.md b/_pages/tag-def/enum-FOSTER.md index dda210c1..4f8c9557 100644 --- a/_pages/tag-def/enum-FOSTER.md +++ b/_pages/tag-def/enum-FOSTER.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-PEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-FRIEND.md b/_pages/tag-def/enum-FRIEND.md index 82cb0976..b66c55f5 100644 --- a/_pages/tag-def/enum-FRIEND.md +++ b/_pages/tag-def/enum-FRIEND.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-GODP.md b/_pages/tag-def/enum-GODP.md index df29e775..55b04d7b 100644 --- a/_pages/tag-def/enum-GODP.md +++ b/_pages/tag-def/enum-GODP.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-HUSB.md b/_pages/tag-def/enum-HUSB.md index 6228a889..33430f37 100644 --- a/_pages/tag-def/enum-HUSB.md +++ b/_pages/tag-def/enum-HUSB.md @@ -19,10 +19,12 @@ uri: https://gedcom.io/terms/v7/enum-HUSB standard tag: HUSB specification: - - Husband; implies SPOU + - Husband; implies `SPOU` value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-IMMIGRANT.md b/_pages/tag-def/enum-IMMIGRANT.md index d1f54ad3..574b4583 100644 --- a/_pages/tag-def/enum-IMMIGRANT.md +++ b/_pages/tag-def/enum-IMMIGRANT.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-NAME-TYPE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-INFANT.md b/_pages/tag-def/enum-INFANT.md index f337ec9a..392f6b1f 100644 --- a/_pages/tag-def/enum-INFANT.md +++ b/_pages/tag-def/enum-INFANT.md @@ -19,12 +19,14 @@ uri: https://gedcom.io/terms/v7/enum-INFANT standard tag: INFANT specification: - - "Applies to: All but SLGC" + - "Applies to: All but `SLGC`" - Died before less than 1 year old, baptism or endowment not required. - - "Status: Deprecated. Use CHILD instead." + - "Status: Deprecated. Use `CHILD` instead." value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-LOCKED.md b/_pages/tag-def/enum-LOCKED.md index 6d4a0a9f..69d17e2f 100644 --- a/_pages/tag-def/enum-LOCKED.md +++ b/_pages/tag-def/enum-LOCKED.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-RESN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-M.md b/_pages/tag-def/enum-M.md index d21a7923..2d34b1fc 100644 --- a/_pages/tag-def/enum-M.md +++ b/_pages/tag-def/enum-M.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-SEX" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-MAGAZINE.md b/_pages/tag-def/enum-MAGAZINE.md index 6aa98f06..a2a7cfcb 100644 --- a/_pages/tag-def/enum-MAGAZINE.md +++ b/_pages/tag-def/enum-MAGAZINE.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-MAIDEN.md b/_pages/tag-def/enum-MAIDEN.md index 27d5b175..bfa946e1 100644 --- a/_pages/tag-def/enum-MAIDEN.md +++ b/_pages/tag-def/enum-MAIDEN.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-NAME-TYPE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-MANUSCRIPT.md b/_pages/tag-def/enum-MANUSCRIPT.md index 16eb2417..9257e26e 100644 --- a/_pages/tag-def/enum-MANUSCRIPT.md +++ b/_pages/tag-def/enum-MANUSCRIPT.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-MAP.md b/_pages/tag-def/enum-MAP.md index 45f0ea41..6b99a635 100644 --- a/_pages/tag-def/enum-MAP.md +++ b/_pages/tag-def/enum-MAP.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-MARRIED.md b/_pages/tag-def/enum-MARRIED.md index b3a3026e..57767e5b 100644 --- a/_pages/tag-def/enum-MARRIED.md +++ b/_pages/tag-def/enum-MARRIED.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-NAME-TYPE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-MOTH.md b/_pages/tag-def/enum-MOTH.md index 9008a9c7..c3014b58 100644 --- a/_pages/tag-def/enum-MOTH.md +++ b/_pages/tag-def/enum-MOTH.md @@ -19,10 +19,12 @@ uri: https://gedcom.io/terms/v7/enum-MOTH standard tag: MOTH specification: - - Mother; implies PARENT + - Mother; implies `PARENT` value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-MULTIPLE.md b/_pages/tag-def/enum-MULTIPLE.md index 5306a163..bf5d036d 100644 --- a/_pages/tag-def/enum-MULTIPLE.md +++ b/_pages/tag-def/enum-MULTIPLE.md @@ -20,10 +20,12 @@ standard tag: MULTIPLE specification: - A sibling from the same pregnancy (twin, triplet, quadruplet, and so on). A - PHRASE can be used to specify the kind of multiple birth. + `PHRASE` can be used to specify the kind of multiple birth. value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-NEWSPAPER.md b/_pages/tag-def/enum-NEWSPAPER.md index 621e4520..bc0bb7ea 100644 --- a/_pages/tag-def/enum-NEWSPAPER.md +++ b/_pages/tag-def/enum-NEWSPAPER.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-NGHBR.md b/_pages/tag-def/enum-NGHBR.md index 07acac52..eb013417 100644 --- a/_pages/tag-def/enum-NGHBR.md +++ b/_pages/tag-def/enum-NGHBR.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-OFFICIATOR.md b/_pages/tag-def/enum-OFFICIATOR.md index b2126004..d4d238ff 100644 --- a/_pages/tag-def/enum-OFFICIATOR.md +++ b/_pages/tag-def/enum-OFFICIATOR.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-OTHER.md b/_pages/tag-def/enum-OTHER.md index f115169e..0d3185c4 100644 --- a/_pages/tag-def/enum-OTHER.md +++ b/_pages/tag-def/enum-OTHER.md @@ -19,13 +19,15 @@ uri: https://gedcom.io/terms/v7/enum-OTHER standard tag: OTHER specification: - - A value not listed here; should have a PHRASE substructure + - A value not listed here; should have a `PHRASE` substructure value of: - "https://gedcom.io/terms/v7/enumset-MEDI" - "https://gedcom.io/terms/v7/enumset-NAME-TYPE" - "https://gedcom.io/terms/v7/enumset-PEDI" - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-PARENT.md b/_pages/tag-def/enum-PARENT.md index 79842b2a..1f1e3ceb 100644 --- a/_pages/tag-def/enum-PARENT.md +++ b/_pages/tag-def/enum-PARENT.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-PHOTO.md b/_pages/tag-def/enum-PHOTO.md index 39588103..b70c23dd 100644 --- a/_pages/tag-def/enum-PHOTO.md +++ b/_pages/tag-def/enum-PHOTO.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-PRE_1970.md b/_pages/tag-def/enum-PRE_1970.md index 410200a7..cefd70d2 100644 --- a/_pages/tag-def/enum-PRE_1970.md +++ b/_pages/tag-def/enum-PRE_1970.md @@ -22,10 +22,12 @@ specification: - "Applies to: All" - Ordinance was likely completed because an ordinance for this person was converted from temple records of work completed before 1970. - - "Status: Deprecated. Use DATE BEF 1970 instead." + - "Status: Deprecated. Use `DATE BEF 1970` instead." value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-PRIVACY.md b/_pages/tag-def/enum-PRIVACY.md index 87c595ab..2448a947 100644 --- a/_pages/tag-def/enum-PRIVACY.md +++ b/_pages/tag-def/enum-PRIVACY.md @@ -19,13 +19,15 @@ uri: https://gedcom.io/terms/v7/enum-PRIVACY standard tag: PRIVACY specification: - - This data is not to be shared outside of a trusted circle, generally - because it contains information about living individuals. This definition - is known to admit multiple interpretations, so use of the PRIVACY - restriction notice is not recommended. + - This data is not to be shared outside of a trusted circle, generally because it + contains information about living individuals. This definition is known to + admit multiple interpretations, so use of the `PRIVACY` restriction notice is + not recommended. value of: - "https://gedcom.io/terms/v7/enumset-RESN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-PROFESSIONAL.md b/_pages/tag-def/enum-PROFESSIONAL.md index cbbc9572..451c2c7a 100644 --- a/_pages/tag-def/enum-PROFESSIONAL.md +++ b/_pages/tag-def/enum-PROFESSIONAL.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-NAME-TYPE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-PROVEN.md b/_pages/tag-def/enum-PROVEN.md index 4bcbc7cd..52122749 100644 --- a/_pages/tag-def/enum-PROVEN.md +++ b/_pages/tag-def/enum-PROVEN.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-FAMC-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-SEALING.md b/_pages/tag-def/enum-SEALING.md index 9aca8989..d63e4610 100644 --- a/_pages/tag-def/enum-SEALING.md +++ b/_pages/tag-def/enum-SEALING.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-PEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-SPOU.md b/_pages/tag-def/enum-SPOU.md index 7d5f4ceb..08964dbe 100644 --- a/_pages/tag-def/enum-SPOU.md +++ b/_pages/tag-def/enum-SPOU.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-STILLBORN.md b/_pages/tag-def/enum-STILLBORN.md index 24f9d768..7125c374 100644 --- a/_pages/tag-def/enum-STILLBORN.md +++ b/_pages/tag-def/enum-STILLBORN.md @@ -25,6 +25,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-SUBMITTED.md b/_pages/tag-def/enum-SUBMITTED.md index a3e5e9ba..70b0082a 100644 --- a/_pages/tag-def/enum-SUBMITTED.md +++ b/_pages/tag-def/enum-SUBMITTED.md @@ -21,11 +21,13 @@ standard tag: SUBMITTED specification: - "Applies to: All" - Ordinance was previously submitted. - - "Status: Deprecated. This status was defined for use with TempleReady which - is no longer in use." + - "Status: Deprecated. This status was defined for use with TempleReady which is + no longer in use." value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-TOMBSTONE.md b/_pages/tag-def/enum-TOMBSTONE.md index 84b561b5..4c2c9ec7 100644 --- a/_pages/tag-def/enum-TOMBSTONE.md +++ b/_pages/tag-def/enum-TOMBSTONE.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-U.md b/_pages/tag-def/enum-U.md index 3a27b40f..14d39f93 100644 --- a/_pages/tag-def/enum-U.md +++ b/_pages/tag-def/enum-U.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-SEX" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-UNCLEARED.md b/_pages/tag-def/enum-UNCLEARED.md index 95638eff..280e59aa 100644 --- a/_pages/tag-def/enum-UNCLEARED.md +++ b/_pages/tag-def/enum-UNCLEARED.md @@ -21,11 +21,13 @@ standard tag: UNCLEARED specification: - "Applies to: All" - Data for clearing the ordinance request was insufficient. - - "Status: Deprecated. This status was defined for use with TempleReady which - is no longer in use." + - "Status: Deprecated. This status was defined for use with TempleReady which is + no longer in use." value of: - "https://gedcom.io/terms/v7/enumset-ord-STAT" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-VIDEO.md b/_pages/tag-def/enum-VIDEO.md index efbcf5e8..612f597f 100644 --- a/_pages/tag-def/enum-VIDEO.md +++ b/_pages/tag-def/enum-VIDEO.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-MEDI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-WIFE.md b/_pages/tag-def/enum-WIFE.md index abf44120..83f6cca8 100644 --- a/_pages/tag-def/enum-WIFE.md +++ b/_pages/tag-def/enum-WIFE.md @@ -19,10 +19,12 @@ uri: https://gedcom.io/terms/v7/enum-WIFE standard tag: WIFE specification: - - Wife; implies SPOU + - Wife; implies `SPOU` value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-WITN.md b/_pages/tag-def/enum-WITN.md index c9c42615..c16a043e 100644 --- a/_pages/tag-def/enum-WITN.md +++ b/_pages/tag-def/enum-WITN.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-ROLE" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enum-X.md b/_pages/tag-def/enum-X.md index d1dc079e..d78b9bb7 100644 --- a/_pages/tag-def/enum-X.md +++ b/_pages/tag-def/enum-X.md @@ -23,6 +23,8 @@ specification: value of: - "https://gedcom.io/terms/v7/enumset-SEX" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-ADOP.md b/_pages/tag-def/enumset-ADOP.md index 162ac8ab..9972c8dc 100644 --- a/_pages/tag-def/enumset-ADOP.md +++ b/_pages/tag-def/enumset-ADOP.md @@ -20,6 +20,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-ADOP-HUSB" - "https://gedcom.io/terms/v7/enum-ADOP-WIFE" - "https://gedcom.io/terms/v7/enum-BOTH" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-EVEN.md b/_pages/tag-def/enumset-EVEN.md index 9cbc1323..ba346f8d 100644 --- a/_pages/tag-def/enumset-EVEN.md +++ b/_pages/tag-def/enumset-EVEN.md @@ -17,6 +17,7 @@ type: enumeration set uri: https://gedcom.io/terms/v7/enumset-EVEN enumeration values: + - "https://gedcom.io/terms/v7/enum-CENS" - "https://gedcom.io/terms/v7/ADOP" - "https://gedcom.io/terms/v7/BAPM" - "https://gedcom.io/terms/v7/BARM" @@ -24,7 +25,6 @@ enumeration values: - "https://gedcom.io/terms/v7/BIRT" - "https://gedcom.io/terms/v7/BLES" - "https://gedcom.io/terms/v7/BURI" - - "https://gedcom.io/terms/v7/INDI-CENS" - "https://gedcom.io/terms/v7/CHR" - "https://gedcom.io/terms/v7/CHRA" - "https://gedcom.io/terms/v7/CONF" @@ -40,7 +40,6 @@ enumeration values: - "https://gedcom.io/terms/v7/RETI" - "https://gedcom.io/terms/v7/WILL" - "https://gedcom.io/terms/v7/ANUL" - - "https://gedcom.io/terms/v7/FAM-CENS" - "https://gedcom.io/terms/v7/DIV" - "https://gedcom.io/terms/v7/DIVF" - "https://gedcom.io/terms/v7/ENGA" @@ -49,6 +48,8 @@ enumeration values: - "https://gedcom.io/terms/v7/MARL" - "https://gedcom.io/terms/v7/MARR" - "https://gedcom.io/terms/v7/MARS" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-EVENATTR.md b/_pages/tag-def/enumset-EVENATTR.md index 6388ffd2..5692b79c 100644 --- a/_pages/tag-def/enumset-EVENATTR.md +++ b/_pages/tag-def/enumset-EVENATTR.md @@ -17,10 +17,11 @@ type: enumeration set uri: https://gedcom.io/terms/v7/enumset-EVENATTR enumeration values: - - "https://gedcom.io/terms/v7/INDI-EVEN" - - "https://gedcom.io/terms/v7/FAM-EVEN" - - "https://gedcom.io/terms/v7/INDI-FACT" - - "https://gedcom.io/terms/v7/FAM-FACT" + - "https://gedcom.io/terms/v7/enum-CENS" + - "https://gedcom.io/terms/v7/enum-NCHI" + - "https://gedcom.io/terms/v7/enum-RESI" + - "https://gedcom.io/terms/v7/enum-FACT" + - "https://gedcom.io/terms/v7/enum-EVEN" - "https://gedcom.io/terms/v7/ADOP" - "https://gedcom.io/terms/v7/BAPM" - "https://gedcom.io/terms/v7/BARM" @@ -28,7 +29,6 @@ enumeration values: - "https://gedcom.io/terms/v7/BIRT" - "https://gedcom.io/terms/v7/BLES" - "https://gedcom.io/terms/v7/BURI" - - "https://gedcom.io/terms/v7/INDI-CENS" - "https://gedcom.io/terms/v7/CHR" - "https://gedcom.io/terms/v7/CHRA" - "https://gedcom.io/terms/v7/CONF" @@ -44,7 +44,6 @@ enumeration values: - "https://gedcom.io/terms/v7/RETI" - "https://gedcom.io/terms/v7/WILL" - "https://gedcom.io/terms/v7/ANUL" - - "https://gedcom.io/terms/v7/FAM-CENS" - "https://gedcom.io/terms/v7/DIV" - "https://gedcom.io/terms/v7/DIVF" - "https://gedcom.io/terms/v7/ENGA" @@ -58,16 +57,14 @@ enumeration values: - "https://gedcom.io/terms/v7/EDUC" - "https://gedcom.io/terms/v7/IDNO" - "https://gedcom.io/terms/v7/NATI" - - "https://gedcom.io/terms/v7/INDI-NCHI" - "https://gedcom.io/terms/v7/NMR" - "https://gedcom.io/terms/v7/OCCU" - "https://gedcom.io/terms/v7/PROP" - "https://gedcom.io/terms/v7/RELI" - - "https://gedcom.io/terms/v7/INDI-RESI" - "https://gedcom.io/terms/v7/SSN" - "https://gedcom.io/terms/v7/TITL" - - "https://gedcom.io/terms/v7/FAM-NCHI" - - "https://gedcom.io/terms/v7/FAM-RESI" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-FAMC-STAT.md b/_pages/tag-def/enumset-FAMC-STAT.md index c3634942..4ee49b0e 100644 --- a/_pages/tag-def/enumset-FAMC-STAT.md +++ b/_pages/tag-def/enumset-FAMC-STAT.md @@ -20,6 +20,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-CHALLENGED" - "https://gedcom.io/terms/v7/enum-DISPROVEN" - "https://gedcom.io/terms/v7/enum-PROVEN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-MEDI.md b/_pages/tag-def/enumset-MEDI.md index c2c06b56..a45536b4 100644 --- a/_pages/tag-def/enumset-MEDI.md +++ b/_pages/tag-def/enumset-MEDI.md @@ -31,6 +31,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-TOMBSTONE" - "https://gedcom.io/terms/v7/enum-VIDEO" - "https://gedcom.io/terms/v7/enum-OTHER" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-NAME-TYPE.md b/_pages/tag-def/enumset-NAME-TYPE.md index acb5c925..d77fde08 100644 --- a/_pages/tag-def/enumset-NAME-TYPE.md +++ b/_pages/tag-def/enumset-NAME-TYPE.md @@ -24,6 +24,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-MARRIED" - "https://gedcom.io/terms/v7/enum-PROFESSIONAL" - "https://gedcom.io/terms/v7/enum-OTHER" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-PEDI.md b/_pages/tag-def/enumset-PEDI.md index 4d3c4fbe..0dcd04ad 100644 --- a/_pages/tag-def/enumset-PEDI.md +++ b/_pages/tag-def/enumset-PEDI.md @@ -22,6 +22,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-FOSTER" - "https://gedcom.io/terms/v7/enum-SEALING" - "https://gedcom.io/terms/v7/enum-OTHER" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-QUAY.md b/_pages/tag-def/enumset-QUAY.md index 0857544d..bf72dcc7 100644 --- a/_pages/tag-def/enumset-QUAY.md +++ b/_pages/tag-def/enumset-QUAY.md @@ -21,6 +21,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-1" - "https://gedcom.io/terms/v7/enum-2" - "https://gedcom.io/terms/v7/enum-3" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-RESN.md b/_pages/tag-def/enumset-RESN.md index 636689c0..718bec08 100644 --- a/_pages/tag-def/enumset-RESN.md +++ b/_pages/tag-def/enumset-RESN.md @@ -20,6 +20,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-CONFIDENTIAL" - "https://gedcom.io/terms/v7/enum-LOCKED" - "https://gedcom.io/terms/v7/enum-PRIVACY" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-ROLE.md b/_pages/tag-def/enumset-ROLE.md index 28b06153..45adf6d8 100644 --- a/_pages/tag-def/enumset-ROLE.md +++ b/_pages/tag-def/enumset-ROLE.md @@ -32,6 +32,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-WIFE" - "https://gedcom.io/terms/v7/enum-WITN" - "https://gedcom.io/terms/v7/enum-OTHER" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-SEX.md b/_pages/tag-def/enumset-SEX.md index f6bfe90a..af8eb30d 100644 --- a/_pages/tag-def/enumset-SEX.md +++ b/_pages/tag-def/enumset-SEX.md @@ -21,6 +21,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-F" - "https://gedcom.io/terms/v7/enum-X" - "https://gedcom.io/terms/v7/enum-U" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/enumset-ord-STAT.md b/_pages/tag-def/enumset-ord-STAT.md index 7a9fb54c..e8f81c1c 100644 --- a/_pages/tag-def/enumset-ord-STAT.md +++ b/_pages/tag-def/enumset-ord-STAT.md @@ -29,6 +29,8 @@ enumeration values: - "https://gedcom.io/terms/v7/enum-STILLBORN" - "https://gedcom.io/terms/v7/enum-SUBMITTED" - "https://gedcom.io/terms/v7/enum-UNCLEARED" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-AAV.md b/_pages/tag-def/month-AAV.md index 468b51fb..cae25212 100644 --- a/_pages/tag-def/month-AAV.md +++ b/_pages/tag-def/month-AAV.md @@ -25,6 +25,8 @@ label: 'Av' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-ADR.md b/_pages/tag-def/month-ADR.md index 21a8146b..d92155f6 100644 --- a/_pages/tag-def/month-ADR.md +++ b/_pages/tag-def/month-ADR.md @@ -25,6 +25,8 @@ label: 'Adar I' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-ADS.md b/_pages/tag-def/month-ADS.md index 0ee56042..0fd4c46d 100644 --- a/_pages/tag-def/month-ADS.md +++ b/_pages/tag-def/month-ADS.md @@ -25,6 +25,8 @@ label: 'Adar' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-APR.md b/_pages/tag-def/month-APR.md index 3a2346bd..3d29c648 100644 --- a/_pages/tag-def/month-APR.md +++ b/_pages/tag-def/month-APR.md @@ -26,6 +26,8 @@ label: 'April' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-AUG.md b/_pages/tag-def/month-AUG.md index 8ffaedc6..36363953 100644 --- a/_pages/tag-def/month-AUG.md +++ b/_pages/tag-def/month-AUG.md @@ -26,6 +26,8 @@ label: 'August' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-BRUM.md b/_pages/tag-def/month-BRUM.md index ebe052d9..423e6e76 100644 --- a/_pages/tag-def/month-BRUM.md +++ b/_pages/tag-def/month-BRUM.md @@ -25,6 +25,8 @@ label: 'Brumaire' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-COMP.md b/_pages/tag-def/month-COMP.md index e4f25f1d..6c1b086f 100644 --- a/_pages/tag-def/month-COMP.md +++ b/_pages/tag-def/month-COMP.md @@ -25,6 +25,8 @@ label: 'Jour Complémentaires' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-CSH.md b/_pages/tag-def/month-CSH.md index 3bd10201..c3ba010a 100644 --- a/_pages/tag-def/month-CSH.md +++ b/_pages/tag-def/month-CSH.md @@ -25,6 +25,8 @@ label: 'Marcheshvan' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-DEC.md b/_pages/tag-def/month-DEC.md index 2eb7088d..8ad77440 100644 --- a/_pages/tag-def/month-DEC.md +++ b/_pages/tag-def/month-DEC.md @@ -26,6 +26,8 @@ label: 'December' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-ELL.md b/_pages/tag-def/month-ELL.md index 93b8b7ac..827fd6d6 100644 --- a/_pages/tag-def/month-ELL.md +++ b/_pages/tag-def/month-ELL.md @@ -25,6 +25,8 @@ label: 'Elul' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-FEB.md b/_pages/tag-def/month-FEB.md index b5bdad76..fa70894a 100644 --- a/_pages/tag-def/month-FEB.md +++ b/_pages/tag-def/month-FEB.md @@ -26,6 +26,8 @@ label: 'February' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-FLOR.md b/_pages/tag-def/month-FLOR.md index bb45c935..141c4ba0 100644 --- a/_pages/tag-def/month-FLOR.md +++ b/_pages/tag-def/month-FLOR.md @@ -25,6 +25,8 @@ label: 'Floréal' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-FRIM.md b/_pages/tag-def/month-FRIM.md index 9fdec638..ac407d9a 100644 --- a/_pages/tag-def/month-FRIM.md +++ b/_pages/tag-def/month-FRIM.md @@ -25,6 +25,8 @@ label: 'Frimaire' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-FRUC.md b/_pages/tag-def/month-FRUC.md index 281a18d9..db1211be 100644 --- a/_pages/tag-def/month-FRUC.md +++ b/_pages/tag-def/month-FRUC.md @@ -25,6 +25,8 @@ label: 'Fructidor' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-GERM.md b/_pages/tag-def/month-GERM.md index 84140d7c..8548ce0f 100644 --- a/_pages/tag-def/month-GERM.md +++ b/_pages/tag-def/month-GERM.md @@ -25,6 +25,8 @@ label: 'Germinal' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-IYR.md b/_pages/tag-def/month-IYR.md index db725de0..ebd24dc5 100644 --- a/_pages/tag-def/month-IYR.md +++ b/_pages/tag-def/month-IYR.md @@ -25,6 +25,8 @@ label: 'Iyar' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-JAN.md b/_pages/tag-def/month-JAN.md index c6e0e815..4d63ec5f 100644 --- a/_pages/tag-def/month-JAN.md +++ b/_pages/tag-def/month-JAN.md @@ -26,6 +26,8 @@ label: 'January' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-JUL.md b/_pages/tag-def/month-JUL.md index 626526b8..3300ab3c 100644 --- a/_pages/tag-def/month-JUL.md +++ b/_pages/tag-def/month-JUL.md @@ -26,6 +26,8 @@ label: 'July' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-JUN.md b/_pages/tag-def/month-JUN.md index e8b55bbd..b35bb0db 100644 --- a/_pages/tag-def/month-JUN.md +++ b/_pages/tag-def/month-JUN.md @@ -26,6 +26,8 @@ label: 'June' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-KSL.md b/_pages/tag-def/month-KSL.md index e4244075..affbc965 100644 --- a/_pages/tag-def/month-KSL.md +++ b/_pages/tag-def/month-KSL.md @@ -25,6 +25,8 @@ label: 'Kislev' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-MAR.md b/_pages/tag-def/month-MAR.md index 9b4cdc33..60fc6b3c 100644 --- a/_pages/tag-def/month-MAR.md +++ b/_pages/tag-def/month-MAR.md @@ -26,6 +26,8 @@ label: 'March' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-MAY.md b/_pages/tag-def/month-MAY.md index 67261958..ae56165a 100644 --- a/_pages/tag-def/month-MAY.md +++ b/_pages/tag-def/month-MAY.md @@ -26,6 +26,8 @@ label: 'May' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-MESS.md b/_pages/tag-def/month-MESS.md index a98538a4..9bf2e2f9 100644 --- a/_pages/tag-def/month-MESS.md +++ b/_pages/tag-def/month-MESS.md @@ -25,6 +25,8 @@ label: 'Messidor' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-NIVO.md b/_pages/tag-def/month-NIVO.md index ffa31135..3e198d6b 100644 --- a/_pages/tag-def/month-NIVO.md +++ b/_pages/tag-def/month-NIVO.md @@ -25,6 +25,8 @@ label: 'Nivôse' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-NOV.md b/_pages/tag-def/month-NOV.md index 6e17fc0b..a2ecefd8 100644 --- a/_pages/tag-def/month-NOV.md +++ b/_pages/tag-def/month-NOV.md @@ -26,6 +26,8 @@ label: 'November' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-NSN.md b/_pages/tag-def/month-NSN.md index 9e0401f9..79f3df81 100644 --- a/_pages/tag-def/month-NSN.md +++ b/_pages/tag-def/month-NSN.md @@ -25,6 +25,8 @@ label: 'Nisan' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-OCT.md b/_pages/tag-def/month-OCT.md index 5a9de0d1..2f4311a8 100644 --- a/_pages/tag-def/month-OCT.md +++ b/_pages/tag-def/month-OCT.md @@ -26,6 +26,8 @@ label: 'October' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-PLUV.md b/_pages/tag-def/month-PLUV.md index c27a861f..28113300 100644 --- a/_pages/tag-def/month-PLUV.md +++ b/_pages/tag-def/month-PLUV.md @@ -25,6 +25,8 @@ label: 'Pluviôse' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-PRAI.md b/_pages/tag-def/month-PRAI.md index b4b97b48..6b506d40 100644 --- a/_pages/tag-def/month-PRAI.md +++ b/_pages/tag-def/month-PRAI.md @@ -25,6 +25,8 @@ label: 'Prairial' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-SEP.md b/_pages/tag-def/month-SEP.md index 4b29b73c..fe4e0720 100644 --- a/_pages/tag-def/month-SEP.md +++ b/_pages/tag-def/month-SEP.md @@ -26,6 +26,8 @@ label: 'September' calendars: - "https://gedcom.io/terms/v7/cal-GREGORIAN" - "https://gedcom.io/terms/v7/cal-JULIAN" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-SHV.md b/_pages/tag-def/month-SHV.md index 7dff3975..9165aebd 100644 --- a/_pages/tag-def/month-SHV.md +++ b/_pages/tag-def/month-SHV.md @@ -25,6 +25,8 @@ label: 'Shevat' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-SVN.md b/_pages/tag-def/month-SVN.md index 8a07f6fb..fdb91922 100644 --- a/_pages/tag-def/month-SVN.md +++ b/_pages/tag-def/month-SVN.md @@ -25,6 +25,8 @@ label: 'Sivan' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-THER.md b/_pages/tag-def/month-THER.md index 28e48825..867a81f6 100644 --- a/_pages/tag-def/month-THER.md +++ b/_pages/tag-def/month-THER.md @@ -25,6 +25,8 @@ label: 'Thermidor' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-TMZ.md b/_pages/tag-def/month-TMZ.md index a222297c..c075ed7e 100644 --- a/_pages/tag-def/month-TMZ.md +++ b/_pages/tag-def/month-TMZ.md @@ -25,6 +25,8 @@ label: 'Tammuz' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-TSH.md b/_pages/tag-def/month-TSH.md index 33f031b6..e8597656 100644 --- a/_pages/tag-def/month-TSH.md +++ b/_pages/tag-def/month-TSH.md @@ -25,6 +25,8 @@ label: 'Tishrei' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-TVT.md b/_pages/tag-def/month-TVT.md index 515c17eb..8032de19 100644 --- a/_pages/tag-def/month-TVT.md +++ b/_pages/tag-def/month-TVT.md @@ -25,6 +25,8 @@ label: 'Tevet' calendars: - "https://gedcom.io/terms/v7/cal-HEBREW" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-VEND.md b/_pages/tag-def/month-VEND.md index 333df4f5..c1ec3852 100644 --- a/_pages/tag-def/month-VEND.md +++ b/_pages/tag-def/month-VEND.md @@ -25,6 +25,8 @@ label: 'Vendémiaire' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/month-VENT.md b/_pages/tag-def/month-VENT.md index 8b544cd0..4b49b406 100644 --- a/_pages/tag-def/month-VENT.md +++ b/_pages/tag-def/month-VENT.md @@ -25,6 +25,8 @@ label: 'Ventôse' calendars: - "https://gedcom.io/terms/v7/cal-FRENCH_R" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/ord-STAT.md b/_pages/tag-def/ord-STAT.md index 048a1ddf..46986794 100644 --- a/_pages/tag-def/ord-STAT.md +++ b/_pages/tag-def/ord-STAT.md @@ -20,7 +20,7 @@ standard tag: STAT specification: - Status - - An enumerated value from set https://gedcom.io/terms/v7/enumset-ord-STAT + - An enumerated value from set `https://gedcom.io/terms/v7/enumset-ord-STAT` assessing of the state or condition of an ordinance. label: 'Status' @@ -39,6 +39,8 @@ superstructures: "https://gedcom.io/terms/v7/INIL": "{0:1}" "https://gedcom.io/terms/v7/SLGC": "{0:1}" "https://gedcom.io/terms/v7/SLGS": "{0:1}" + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/record-FAM.md b/_pages/tag-def/record-FAM.md index c56f191d..321abd37 100644 --- a/_pages/tag-def/record-FAM.md +++ b/_pages/tag-def/record-FAM.md @@ -21,52 +21,68 @@ standard tag: FAM specification: - Family record - | - See FAMILY_RECORD + See `FAMILY_RECORD` - The common case is that each couple has one FAM record, but that is not +
+ + The common case is that each couple has one `FAM` record, but that is not always the case. - A couple that separates and then gets together again can be represented - either as a single FAM with multiple events (MARR, DIV, etc.) or as a - separate FAM for each time together. Some user interfaces may display these - two in different ways and the two admit different semantics in sourcing. A - single FAM with two MARR with distinct dates might also represent - uncertainty about dates and a pair of FAM with same spouses might also be - the result of merging multiple files. + A couple that separates and then gets together again can be represented either + as a single `FAM` with multiple events (`MARR`, `DIV`, etc.) or as a separate + `FAM` for each time together. Some user interfaces may display these two in + different ways and the two admit different semantics in sourcing. A single + `FAM` with two `MARR` with distinct dates might also represent uncertainty + about dates and a pair of `FAM` with same spouses might also be the result of + merging multiple files. Implementers should support both representations, and should choose between - them based on user input or other context beyond that provided in the - datasets themselves. + them based on user input or other context beyond that provided in the datasets + themselves. + +
- | - The FAM record was originally structured to represent families where a male - HUSB (husband or father) and female WIFE (wife or mother) produce CHIL - (children). The FAM record may also be used for cultural parallels to this, - including nuclear families, marriage, cohabitation, fostering, adoption, - and so on, regardless of the gender of the partners. Sex, gender, titles, - and roles of partners should not be inferred based on the partner that the - HUSB or WIFE structure points to. + The `FAM` record was originally structured to represent families where a male + `HUSB` (husband or father) and female `WIFE` (wife or mother) produce `CHIL` + (children). The `FAM` record may also be used for cultural parallels to this, + including nuclear families, marriage, cohabitation, fostering, adoption, and so + on, regardless of the gender of the partners. Sex, gender, titles, and roles of + partners should not be inferred based on the partner that the `HUSB` or `WIFE` + structure points to. + + The individuals pointed to by the `HUSB` and `WIFE` are collectively referred + to as "partners", "parents" or "spouses". + + Some displays may be unable to display more than 2 partners. Displays may use + `HUSB` and `WIFE` as layout hints, for example, by consistently displaying the + `HUSB` on the same side of the `WIFE` in a tree view. Family structures with + more than 2 partners may either use several `FAM` records or use + `ASSOCIATION_STRUCTURE`s to indicate additional partners. - The individuals pointed to by the HUSB and WIFE are collectively referred - to as “partners”, “parents” or “spouses”. +
- Some displays may be unable to display more than 2 partners. Displays may - use HUSB and WIFE as layout hints, for example, by consistently displaying - the HUSB on the same side of the WIFE in a tree view. Family structures - with more than 2 partners may either use several FAM records or use - ASSOCIATION_STRUCTUREs to indicate additional partners. + The `FAM` record will be revised in a future version to more fully express the + diversity of human family relationships. - The FAM record will be revised in a future version to more fully express - the diversity of human family relationships. +
- The order of the CHIL (children) pointers within a FAM (family) structure - should be chronological by birth; this is an exception to the usual “most - preferred value first” rule. A CHIL with a voidPtr indicates a placeholder + The order of the `CHIL` (children) pointers within a `FAM` (family) structure + should be chronological by birth; this is an exception to the usual "most + preferred value first" rule. A `CHIL` with a `voidPtr` indicates a placeholder for an unknown child in this birth order. - If a FAM record uses HUSB or WIFE to point to an INDI record, the INDI - record must use FAMS to point to the FAM record. If a FAM record uses CHIL - to point to an INDI record, the INDI record must use a FAMC to point to the - FAM record. + If a `FAM` record uses `HUSB` or `WIFE` to point to an `INDI` record, the + `INDI` record must use `FAMS` to point to the `FAM` record. If a `FAM` record + uses `CHIL` to point to an `INDI` record, the `INDI` record must use a `FAMC` + to point to the `FAM` record. + + An `INDI` record should not have multiple `FAMS` substructures pointing to the + same `FAM`. + + A `FAM` record should not have multiple `CHIL` substructures pointing to the + same `INDI`; doing so implies a nonsensical birth order. An `INDI` record may + have multiple `FAMC` substructures pointing to the same `FAM`, but doing so is + not recommended. label: 'Family record' @@ -106,6 +122,8 @@ substructures: "https://gedcom.io/terms/v7/UID": "{0:M}" superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/record-INDI.md b/_pages/tag-def/record-INDI.md index 72d6964e..6ad0391e 100644 --- a/_pages/tag-def/record-INDI.md +++ b/_pages/tag-def/record-INDI.md @@ -20,41 +20,47 @@ standard tag: INDI specification: - Individual - - See INDIVIDUAL_RECORD. + - See `INDIVIDUAL_RECORD`. - | - The individual record is a compilation of facts or hypothesized facts about - an individual. These facts may come from multiple sources. Source citations - and notes allow documentation of the source where each of the facts were + The individual record is a compilation of facts or hypothesized facts about an + individual. These facts may come from multiple sources. Source citations and + notes allow documentation of the source where each of the facts were discovered. A single individual may have facts distributed across multiple individual - records, connected by ALIA (alias, in the computing sense not the pseudonym - sense) pointers. See ALIA for more. + records, connected by `ALIA` (alias, in the computing sense not the pseudonym + sense) pointers. See `ALIA` for more details. Individual records are linked to Family records by use of bi-directional - pointers. Details about those links are stored as substructures of the - pointers in the individual record. + pointers. Details about those links are stored as substructures of the pointers + in the individual record. - Other associations or relationships are represented by the ASSO - (association) tag. The person’s relation or associate is the person being - pointed to. The association or relationship is stated by the value on the - subordinate ROLE line. + Other associations or relationships are represented by the `ASSO` (association) + tag. The person's relation or associate is the person being pointed to. The + association or relationship is stated by the value on the subordinate `ROLE` + line. - The following example refers to 2 individuals, @I1@ and @I2@, where @I2@ is - a godparent of @I1@: +
- 0 @I1@ INDI - 1 ASSO @I2@ - 2 ROLE GODP + The following example refers to 2 individuals, `@I1@` and `@I2@`, where `@I2@` + is a godparent of `@I1@`: - Events stored as facts within an INDI record may also have FAMC or ASSO - tags to indicate families and individuals that participated in those - events. For example, a FAMC pointer subordinate to an adoption event - indicates a relationship to family by adoption; biological parents can be - shown by a FAMC pointer subordinate to the birth event; the eulogist at a - funeral can be shown by an ASSO pointer subordinate to the burial event; - and so on. A subordinate FAMC pointer is allowed to refer to a family where - the individual does not appear as a child. + ```gedcom + 0 @I1@ INDI + 1 ASSO @I2@ + 2 ROLE GODP + ``` + +
+ + Events stored as facts within an `INDI` record may also have `FAMC` or `ASSO` + tags to indicate families and individuals that participated in those events. + For example, a `FAMC` pointer subordinate to an adoption event indicates a + relationship to family by adoption; biological parents can be shown by a `FAMC` + pointer subordinate to the birth event; the eulogist at a funeral can be shown + by an `ASSO` pointer subordinate to the burial event; and so on. A subordinate + `FAMC` pointer is allowed to refer to a family where the individual does not + appear as a child. label: 'Individual' @@ -125,6 +131,8 @@ substructures: "https://gedcom.io/terms/v7/WILL": "{0:M}" superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/record-OBJE.md b/_pages/tag-def/record-OBJE.md index f6128f00..520b23a0 100644 --- a/_pages/tag-def/record-OBJE.md +++ b/_pages/tag-def/record-OBJE.md @@ -20,18 +20,16 @@ standard tag: OBJE specification: - Object - - See MULTIMEDIA_RECORD. + - See `MULTIMEDIA_RECORD`. - | The multimedia record refers to 1 or more external digital files, and may - provide some additional information about the files and the media they - encode. + provide some additional information about the files and the media they encode. - The file reference can occur more than once to group multiple files - together. Grouped files should each pertain to the same context. For - example, a sound clip and a photo both of the same event might be grouped - in a single OBJE. + The file reference can occur more than once to group multiple files together. + Grouped files should each pertain to the same context. For example, a sound + clip and a photo both of the same event might be grouped in a single `OBJE`. - The change and creation dates should be for the OBJE record itself, not the + The change and creation dates should be for the `OBJE` record itself, not the underlying files. label: 'Object' @@ -51,6 +49,8 @@ substructures: "https://gedcom.io/terms/v7/UID": "{0:M}" superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/record-REPO.md b/_pages/tag-def/record-REPO.md index af39ea0a..ff1316b6 100644 --- a/_pages/tag-def/record-REPO.md +++ b/_pages/tag-def/record-REPO.md @@ -20,20 +20,20 @@ standard tag: REPO specification: - Repository - - See REPOSITORY_RECORD. + - See `REPOSITORY_RECORD`. - | - The repository record provides information about an institution or person - that has a collection of sources. Informal repositories include the owner - of an unpublished work or of a rare published source, or a keeper of - personal collections. An example would be the owner of a family Bible - containing unpublished family genealogical entries. + The repository record provides information about an institution or person that + has a collection of sources. Informal repositories include the owner of an + unpublished work or of a rare published source, or a keeper of personal + collections. An example would be the owner of a family Bible containing + unpublished family genealogical entries. Layered repositories, such as an archive containing copies of a subset of records from another archive or archives that have moved or been bought by other archives, are not modeled in this version of the specification. It is expected they will be added in a later version. Until such time, it is - recommended that the repository record store current contact information, - if known. + recommended that the repository record store current contact information, if + known. label: 'Repository' @@ -55,6 +55,8 @@ substructures: "https://gedcom.io/terms/v7/WWW": "{0:M}" superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/record-SNOTE.md b/_pages/tag-def/record-SNOTE.md index a8219175..75d49979 100644 --- a/_pages/tag-def/record-SNOTE.md +++ b/_pages/tag-def/record-SNOTE.md @@ -20,41 +20,51 @@ standard tag: SNOTE specification: - Shared note - - A note that is shared by multiple structures. See SHARED_NOTE_RECORD for - more. + - A note that is shared by multiple structures. See `SHARED_NOTE_RECORD` for more + details. - | A catch-all location for information that does not fully fit within other structures. It may include research notes, additional context, alternative interpretations, reasoning, and so forth. A shared note record may be pointed to by multiple other structures. Shared - notes should only be used if editing the note in one place should edit it - in all other places or if the note itself requires an IDENTIFIER_STRUCTURE. - If each instance of the note may be edited separately and no identifier is - needed, a NOTE should be used instead. + notes should only be used if editing the note in one place should edit it in + all other places or if the note itself requires an `IDENTIFIER_STRUCTURE`. If + each instance of the note may be edited separately and no identifier is needed, + a `NOTE` should be used instead. - Each SNOTE.TRAN must have either a MIME or LANG substructure or both. + Each [`SNOTE`.`TRAN`] must have either a `MIME` or `LANG` substructure or + both. + +
The origin of a name might be a reasonable shared note, while the reason a - particular person was given that name may make more sense as a non-shared - note. + particular person was given that name may make more sense as a non-shared note. + + ```gedcom + 0 @GORDON@ SNOTE "Gordon" is a traditional Scottish surname. + 1 CONT It became a given name in honor of Charles George Gordon. + 0 @I1@ INDI + 1 NAME Gordon /Jones/ + 2 NOTE Named after the astronaut Gordon Cooper + 2 SNOTE @GORDON@ + ``` + +
- 0 @GORDON@ SNOTE "Gordon" is a traditional Scottish surname. - 1 CONT It became a given name in honor of Charles George Gordon. - 0 @I1@ INDI - 1 NAME Gordon /Jones/ - 2 NOTE Named after the astronaut Gordon Cooper - 2 SNOTE @GORDON@ +
- The ability to have multiple structures share a single note using pointers - was introduced in version 5.0 in 1991. However, as of 2021 relatively few - applications have a user interface that presents shared notes as such to - users. It is recommended that SNOTE be avoided when NOTE will suffice. + The ability to have multiple structures share a single note using pointers was + introduced in version 5.0 in 1991. However, as of 2021 relatively few + applications have a user interface that presents shared notes as such to users. + It is recommended that `SNOTE` be avoided when `NOTE` will suffice. - A SHARED_NOTE_RECORD may contain a pointer to a SOURCE_RECORD and vice - versa. Applications must not create datasets where these mutual pointers - form a cycle. Applications should also ensure they can handle invalid files - with such cycles in a safe manner. +
+ + A `SHARED_NOTE_RECORD` may contain a pointer to a `SOURCE_RECORD` and vice + versa. Applications must not create datasets where these mutual pointers form a + cycle. Applications should also ensure they can handle invalid files with such + cycles in a safe manner. label: 'Shared note' @@ -72,6 +82,8 @@ substructures: "https://gedcom.io/terms/v7/UID": "{0:M}" superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/record-SOUR.md b/_pages/tag-def/record-SOUR.md index e74f3f08..8f071373 100644 --- a/_pages/tag-def/record-SOUR.md +++ b/_pages/tag-def/record-SOUR.md @@ -20,21 +20,24 @@ standard tag: SOUR specification: - Source - - A description of an entire source. See SOURCE_RECORD for more. + - A description of an entire source. See `SOURCE_RECORD` for more details. - | - A source record describes an entire source. A source may also point to - REPOs to describe repositories or archives where the source document may be - found. The part of a source relevant to a specific fact, such as a specific - page or entry, is indicated in a SOURCE_CITATION that points to the source - record. + A source record describes an entire source. A source may also point to `REPO`s + to describe repositories or archives where the source document may be found. + The part of a source relevant to a specific fact, such as a specific page or + entry, is indicated in a `SOURCE_CITATION` that points to the source record. - This sourcing model is known to be insufficient for some use cases and may - be refined in a future version of this specification. +
- A SOURCE_RECORD may contain a pointer to a SHARED_NOTE_RECORD and vice - versa. Applications must not create datasets where these mutual pointers - form a cycle. Applications should also ensure they can handle invalid files - with such cycles in a safe manner. + This sourcing model is known to be insufficient for some use cases and may be + refined in a future version of this specification. + +
+ + A `SOURCE_RECORD` may contain a pointer to a `SHARED_NOTE_RECORD` and vice + versa. Applications must not create datasets where these mutual pointers form a + cycle. Applications should also ensure they can handle invalid files with such + cycles in a safe manner. label: 'Source' @@ -58,6 +61,8 @@ substructures: "https://gedcom.io/terms/v7/UID": "{0:M}" superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/record-SUBM.md b/_pages/tag-def/record-SUBM.md index 607b6c9d..5745b623 100644 --- a/_pages/tag-def/record-SUBM.md +++ b/_pages/tag-def/record-SUBM.md @@ -21,12 +21,11 @@ standard tag: SUBM specification: - Submitter - A description of a contributor of information to the document. See - SUBMITTER_RECORD for more. - - The submitter record identifies an individual or organization that - contributed information contained in the dataset. All records in the - document are assumed to be contributed by the submitter referenced in the - HEAD, unless a SUBM structure inside a specific record points at a - different submitter record. + `SUBMITTER_RECORD` for more details. + - The submitter record identifies an individual or organization that contributed + information contained in the dataset. All records in the document are assumed + to be contributed by the submitter referenced in the `HEAD`, unless a `SUBM` + structure inside a specific record points at a different submitter record. label: 'Submitter' @@ -50,6 +49,8 @@ substructures: "https://gedcom.io/terms/v7/WWW": "{0:M}" superstructures: {} + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/type-Age.md b/_pages/tag-def/type-Age.md index 62d02341..5f0b1b12 100644 --- a/_pages/tag-def/type-Age.md +++ b/_pages/tag-def/type-Age.md @@ -20,50 +20,68 @@ specification: - | Ages are represented by counts of years, months, weeks, and days. - Age = [[ageBound D] ageDuration] + ```abnf + Age = [[ageBound D] ageDuration] - ageBound = "<" / ">" - ageDuration = years [D months] [D weeks] [D days] - / months [D weeks] [D days] - / weeks [D days] - / days + ageBound = "<" / ">" + ageDuration = years [D months] [D weeks] [D days] + / months [D weeks] [D days] + / weeks [D days] + / days - years = Integer %x79 ; 35y - months = Integer %x6D ; 11m - weeks = Integer %x77 ; 8w - days = Integer %x64 ; 21d + years = Integer %x79 ; 35y + months = Integer %x6D ; 11m + weeks = Integer %x77 ; 8w + days = Integer %x64 ; 21d + ``` Where - Production Meaning - ------------ ------------------------------------------------ - < The real age was less than the provided age - > The real age was greater than the provided age - years a number of years - months a number of months - weeks a number of weeks - days a number of days + | Production | Meaning | + | :--------- | :--------------------------------------------- | + | `<` | The real age was less than the provided age | + | `>` | The real age was greater than the provided age | + | `years` | a number of years | + | `months` | a number of months | + | `weeks` | a number of weeks | + | `days` | a number of days | - Non-integer numbers should be rounded down to an integer. Thus, if someone - has lived for 363.5 days, their age might be written as 363d, 51w 6d, 51w, - 0y, etc. + Non-integer numbers should be rounded down to an integer. Thus, if someone has + lived for 363.5 days, their age might be written as `363d`, `51w 6d`, `51w`, + `0y`, etc. - Because numbers are rounded down, > effectively includes its endpoint; that - is, the age > 8d includes people who have lived 8 days + a few seconds. + Because numbers are rounded down, `>` effectively includes its endpoint; that + is, the age `> 8d` includes people who have lived 8 days + a few seconds. Different cultures count ages differently. Some increment years on the anniversary of birth and others at particular seasons. Some round to the - nearest year, others round years down, others round years up. Because users - may be unaware of these traditions or may fail to convert them to the - round-down convention, errors in age of up to a year are common. + nearest year, others round years down, others round years up. Because users may + be unaware of these traditions or may fail to convert them to the round-down + convention, errors in age of up to a year are common. - Age payloads may also be omitted entirely if no suitable form is known but - a substructure (such as a PHRASE) is desired. +
- Versions 5.5 and 5.5.1 allowed a few specific phrases inside Age payloads. - Age phrases were moved to the PHRASE substructure in 7.0. + Because age payloads are intended to allow recording the age as it was recorded + in records that could contain errors, odd ages such as `8w 30d`, `1y 400d`, + `1y 30m`, etc. are permitted. Some applications might convert these to more + standard forms; if so, it is recommended that they use a `PHRASE` substructure + to hold the original form. - The URI for the Age data type is https://gedcom.io/terms/v7/type-Age. +
+ + Age payloads may also be omitted entirely if no suitable form is known but a + substructure (such as a `PHRASE`) is desired. + +
+ + Versions 5.5 and 5.5.1 allowed a few specific phrases inside `Age` payloads. + Age phrases were moved to the `PHRASE` substructure in 7.0. + +
+ + The URI for the `Age` data type is `https://gedcom.io/terms/v7/type-Age`. + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/type-Date.md b/_pages/tag-def/type-Date.md index 8193585e..8f4960ef 100644 --- a/_pages/tag-def/type-Date.md +++ b/_pages/tag-def/type-Date.md @@ -19,115 +19,121 @@ uri: https://gedcom.io/terms/v7/type-Date specification: - | The date formats defined in this specification include the ability to store - approximate dates, date periods, and dates expressed in different - calendars. + approximate dates, date periods, and dates expressed in different calendars. Technically, there are 3 distinct date data types: - - DateValue is a generic type that can express many kinds of dates. - - DateExact is used for timestamps and other fully-known dates. - - DatePeriod is used to express time intervals that span multiple days. + - `DateValue` is a generic type that can express many kinds of dates. + - `DateExact` is used for timestamps and other fully-known dates. + - `DatePeriod` is used to express time intervals that span multiple days. - DateValue = [ date / DatePeriod / dateRange / dateApprox ] - DateExact = day D month D year ; in Gregorian calendar - DatePeriod = [ %s"TO" D date ] - / %s"FROM" D date [ D %s"TO" D date ] - ; note both DateValue and DatePeriod can be the empty string + ```abnf + DateValue = [ date / DatePeriod / dateRange / dateApprox ] + DateExact = day D month D year ; in Gregorian calendar + DatePeriod = [ %s"TO" D date ] + / %s"FROM" D date [ D %s"TO" D date ] + ; note both DateValue and DatePeriod can be the empty string - date = [calendar D] [[day D] month D] year [D epoch] - dateRange = %s"BET" D date D %s"AND" D date - / %s"AFT" D date - / %s"BEF" D date - dateApprox = (%s"ABT" / %s"CAL" / %s"EST") D date + date = [calendar D] [[day D] month D] year [D epoch] + dateRange = %s"BET" D date D %s"AND" D date + / %s"AFT" D date + / %s"BEF" D date + dateApprox = (%s"ABT" / %s"CAL" / %s"EST") D date - dateRestrict = %s"FROM" / %s"TO" / %s"BET" / %s"AND" / %s"BEF" - / %s"AFT" / %s"ABT" / %s"CAL" / %s"EST" + dateRestrict = %s"FROM" / %s"TO" / %s"BET" / %s"AND" / %s"BEF" + / %s"AFT" / %s"ABT" / %s"CAL" / %s"EST" - calendar = %s"GREGORIAN" / %s"JULIAN" / %s"FRENCH_R" / %s"HEBREW" - / extTag + calendar = %s"GREGORIAN" / %s"JULIAN" / %s"FRENCH_R" / %s"HEBREW" + / extTag - day = Integer - year = Integer - month = stdTag / extTag ; constrained by calendar - epoch = %s"BCE" / extTag ; constrained by calendar + day = Integer + year = Integer + month = stdTag / extTag ; constrained by calendar + epoch = %s"BCE" / extTag ; constrained by calendar + ``` In addition to the constraints above: - - The allowable days, months, years, and epochs are determined by the - calendar. All known calendars restrict day to be between 1 and a - month-specific maximum. The largest known maximum is 36, and most - months in most calendars have a lower maximum. - - No calendar names, months, or epochs match dateRestrict. - - Extension calendars (those with extTag for their calendar) must use - extTag, not stdTag, for months. + - The allowable `day`s, `month`s, `year`s, and `epoch`s are determined by the + `calendar`. All known calendars restrict `day` to be between 1 and a + month-specific maximum. The largest known maximum is 36, and most months in + most calendars have a lower maximum. + - No calendar names, months, or epochs match `dateRestrict`. + - Extension calendars (those with `extTag` for their `calendar`) must use + `extTag`, not `stdTag`, for months. - It is recommended that calendars avoid using a single tag to refer to both - a month and an epoch. + It is recommended that calendars avoid using a single tag to refer to both a + month and an epoch. - An absent calendar is equivalent to the calendar GREGORIAN. + An absent `calendar` is equivalent to the calendar `GREGORIAN`. - The grammar above allows for dates to be preceded by various words. The + The grammar above allows for `date`s to be preceded by various words. The meaning of these words is given as follows: - -------------------------------------------------------------------------- - Production Meaning - ------------- ------------------------------------------------------------ - FROM x Lasted for multiple days, beginning on x. - - TO x Lasted for multiple days, ending on x. - - BET x Exact date unknown, but no earlier than x. - - AND x Exact date unknown, but no later than x. - - BEF x Exact date unknown, but no later than x. - - AFT x Exact date unknown, but no earlier than x. - - ABT x Exact date unknown, but near x. - - CAL x x is calculated from other data. - - EST x Exact date unknown, but near x; and x is calculated from - other data. - -------------------------------------------------------------------------- - - Known calendars and tips for handling dual dating and extension calendars - are given in Appendix A: Calendars and Dates. - - DateValue and DatePeriod payloads may also be the empty string if no - suitable form is known but a substructure (such as a PHRASE or TIME) is + | Production | Meaning | + | :--------- | :----------------------------------------------------------------------- | + | `FROM` *x* | Lasted for multiple days, beginning on *x*. | + | `TO` *x* | Lasted for multiple days, ending on *x*. | + | `BET` *x* | Exact date unknown, but no earlier than *x*. | + | `AND` *x* | Exact date unknown, but no later than *x*. | + | `BEF` *x* | Exact date unknown, but no later than *x*. | + | `AFT` *x* | Exact date unknown, but no earlier than *x*. | + | `ABT` *x* | Exact date unknown, but near *x*. | + | `CAL` *x* | *x* is calculated from other data. | + | `EST` *x* | Exact date unknown, but near *x*; and *x* is calculated from other data. | + + Known calendars and tips for handling dual dating and extension calendars are + given in [Appendix A: Calendars and Dates]. + + `DateValue` and `DatePeriod` payloads may also be the empty string if no + suitable form is known but a substructure (such as a `PHRASE` or `TIME`) is desired. - Versions 5.3 through 5.5.1 allowed phrases inside DateValue payloads. Date - phrases were moved to the PHRASE substructure in version 7.0. A current - limitation, however, is that a phrase in the PHRASE substructure cannot +
+ + Versions 5.3 through 5.5.1 allowed phrases inside `DateValue` payloads. Date + phrases were moved to the `PHRASE` substructure in version 7.0. A current + limitation, however, is that a phrase in the `PHRASE` substructure cannot specify a language, so if a non-default language is needed to correctly interpret the phrase two options exist: - - PHRASE can be used with a documented extension tag for the language, as - discussed in https://gedcom.io/terms/v7/LANG. + - `PHRASE` can be used with a documented extension tag for the language, as + discussed in `https://gedcom.io/terms/v7/LANG`. + + - `<>.SOUR.DATA.TEXT` can be used instead along with a `LANG` + substructure; this loses the connection with the date, but includes the + language with a standard tag. + +
- - <>.SOUR.DATA.TEXT can be used instead along with a LANG - substructure; this loses the connection with the date, but includes the - language with a standard tag. +
As defined by the grammar above, every date must have a year. If no year is known, the entire date may be omitted. +
+ The following is an appropriate way to handle a missing year - 2 DATE - 3 PHRASE 5 January (year unknown) + ```gedcom + 2 DATE + 3 PHRASE 5 January (year unknown) + ``` + +
- The URI for the DateValue data type is - https://gedcom.io/terms/v7/type-Date. +
- The URI for the DateExact data type is - https://gedcom.io/terms/v7/type-Date#exact. + The URI for the `DateValue` data type is + `https://gedcom.io/terms/v7/type-Date`. - The URI for the DatePeriod data type is - https://gedcom.io/terms/v7/type-Date#period. + The URI for the `DateExact` data type is + `https://gedcom.io/terms/v7/type-Date#exact`. + + The URI for the `DatePeriod` data type is + `https://gedcom.io/terms/v7/type-Date#period`. + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/type-Enum.md b/_pages/tag-def/type-Enum.md index 990b5ab7..e7ee01be 100644 --- a/_pages/tag-def/type-Enum.md +++ b/_pages/tag-def/type-Enum.md @@ -18,18 +18,20 @@ uri: https://gedcom.io/terms/v7/type-Enum specification: - | - An enumeration is a selection from a set of options. They are represented - as a string matching the same production as a tag, with the additional - permission that standard enumerations may be integers. + An enumeration is a selection from a set of options. They are represented as a + string matching the same production as a tag, with the additional permission + that standard enumerations may be integers. - stdEnum = stdTag / Integer - Enum = stdEnum / extTag + ```abnf + stdEnum = stdTag / Integer + Enum = stdEnum / extTag + ``` - Each structure type with an enumeration payload also defines specific - payload values it permits. These permitted payloads match production - stdEnum and should each have a defined URI. Payload values that match - production extTag are always permitted in structures with an enumeration - payload and have their URI defined by the schema. + Each structure type with an enumeration payload also defines specific payload + values it permits. These permitted payloads match production `stdEnum` and + should each have a defined URI. Payload values that match production `extTag` + are always permitted in structures with an enumeration payload and have their + URI defined by the schema. Each enumeration value has a distinct meaning as identified by its corresponding URI. @@ -37,26 +39,29 @@ specification: The URI of a given tag in an enumeration payload is determined by the tag itself and by the structure type of the structure it is in the payload of. - The tag HUSB is used in this document to represent two enumeration values. +
+ + The tag `HUSB` is used in this document to represent two enumeration values. Which one is meant can be identified by the structure type it appears in as follows: - ---------------------------------------------------------------------------------- - Containing structure type Enumeration value identified by tag HUSB - -------------------------------------- ------------------------------------------- - https://gedcom.io/terms/v7/FAMC-ADOP https://gedcom.io/terms/v7/enum-ADOP-HUSB + | Containing structure type | Enumeration value identified by tag `HUSB` | + | -------------------------------------- | ------------------------------------------- | + | `https://gedcom.io/terms/v7/FAMC-ADOP` | `https://gedcom.io/terms/v7/enum-ADOP-HUSB` | + | `https://gedcom.io/terms/v7/ROLE` | `https://gedcom.io/terms/v7/enum-HUSB` | - https://gedcom.io/terms/v7/ROLE https://gedcom.io/terms/v7/enum-HUSB - ---------------------------------------------------------------------------------- + An [extension] could also place either of these enumeration values in an + extension structure type; the extension authors should document which one they + permit. - An extension could also place either of these enumeration values in an - extension structure type; the extension authors should document which one - they permit. + The `HUSB` tag is also used to identify two different structure types, + `https://gedcom.io/terms/v7/FAM-HUSB` and `https://gedcom.io/terms/v7/HUSB`. - The HUSB tag is also used to identify two different structure types, - https://gedcom.io/terms/v7/FAM-HUSB and https://gedcom.io/terms/v7/HUSB. +
- The URI for the Enum data type is https://gedcom.io/terms/v7/type-Enum. + The URI for the `Enum` data type is `https://gedcom.io/terms/v7/type-Enum`. + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/type-List.md b/_pages/tag-def/type-List.md index 2262d98f..046a0f80 100644 --- a/_pages/tag-def/type-List.md +++ b/_pages/tag-def/type-List.md @@ -19,35 +19,42 @@ uri: https://gedcom.io/terms/v7/type-List specification: - | A list is a meta-syntax representing a sequence of values with another data - type. Two list data types are used in this document: List:Text and - List:Enum. Lists are serialized in a comma-separated form, delimited by a - comma (U+002C ,) and any number of spaces (U+0020) between each item. It is - recommended that a comma-space pair (U+002C U+0020) be used as the - delimiter. + type. Two list data types are used in this document: List:Text and List:Enum. + Lists are serialized in a comma-separated form, delimited by a comma (U+002C + `,`) and any number of spaces (U+0020) between each item. It is recommended + that a comma-space pair (U+002C U+0020) be used as the delimiter. - list = listItem *(listDelim listItem) - listItem = [ nocommasp / nocommasp *nocomma nocommasp ] - listDelim = *D "," *D - nocomma = %x09-2B / %x2D-10FFFF - nocommasp = %x09-1D / %x21-2B / %x2D-10FFFF + ```abnf + list = listItem *(listDelim listItem) + listItem = [ nocommasp / nocommasp *nocomma nocommasp ] + listDelim = *D "," *D + nocomma = %x09-2B / %x2D-10FFFF + nocommasp = %x09-1D / %x21-2B / %x2D-10FFFF - List-Text = list - List-Enum = Enum *(listDelim Enum) + List-Text = list + List-Enum = Enum *(listDelim Enum) + ``` - If valid for the underlying type, empty strings may be included in a list - by having no characters between delimiters. + If valid for the underlying type, empty strings may be included in a list by + having no characters between delimiters. - A List:Text with value “, , one, more,” has 5 Text-type values: 2 empty - strings, the string “one”, the string “more”, and 1 more empty string. +
- There is no escaping mechanism to allow lists of entries that begin or end - with spaces or that contain comma characters. + A `List:Text` with value "`, , one, more,`" has 5 `Text`-type values: 2 empty + strings, the string "`one`", the string "`more`", and 1 more empty string. - The URI for the List:Text data type is - https://gedcom.io/terms/v7/type-List#Text. +
- The URI for the List:Enum data type is - https://gedcom.io/terms/v7/type-List#Enum. + There is no escaping mechanism to allow lists of entries that begin or end with + spaces or that contain comma characters. + + The URI for the `List:Text` data type is + `https://gedcom.io/terms/v7/type-List#Text`. + + The URI for the `List:Enum` data type is + `https://gedcom.io/terms/v7/type-List#Enum`. + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/type-Name.md b/_pages/tag-def/type-Name.md index 24e46bb6..ab64da73 100644 --- a/_pages/tag-def/type-Name.md +++ b/_pages/tag-def/type-Name.md @@ -18,25 +18,28 @@ uri: https://gedcom.io/terms/v7/type-Name specification: - | - A personal name is mostly free-text. It should be the name as written in - the culture of the individual and should not contain line breaks, repeated - spaces, or characters not part of the written form of a name (except for - U+002F as explained below). + A personal name is mostly free-text. It should be the name as written in the + culture of the individual and should not contain line breaks, repeated spaces, + or characters not part of the written form of a name (except for U+002F as + explained below). - PersonalName = nameStr - / [nameStr] "/" [nameStr] "/" [nameStr] + ```abnf + PersonalName = nameStr + / [nameStr] "/" [nameStr] "/" [nameStr] - nameChar = %x20-2E / %x30-10FFFF ; any but '/' and '\t' - nameStr = 1*nameChar + nameChar = %x20-2E / %x30-10FFFF ; any but '/' and '\t' + nameStr = 1*nameChar + ``` - The character U+002F (/, slash or solidus) has special meaning in a - personal name, being used to delimit the portion of the name that most - closely matches the concept of a surname, family name, or the like. This - specification does not provide any standard way of representing names that - contain U+002F. + The character U+002F (`/`, slash or solidus) has special meaning in a personal + name, being used to delimit the portion of the name that most closely matches + the concept of a surname, family name, or the like. This specification does not + provide any standard way of representing names that contain U+002F. - The URI for the PersonalName data type is - https://gedcom.io/terms/v7/type-Name. + The URI for the `PersonalName` data type is + `https://gedcom.io/terms/v7/type-Name`. + +contact: "https://gedcom.io/community/" ... ``` diff --git a/_pages/tag-def/type-Time.md b/_pages/tag-def/type-Time.md index 92d554e3..85487a3e 100644 --- a/_pages/tag-def/type-Time.md +++ b/_pages/tag-def/type-Time.md @@ -18,24 +18,32 @@ uri: https://gedcom.io/terms/v7/type-Time specification: - | - Time is represented on a 24-hour clock (for example, 23:00 rather than - 11:00 PM). It may be represented either in event-local time or in - Coordinated Universal Time (UTC). UTC is indicated by including a Z - (U+005A) after the time value; event-local time is indicated by its - absence. When a time is used together with a DateExact, it is recommended - that UTC time be used rather than event-local time. + Time is represented on a 24-hour clock (for example, 23:00 rather than 11:00 + PM). It may be represented either in event-local time or in Coordinated + Universal Time (UTC). UTC is indicated by including a `Z` (U+005A) after the + time value; event-local time is indicated by its absence. When a time is used + together with a `DateExact`, it is recommended that UTC time be used rather + than event-local time. - Time = hour ":" minute [":" second ["." fraction]] [%s"Z"] + ```abnf + Time = hour ":" minute [":" second ["." fraction]] [%s"Z"] - hour = digit / ("0" / "1") digit / "2" ("0" / "1" / "2" / "3") - minute = ("0" / "1" / "2" / "3" / "4" / "5") digit - second = ("0" / "1" / "2" / "3" / "4" / "5") digit - fraction = 1*digit + hour = DIGIT / ("0" / "1") DIGIT / "2" ("0" / "1" / "2" / "3") + minute = ("0" / "1" / "2" / "3" / "4" / "5") DIGIT + second = ("0" / "1" / "2" / "3" / "4" / "5") DIGIT + fraction = 1*DIGIT + ``` - The above grammar prohibits end-of-day instant 24:00:00 and leap-seconds. - It allows both 02:50 and 2:50 as the same time. +
- The URI for the Time data type is https://gedcom.io/terms/v7/type-Time. + The above grammar prohibits end-of-day instant `24:00:00` and leap-seconds. It + allows both `02:50` and `2:50` as the same time. + +
+ + The URI for the `Time` data type is `https://gedcom.io/terms/v7/type-Time`. + +contact: "https://gedcom.io/community/" ... ``` diff --git a/specifications/FamilySearchGEDCOMv7.html b/specifications/FamilySearchGEDCOMv7.html index f3ff5dc6..5149d556 100644 --- a/specifications/FamilySearchGEDCOMv7.html +++ b/specifications/FamilySearchGEDCOMv7.html @@ -3,7 +3,7 @@ - + The FamilySearch GEDCOM Specification