genealogy: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(moved and copy-edited problem statement)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(11 intermediate revisions by 7 users not shown)
Line 1: Line 1:
= Genealogy =
{{DISPLAYTITLE: Genealogy }}


This is a page for tracking the effort to develop a genealogy microformat for authors and publishers to people and sets of related people that they create and publish.
This is a page for tracking the effort to develop a genealogy (<abbr title="also known as">aka</abbr> family history) microformat for authors and publishers to use, to mark up details of people and sets of related people.


== Problem Statement ==
== Problem Statement ==
Many people are posting their family trees, but if you were searching for your ancestors, there is no semantic in these pages which helps you link them to similar named individuals in your own tree. Some sites like FreeCEN and FreeBMD have databases which can assist in this linkage, but they are incomplete and frustrating to use.
Many people are posting their family trees, but if you were searching for your ancestors, there is no apparent semantic in these pages which helps you link them to similar named individuals in your own tree.


If there were some kind of order to this process, ordinary web searching might be used; and we could interlink family trees more readily.
To start, performing some amount of [[hcard-advocacy|hCard advocacy]] would help find the people on family trees, and advocating use of [[XFN]] across pages representing people in a family tree would also help map out the trees themselves.


[http://jay.askren.net/Projects/SemWeb/ RDF] and the semantic web has been used to tackle this problem, but this doesn't help people who want to publish-, or search published-, trees until there is a real semantic web.
Some sites like FreeCEN and FreeBMD have databases which can assist in this linkage, but they are incomplete and frustrating to use.


What may be needed is a microformat to add to examples like [http://jay.askren.net/Projects/SemWeb/FamilyTrees/AbrahamLincoln.html this tree of Abraham Lincoln].
What may be needed is a microformat to add to examples like [http://jay.askren.net/Projects/SemWeb/FamilyTrees/AbrahamLincoln.html this tree of Abraham Lincoln] that goes beyond hCard, or perhaps with extensions to hCard to cover genealogical properties/assertions such as  "flourished" or "baptised" ([[vcard-suggestions#Alternative_dates|these have been proposed]]), [[vcard-suggestions#Deceased|date of death]], or [[vcard-suggestions#Gender|gender]] (which is present in [[vcard4|vCard4]] and thus expected in an update to [[hCard]]).
 
==See also==


== Next Steps ==
Per the microformats [[process]]:
Per the microformats [[process]]:


{{genealogy-related-pages}}
{{genealogy-related-pages}}
== See Also ==
* [[hCard]]
* [[hcard-advocacy|hCard advocacy]]
* [[XFN]]
* [[history-microformat]]

Latest revision as of 16:22, 18 July 2020


This is a page for tracking the effort to develop a genealogy (aka family history) microformat for authors and publishers to use, to mark up details of people and sets of related people.

Problem Statement

Many people are posting their family trees, but if you were searching for your ancestors, there is no apparent semantic in these pages which helps you link them to similar named individuals in your own tree.

To start, performing some amount of hCard advocacy would help find the people on family trees, and advocating use of XFN across pages representing people in a family tree would also help map out the trees themselves.

Some sites like FreeCEN and FreeBMD have databases which can assist in this linkage, but they are incomplete and frustrating to use.

What may be needed is a microformat to add to examples like this tree of Abraham Lincoln that goes beyond hCard, or perhaps with extensions to hCard to cover genealogical properties/assertions such as "flourished" or "baptised" (these have been proposed), date of death, or gender (which is present in vCard4 and thus expected in an update to hCard).

Next Steps

Per the microformats process:

See Also