genealogy-brainstorming

Genealogy Brainstorming

Contributors

• Andy Mabbett

Building blocks

Since genealogy is about people and their relationships, it is likely that any genealogical microformat will be built from hCard and XFN microformats; with hCalendar used for dates such as marriages and divorces. The proposed citation microformat could be incorporated, as many genealogists cite the records they use.

Document types

Genealogy documents on the web tend to fall into one of several types:

1. A family tree with many members (e.g. [1]).
2. A page for an individual, listing their ancestors and descendants for one generation in each direction, plus their spouse(s) and, sometimes, their sibling(s) (e.g. [2], [3]).
3. As above, but for a couple (e.g. [4])
4. Prose pages which may discuss the families of one or more, sometimes unrelated, individuals (not necessarily in the context of genealogy) (e.g. [5]).

Only the second of these, and some, but by no means all, of the others, are suited to XFN markup.

Properties

Gender

To make life easier for publishers, the following values could all equate, without requiring the use of abbr to:

Male

• male
• he
• man
• m
• son
• father
• husband
• brother
• uncle
• nephew
• grandfather/ grand-father / great-grand-father etc.
• grandson/ grand-son / great-grand-son etc.
• ...

Female

• female
• she
• woman
• f
• fem
• wife
• daughter
• mother
• sister
• aunt
• niece
• grandmother/ grand-mother / great-grand-mother etc.
• granddaughter/ grand-daughter / great-grand-daughter etc.
• ...

Issue

• What about other languages?
  • See: internationalisation
• Gender reassignment and other edge cases
  • Outside the 80/20 cut-off
  • Could use abbr
  • See also GenderHack

Relationships

XFN has some family rel values: "parent", "child", "sibling", "spouse".

Although, from existing publishing practices, it seems that the above ("primary") relationships are more commonly expressed than secondary relationships ("aunt", "grand-father") when linking from one page to another, additional values may be required (see above for further examples). These could, of course, be used outside a genealogy microformat, as with other XFN values.

Non-marriage partnerships

• follow-up: specific examples/citations needed.

... and short-term liaisons should also be catered for (for the parents of illegitimate children).

• follow-up: some short-term liasons may already be documented with the XFN values "date" and "sweetheart".

In addition to the gender-neutral primary relationships already in XFN, gender-specific terms may be required ("father" and "mother" for "parent", for example).

• follow-up: gender-specific relationship terms are undesirable as described in XFN:Background: Gender neutrality (and avoiding other personal attributes).

There might also be a need for "step-sibling",

• follow-up: it may be better to update the XFN definition of "sibling" to explicitly include "step-sibling" as it can be reasonably asserted that the current definition and background allows for it.

... "step-mother"

• follow-up: it may be better to update the XFN definition of "parent" to explicitly include "step-parent" as it can be reasonably asserted that the current definition and background allows for it. See above about avoiding gender-specific terms like "mother".

... and "half-sibling", etc.

• follow-up: "half-sibling" is already covered by the current definition and background of "sibling" in XFN.

If XFN is used, then it would be prudent to add a couple of rules or guidelines:

• Each page SHOULD or MUST have one and only one hCard for a person, who MUST be the person in the relationship (this allows for non- personal hCards for publishing organisations, in hResume, etc.

Otherwise, the system would fail if, say, rel-spouse linked to page, about a person whose sibling or colleague was also hCarded on that page, even if that page was primarily about the person referred to by the "rel".

See also: xfn-brainstorming#Extending_family_relationships

Date of death

Inevitably, more of our ancestors are dead than alive.

Since non-genealogical web pages also publish death dates, it is proposed that hCard be extended to incorporate them. See hcard-date-of-death

Date of baptism

Older records, from times when registration of births was not carried out, rely on baptism records, A date-of-baptism property is thus required. This could be added to hCard, or be specific to a genealogy microformat, and should be based on hCards "bday".

See also

• genealogy - overview of genealogy microformat effort
• genealogy-examples - research and documentation of existing real world genealogy publishing examples on the web
• genealogy-formats - research and documentation of previous genealogy related formats
• genealogy-brainstorming - brainstorm proposals for a genealogy microformat