diff --git a/build/README.md b/build/README.md index 82d44174..9dfe3f1e 100644 --- a/build/README.md +++ b/build/README.md @@ -9,6 +9,7 @@ This directory is used to convert the `specifications/gedcom.md` source file int - [weasyprint](https://weasyprint.org) installed by running `python3 -mpip install --user --upgrade weasyprint` - Note: version 52.5 was notably faster than later versions; `python3 -mpip install --user weasyprint==52.5` will install that version instead of the latest version. + - [mdformat_gfm](https://pypi.org/project/mdformat-gfm/) installed by running `python3 -mpip install --user --upgrade mdformat_gfm` - [git](https://git-scm.com/) - `make`-compatible executable diff --git a/build/uri-def.py b/build/uri-def.py index b4336448..847cf685 100644 --- a/build/uri-def.py +++ b/build/uri-def.py @@ -302,12 +302,41 @@ def find_enumsets(txt): return res def tidy_markdown(md, indent, width=79): - """Run markdown through pandoc to remove markup and wrap columns""" + """ + The markdown files in the specification directory use the following Markdown dialect: + + Part of GFM: + + - setext headers with classes like `{.unnumbered}`, unlisting marks like `{-}`, and anchors like `{#container}` + - language-specific code blocks both \`\`\`gedcom and \`\`\` {.gedstruct .long} headers + - markdown inside HTML between lines `
` and `
` (only inside lists) and between definition list tags `
`, `
`, and `
` (only in acknowledgements) + - code blocks with no leading blank line + - tables with `|---|:--|` format + - tables with `--- | --- | ---` format + + Not part of GFM: + + - YAML front matter + - divs with `:::class` headers and `:::` footers + - automatic links with `[name of section to link to]` + - inline code with class `1 NO MARR`{.gedcom} (used only once) + + pip install mdformat-gfm + """ global prefixes for k,v in prefixes.items(): md = re.sub(r'\b'+k+':', v, md) - out = run(['pandoc','-t','plain','--columns='+str(width-indent)], input=md.encode('utf-8'), capture_output=True) - return out.stdout.rstrip().decode('utf-8').replace('\n','\n'+' '*indent) + + # for now ignoring YAML frontmatter + md = re.sub(r':::(\S+)', r'
\n', md) # convert ::: divs to
s + md = re.sub(r':::', '\n
', md) # convert ::: divs to
s + md = re.sub(r'\]\([^\)]*\)({[^}]*})?', ']', md) # remove links + md = re.sub(r'`{\.\S+\}', '`', md) # remove inline code classes + + import mdformat + out = mdformat.text(md, extensions={"gfm"}, options={"number":True, "wrap":width}) + + return out.rstrip().replace('\n','\n'+' '*indent).replace('\[','[').replace('\]',']') def yaml_str_helper(pfx, md, width=79): txt = tidy_markdown(md, len(pfx), width) diff --git a/extracted-files/grammar.gedstruct b/extracted-files/grammar.gedstruct index ee931f67..7d0309c9 100644 --- a/extracted-files/grammar.gedstruct +++ b/extracted-files/grammar.gedstruct @@ -109,12 +109,12 @@ n @XREF:INDI@ INDI {1:1} g7:record-INDI MULTIMEDIA_RECORD := n @XREF:OBJE@ OBJE {1:1} g7:record-OBJE +1 RESN {0:1} g7:RESN - +1 FILE {1:M} g7:FILE + +1 FILE {1:M} g7:FILE +2 FORM {1:1} g7:FORM +3 MEDI {0:1} g7:MEDI +4 PHRASE {0:1} g7:PHRASE +2 TITL {0:1} g7:TITL - +2 TRAN {0:M} g7:FILE-TRAN + +2 TRAN {0:M} g7:FILE-TRAN +3 FORM {1:1} g7:FORM +1 <> {0:M} +1 <> {0:M} diff --git a/extracted-files/payloads.tsv b/extracted-files/payloads.tsv index 270a695d..f9224ee4 100644 --- a/extracted-files/payloads.tsv +++ b/extracted-files/payloads.tsv @@ -71,7 +71,7 @@ https://gedcom.io/terms/v7/ADOP-FAMC @@ https://gedcom.io/terms/v7/FAMS @@ https://gedcom.io/terms/v7/FAX http://www.w3.org/2001/XMLSchema#string https://gedcom.io/terms/v7/FCOM Y| -https://gedcom.io/terms/v7/FILE http://www.w3.org/2001/XMLSchema#string +https://gedcom.io/terms/v7/FILE https://gedcom.io/terms/v7/type-FilePath https://gedcom.io/terms/v7/FORM http://www.w3.org/ns/dcat#mediaType https://gedcom.io/terms/v7/PLAC-FORM https://gedcom.io/terms/v7/type-List#Text https://gedcom.io/terms/v7/HEAD-PLAC-FORM https://gedcom.io/terms/v7/type-List#Text @@ -165,7 +165,7 @@ https://gedcom.io/terms/v7/TOP http://www.w3.org/2001/XMLSchema#nonNegativeInteg https://gedcom.io/terms/v7/NAME-TRAN https://gedcom.io/terms/v7/type-Name https://gedcom.io/terms/v7/PLAC-TRAN https://gedcom.io/terms/v7/type-List#Text https://gedcom.io/terms/v7/NOTE-TRAN http://www.w3.org/2001/XMLSchema#string -https://gedcom.io/terms/v7/FILE-TRAN http://www.w3.org/2001/XMLSchema#string +https://gedcom.io/terms/v7/FILE-TRAN https://gedcom.io/terms/v7/type-FilePath https://gedcom.io/terms/v7/TRLR https://gedcom.io/terms/v7/TYPE http://www.w3.org/2001/XMLSchema#string https://gedcom.io/terms/v7/NAME-TYPE https://gedcom.io/terms/v7/type-Enum diff --git a/extracted-files/tags/ADDR b/extracted-files/tags/ADDR index 59071868..eec22d02 100644 --- a/extracted-files/tags/ADDR +++ b/extracted-files/tags/ADDR @@ -10,31 +10,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. - | 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' diff --git a/extracted-files/tags/ADOP b/extracted-files/tags/ADOP index 5fc737c7..99c0e227 100644 --- a/extracted-files/tags/ADOP +++ b/extracted-files/tags/ADOP @@ -10,10 +10,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' diff --git a/extracted-files/tags/ADOP-FAMC b/extracted-files/tags/ADOP-FAMC index 83ce0b77..69cd5f02 100644 --- a/extracted-files/tags/ADOP-FAMC +++ b/extracted-files/tags/ADOP-FAMC @@ -13,11 +13,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' diff --git a/extracted-files/tags/ADR1 b/extracted-files/tags/ADR1 index f495bbb9..d5e60987 100644 --- a/extracted-files/tags/ADR1 +++ b/extracted-files/tags/ADR1 @@ -11,11 +11,15 @@ 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. - 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. + +
label: 'Address Line 1' diff --git a/extracted-files/tags/ADR2 b/extracted-files/tags/ADR2 index 1f13af74..e6c9ca29 100644 --- a/extracted-files/tags/ADR2 +++ b/extracted-files/tags/ADR2 @@ -11,11 +11,15 @@ 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. - 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. + +
label: 'Address Line 2' diff --git a/extracted-files/tags/ADR3 b/extracted-files/tags/ADR3 index 9cc9b309..79cb94cb 100644 --- a/extracted-files/tags/ADR3 +++ b/extracted-files/tags/ADR3 @@ -11,11 +11,15 @@ 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. - 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. + +
label: 'Address Line 3' diff --git a/extracted-files/tags/AGE b/extracted-files/tags/AGE index f4c17971..7daffa5b 100644 --- a/extracted-files/tags/AGE +++ b/extracted-files/tags/AGE @@ -10,8 +10,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' diff --git a/extracted-files/tags/AGNC b/extracted-files/tags/AGNC index a6030b0f..22451f6c 100644 --- a/extracted-files/tags/AGNC +++ b/extracted-files/tags/AGNC @@ -10,11 +10,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' diff --git a/extracted-files/tags/ALIA b/extracted-files/tags/ALIA index 2bbe3d92..4efcb720 100644 --- a/extracted-files/tags/ALIA +++ b/extracted-files/tags/ALIA @@ -12,15 +12,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' diff --git a/extracted-files/tags/ANCI b/extracted-files/tags/ANCI index f8511995..8e39bbe9 100644 --- a/extracted-files/tags/ANCI +++ b/extracted-files/tags/ANCI @@ -10,8 +10,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' diff --git a/extracted-files/tags/ANUL b/extracted-files/tags/ANUL index e62478fe..a69daf96 100644 --- a/extracted-files/tags/ANUL +++ b/extracted-files/tags/ANUL @@ -10,7 +10,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). diff --git a/extracted-files/tags/ASSO b/extracted-files/tags/ASSO index 92a7cd8c..99fe9bba 100644 --- a/extracted-files/tags/ASSO +++ b/extracted-files/tags/ASSO @@ -10,26 +10,32 @@ 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. - | - 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' diff --git a/extracted-files/tags/AUTH b/extracted-files/tags/AUTH index 448b1726..a68de77e 100644 --- a/extracted-files/tags/AUTH +++ b/extracted-files/tags/AUTH @@ -11,9 +11,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' diff --git a/extracted-files/tags/BAPL b/extracted-files/tags/BAPL index 3a6466f3..ddf20bbc 100644 --- a/extracted-files/tags/BAPL +++ b/extracted-files/tags/BAPL @@ -10,10 +10,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' diff --git a/extracted-files/tags/BAPM b/extracted-files/tags/BAPM index 53716725..31d0a514 100644 --- a/extracted-files/tags/BAPM +++ b/extracted-files/tags/BAPM @@ -10,9 +10,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' diff --git a/extracted-files/tags/BARM b/extracted-files/tags/BARM index dddee99a..e7765c11 100644 --- a/extracted-files/tags/BARM +++ b/extracted-files/tags/BARM @@ -10,7 +10,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. diff --git a/extracted-files/tags/BASM b/extracted-files/tags/BASM index 19a6d382..a2b9200b 100644 --- a/extracted-files/tags/BASM +++ b/extracted-files/tags/BASM @@ -10,10 +10,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' diff --git a/extracted-files/tags/BIRT b/extracted-files/tags/BIRT index 4555272a..a3cd24b0 100644 --- a/extracted-files/tags/BIRT +++ b/extracted-files/tags/BIRT @@ -10,7 +10,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. diff --git a/extracted-files/tags/BLES b/extracted-files/tags/BLES index a8d42505..50a956a5 100644 --- a/extracted-files/tags/BLES +++ b/extracted-files/tags/BLES @@ -10,7 +10,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. diff --git a/extracted-files/tags/BURI b/extracted-files/tags/BURI index cba28756..ce193931 100644 --- a/extracted-files/tags/BURI +++ b/extracted-files/tags/BURI @@ -11,14 +11,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. diff --git a/extracted-files/tags/CALN b/extracted-files/tags/CALN index 54ecff96..b88c5469 100644 --- a/extracted-files/tags/CALN +++ b/extracted-files/tags/CALN @@ -10,9 +10,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' diff --git a/extracted-files/tags/CAST b/extracted-files/tags/CAST index 9e3f611b..a7f7acf4 100644 --- a/extracted-files/tags/CAST +++ b/extracted-files/tags/CAST @@ -10,11 +10,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' diff --git a/extracted-files/tags/CHAN b/extracted-files/tags/CHAN index ed0183c5..d3d69f1e 100644 --- a/extracted-files/tags/CHAN +++ b/extracted-files/tags/CHAN @@ -11,13 +11,13 @@ 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. - | - 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' diff --git a/extracted-files/tags/CHIL b/extracted-files/tags/CHIL index e9bf0278..97a65f57 100644 --- a/extracted-files/tags/CHIL +++ b/extracted-files/tags/CHIL @@ -10,8 +10,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' diff --git a/extracted-files/tags/CHR b/extracted-files/tags/CHR index 3e1a2dd8..9d3275e1 100644 --- a/extracted-files/tags/CHR +++ b/extracted-files/tags/CHR @@ -10,7 +10,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. diff --git a/extracted-files/tags/CHRA b/extracted-files/tags/CHRA index a601843a..3c609b2f 100644 --- a/extracted-files/tags/CHRA +++ b/extracted-files/tags/CHRA @@ -10,7 +10,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. diff --git a/extracted-files/tags/CITY b/extracted-files/tags/CITY index f63edd64..4b3e241c 100644 --- a/extracted-files/tags/CITY +++ b/extracted-files/tags/CITY @@ -10,7 +10,7 @@ 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. label: 'City' diff --git a/extracted-files/tags/CONF b/extracted-files/tags/CONF index 0a557d66..e255f82a 100644 --- a/extracted-files/tags/CONF +++ b/extracted-files/tags/CONF @@ -10,7 +10,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. diff --git a/extracted-files/tags/CONL b/extracted-files/tags/CONL index 842e978e..fd6e3540 100644 --- a/extracted-files/tags/CONL +++ b/extracted-files/tags/CONL @@ -10,10 +10,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' diff --git a/extracted-files/tags/CONT b/extracted-files/tags/CONT index 1505376e..6697f51b 100644 --- a/extracted-files/tags/CONT +++ b/extracted-files/tags/CONT @@ -10,9 +10,8 @@ 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. label: 'Continued' diff --git a/extracted-files/tags/COPR b/extracted-files/tags/COPR index e2e41a16..8a4ec02d 100644 --- a/extracted-files/tags/COPR +++ b/extracted-files/tags/COPR @@ -10,8 +10,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' diff --git a/extracted-files/tags/CORP b/extracted-files/tags/CORP index 0efb5f5a..2b82cbba 100644 --- a/extracted-files/tags/CORP +++ b/extracted-files/tags/CORP @@ -10,8 +10,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' diff --git a/extracted-files/tags/CREA b/extracted-files/tags/CREA index ce9f2726..e6fed26a 100644 --- a/extracted-files/tags/CREA +++ b/extracted-files/tags/CREA @@ -11,10 +11,9 @@ 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. + - 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' diff --git a/extracted-files/tags/CREM b/extracted-files/tags/CREM index d7510843..69ae4cad 100644 --- a/extracted-files/tags/CREM +++ b/extracted-files/tags/CREM @@ -10,7 +10,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. diff --git a/extracted-files/tags/CROP b/extracted-files/tags/CROP index 40eeaf5b..f1d47ef8 100644 --- a/extracted-files/tags/CROP +++ b/extracted-files/tags/CROP @@ -11,27 +11,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' diff --git a/extracted-files/tags/CTRY b/extracted-files/tags/CTRY index ba9d493b..78b51e1f 100644 --- a/extracted-files/tags/CTRY +++ b/extracted-files/tags/CTRY @@ -11,7 +11,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. label: 'Country' diff --git a/extracted-files/tags/DATA b/extracted-files/tags/DATA index ab5e399e..e80fea8e 100644 --- a/extracted-files/tags/DATA +++ b/extracted-files/tags/DATA @@ -10,10 +10,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' diff --git a/extracted-files/tags/DATA-EVEN b/extracted-files/tags/DATA-EVEN index c020c271..c38a6dc4 100644 --- a/extracted-files/tags/DATA-EVEN +++ b/extracted-files/tags/DATA-EVEN @@ -11,10 +11,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' diff --git a/extracted-files/tags/DATA-EVEN-DATE b/extracted-files/tags/DATA-EVEN-DATE index c44ce9fa..ce73e48b 100644 --- a/extracted-files/tags/DATA-EVEN-DATE +++ b/extracted-files/tags/DATA-EVEN-DATE @@ -10,7 +10,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' diff --git a/extracted-files/tags/DATE b/extracted-files/tags/DATE index d4f1b45d..dd114fa4 100644 --- a/extracted-files/tags/DATE +++ b/extracted-files/tags/DATE @@ -12,16 +12,20 @@ specification: - Date - | The principal date of the subject of the superstructure. The payload is a - DateValue. + `DateValue`. - See DATE_VALUE for more. + See `DATE_VALUE` for more. - | - 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' diff --git a/extracted-files/tags/DATE-exact b/extracted-files/tags/DATE-exact index 00cfb1f7..cbfcd07b 100644 --- a/extracted-files/tags/DATE-exact +++ b/extracted-files/tags/DATE-exact @@ -11,7 +11,7 @@ standard tag: DATE specification: - Date - The principal date of the subject of the superstructure. The payload is a - DateExact. + `DateExact`. label: 'Date' diff --git a/extracted-files/tags/DEAT b/extracted-files/tags/DEAT index abca8dc2..8262217f 100644 --- a/extracted-files/tags/DEAT +++ b/extracted-files/tags/DEAT @@ -10,7 +10,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. diff --git a/extracted-files/tags/DESI b/extracted-files/tags/DESI index ef20d28a..a13e779f 100644 --- a/extracted-files/tags/DESI +++ b/extracted-files/tags/DESI @@ -10,8 +10,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' diff --git a/extracted-files/tags/DEST b/extracted-files/tags/DEST index 86d9c9a4..13b12e47 100644 --- a/extracted-files/tags/DEST +++ b/extracted-files/tags/DEST @@ -11,7 +11,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' diff --git a/extracted-files/tags/DIV b/extracted-files/tags/DIV index 8d569a23..7be4efae 100644 --- a/extracted-files/tags/DIV +++ b/extracted-files/tags/DIV @@ -10,7 +10,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. diff --git a/extracted-files/tags/DIVF b/extracted-files/tags/DIVF index 8b3e31ac..efeae320 100644 --- a/extracted-files/tags/DIVF +++ b/extracted-files/tags/DIVF @@ -10,7 +10,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. diff --git a/extracted-files/tags/DSCR b/extracted-files/tags/DSCR index 65007622..9857f289 100644 --- a/extracted-files/tags/DSCR +++ b/extracted-files/tags/DSCR @@ -10,7 +10,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. diff --git a/extracted-files/tags/EDUC b/extracted-files/tags/EDUC index 90959662..da3e8c38 100644 --- a/extracted-files/tags/EDUC +++ b/extracted-files/tags/EDUC @@ -10,7 +10,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. diff --git a/extracted-files/tags/EMAIL b/extracted-files/tags/EMAIL index aaf78aff..1e244290 100644 --- a/extracted-files/tags/EMAIL +++ b/extracted-files/tags/EMAIL @@ -11,15 +11,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' diff --git a/extracted-files/tags/EMIG b/extracted-files/tags/EMIG index af1dd620..4b8b2a76 100644 --- a/extracted-files/tags/EMIG +++ b/extracted-files/tags/EMIG @@ -10,9 +10,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' diff --git a/extracted-files/tags/ENDL b/extracted-files/tags/ENDL index 41bc2f04..bdcce125 100644 --- a/extracted-files/tags/ENDL +++ b/extracted-files/tags/ENDL @@ -10,11 +10,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' diff --git a/extracted-files/tags/ENGA b/extracted-files/tags/ENGA index 8ade6ef5..1ae95341 100644 --- a/extracted-files/tags/ENGA +++ b/extracted-files/tags/ENGA @@ -10,7 +10,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. diff --git a/extracted-files/tags/EXID b/extracted-files/tags/EXID index 0f1c230e..a6aa44bf 100644 --- a/extracted-files/tags/EXID +++ b/extracted-files/tags/EXID @@ -12,17 +12,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. - 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' diff --git a/extracted-files/tags/EXID-TYPE b/extracted-files/tags/EXID-TYPE index e56c6372..79b50158 100644 --- a/extracted-files/tags/EXID-TYPE +++ b/extracted-files/tags/EXID-TYPE @@ -11,31 +11,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' diff --git a/extracted-files/tags/FAM-CENS b/extracted-files/tags/FAM-CENS index 79f8973f..9dbfcfd7 100644 --- a/extracted-files/tags/FAM-CENS +++ b/extracted-files/tags/FAM-CENS @@ -10,10 +10,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' diff --git a/extracted-files/tags/FAM-EVEN b/extracted-files/tags/FAM-EVEN index 1f600b1f..5978a008 100644 --- a/extracted-files/tags/FAM-EVEN +++ b/extracted-files/tags/FAM-EVEN @@ -10,7 +10,7 @@ standard tag: EVEN specification: - Event - - See https://gedcom.io/terms/v7/INDI-EVEN. + - See `https://gedcom.io/terms/v7/INDI-EVEN`. label: 'Event' diff --git a/extracted-files/tags/FAM-FACT b/extracted-files/tags/FAM-FACT index 96d52381..19835bb5 100644 --- a/extracted-files/tags/FAM-FACT +++ b/extracted-files/tags/FAM-FACT @@ -10,7 +10,7 @@ standard tag: FACT specification: - Fact - - See https://gedcom.io/terms/v7/INDI-FACT. + - See `https://gedcom.io/terms/v7/INDI-FACT`. label: 'Fact' diff --git a/extracted-files/tags/FAM-HUSB b/extracted-files/tags/FAM-HUSB index f808daed..9d9bf07e 100644 --- a/extracted-files/tags/FAM-HUSB +++ b/extracted-files/tags/FAM-HUSB @@ -10,7 +10,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. label: 'Husband' diff --git a/extracted-files/tags/FAM-NCHI b/extracted-files/tags/FAM-NCHI index 24a2c0ff..1d9f5cc6 100644 --- a/extracted-files/tags/FAM-NCHI +++ b/extracted-files/tags/FAM-NCHI @@ -10,7 +10,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. diff --git a/extracted-files/tags/FAM-RESI b/extracted-files/tags/FAM-RESI index f20a926c..053daeb3 100644 --- a/extracted-files/tags/FAM-RESI +++ b/extracted-files/tags/FAM-RESI @@ -11,10 +11,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. diff --git a/extracted-files/tags/FAM-WIFE b/extracted-files/tags/FAM-WIFE index 35ea8ad6..e1d09666 100644 --- a/extracted-files/tags/FAM-WIFE +++ b/extracted-files/tags/FAM-WIFE @@ -10,7 +10,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. label: 'Wife' diff --git a/extracted-files/tags/FAMC-ADOP b/extracted-files/tags/FAMC-ADOP index d3aad54f..15251ecd 100644 --- a/extracted-files/tags/FAMC-ADOP +++ b/extracted-files/tags/FAMC-ADOP @@ -10,7 +10,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' diff --git a/extracted-files/tags/FAMC-STAT b/extracted-files/tags/FAMC-STAT index c6fa6b02..c9efec79 100644 --- a/extracted-files/tags/FAMC-STAT +++ b/extracted-files/tags/FAMC-STAT @@ -10,8 +10,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' diff --git a/extracted-files/tags/FAMS b/extracted-files/tags/FAMS index dad09eec..189e0f2b 100644 --- a/extracted-files/tags/FAMS +++ b/extracted-files/tags/FAMS @@ -10,7 +10,7 @@ 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 `FAM` for more. label: 'Family spouse' diff --git a/extracted-files/tags/FAX b/extracted-files/tags/FAX index ae5fbda2..bfc2d135 100644 --- a/extracted-files/tags/FAX +++ b/extracted-files/tags/FAX @@ -10,8 +10,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 + more. label: 'Facsimile' diff --git a/extracted-files/tags/FCOM b/extracted-files/tags/FCOM index 65f7b027..d6f3690d 100644 --- a/extracted-files/tags/FCOM +++ b/extracted-files/tags/FCOM @@ -10,9 +10,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' diff --git a/extracted-files/tags/FILE b/extracted-files/tags/FILE index f25bac16..372a5d39 100644 --- a/extracted-files/tags/FILE +++ b/extracted-files/tags/FILE @@ -10,52 +10,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}" diff --git a/extracted-files/tags/FILE-TRAN b/extracted-files/tags/FILE-TRAN index 855fd3de..ad267770 100644 --- a/extracted-files/tags/FILE-TRAN +++ b/extracted-files/tags/FILE-TRAN @@ -11,48 +11,54 @@ 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}" diff --git a/extracted-files/tags/FORM b/extracted-files/tags/FORM index 93925e00..fc6d4875 100644 --- a/extracted-files/tags/FORM +++ b/extracted-files/tags/FORM @@ -10,7 +10,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' diff --git a/extracted-files/tags/GEDC b/extracted-files/tags/GEDC index 36508117..82739146 100644 --- a/extracted-files/tags/GEDC +++ b/extracted-files/tags/GEDC @@ -13,9 +13,8 @@ specification: - | A container for information about the entire document. - It is recommended that applications write GEDC with its required - substructure https://gedcom.io/terms/v7/GEDC-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' diff --git a/extracted-files/tags/GEDC-VERS b/extracted-files/tags/GEDC-VERS index c0fd8560..3b0b06e1 100644 --- a/extracted-files/tags/GEDC-VERS +++ b/extracted-files/tags/GEDC-VERS @@ -10,9 +10,9 @@ 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 + "`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. label: 'Version' diff --git a/extracted-files/tags/GRAD b/extracted-files/tags/GRAD index ced5c02c..5561d1b5 100644 --- a/extracted-files/tags/GRAD +++ b/extracted-files/tags/GRAD @@ -10,7 +10,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. diff --git a/extracted-files/tags/HEAD b/extracted-files/tags/HEAD index 4f0005fa..91c18ae8 100644 --- a/extracted-files/tags/HEAD +++ b/extracted-files/tags/HEAD @@ -10,20 +10,20 @@ 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. - | - 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. + - `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' diff --git a/extracted-files/tags/HEAD-DATE b/extracted-files/tags/HEAD-DATE index 599e029d..212a7b05 100644 --- a/extracted-files/tags/HEAD-DATE +++ b/extracted-files/tags/HEAD-DATE @@ -10,7 +10,7 @@ standard tag: DATE specification: - Date - - The DateExact that this document was created. + - The `DateExact` that this document was created. label: 'Date' diff --git a/extracted-files/tags/HEAD-LANG b/extracted-files/tags/HEAD-LANG index e6a6540f..eddaf469 100644 --- a/extracted-files/tags/HEAD-LANG +++ b/extracted-files/tags/HEAD-LANG @@ -11,25 +11,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' diff --git a/extracted-files/tags/HEAD-PLAC b/extracted-files/tags/HEAD-PLAC index b3be0440..0fd5f01e 100644 --- a/extracted-files/tags/HEAD-PLAC +++ b/extracted-files/tags/HEAD-PLAC @@ -10,7 +10,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' diff --git a/extracted-files/tags/HEAD-PLAC-FORM b/extracted-files/tags/HEAD-PLAC-FORM index ec125260..f07157b9 100644 --- a/extracted-files/tags/HEAD-PLAC-FORM +++ b/extracted-files/tags/HEAD-PLAC-FORM @@ -10,7 +10,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' diff --git a/extracted-files/tags/HEAD-SOUR b/extracted-files/tags/HEAD-SOUR index b07af0f3..c6cf055c 100644 --- a/extracted-files/tags/HEAD-SOUR +++ b/extracted-files/tags/HEAD-SOUR @@ -10,10 +10,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' diff --git a/extracted-files/tags/HEAD-SOUR-DATA b/extracted-files/tags/HEAD-SOUR-DATA index 3b6726c6..0486cabe 100644 --- a/extracted-files/tags/HEAD-SOUR-DATA +++ b/extracted-files/tags/HEAD-SOUR-DATA @@ -10,9 +10,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' diff --git a/extracted-files/tags/HEIGHT b/extracted-files/tags/HEIGHT index 3b32258a..e1591584 100644 --- a/extracted-files/tags/HEIGHT +++ b/extracted-files/tags/HEIGHT @@ -11,13 +11,23 @@ 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. - 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' diff --git a/extracted-files/tags/HUSB b/extracted-files/tags/HUSB index 1f9978ce..3f323dde 100644 --- a/extracted-files/tags/HUSB +++ b/extracted-files/tags/HUSB @@ -11,7 +11,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' diff --git a/extracted-files/tags/IDNO b/extracted-files/tags/IDNO index 5d0910ad..2c35861f 100644 --- a/extracted-files/tags/IDNO +++ b/extracted-files/tags/IDNO @@ -10,11 +10,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' diff --git a/extracted-files/tags/IMMI b/extracted-files/tags/IMMI index c93c1e42..a7a881c6 100644 --- a/extracted-files/tags/IMMI +++ b/extracted-files/tags/IMMI @@ -10,7 +10,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. diff --git a/extracted-files/tags/INDI-CENS b/extracted-files/tags/INDI-CENS index 02ca034c..13b9ce58 100644 --- a/extracted-files/tags/INDI-CENS +++ b/extracted-files/tags/INDI-CENS @@ -10,10 +10,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' diff --git a/extracted-files/tags/INDI-EVEN b/extracted-files/tags/INDI-EVEN index c9d0050c..b779cb72 100644 --- a/extracted-files/tags/INDI-EVEN +++ b/extracted-files/tags/INDI-EVEN @@ -12,20 +12,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' diff --git a/extracted-files/tags/INDI-FACT b/extracted-files/tags/INDI-FACT index 097700dd..6f3a47fe 100644 --- a/extracted-files/tags/INDI-FACT +++ b/extracted-files/tags/INDI-FACT @@ -12,17 +12,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' diff --git a/extracted-files/tags/INDI-FAMC b/extracted-files/tags/INDI-FAMC index 64d239ba..4894c22e 100644 --- a/extracted-files/tags/INDI-FAMC +++ b/extracted-files/tags/INDI-FAMC @@ -10,9 +10,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 + `STAT` substructure to show individuals who are not children of the family. See + `FAM` and `FAMC`.`STAT` for more. label: 'Family child' diff --git a/extracted-files/tags/INDI-NAME b/extracted-files/tags/INDI-NAME index 1de4f927..b2af95c3 100644 --- a/extracted-files/tags/INDI-NAME +++ b/extracted-files/tags/INDI-NAME @@ -10,34 +10,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. - 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' diff --git a/extracted-files/tags/INDI-NCHI b/extracted-files/tags/INDI-NCHI index 9c428729..ac841731 100644 --- a/extracted-files/tags/INDI-NCHI +++ b/extracted-files/tags/INDI-NCHI @@ -10,7 +10,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). diff --git a/extracted-files/tags/INDI-RELI b/extracted-files/tags/INDI-RELI index 99602db4..aa7ec256 100644 --- a/extracted-files/tags/INDI-RELI +++ b/extracted-files/tags/INDI-RELI @@ -10,7 +10,7 @@ standard tag: RELI specification: - Religion - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. label: 'Religion' diff --git a/extracted-files/tags/INDI-RESI b/extracted-files/tags/INDI-RESI index 44ee2742..40b16406 100644 --- a/extracted-files/tags/INDI-RESI +++ b/extracted-files/tags/INDI-RESI @@ -11,22 +11,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. diff --git a/extracted-files/tags/INDI-TITL b/extracted-files/tags/INDI-TITL index 752486d2..5b448aa3 100644 --- a/extracted-files/tags/INDI-TITL +++ b/extracted-files/tags/INDI-TITL @@ -10,7 +10,7 @@ standard tag: TITL specification: - Title - - An Individual Attribute. See also INDIVIDUAL_ATTRIBUTE_STRUCTURE. + - An [Individual Attribute]. See also `INDIVIDUAL_ATTRIBUTE_STRUCTURE`. label: 'Title' diff --git a/extracted-files/tags/INIL b/extracted-files/tags/INIL index faaa05f0..a687ad32 100644 --- a/extracted-files/tags/INIL +++ b/extracted-files/tags/INIL @@ -10,14 +10,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' diff --git a/extracted-files/tags/LANG b/extracted-files/tags/LANG index db1d45ce..dfc510e4 100644 --- a/extracted-files/tags/LANG +++ b/extracted-files/tags/LANG @@ -11,48 +11,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: +
- 1 SCHEMA - 2 TAG _LANG https://gedcom.io/terms/v7/LANG + 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: + + ```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' diff --git a/extracted-files/tags/LATI b/extracted-files/tags/LATI index cedd77c3..f604e17b 100644 --- a/extracted-files/tags/LATI +++ b/extracted-files/tags/LATI @@ -11,13 +11,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' diff --git a/extracted-files/tags/LEFT b/extracted-files/tags/LEFT index ebd820d4..7c90afcd 100644 --- a/extracted-files/tags/LEFT +++ b/extracted-files/tags/LEFT @@ -10,8 +10,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. label: 'Left crop width' diff --git a/extracted-files/tags/LONG b/extracted-files/tags/LONG index 02214124..65e85eaf 100644 --- a/extracted-files/tags/LONG +++ b/extracted-files/tags/LONG @@ -11,13 +11,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' diff --git a/extracted-files/tags/MAP b/extracted-files/tags/MAP index bcc614e5..bc518417 100644 --- a/extracted-files/tags/MAP +++ b/extracted-files/tags/MAP @@ -11,14 +11,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' diff --git a/extracted-files/tags/MARB b/extracted-files/tags/MARB index 0a5f9060..dc822820 100644 --- a/extracted-files/tags/MARB +++ b/extracted-files/tags/MARB @@ -10,7 +10,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. diff --git a/extracted-files/tags/MARC b/extracted-files/tags/MARC index 7f799aac..d497222d 100644 --- a/extracted-files/tags/MARC +++ b/extracted-files/tags/MARC @@ -10,11 +10,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' diff --git a/extracted-files/tags/MARL b/extracted-files/tags/MARL index 0d5c7228..83dc33f7 100644 --- a/extracted-files/tags/MARL +++ b/extracted-files/tags/MARL @@ -10,7 +10,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. diff --git a/extracted-files/tags/MARR b/extracted-files/tags/MARR index 7f296d67..59d2e1c2 100644 --- a/extracted-files/tags/MARR +++ b/extracted-files/tags/MARR @@ -10,10 +10,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' diff --git a/extracted-files/tags/MARS b/extracted-files/tags/MARS index b8f9f71a..382b09c6 100644 --- a/extracted-files/tags/MARS +++ b/extracted-files/tags/MARS @@ -10,11 +10,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' diff --git a/extracted-files/tags/MEDI b/extracted-files/tags/MEDI index ae7ad7d2..b8dd74d7 100644 --- a/extracted-files/tags/MEDI +++ b/extracted-files/tags/MEDI @@ -11,17 +11,21 @@ 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`. + +
label: 'Medium' diff --git a/extracted-files/tags/MIME b/extracted-files/tags/MIME index ca5e04a4..e2cb3f28 100644 --- a/extracted-files/tags/MIME +++ b/extracted-files/tags/MIME @@ -11,51 +11,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`. - 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 + 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' diff --git a/extracted-files/tags/NAME b/extracted-files/tags/NAME index 7f10a645..56cfc980 100644 --- a/extracted-files/tags/NAME +++ b/extracted-files/tags/NAME @@ -10,7 +10,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' diff --git a/extracted-files/tags/NAME-TRAN b/extracted-files/tags/NAME-TRAN index dad0959a..29786481 100644 --- a/extracted-files/tags/NAME-TRAN +++ b/extracted-files/tags/NAME-TRAN @@ -11,36 +11,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' diff --git a/extracted-files/tags/NAME-TYPE b/extracted-files/tags/NAME-TYPE index da068d2d..da14bfef 100644 --- a/extracted-files/tags/NAME-TYPE +++ b/extracted-files/tags/NAME-TYPE @@ -10,7 +10,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' diff --git a/extracted-files/tags/NATI b/extracted-files/tags/NATI index e12164b8..edce4c74 100644 --- a/extracted-files/tags/NATI +++ b/extracted-files/tags/NATI @@ -10,9 +10,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' diff --git a/extracted-files/tags/NATU b/extracted-files/tags/NATU index eba08c02..2aab5dbf 100644 --- a/extracted-files/tags/NATU +++ b/extracted-files/tags/NATU @@ -10,7 +10,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. diff --git a/extracted-files/tags/NMR b/extracted-files/tags/NMR index 35bdf0ca..569f23d9 100644 --- a/extracted-files/tags/NMR +++ b/extracted-files/tags/NMR @@ -10,7 +10,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. diff --git a/extracted-files/tags/NO b/extracted-files/tags/NO index 6af05943..193bb972 100644 --- a/extracted-files/tags/NO +++ b/extracted-files/tags/NO @@ -10,24 +10,34 @@ 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. + - 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 + 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 - 2 DATE TO 24 MAR 1880 + `1 NO MARR` means "no marriage occurred" - 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' diff --git a/extracted-files/tags/NO-DATE b/extracted-files/tags/NO-DATE index c9f7924e..711d3248 100644 --- a/extracted-files/tags/NO-DATE +++ b/extracted-files/tags/NO-DATE @@ -10,8 +10,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' diff --git a/extracted-files/tags/NOTE b/extracted-files/tags/NOTE index 927b97d4..0b3bf722 100644 --- a/extracted-files/tags/NOTE +++ b/extracted-files/tags/NOTE @@ -11,13 +11,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' diff --git a/extracted-files/tags/NOTE-TRAN b/extracted-files/tags/NOTE-TRAN index c5e75ed3..76a480fc 100644 --- a/extracted-files/tags/NOTE-TRAN +++ b/extracted-files/tags/NOTE-TRAN @@ -11,47 +11,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' diff --git a/extracted-files/tags/NPFX b/extracted-files/tags/NPFX index cb9c33ae..bd973b74 100644 --- a/extracted-files/tags/NPFX +++ b/extracted-files/tags/NPFX @@ -10,8 +10,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' diff --git a/extracted-files/tags/NSFX b/extracted-files/tags/NSFX index cf29acd9..8c685531 100644 --- a/extracted-files/tags/NSFX +++ b/extracted-files/tags/NSFX @@ -10,8 +10,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' diff --git a/extracted-files/tags/OBJE b/extracted-files/tags/OBJE index 2ac048cf..17c8ecf9 100644 --- a/extracted-files/tags/OBJE +++ b/extracted-files/tags/OBJE @@ -10,15 +10,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' diff --git a/extracted-files/tags/OCCU b/extracted-files/tags/OCCU index b918456b..43a03f90 100644 --- a/extracted-files/tags/OCCU +++ b/extracted-files/tags/OCCU @@ -10,7 +10,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. diff --git a/extracted-files/tags/ORDN b/extracted-files/tags/ORDN index 4fd48d89..15bc634c 100644 --- a/extracted-files/tags/ORDN +++ b/extracted-files/tags/ORDN @@ -10,7 +10,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. diff --git a/extracted-files/tags/PAGE b/extracted-files/tags/PAGE index 1d5cfbae..7eb4ffc0 100644 --- a/extracted-files/tags/PAGE +++ b/extracted-files/tags/PAGE @@ -11,27 +11,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. - - 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. - - 1 DSCR Tall enough his head touched the ceiling - 2 SOUR @VOID@ - 3 PAGE His grand-daughter Lydia told me this in 1980 + 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 + +
+ + ```gedcom + 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 + 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' diff --git a/extracted-files/tags/PEDI b/extracted-files/tags/PEDI index 5ef8c6b9..a1f385ff 100644 --- a/extracted-files/tags/PEDI +++ b/extracted-files/tags/PEDI @@ -10,7 +10,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. diff --git a/extracted-files/tags/PHON b/extracted-files/tags/PHON index 7c3dba6c..c7a27ec5 100644 --- a/extracted-files/tags/PHON +++ b/extracted-files/tags/PHON @@ -13,13 +13,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' diff --git a/extracted-files/tags/PHRASE b/extracted-files/tags/PHRASE index a6de89b2..97d6d57f 100644 --- a/extracted-files/tags/PHRASE +++ b/extracted-files/tags/PHRASE @@ -11,45 +11,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' diff --git a/extracted-files/tags/PLAC b/extracted-files/tags/PLAC index 31fb849c..ad1ec44b 100644 --- a/extracted-files/tags/PLAC +++ b/extracted-files/tags/PLAC @@ -11,47 +11,59 @@ 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. 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. 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' diff --git a/extracted-files/tags/PLAC-FORM b/extracted-files/tags/PLAC-FORM index 775633fb..1f27dc02 100644 --- a/extracted-files/tags/PLAC-FORM +++ b/extracted-files/tags/PLAC-FORM @@ -11,14 +11,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' diff --git a/extracted-files/tags/PLAC-TRAN b/extracted-files/tags/PLAC-TRAN index f23c23c9..80c8144e 100644 --- a/extracted-files/tags/PLAC-TRAN +++ b/extracted-files/tags/PLAC-TRAN @@ -11,37 +11,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' diff --git a/extracted-files/tags/POST b/extracted-files/tags/POST index 02fc2a34..89ceef1b 100644 --- a/extracted-files/tags/POST +++ b/extracted-files/tags/POST @@ -11,7 +11,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. label: 'Postal code' diff --git a/extracted-files/tags/PROB b/extracted-files/tags/PROB index 2f1b6743..86f5c37c 100644 --- a/extracted-files/tags/PROB +++ b/extracted-files/tags/PROB @@ -10,7 +10,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. diff --git a/extracted-files/tags/PROP b/extracted-files/tags/PROP index 0c496487..769b9f55 100644 --- a/extracted-files/tags/PROP +++ b/extracted-files/tags/PROP @@ -10,10 +10,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' diff --git a/extracted-files/tags/PUBL b/extracted-files/tags/PUBL index 8da7ca18..6a7deb77 100644 --- a/extracted-files/tags/PUBL +++ b/extracted-files/tags/PUBL @@ -12,13 +12,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' diff --git a/extracted-files/tags/QUAY b/extracted-files/tags/QUAY index 3ffd58d2..21c4543a 100644 --- a/extracted-files/tags/QUAY +++ b/extracted-files/tags/QUAY @@ -10,12 +10,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' diff --git a/extracted-files/tags/REFN b/extracted-files/tags/REFN index 4d417dde..3598ea23 100644 --- a/extracted-files/tags/REFN +++ b/extracted-files/tags/REFN @@ -12,13 +12,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' diff --git a/extracted-files/tags/RELI b/extracted-files/tags/RELI index c469e06e..65a1a05f 100644 --- a/extracted-files/tags/RELI +++ b/extracted-files/tags/RELI @@ -10,11 +10,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' diff --git a/extracted-files/tags/REPO b/extracted-files/tags/REPO index 3a892cc5..8699b972 100644 --- a/extracted-files/tags/REPO +++ b/extracted-files/tags/REPO @@ -10,13 +10,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' diff --git a/extracted-files/tags/RESN b/extracted-files/tags/RESN index 3727cc09..49f182c7 100644 --- a/extracted-files/tags/RESN +++ b/extracted-files/tags/RESN @@ -12,15 +12,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. This is metadata about the structure itself, not data about its subject. diff --git a/extracted-files/tags/RETI b/extracted-files/tags/RETI index b72dc774..ff730a3a 100644 --- a/extracted-files/tags/RETI +++ b/extracted-files/tags/RETI @@ -10,10 +10,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' diff --git a/extracted-files/tags/ROLE b/extracted-files/tags/ROLE index a064dcde..c92067cb 100644 --- a/extracted-files/tags/ROLE +++ b/extracted-files/tags/ROLE @@ -11,28 +11,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' diff --git a/extracted-files/tags/SCHMA b/extracted-files/tags/SCHMA index b1e7a2c1..ae66c328 100644 --- a/extracted-files/tags/SCHMA +++ b/extracted-files/tags/SCHMA @@ -10,8 +10,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. label: 'Extension schema' diff --git a/extracted-files/tags/SDATE b/extracted-files/tags/SDATE index 02fd5f00..2d9877f4 100644 --- a/extracted-files/tags/SDATE +++ b/extracted-files/tags/SDATE @@ -14,19 +14,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' diff --git a/extracted-files/tags/SEX b/extracted-files/tags/SEX index b60d2bb6..b36ee962 100644 --- a/extracted-files/tags/SEX +++ b/extracted-files/tags/SEX @@ -10,7 +10,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' diff --git a/extracted-files/tags/SLGC b/extracted-files/tags/SLGC index 5db88ea3..4e59bdc2 100644 --- a/extracted-files/tags/SLGC +++ b/extracted-files/tags/SLGC @@ -10,11 +10,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' diff --git a/extracted-files/tags/SLGS b/extracted-files/tags/SLGS index d73a4129..88a73933 100644 --- a/extracted-files/tags/SLGS +++ b/extracted-files/tags/SLGS @@ -10,13 +10,13 @@ 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. - 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' diff --git a/extracted-files/tags/SNOTE b/extracted-files/tags/SNOTE index dd1ae2e6..2d9ae7f3 100644 --- a/extracted-files/tags/SNOTE +++ b/extracted-files/tags/SNOTE @@ -10,8 +10,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. label: 'Shared note' diff --git a/extracted-files/tags/SOUR b/extracted-files/tags/SOUR index 91a65c85..3da0ee8d 100644 --- a/extracted-files/tags/SOUR +++ b/extracted-files/tags/SOUR @@ -10,31 +10,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. - | 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' diff --git a/extracted-files/tags/SOUR-DATA b/extracted-files/tags/SOUR-DATA index 062c5454..e446bea6 100644 --- a/extracted-files/tags/SOUR-DATA +++ b/extracted-files/tags/SOUR-DATA @@ -10,7 +10,7 @@ standard tag: DATA specification: - Data - - See https://gedcom.io/terms/v7/DATA. + - See `https://gedcom.io/terms/v7/DATA`. label: 'Data' diff --git a/extracted-files/tags/SOUR-EVEN b/extracted-files/tags/SOUR-EVEN index 3dee82b1..bd854b1d 100644 --- a/extracted-files/tags/SOUR-EVEN +++ b/extracted-files/tags/SOUR-EVEN @@ -10,12 +10,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' diff --git a/extracted-files/tags/SSN b/extracted-files/tags/SSN index a0aafd59..ff8172dc 100644 --- a/extracted-files/tags/SSN +++ b/extracted-files/tags/SSN @@ -10,10 +10,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' diff --git a/extracted-files/tags/STAE b/extracted-files/tags/STAE index b5978f9a..659053b7 100644 --- a/extracted-files/tags/STAE +++ b/extracted-files/tags/STAE @@ -10,8 +10,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. label: 'State' diff --git a/extracted-files/tags/SUBM b/extracted-files/tags/SUBM index f49de6ba..7999d56e 100644 --- a/extracted-files/tags/SUBM +++ b/extracted-files/tags/SUBM @@ -10,8 +10,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' diff --git a/extracted-files/tags/SUBM-LANG b/extracted-files/tags/SUBM-LANG index db4d4002..c311854b 100644 --- a/extracted-files/tags/SUBM-LANG +++ b/extracted-files/tags/SUBM-LANG @@ -13,7 +13,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' diff --git a/extracted-files/tags/TAG b/extracted-files/tags/TAG index 72c361dc..53c564f0 100644 --- a/extracted-files/tags/TAG +++ b/extracted-files/tags/TAG @@ -10,8 +10,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. label: 'Extension tag' diff --git a/extracted-files/tags/TEMP b/extracted-files/tags/TEMP index 40264ee3..83ad0ab4 100644 --- a/extracted-files/tags/TEMP +++ b/extracted-files/tags/TEMP @@ -11,9 +11,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' diff --git a/extracted-files/tags/TEXT b/extracted-files/tags/TEXT index 33684e86..aff51104 100644 --- a/extracted-files/tags/TEXT +++ b/extracted-files/tags/TEXT @@ -10,11 +10,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' diff --git a/extracted-files/tags/TIME b/extracted-files/tags/TIME index e439e800..5e97b64a 100644 --- a/extracted-files/tags/TIME +++ b/extracted-files/tags/TIME @@ -10,7 +10,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' diff --git a/extracted-files/tags/TITL b/extracted-files/tags/TITL index 744d81f8..05d34ce8 100644 --- a/extracted-files/tags/TITL +++ b/extracted-files/tags/TITL @@ -14,25 +14,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. diff --git a/extracted-files/tags/TOP b/extracted-files/tags/TOP index e70442ff..dbbd148a 100644 --- a/extracted-files/tags/TOP +++ b/extracted-files/tags/TOP @@ -10,7 +10,7 @@ standard tag: TOP specification: - Top crop width - - A number of pixels to not display from the top side of the image. See CROP + - A number of pixels to not display from the top side of the image. See `CROP` for more. label: 'Top crop width' diff --git a/extracted-files/tags/TRLR b/extracted-files/tags/TRLR index 8a2b2742..19416469 100644 --- a/extracted-files/tags/TRLR +++ b/extracted-files/tags/TRLR @@ -10,7 +10,7 @@ standard tag: TRLR specification: - Trailer - - A pseudo-structure marking the end of a dataset. See The Header and Trailer + - A pseudo-structure marking the end of a dataset. See [The Header and Trailer] for more. label: 'Trailer' diff --git a/extracted-files/tags/TYPE b/extracted-files/tags/TYPE index 88da60cf..429c3d29 100644 --- a/extracted-files/tags/TYPE +++ b/extracted-files/tags/TYPE @@ -13,35 +13,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' diff --git a/extracted-files/tags/UID b/extracted-files/tags/UID index 8c0f4914..f2fcd7d3 100644 --- a/extracted-files/tags/UID +++ b/extracted-files/tags/UID @@ -12,32 +12,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' diff --git a/extracted-files/tags/WIDTH b/extracted-files/tags/WIDTH index f65b2607..e9fdb563 100644 --- a/extracted-files/tags/WIDTH +++ b/extracted-files/tags/WIDTH @@ -10,7 +10,7 @@ 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. label: 'Width in pixels' diff --git a/extracted-files/tags/WIFE b/extracted-files/tags/WIFE index 4d6aaba1..2f126722 100644 --- a/extracted-files/tags/WIFE +++ b/extracted-files/tags/WIFE @@ -11,7 +11,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' diff --git a/extracted-files/tags/WILL b/extracted-files/tags/WILL index f1689bdb..19f6b753 100644 --- a/extracted-files/tags/WILL +++ b/extracted-files/tags/WILL @@ -10,11 +10,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' diff --git a/extracted-files/tags/WWW b/extracted-files/tags/WWW index 925f0ee5..3b005a1c 100644 --- a/extracted-files/tags/WWW +++ b/extracted-files/tags/WWW @@ -11,8 +11,8 @@ 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, as defined by any relevant + standard such as [whatwg/url], [RFC 3986], [RFC 3987], and so forth. If an invalid or no longer existing web address is present upon import, it should be preserved as-is on export. diff --git a/extracted-files/tags/cal-FRENCH_R b/extracted-files/tags/cal-FRENCH_R index 568c85d8..251bc28d 100644 --- a/extracted-files/tags/cal-FRENCH_R +++ b/extracted-files/tags/cal-FRENCH_R @@ -10,33 +10,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' diff --git a/extracted-files/tags/cal-GREGORIAN b/extracted-files/tags/cal-GREGORIAN index 45e9f8c0..19b636b4 100644 --- a/extracted-files/tags/cal-GREGORIAN +++ b/extracted-files/tags/cal-GREGORIAN @@ -11,31 +11,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' diff --git a/extracted-files/tags/cal-HEBREW b/extracted-files/tags/cal-HEBREW index 754855ed..c86a82ac 100644 --- a/extracted-files/tags/cal-HEBREW +++ b/extracted-files/tags/cal-HEBREW @@ -10,55 +10,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' diff --git a/extracted-files/tags/cal-JULIAN b/extracted-files/tags/cal-JULIAN index ab9093b5..c7917aa4 100644 --- a/extracted-files/tags/cal-JULIAN +++ b/extracted-files/tags/cal-JULIAN @@ -10,21 +10,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' diff --git a/extracted-files/tags/enum-1 b/extracted-files/tags/enum-1 index f5e2e0e2..8847a8b9 100644 --- a/extracted-files/tags/enum-1 +++ b/extracted-files/tags/enum-1 @@ -9,8 +9,8 @@ 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" diff --git a/extracted-files/tags/enum-ADOP-HUSB b/extracted-files/tags/enum-ADOP-HUSB index 3d5ee946..2cb82a43 100644 --- a/extracted-files/tags/enum-ADOP-HUSB +++ b/extracted-files/tags/enum-ADOP-HUSB @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-ADOP-WIFE b/extracted-files/tags/enum-ADOP-WIFE index 0c516c8e..16941a1c 100644 --- a/extracted-files/tags/enum-ADOP-WIFE +++ b/extracted-files/tags/enum-ADOP-WIFE @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-BIC b/extracted-files/tags/enum-BIC index 41c0d85d..c789b9bb 100644 --- a/extracted-files/tags/enum-BIC +++ b/extracted-files/tags/enum-BIC @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-BOTH b/extracted-files/tags/enum-BOTH index f9e69323..6755aec6 100644 --- a/extracted-files/tags/enum-BOTH +++ b/extracted-files/tags/enum-BOTH @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-CANCELED b/extracted-files/tags/enum-CANCELED index 39747d08..eac25309 100644 --- a/extracted-files/tags/enum-CANCELED +++ b/extracted-files/tags/enum-CANCELED @@ -9,7 +9,7 @@ uri: https://gedcom.io/terms/v7/enum-CANCELED standard tag: CANCELED specification: - - "Applies to: SLGS" + - "Applies to: `SLGS`" - Canceled and considered invalid. - "Status: Current" diff --git a/extracted-files/tags/enum-CENS b/extracted-files/tags/enum-CENS index ce181a38..b0dd4ac1 100644 --- a/extracted-files/tags/enum-CENS +++ b/extracted-files/tags/enum-CENS @@ -9,8 +9,8 @@ uri: https://gedcom.io/terms/v7/enum-CENS standard tag: CENS specification: - - A census event; either https://gedcom.io/terms/v7/INDI-CENS or - https://gedcom.io/terms/v7/FAM-CENS + - A census event; either `https://gedcom.io/terms/v7/INDI-CENS` or + `https://gedcom.io/terms/v7/FAM-CENS` value of: - "https://gedcom.io/terms/v7/enumset-EVEN" diff --git a/extracted-files/tags/enum-CHALLENGED b/extracted-files/tags/enum-CHALLENGED index 251ec108..216b340d 100644 --- a/extracted-files/tags/enum-CHALLENGED +++ b/extracted-files/tags/enum-CHALLENGED @@ -9,8 +9,8 @@ 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" diff --git a/extracted-files/tags/enum-CHILD b/extracted-files/tags/enum-CHILD index e4b561ce..20e1b537 100644 --- a/extracted-files/tags/enum-CHILD +++ b/extracted-files/tags/enum-CHILD @@ -9,9 +9,9 @@ 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: diff --git a/extracted-files/tags/enum-CLERGY b/extracted-files/tags/enum-CLERGY index e7a15395..6555f166 100644 --- a/extracted-files/tags/enum-CLERGY +++ b/extracted-files/tags/enum-CLERGY @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-COMPLETED b/extracted-files/tags/enum-COMPLETED index f2435f8e..fec7a3cc 100644 --- a/extracted-files/tags/enum-COMPLETED +++ b/extracted-files/tags/enum-COMPLETED @@ -11,8 +11,8 @@ 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" diff --git a/extracted-files/tags/enum-DISPROVEN b/extracted-files/tags/enum-DISPROVEN index 3ba80a8f..8be0b9e7 100644 --- a/extracted-files/tags/enum-DISPROVEN +++ b/extracted-files/tags/enum-DISPROVEN @@ -9,8 +9,8 @@ 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" diff --git a/extracted-files/tags/enum-DNS b/extracted-files/tags/enum-DNS index ef584008..6e849516 100644 --- a/extracted-files/tags/enum-DNS +++ b/extracted-files/tags/enum-DNS @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-DNS_CAN b/extracted-files/tags/enum-DNS_CAN index eafd8f61..ef053b5a 100644 --- a/extracted-files/tags/enum-DNS_CAN +++ b/extracted-files/tags/enum-DNS_CAN @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-EVEN b/extracted-files/tags/enum-EVEN index 0feb590d..2c064306 100644 --- a/extracted-files/tags/enum-EVEN +++ b/extracted-files/tags/enum-EVEN @@ -9,8 +9,8 @@ uri: https://gedcom.io/terms/v7/enum-EVEN standard tag: EVEN specification: - - A generic event; either https://gedcom.io/terms/v7/INDI-EVEN or - https://gedcom.io/terms/v7/FAM-EVEN + - A generic event; either `https://gedcom.io/terms/v7/INDI-EVEN` or + `https://gedcom.io/terms/v7/FAM-EVEN` value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" diff --git a/extracted-files/tags/enum-EXCLUDED b/extracted-files/tags/enum-EXCLUDED index b78891ae..4b4fa2e9 100644 --- a/extracted-files/tags/enum-EXCLUDED +++ b/extracted-files/tags/enum-EXCLUDED @@ -11,8 +11,8 @@ 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" diff --git a/extracted-files/tags/enum-FACT b/extracted-files/tags/enum-FACT index 5f5c5a32..9fb09e08 100644 --- a/extracted-files/tags/enum-FACT +++ b/extracted-files/tags/enum-FACT @@ -9,8 +9,8 @@ uri: https://gedcom.io/terms/v7/enum-FACT standard tag: FACT specification: - - A generic attribute; either https://gedcom.io/terms/v7/INDI-FACT or - https://gedcom.io/terms/v7/FAM-FACT + - A generic attribute; either `https://gedcom.io/terms/v7/INDI-FACT` or + `https://gedcom.io/terms/v7/FAM-FACT` value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" diff --git a/extracted-files/tags/enum-FATH b/extracted-files/tags/enum-FATH index 12cb3e59..7f875cfb 100644 --- a/extracted-files/tags/enum-FATH +++ b/extracted-files/tags/enum-FATH @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-HUSB b/extracted-files/tags/enum-HUSB index 065523cb..796299bf 100644 --- a/extracted-files/tags/enum-HUSB +++ b/extracted-files/tags/enum-HUSB @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-INFANT b/extracted-files/tags/enum-INFANT index 6633cef4..09a1ae0f 100644 --- a/extracted-files/tags/enum-INFANT +++ b/extracted-files/tags/enum-INFANT @@ -9,9 +9,9 @@ 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" diff --git a/extracted-files/tags/enum-MOTH b/extracted-files/tags/enum-MOTH index 6ed27501..6db1082d 100644 --- a/extracted-files/tags/enum-MOTH +++ b/extracted-files/tags/enum-MOTH @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-MULTIPLE b/extracted-files/tags/enum-MULTIPLE index 9c47e550..91f93a9c 100644 --- a/extracted-files/tags/enum-MULTIPLE +++ b/extracted-files/tags/enum-MULTIPLE @@ -10,7 +10,7 @@ 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" diff --git a/extracted-files/tags/enum-NCHI b/extracted-files/tags/enum-NCHI index a9dd5b81..4fb39685 100644 --- a/extracted-files/tags/enum-NCHI +++ b/extracted-files/tags/enum-NCHI @@ -9,8 +9,8 @@ uri: https://gedcom.io/terms/v7/enum-NCHI standard tag: NCHI specification: - - A count of children; either https://gedcom.io/terms/v7/INDI-NCHI or - https://gedcom.io/terms/v7/FAM-NCHI + - A count of children; either `https://gedcom.io/terms/v7/INDI-NCHI` or + `https://gedcom.io/terms/v7/FAM-NCHI` value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" diff --git a/extracted-files/tags/enum-OTHER b/extracted-files/tags/enum-OTHER index dc5b0409..adcc706d 100644 --- a/extracted-files/tags/enum-OTHER +++ b/extracted-files/tags/enum-OTHER @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/enum-PRE_1970 b/extracted-files/tags/enum-PRE_1970 index 349908b6..875cf072 100644 --- a/extracted-files/tags/enum-PRE_1970 +++ b/extracted-files/tags/enum-PRE_1970 @@ -12,7 +12,7 @@ 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" diff --git a/extracted-files/tags/enum-PRIVACY b/extracted-files/tags/enum-PRIVACY index 6f965cd0..79f9f57e 100644 --- a/extracted-files/tags/enum-PRIVACY +++ b/extracted-files/tags/enum-PRIVACY @@ -9,10 +9,10 @@ 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" diff --git a/extracted-files/tags/enum-RESI b/extracted-files/tags/enum-RESI index 1375784a..543eeaea 100644 --- a/extracted-files/tags/enum-RESI +++ b/extracted-files/tags/enum-RESI @@ -9,8 +9,8 @@ uri: https://gedcom.io/terms/v7/enum-RESI standard tag: RESI specification: - - A residence attribute; either https://gedcom.io/terms/v7/INDI-RESI or - https://gedcom.io/terms/v7/FAM-RESI + - A residence attribute; either `https://gedcom.io/terms/v7/INDI-RESI` or + `https://gedcom.io/terms/v7/FAM-RESI` value of: - "https://gedcom.io/terms/v7/enumset-EVENATTR" diff --git a/extracted-files/tags/enum-SUBMITTED b/extracted-files/tags/enum-SUBMITTED index 2da1e31a..f3445535 100644 --- a/extracted-files/tags/enum-SUBMITTED +++ b/extracted-files/tags/enum-SUBMITTED @@ -11,8 +11,8 @@ 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" diff --git a/extracted-files/tags/enum-UNCLEARED b/extracted-files/tags/enum-UNCLEARED index 7f4bea37..64787fbb 100644 --- a/extracted-files/tags/enum-UNCLEARED +++ b/extracted-files/tags/enum-UNCLEARED @@ -11,8 +11,8 @@ 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" diff --git a/extracted-files/tags/enum-WIFE b/extracted-files/tags/enum-WIFE index d6d50ca4..78dae597 100644 --- a/extracted-files/tags/enum-WIFE +++ b/extracted-files/tags/enum-WIFE @@ -9,7 +9,7 @@ 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" diff --git a/extracted-files/tags/ord-STAT b/extracted-files/tags/ord-STAT index bb6469c3..f78bea02 100644 --- a/extracted-files/tags/ord-STAT +++ b/extracted-files/tags/ord-STAT @@ -10,7 +10,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' diff --git a/extracted-files/tags/record-FAM b/extracted-files/tags/record-FAM index 0dfa0d11..11d5551c 100644 --- a/extracted-files/tags/record-FAM +++ b/extracted-files/tags/record-FAM @@ -11,59 +11,67 @@ 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. + 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 + 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' diff --git a/extracted-files/tags/record-INDI b/extracted-files/tags/record-INDI index 46c57ebd..71d59a06 100644 --- a/extracted-files/tags/record-INDI +++ b/extracted-files/tags/record-INDI @@ -10,41 +10,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. 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' diff --git a/extracted-files/tags/record-OBJE b/extracted-files/tags/record-OBJE index 71b49db9..fb825b52 100644 --- a/extracted-files/tags/record-OBJE +++ b/extracted-files/tags/record-OBJE @@ -10,18 +10,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' diff --git a/extracted-files/tags/record-REPO b/extracted-files/tags/record-REPO index ceb7e6af..4eadba74 100644 --- a/extracted-files/tags/record-REPO +++ b/extracted-files/tags/record-REPO @@ -10,20 +10,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' diff --git a/extracted-files/tags/record-SNOTE b/extracted-files/tags/record-SNOTE index bcf800cc..2d1affe0 100644 --- a/extracted-files/tags/record-SNOTE +++ b/extracted-files/tags/record-SNOTE @@ -10,7 +10,7 @@ standard tag: SNOTE specification: - Shared note - - A note that is shared by multiple structures. See SHARED_NOTE_RECORD for + - A note that is shared by multiple structures. See `SHARED_NOTE_RECORD` for more. - | A catch-all location for information that does not fully fit within other @@ -18,33 +18,43 @@ specification: 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' diff --git a/extracted-files/tags/record-SOUR b/extracted-files/tags/record-SOUR index e450c588..70c5c049 100644 --- a/extracted-files/tags/record-SOUR +++ b/extracted-files/tags/record-SOUR @@ -10,21 +10,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. - | - 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' diff --git a/extracted-files/tags/record-SUBM b/extracted-files/tags/record-SUBM index b5dbf438..116cca43 100644 --- a/extracted-files/tags/record-SUBM +++ b/extracted-files/tags/record-SUBM @@ -11,12 +11,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. + - 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' diff --git a/extracted-files/tags/type-Age b/extracted-files/tags/type-Age index 5b9d618b..4e176f39 100644 --- a/extracted-files/tags/type-Age +++ b/extracted-files/tags/type-Age @@ -10,48 +10,54 @@ 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. + 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. + 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`. ... diff --git a/extracted-files/tags/type-Date b/extracted-files/tags/type-Date index 8d5ed2e4..c7adae67 100644 --- a/extracted-files/tags/type-Date +++ b/extracted-files/tags/type-Date @@ -9,113 +9,117 @@ 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 `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 `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. + The URI for the `DatePeriod` data type is + `https://gedcom.io/terms/v7/type-Date#period`. ... diff --git a/extracted-files/tags/type-Enum b/extracted-files/tags/type-Enum index 14b8833e..6b6fa51e 100644 --- a/extracted-files/tags/type-Enum +++ b/extracted-files/tags/type-Enum @@ -8,18 +8,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. @@ -27,24 +29,25 @@ 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`. ... diff --git a/extracted-files/tags/type-List b/extracted-files/tags/type-List index 4b7e8e2d..e85c72e2 100644 --- a/extracted-files/tags/type-List +++ b/extracted-files/tags/type-List @@ -9,33 +9,38 @@ 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`. ... diff --git a/extracted-files/tags/type-Name b/extracted-files/tags/type-Name index c3af5a7e..4863b95f 100644 --- a/extracted-files/tags/type-Name +++ b/extracted-files/tags/type-Name @@ -8,23 +8,24 @@ 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`. ... diff --git a/extracted-files/tags/type-Time b/extracted-files/tags/type-Time index 91909f18..e21ca3ba 100644 --- a/extracted-files/tags/type-Time +++ b/extracted-files/tags/type-Time @@ -8,22 +8,28 @@ 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`. ...