genealogy-brainstorming: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(→‎Relationships: use outside genealogy)
(→‎Relationships: rewrite to mention existing XFN family, er, values. Also "step" relationships)
Line 51: Line 51:


==Relationships==
==Relationships==
Additional [[XFN]] <code>rel</code> values may be required (e.g. "uncle"; see above for further examples).


From existing publishing practices, it seems likely that primary relationships ("mother", "father", "son", "daughter", "brother", "sister", "husband", "wife"; or perhaps the gender-neutral "parent", "child", "sibling", "spouse") are more commonly expressed when linking from one page to another; though non-marriage partnerships and short-term liaisons should also be catered for.
[[XFN]] has [http://gmpg.org/xfn/1 family rel values].  


These could, of course, be used outside a genealogy microformat, as with other XFN values.
Although, from existing publishing practices, it seems likely that primary relationships ("parent", "child", "sibling", "spouse") are more commonly expressed than secondarty relationships ("aunt", "grand-father") when linking from one page to another, additional values may be required (e.g. "uncle"; see above for further examples). These could, of course, be used outside a genealogy microformat, as with other XFN values.
 
Non-marriage partnerships and short-term liaisons should also be catered for (for the parents of illegitimate children).
 
In addition to the gender-neutral primary relationships already in XFN, gender-specific terms may be required ("father" and "mother" for "parent", for example). There might also be a need for "step-sibling", "step-mother" and "half-sibling", etc.


==Date of death==
==Date of death==

Revision as of 10:47, 27 September 2007

Genealogy Brainstorming

Contributors

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.

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?
  • Gender reassignment and other edge cases
    • Outside the 80/20 cut-off
    • Could use abbr

Relationships

XFN has family rel values.

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

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

In addition to the gender-neutral primary relationships already in XFN, gender-specific terms may be required ("father" and "mother" for "parent", for example). There might also be a need for "step-sibling", "step-mother" and "half-sibling", etc.

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

See also