https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=SeanHayesMicroformats Wiki - User contributions [en]2026-06-09T08:33:21ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=abbr-design-pattern&diff=15988abbr-design-pattern2007-04-20T01:49:57Z<p>SeanHayes: /* Discussion */</p>
<hr />
<div>= Abbr design pattern =<br />
<br />
== Purpose ==<br />
* Use the [[abbr-design-pattern]] to make text that is human readable also formally machine readable<br />
* Avoiding using the [[abbr-design-pattern]] to re-encode human text or to hide data<br />
<br />
== How to use it ==<br />
* enclose the human-friendly text that you want to make machine readable with <code>&lt;abbr></code> <br />
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element<br />
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable data as the value<br />
<br />
== Example ==<br />
The [[datetime-design-pattern]] formally encodes (the notoriously unparsable) datetimes into an <code>abbr</code> element.<br />
<br />
Before:<br />
<br />
<pre><br />
The party is at 10 o'clock on the 10th.<br />
</pre><br />
<br />
After:<br />
<br />
<pre><br />
The party is at <br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr>.<br />
</pre><br />
<br />
== Discussion ==<br />
''This discussion is culled from [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html here]''. Consider two possible uses for the [[abbr-design-pattern]]:<br />
<br />
<ol><br />
<li><br />
using ABBR to encode machine readable data around human readable data<br />
<br />
<pre><br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr><br />
</pre><br />
</li><br />
<li><br />
using ABBR to encode more formal human data around something less formal <br />
<br />
<pre><br />
<abbr class="author" title="Danny Ayers">Danny</abbr> <br />
</pre><br />
</li><br />
</ol><br />
<br />
Use #1 is encouraged if there's a reasonable need for it. Use #2 is discouraged under the [http://c2.com/cgi-bin/wiki?DontRepeatYourself Don't Repeat Yourself principle], as: "#2 is a case of *more* information being invisibly present, namely, the<br />
last name in this case. If someone is not willing to make some information visible, then we<br />
shouldn't be encouraging them to store that information invisibly, for all<br />
the same reasons that invisible metadata is bad/futile in the first place."<br />
<br />
''I'd like to delete this below, as the points are covered above''<br />
<br />
* Theoretically, this could be done with almost any HTML element. But is it a good idea? If it's not, is abbr the only one? [[DavidJanes]]<br />
* abbr-design-pattern should be avoided, if possible. [[User:RobertBachmann|RobertBachmann]]<br />
** why, or under what circumstances? For example, it is quite useful with datetimes. Should there not be other potentially analogous situations? [[DavidJanes]]<br />
** Under circumstances where the text in the title would be gobbledegook if read by a screenreader. JAWS and other screenreaders use title attributes from abbr, when used properly (as in this example from the WCAG group), to pronounce words which would otherwise be unreadable or confusing. Using machine data such as datetime as a title is an bending of the dictionary definition of abbreviation (contraction by ommision or initialisation, applied at the word and not semantic level), this may not be a great issue in itself, but if screen readers are unable to turn title content into something comprehensible, this will lead to accessibility failures.<br />
<br />
<pre><br />
<p>Sugar is commonly sold in 5 <abbr title="pound">lb.<abbr> bags.</p><br />
<p>Welcome to the <abbr title="World Wide Web">WWW</abbr>!</p><br />
</pre><br />
<br />
== See Also ==<br />
* [[Main_Page#Design_Patterns|All microformat design patterns]]<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html discussion in microformats-discuss]<br />
* [[datetime-design-pattern]] uses [[abbr-design-pattern]]<br />
* [http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR HTML 4.01 definition]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=19284genealogy-formats2007-04-19T12:27:48Z<p>SeanHayes: /* GEDCOM */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
<br />
== In the wild ==<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/wc01/wc01_045.html this family group] is pretty much a direct translation of a gedcom FAM structure, but with some names added to the links. It also includes back links to parents.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/ps02/ps02_361.html an individual from the same tree] This is basically an INDI record from GEDCOM.<br />
<br />
== problem statement ==<br />
The main problem for geneaology on the web is that 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.<br />
<br />
If there were some kind of order to this process, ordinary web searching might be used; and we could interlink family trees more readily.<br />
<br />
[http://jay.askren.net/Projects/SemWeb/ RDF] and the semantic web has been used to tackle this problem, but this doesnt help people that want to publish, or search published trees until there is a real semantic web.<br />
<br />
What I think we need is some kind of microformat markup to add to examples like [http://jay.askren.net/Projects/SemWeb/FamilyTrees/AbrahamLincoln.html this tree of Abraham Lincoln].<br />
<br />
== GEDCOM ==<br />
<br />
GEDCOM has become pretty much the defacto standard for sharing data between geneaology systems, it is a transmission format. It is not specifically a format for geneaology, but rather a religious tool created by the Church of Jesus Christ of Latter-Day Saints who have a specific interest in family history. It is hierachical and link based, much like HTML; but it encodes family structure (which is a general graph) outside of this structural hierachy.<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* I'm not sure whether it makes sense to do GEDCOM as its own format, the FAM structure and the need to present different reports, suggest to me that we need some kind of post GEDCOM markup. To see how direct use of GEDCOM might pan out I hacked up this [[GEDCOM Worked example]]. To me the main issue seems to revolve around the FAM structure. I think the [http://jay.askren.net/Projects/SemWeb/ Jay Askren] approach might be better thsn the Gene Stark work as a starting point.<br />
<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
* GEDCOM is basically a set of INDIvidual records, related by FAMily nodes the family nodes contain the HUSBand, WIFE and CHILd. The INDI records are quite similar and might be replaced by hCard records, but the graph structure is a little harder to capture; families arent strict trees, so a direct mapping to XML doesnt really work. Publishing a GEDCOM database directly to the web might not be the most logical thing to do.<br />
<br />
* Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15804genealogy-formats2007-04-19T12:19:50Z<p>SeanHayes: /* In the wild */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
<br />
== In the wild ==<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/wc01/wc01_045.html this family group] is pretty much a direct translation of a gedcom FAM structure, but with some names added to the links. It also includes back links to parents.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/ps02/ps02_361.html an individual from the same tree] This is basically an INDI record from GEDCOM.<br />
<br />
== problem statement ==<br />
The main problem for geneaology on the web is that 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.<br />
<br />
If there were some kind of order to this process, ordinary web searching might be used; and we could interlink family trees more readily.<br />
<br />
[http://jay.askren.net/Projects/SemWeb/ RDF] and the semantic web has been used to tackle this problem, but this doesnt help people that want to publish, or search published trees until there is a real semantic web.<br />
<br />
What I think we need is some kind of microformat markup to add to examples like [http://jay.askren.net/Projects/SemWeb/FamilyTrees/AbrahamLincoln.html this tree of Abraham Lincoln].<br />
<br />
== GEDCOM ==<br />
<br />
GEDCOM has become pretty much the defacto standard for sharing data between geneaology systems, it is a transmission format. It is not specifically a format for geneaology, but rather a religious tool created by the Church of Jesus Christ of Latter-Day Saints who have a specific interest in family history. It is hierachical and link based, much like HTML; but it encodes family structure (which is a general graph) outside of this structural hierachy.<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.-[[User:SeanHayes|SeanHayes]] it might go away at any time. The issue seems to revolve around the FAM structure.<br />
<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
* GEDCOM is basically a set of INDIvidual records, related by FAMily nodes the family nodes contain the HUSBand, WIFE and CHILd. The INDI records are quite similar and might be replaced by hCard records, but the graph structure is a little harder to capture; families arent strict trees, so a direct mapping to XML doesnt really work. Publishing a GEDCOM database directly to the web might not be the most logical thing to do.<br />
<br />
* Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15803genealogy-formats2007-04-19T12:18:32Z<p>SeanHayes: /* problem statement */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
<br />
== In the wild ==<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/wc01/wc01_045.html] this is pretty much a direct translation of a gedcom FAM structure, but with some names added to the links. It also includes back links to parents.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/ps02/ps02_361.html an individual from the same tree] This is basically an INDI record from GEDCOM.<br />
<br />
== problem statement ==<br />
The main problem for geneaology on the web is that 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.<br />
<br />
If there were some kind of order to this process, ordinary web searching might be used; and we could interlink family trees more readily.<br />
<br />
[http://jay.askren.net/Projects/SemWeb/ RDF] and the semantic web has been used to tackle this problem, but this doesnt help people that want to publish, or search published trees until there is a real semantic web.<br />
<br />
What I think we need is some kind of microformat markup to add to examples like [http://jay.askren.net/Projects/SemWeb/FamilyTrees/AbrahamLincoln.html this tree of Abraham Lincoln].<br />
<br />
== GEDCOM ==<br />
<br />
GEDCOM has become pretty much the defacto standard for sharing data between geneaology systems, it is a transmission format. It is not specifically a format for geneaology, but rather a religious tool created by the Church of Jesus Christ of Latter-Day Saints who have a specific interest in family history. It is hierachical and link based, much like HTML; but it encodes family structure (which is a general graph) outside of this structural hierachy.<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.-[[User:SeanHayes|SeanHayes]] it might go away at any time. The issue seems to revolve around the FAM structure.<br />
<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
* GEDCOM is basically a set of INDIvidual records, related by FAMily nodes the family nodes contain the HUSBand, WIFE and CHILd. The INDI records are quite similar and might be replaced by hCard records, but the graph structure is a little harder to capture; families arent strict trees, so a direct mapping to XML doesnt really work. Publishing a GEDCOM database directly to the web might not be the most logical thing to do.<br />
<br />
* Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15802genealogy-formats2007-04-19T12:15:34Z<p>SeanHayes: </p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
<br />
== In the wild ==<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/wc01/wc01_045.html] this is pretty much a direct translation of a gedcom FAM structure, but with some names added to the links. It also includes back links to parents.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/ps02/ps02_361.html an individual from the same tree] This is basically an INDI record from GEDCOM.<br />
<br />
== problem statement ==<br />
The main problem for geneaology on the web is that 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.<br />
<br />
If there were some kind of order to this process, ordinary web searching might be used; and we could interlink family trees more readily.<br />
<br />
[http://jay.askren.net/Projects/SemWeb/ RDF] and the semantic web has been used to tackle this problem, but this doesnt help people that want to publish, or search published trees until there is a real semantic web.<br />
<br />
== GEDCOM ==<br />
<br />
GEDCOM has become pretty much the defacto standard for sharing data between geneaology systems, it is a transmission format. It is not specifically a format for geneaology, but rather a religious tool created by the Church of Jesus Christ of Latter-Day Saints who have a specific interest in family history. It is hierachical and link based, much like HTML; but it encodes family structure (which is a general graph) outside of this structural hierachy.<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.-[[User:SeanHayes|SeanHayes]] it might go away at any time. The issue seems to revolve around the FAM structure.<br />
<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
* GEDCOM is basically a set of INDIvidual records, related by FAMily nodes the family nodes contain the HUSBand, WIFE and CHILd. The INDI records are quite similar and might be replaced by hCard records, but the graph structure is a little harder to capture; families arent strict trees, so a direct mapping to XML doesnt really work. Publishing a GEDCOM database directly to the web might not be the most logical thing to do.<br />
<br />
* Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15801genealogy-formats2007-04-19T11:52:41Z<p>SeanHayes: /* GEDCOM */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
<br />
== In the wild ==<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/wc01/wc01_045.html] this is pretty much a direct translation of a gedcom FAM structure, but with some names added to the links. It also includes back links to parents.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/ps02/ps02_361.html an individual from the same tree] This is basically an INDI record from GEDCOM.<br />
<br />
== problem statement ==<br />
The main problem for geneaology on the web is that 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.<br />
<br />
If there were some kind of order to this process, ordinary web searching might be used; and we could interlink family trees more readily.<br />
<br />
== GEDCOM ==<br />
<br />
GEDCOM has become pretty much the defacto standard for sharing data between geneaology systems, it is a transmission format. It is not specifically a format for geneaology, but rather a religious tool created by the Church of Jesus Christ of Latter-Day Saints who have a specific interest in family history. It is hierachical and link based, much like HTML; but it encodes family structure (which is a general graph) outside of this structural hierachy.<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.-[[User:SeanHayes|SeanHayes]] it might go away at any time. The issue seems to revolve around the FAM structure.<br />
<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
* GEDCOM is basically a set of INDIvidual records, related by FAMily nodes the family nodes contain the HUSBand, WIFE and CHILd. The INDI records are quite similar and might be replaced by hCard records, but the graph structure is a little harder to capture; families arent strict trees, so a direct mapping to XML doesnt really work. Publishing a GEDCOM database directly to the web might not be the most logical thing to do.<br />
<br />
* Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15800genealogy-formats2007-04-19T11:46:41Z<p>SeanHayes: </p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
<br />
== In the wild ==<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/wc01/wc01_045.html] this is pretty much a direct translation of a gedcom FAM structure, but with some names added to the links. It also includes back links to parents.<br />
<br />
[http://www.comp.utas.edu.au/users/rsmith/levett/ps02/ps02_361.html an individual from the same tree] This is basically an INDI record from GEDCOM.<br />
<br />
== problem statement ==<br />
The main problem for geneaology on the web is that 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.<br />
<br />
If there were some kind of order to this process, ordinary web searching might be used; and we could interlink family trees more readily.<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.-[[User:SeanHayes|SeanHayes]] it might go away at any time. The issue seems to revolve around the FAM structure.<br />
<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
* GEDCOM is basically a set of INDIvidual records, related by FAMily nodes the family nodes contain the HUSBand, WIFE and CHILd. The INDI records are quite similar and might be replaced by hCard records, but the graph structure is a little harder to capture; families arent strict trees, so a direct mapping to XML doesnt really work. Publishing a GEDCOM database directly to the web might not be the most logical thing to do.<br />
<br />
* Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=32073GEDCOM Worked example2007-04-19T11:33:45Z<p>SeanHayes: </p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
Actually this document '''is part of''' the [[genealogy-formats|genealogy exploration]] process. This is a work in progress. think of it as an extended public brainfart if it helps. It is simple exploring some ideas from that discussion.<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<br />
The below is a pretty literal translation of the above. GEDCOM uses a hierachical record structure, which maps to XML relatively easily, and also uses links which map reasonably well to id and <a> in HTML. I've done a simple styling here which positions the family grouping. I'll try and get this up on a webserver somewhere soon. This is not really a proposal at this stage, but an exploration to see if a GEDCOM microformat even makes sense.<br />
<br />
<br />
<pre><br />
<nowiki><br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<title>Enter the title of your XHTML document here</title><br />
<style type="text/css"><br />
.CHAN { display:none }<br />
.HEAD { display:none }<br />
.INDI { font-family:'Arial'; font-size:7pt; position: absolute; width:20em; height:14; left: 0; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } .MARR { font-family:'Arial'; font-size:7pt; position: absolute; left:21em; top:4.5em; width:9.7em; height:14; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAM { font-family:'Arial'; font-size:7pt; position: absolute; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAMS { font-family:'Arial'; font-size:6pt; padding-left: 20em; } <br />
</style><br />
</head><br />
<body><br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<div id="I1" class="INDI" style="left:10em; top:10em"><br />
<div class="NAME"><br />
Edward Sean<br />
<span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"><br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I2" class="INDI" style="left:40em; top:10em"><br />
<div class="NAME"><br />
Tamsin Clare <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">25 JUL 1963</div><br />
<div class="PLAC">London</div><br />
</div><br />
<div class="OCCU">Therapist</div><br />
<div class="EDUC">School</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I3" class="INDI" style="left:10em; top:30em"><br />
<div class="NAME"><br />
Alice Rose <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">17 FEB 1986</div><br />
<div class="PLAC">Park Royal Hospital London</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">BristolCollege</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I4" class="INDI" style="left:40em; top:30em"><br />
<div class="NAME"><br />
Megan Christine <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">21 NOV 1988</div><br />
<div class="PLAC">Southmead Hospital Bristol</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">Bristol College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div class="FAM" id="F1" style="left:9em; top:8em; width:52em; height:32em; "><br />
<a class="HUSB" href="#I1"> @I1@</a><br />
<a class="WIFE" href="#I2"> @I2@</a><br />
<a class="CHIL" href="#I3"> @I3@</a><br />
<a class="CHIL" href="#I4"> @I4@</a><br />
<div class="MARR"><br />
<div class="DATE"> 25 SEP 1985</div><br />
<div class="PLAC"> London</div><br />
</div><br />
</div><br />
</div><br />
</body><br />
</html><br />
<br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
*The INDI records could be replaced by hCard records. Need to look at a tag by tag mapping here.<br />
<br />
*This example doesnt use EVENt tags, which might map to hCalendar<br />
<br />
*The FAM records are the graph structure. This is really what is needed over and above an hCard, along with the more specialised SOURce records which record documentaiton (hCite?). <br />
<br />
*It's basically a linkage structure, made slightly more complicated by the fact that an INDIvidual can appear in more than one FAMily record. e.g. if they remarry. rather than a specific geneaology microformat, maybe a general hGraph structure might be appropriate?</div>SeanHayeshttps://microformats.org/wiki/index.php?title=abbr-design-pattern&diff=15836abbr-design-pattern2007-04-19T11:11:32Z<p>SeanHayes: /* Discussion */</p>
<hr />
<div>= Abbr design pattern =<br />
<br />
== Purpose ==<br />
* Use the [[abbr-design-pattern]] to make text that is human readable also formally machine readable<br />
* Avoiding using the [[abbr-design-pattern]] to re-encode human text or to hide data<br />
<br />
== How to use it ==<br />
* enclose the human-friendly text that you want to make machine readable with <code>&lt;abbr></code> <br />
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element<br />
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable data as the value<br />
<br />
== Example ==<br />
The [[datetime-design-pattern]] formally encodes (the notoriously unparsable) datetimes into an <code>abbr</code> element.<br />
<br />
Before:<br />
<br />
<pre><br />
The party is at 10 o'clock on the 10th.<br />
</pre><br />
<br />
After:<br />
<br />
<pre><br />
The party is at <br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr>.<br />
</pre><br />
<br />
== Discussion ==<br />
''This discussion is culled from [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html here]''. Consider two possible uses for the [[abbr-design-pattern]]:<br />
<br />
<ol><br />
<li><br />
using ABBR to encode machine readable data around human readable data<br />
<br />
<pre><br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr><br />
</pre><br />
</li><br />
<li><br />
using ABBR to encode more formal human data around something less formal <br />
<br />
<pre><br />
<abbr class="author" title="Danny Ayers">Danny</abbr> <br />
</pre><br />
</li><br />
</ol><br />
<br />
Use #1 is encouraged if there's a reasonable need for it. Use #2 is discouraged under the [http://c2.com/cgi-bin/wiki?DontRepeatYourself Don't Repeat Yourself principle], as: "#2 is a case of *more* information being invisibly present, namely, the<br />
last name in this case. If someone is not willing to make some information visible, then we<br />
shouldn't be encouraging them to store that information invisibly, for all<br />
the same reasons that invisible metadata is bad/futile in the first place."<br />
<br />
''I'd like to delete this below, as the points are covered above''<br />
<br />
* Theoretically, this could be done with almost any HTML element. But is it a good idea? If it's not, is abbr the only one? [[DavidJanes]]<br />
* abbr-design-pattern should be avoided, if possible. [[User:RobertBachmann|RobertBachmann]]<br />
** why, or under what circumstances? For example, it is quite useful with datetimes. Should there not be other potentially analogous situations? [[DavidJanes]]<br />
** Under circumstances where the text in the title would be gobbledegook if read by a screenreader. JAWS and other screenreaders use abbr, when used properly (as in this example from the WCAG group) to pronounce words which would otherwise be unreadable or confusing. Using Datetime as a title might technically be a correct semantic use of abbr, but until screen readers can turn DATETIME's into something comprehensible, this will lead to poor accessibility.<br />
<br />
<pre><br />
<p>Sugar is commonly sold in 5 <abbr title="pound">lb.<abbr> bags.</p><br />
<p>Welcome to the <abbr title="World Wide Web">WWW</abbr>!</p><br />
</pre><br />
<br />
== See Also ==<br />
* [[Main_Page#Design_Patterns|All microformat design patterns]]<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html discussion in microformats-discuss]<br />
* [[datetime-design-pattern]] uses [[abbr-design-pattern]]<br />
* [http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR HTML 4.01 definition]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=abbr-design-pattern&diff=15797abbr-design-pattern2007-04-19T11:10:32Z<p>SeanHayes: /* Discussion */</p>
<hr />
<div>= Abbr design pattern =<br />
<br />
== Purpose ==<br />
* Use the [[abbr-design-pattern]] to make text that is human readable also formally machine readable<br />
* Avoiding using the [[abbr-design-pattern]] to re-encode human text or to hide data<br />
<br />
== How to use it ==<br />
* enclose the human-friendly text that you want to make machine readable with <code>&lt;abbr></code> <br />
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element<br />
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable data as the value<br />
<br />
== Example ==<br />
The [[datetime-design-pattern]] formally encodes (the notoriously unparsable) datetimes into an <code>abbr</code> element.<br />
<br />
Before:<br />
<br />
<pre><br />
The party is at 10 o'clock on the 10th.<br />
</pre><br />
<br />
After:<br />
<br />
<pre><br />
The party is at <br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr>.<br />
</pre><br />
<br />
== Discussion ==<br />
''This discussion is culled from [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html here]''. Consider two possible uses for the [[abbr-design-pattern]]:<br />
<br />
<ol><br />
<li><br />
using ABBR to encode machine readable data around human readable data<br />
<br />
<pre><br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr><br />
</pre><br />
</li><br />
<li><br />
using ABBR to encode more formal human data around something less formal <br />
<br />
<pre><br />
<abbr class="author" title="Danny Ayers">Danny</abbr> <br />
</pre><br />
</li><br />
</ol><br />
<br />
Use #1 is encouraged if there's a reasonable need for it. Use #2 is discouraged under the [http://c2.com/cgi-bin/wiki?DontRepeatYourself Don't Repeat Yourself principle], as: "#2 is a case of *more* information being invisibly present, namely, the<br />
last name in this case. If someone is not willing to make some information visible, then we<br />
shouldn't be encouraging them to store that information invisibly, for all<br />
the same reasons that invisible metadata is bad/futile in the first place."<br />
<br />
''I'd like to delete this below, as the points are covered above''<br />
<br />
* Theoretically, this could be done with almost any HTML element. But is it a good idea? If it's not, is abbr the only one? [[DavidJanes]]<br />
* abbr-design-pattern should be avoided, if possible. [[User:RobertBachmann|RobertBachmann]]<br />
** why, or under what circumstances? For example, it is quite useful with datetimes. Should there not be other potentially analogous situations? [[DavidJanes]]<br />
** Under circumstances where the text in the title would be gobbledegook if read by a screenreader. JAWS and other screenreaders use abbr, when used properly (as in this example from the WCAG group) to pronounce words which would otherwise be unreadable or confusing.<br />
<pre><br />
<p>Sugar is commonly sold in 5 <abbr title="pound">lb.<abbr> bags.</p><br />
<p>Welcome to the <abbr title="World Wide Web">WWW</abbr>!</p><br />
</pre><br />
Using Datetime as a title might technically be a correct semantic use of abbr, but until screen readers can turn DATETIME's into something comprehensible, this will lead to poor accessibility.<br />
<br />
== See Also ==<br />
* [[Main_Page#Design_Patterns|All microformat design patterns]]<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html discussion in microformats-discuss]<br />
* [[datetime-design-pattern]] uses [[abbr-design-pattern]]<br />
* [http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR HTML 4.01 definition]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=abbr-design-pattern&diff=15796abbr-design-pattern2007-04-19T11:08:42Z<p>SeanHayes: /* Discussion */</p>
<hr />
<div>= Abbr design pattern =<br />
<br />
== Purpose ==<br />
* Use the [[abbr-design-pattern]] to make text that is human readable also formally machine readable<br />
* Avoiding using the [[abbr-design-pattern]] to re-encode human text or to hide data<br />
<br />
== How to use it ==<br />
* enclose the human-friendly text that you want to make machine readable with <code>&lt;abbr></code> <br />
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element<br />
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable data as the value<br />
<br />
== Example ==<br />
The [[datetime-design-pattern]] formally encodes (the notoriously unparsable) datetimes into an <code>abbr</code> element.<br />
<br />
Before:<br />
<br />
<pre><br />
The party is at 10 o'clock on the 10th.<br />
</pre><br />
<br />
After:<br />
<br />
<pre><br />
The party is at <br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr>.<br />
</pre><br />
<br />
== Discussion ==<br />
''This discussion is culled from [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html here]''. Consider two possible uses for the [[abbr-design-pattern]]:<br />
<br />
<ol><br />
<li><br />
using ABBR to encode machine readable data around human readable data<br />
<br />
<pre><br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr><br />
</pre><br />
</li><br />
<li><br />
using ABBR to encode more formal human data around something less formal <br />
<br />
<pre><br />
<abbr class="author" title="Danny Ayers">Danny</abbr> <br />
</pre><br />
</li><br />
</ol><br />
<br />
Use #1 is encouraged if there's a reasonable need for it. Use #2 is discouraged under the [http://c2.com/cgi-bin/wiki?DontRepeatYourself Don't Repeat Yourself principle], as: "#2 is a case of *more* information being invisibly present, namely, the<br />
last name in this case. If someone is not willing to make some information visible, then we<br />
shouldn't be encouraging them to store that information invisibly, for all<br />
the same reasons that invisible metadata is bad/futile in the first place."<br />
<br />
''I'd like to delete this below, as the points are covered above''<br />
<br />
* Theoretically, this could be done with almost any HTML element. But is it a good idea? If it's not, is abbr the only one? [[DavidJanes]]<br />
* abbr-design-pattern should be avoided, if possible. [[User:RobertBachmann|RobertBachmann]]<br />
** why, or under what circumstances? For example, it is quite useful with datetimes. Should there not be other potentially analogous situations? [[DavidJanes]]<br />
** Under circumstances where the text in the title would be gobbledegook if read by a screenreader. JAWS and other screenreaders use abbr, when used properly (as in this example from the WCAG group) to pronounce words which would otherwise be unreadable or confusing.<br />
<br />
<pre><br />
<p>Sugar is commonly sold in 5 <abbr title="pound">lb.<abbr> bags.</p><br />
<p>Welcome to the <abbr title="World Wide Web">WWW</abbr>!</p><br />
</pre><br />
<br />
A Datetime as a title would not be a good use of abbr, and is using abbr in the wrong direction.<br />
<br />
== See Also ==<br />
* [[Main_Page#Design_Patterns|All microformat design patterns]]<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html discussion in microformats-discuss]<br />
* [[datetime-design-pattern]] uses [[abbr-design-pattern]]<br />
* [http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR HTML 4.01 definition]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=datetime-design-pattern&diff=16005datetime-design-pattern2007-04-19T10:46:03Z<p>SeanHayes: /* Current uses */</p>
<hr />
<div>'''This page is a draft.'''<br />
<br />
= Datetime Design Pattern =<br />
This is a page for exploring a datetime design pattern.<br />
<br />
== Purpose ==<br />
* Use the [[datetime-design-pattern]] to make datetimes that are human readable also formally machine readable.<br />
<br />
== Practical Need ==<br />
* This design pattern arose as a result of solving the practical need for human readable dates for [[hcalendar|hCalendar]].<br />
<br />
== How to use it ==<br />
* enclose the human-friendly datetime that you want to make machine readable with <code>&lt;abbr></code> <br />
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element<br />
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable ISO8601 datetime or date as the value<br />
<br />
== Current uses ==<br />
<br />
'''note using these formats will mean your content will likely fail WCAG2.0 accessibility'''<br />
<br />
The pattern which is now used in [[hcalendar|hCalendar]] and [[hreview|hReview]] is something like this:<br />
<br />
<pre>&lt;abbr class="foo" title="YYYY-MM-DDTHH:MM:SS+ZZ:ZZ"&gt;Date Time&lt;/abbr&gt;</pre><br />
<br />
where foo is the semantic classname which is being applied to this date/time, the title of the &lt;abbr&gt; is an ISO 8601 date/time and "Date Time" is a human-friendly representation of the same date/time.<br />
<br />
<br />
An alternative, if you are using UTC-based timestamps, would be:<br />
<br />
<pre>&lt;abbr class="foo" title="YYYY-MM-DDTHH:MM:SSZ"&gt;Date Time&lt;/abbr&gt;</pre><br />
<br />
with a single "Z" as per [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]<br />
<br />
== Profile of ISO8601 ==<br />
<br />
We recommend that any [[microformat]] using the date-time-design pattern use a profile of ISO8601. There are currently two widely used profiles which SHOULD be reused.<br />
<br />
* RFC 3339<br />
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Datetimes] <br />
<br />
<br />
== Discussion ==<br />
<br />
This pattern is likely to be highly resuable.<br />
<br />
--[[User:RyanKing]]<br />
<br />
Can this not be viewed as a microformat in itself?<br />
<br />
--[[User:DimitriGlazkov]]<br />
<br />
It could, but inventing a microformat for the sake of inventing a microformat is against the microformat principles.<br />
If there is a specific real world problem (and uses cases) that such an elemental microformat would solve, then it would be worth considering.<br />
<br />
Until then it is best to keep the &lt;abbr&gt; datetime concept merely as a microformat design pattern, to be used in _actual_ microformats that have a demonstrated practical need.<br />
<br />
-- [http://tantek.com/log/ Tantek]<br />
<br />
Excerpt from #microformats Aug 18th. Please edit!<br />
<br />
<pre><br />
Aug 18 15:16:14 <Tantek> DanC, what do you think of RFC3339?<br />
Aug 18 15:17:14 <Tantek> ISO8601 subset<br />
Aug 18 15:17:19 <DanC> Date and Time on the Internet: Timestamps http://www.ietf.org/rfc/rfc3339.txt<br />
Aug 18 15:17:30 <DanC> Klyne is a good guy. I wonder if I talked with him about this.<br />
Aug 18 15:17:32 <Tantek> compat with W3C-NOTE-DATETIME<br />
Aug 18 15:17:50 <Tantek> compat with xsd:dateTime<br />
Aug 18 15:17:57 <Tantek> it's a strict intersection subset<br />
Aug 18 15:17:59 <DanC> I consider W3C-NOTE-DATETIME obsoleted by XML Schema datatype-- yeah.. xsd:dateTime<br />
Aug 18 15:18:32 <Tantek> compare/contrast normatively using xsd:dateTime vs. RFC3339<br />
Aug 18 15:18:41 <Tantek> note: Atom 1.0 chose RFC3339<br />
Aug 18 15:18:50 <Tantek> i would like input from the microformats community on this<br />
Aug 18 15:19:27 <DanC> in what context are you evaluating RFC 3339?<br />
Aug 18 15:19:28 <jcgregorio> http://bitworking.org/news/Date_Constructs_in_the_Atom_Syndication_Format<br />
Aug 18 15:21:24 <DanC> which microformat is the question coming from, Tantek ?<br />
Aug 18 15:23:31 <DanC> " The grammar element time-second may have the value "60" at the end of<br />
Aug 18 15:23:31 <DanC> months in which a leap second occurs" The XML Schema WG is in the 27th level of<br />
leap-second-hell for the past few months, I gather.<br />
Aug 18 15:24:21 <DanC> yeah... here's the scary bit: " Leap seconds cannot be predicted far into the<br />
future. The<br />
Aug 18 15:24:21 <DanC> International Earth Rotation Service publishes bulletins [IERS] that<br />
Aug 18 15:24:21 <DanC> announce leap seconds with a few weeks' warning."<br />
Aug 18 15:26:03 <Tantek> DanC, which microformats? any/all that use datetime fields.<br />
Aug 18 15:26:36 <DanC> hard to give useful advice, then.<br />
Aug 18 15:26:58 <DanC> I expect they'll use datetime fields for different things that have different<br />
cost/benefit trade-offs<br />
Aug 18 15:27:26 <DanC> do you know of any particular differences that matter to anybody?<br />
Aug 18 15:56:43 <KragenSitaker> RFC3339 suggests -07:00, which seems like an improvement over -0700 anyway<br />
Aug 18 15:56:49 <Tantek> Kragen, agreed<br />
Aug 18 15:57:01 <Tantek> RFC3339 is certainly preferable to the ISO8601 subset in iCalendar<br />
Aug 18 16:05:57 <DanC> Tantek's right, Kragen; iCalendar looks like it solves the local timezone<br />
problem but doesn't.<br />
Aug 18 16:06:14 <DanC> and it's true that there's no standard solution to the local timezone problem<br />
Aug 18 16:06:39 <Tantek> so instead of appearing to solve the problem but not solving it, we chose to<br />
provide the ability to *approximate* the local timezone using e.g. "-07:00"<br />
Aug 18 16:06:49 <DanC> the simplest thing is to have people use Z time in hCalendar. But I gather<br />
that's unacceptably unusable?<br />
Aug 18 16:07:35 <Tantek> DanC, yes, the simplest thing is to have everyone use UTC Z<br />
Aug 18 16:07:38 <Tantek> However<br />
Aug 18 16:07:50 <Tantek> it is not *nearly* as usuable/verifiable<br />
Aug 18 16:07:55 <Tantek> as -07:00 etc.<br />
Aug 18 16:08:02 <Tantek> hence the decision to go with the latter<br />
Aug 18 16:08:12 <Tantek> some degree of human verifiability is important here<br />
Aug 18 16:14:21 <Tantek> DanC, my perception is that RFC3339 is a subset<br />
Aug 18 16:17:00 <DanC> time-numoffset = ("+" / "-") time-hour ":" time-minute<br />
Aug 18 16:17:34 <DanC> ok, then I can't see any differences. (modulo recent leap seconds issues that<br />
may affect xsd:dateTime )<br />
Aug 18 16:18:07 <Tantek> would be interesting to know why Atom 1.0 chose RFC3339 over xsd:dateTime<br />
Aug 18 16:18:21 <Tantek> if there was a "real" reason or if it was arbitrary / coin-flip.<br />
</pre><br />
<br />
Here's an exhaustive [http://www.imc.org/atom-syntax/mail-archive/msg13103.html comparison] from ndw. I think xsd:dateTime also allows unqualified local times, while RFC3339 allows only UTC with no known timezone (-00:00). In the end, Atompub followed the advice of [http://www.imc.org/atom-syntax/mail-archive/msg13244.html Sam Ruby] and [http://www.imc.org/atom-syntax/mail-archive/msg13248.html Scott Hollenbeck], our area director. Atom dates make some additional restrictions on RFC3339, such as uppercase T and Z characters for compatibility with xsd:dateTime, RFC3339, W3C-DTF, and ISO8601. --[http://franklinmint.fm Robert Sayre]<br />
<br />
<pre><br />
Aug 18 16:18:43 <KragenSitaker> rfc3339 is pretty short.<br />
Aug 18 16:19:36 <Tantek> DanC, BTW, which came first? REC for xsd:dateTime or RFC3339?<br />
Aug 18 16:19:50 <DanC> RFC3339 is dated July 2002 ...<br />
Aug 18 16:19:54 <KragenSitaker> Right --- and you might be able to understand xsd:dateTime without<br />
reading all of xml schema, you wouldn't be confident of it<br />
Aug 18 16:20:25 <DanC> W3C Recommendation 28 October 2004 ... but that's 2nd ed...<br />
Aug 18 16:20:47 <DanC> W3C Recommendation 02 May 2001<br />
Aug 18 16:22:10 <DanC> I don't see a BNF in http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dateTime ...<br />
Aug 18 16:22:43 <KragenSitaker> yeah, appendix D of the current xml schema datatypes document seems<br />
a little scanty, actually<br />
Aug 18 16:23:28 <DanC> ah... 2nd ed of http://www.w3.org/TR/xmlschema-2/#date is much more<br />
explicit about syntax.<br />
Aug 18 16:23:30 <KragenSitaker> it's 1100 words but still doesn't give any examples<br />
Aug 18 16:23:35 <DanC> still, it's given in prose and not BNF<br />
Aug 18 16:24:17 <KragenSitaker> sections 3.2.9 through 3.2.14 seem to be the relevant ones around #date<br />
Aug 18 16:24:29 <KragenSitaker> which is another 2200 words<br />
Aug 18 16:24:42 <DanC> wow... they changed the canonical form of date from always-Z to<br />
timezone-allowed between 1st edition and 2nd edition<br />
Aug 18 16:25:01 <Tantek> Kragen, DanC, these are very good analyses<br />
Aug 18 16:25:21 <Tantek> could I ask you to summarize the pros/cons for each in a new section at<br />
end of http://microformats.org/wiki/datetime-design-pattern<br />
Aug 18 16:25:22 <Tantek> ?<br />
Aug 18 16:25:58 <KragenSitaker> rfc 3339 is 4000 words, excluding the last two pages of boilerplate.<br />
Aug 18 16:26:31 <KragenSitaker> so it's actually longer than the datetime-relevant parts of XSD but it<br />
seems much more rigorous and clear<br />
Aug 18 16:28:37 <DanC> my advice is: normatively cite both, and claim they specify the same<br />
syntax, and let anybody who discovers otherwise send you a bug report<br />
with a test case<br />
Aug 18 16:29:12 <KragenSitaker> danc: nice hack<br />
</pre><br />
<br />
<br />
The RFC3339 has a mandatory TIME portion of the DATE-TIME. Some vCard/iCalendar DATE-TIME stamps can omit the TIME. For instance, DTSTART, if that is a full day event, then you can omit the time. BDAY in vCard can be respresented by only a DATE. I like the idea of restricting the possible date formats, but i think that TIME should be optional, which it isn't in RFC3339. - [http://suda.co.uk/ brian suda]<br />
<br />
RFC 3339 allows lowercase 't' and 'z' while XSD doesn't. Specifying RFC 3339 plus 'T' and 'Z' MUST be caps will make them the same. - [http://bitworking.org Joe Gregorio]<br />
<br />
<br />
<br />
== Code ==<br />
The following regular expression (parsed VERBOSE) should break apart a datetime and cover many lightly broken cases seen in the wild. This has been tested under Python.<br />
<br />
<pre><nowiki><br />
^<br />
(?P<year>\d\d\d\d)<br />
([-])?(?P<month>\d\d)<br />
([-])?(?P<day>\d\d)<br />
(<br />
(T|\s+)<br />
(?P<hour>\d\d)<br />
(<br />
([:])?(?P<minute>\d\d)<br />
(<br />
([:])?(?P<second>\d\d)<br />
(<br />
([.])?(?P<fraction>\d+)<br />
)?<br />
)?<br />
)?<br />
)?<br />
(<br />
(?P<tzzulu>Z)<br />
|<br />
(?P<tzoffset>[-+])<br />
(?P<tzhour>\d\d)<br />
([:])?(?P<tzminute>\d\d)<br />
)?<br />
$<br />
</nowiki></pre><br />
<br />
== See Also ==<br />
<br />
* [[Main_Page#Design_Patterns|All microformat design patterns]]<br />
* [[abbr-design-pattern]] is used by [[datetime-design-pattern]]<br />
* HTML 4.01 definition of <code>&lt;[http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR abbr]></code> element<br />
* RFC [http://www.faqs.org/rfcs/rfc3339.html 3339]: Date and Time on the Internet: Timestamps<br />
* W3C: [http://www.w3.org/TR/NOTE-datetime Note on Datetimes] <br />
* Markus Kuhn: [http://www.cl.cam.ac.uk/~mgk25/iso-time.html A summary of the international standard date and time notation]<br />
* Wikipedia: [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=abbr-design-pattern&diff=15795abbr-design-pattern2007-04-19T10:42:35Z<p>SeanHayes: /* Discussion */</p>
<hr />
<div>= Abbr design pattern =<br />
<br />
== Purpose ==<br />
* Use the [[abbr-design-pattern]] to make text that is human readable also formally machine readable<br />
* Avoiding using the [[abbr-design-pattern]] to re-encode human text or to hide data<br />
<br />
== How to use it ==<br />
* enclose the human-friendly text that you want to make machine readable with <code>&lt;abbr></code> <br />
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element<br />
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable data as the value<br />
<br />
== Example ==<br />
The [[datetime-design-pattern]] formally encodes (the notoriously unparsable) datetimes into an <code>abbr</code> element.<br />
<br />
Before:<br />
<br />
<pre><br />
The party is at 10 o'clock on the 10th.<br />
</pre><br />
<br />
After:<br />
<br />
<pre><br />
The party is at <br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr>.<br />
</pre><br />
<br />
== Discussion ==<br />
''This discussion is culled from [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html here]''. Consider two possible uses for the [[abbr-design-pattern]]:<br />
<br />
<ol><br />
<li><br />
using ABBR to encode machine readable data around human readable data<br />
<br />
<pre><br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr><br />
</pre><br />
</li><br />
<li><br />
using ABBR to encode more formal human data around something less formal <br />
<br />
<pre><br />
<abbr class="author" title="Danny Ayers">Danny</abbr> <br />
</pre><br />
</li><br />
</ol><br />
<br />
Use #1 is encouraged if there's a reasonable need for it. Use #2 is discouraged under the [http://c2.com/cgi-bin/wiki?DontRepeatYourself Don't Repeat Yourself principle], as: "#2 is a case of *more* information being invisibly present, namely, the<br />
last name in this case. If someone is not willing to make some information visible, then we<br />
shouldn't be encouraging them to store that information invisibly, for all<br />
the same reasons that invisible metadata is bad/futile in the first place."<br />
<br />
''I'd like to delete this below, as the points are covered above''<br />
<br />
* Theoretically, this could be done with almost any HTML element. But is it a good idea? If it's not, is abbr the only one? [[DavidJanes]]<br />
* abbr-design-pattern should be avoided, if possible. [[User:RobertBachmann|RobertBachmann]]<br />
** why, or under what circumstances? For example, it is quite useful with datetimes. Should there not be other potentially analogous situations? [[DavidJanes]]<br />
<br />
** Under circumstances where the text in the title would be gobbledegook if read by a screenreader. JAWS and other screenreaders use abbr, when used properly (as in this example from the WCAG group) to pronounce words which would otherwise be unreadable or confusing.<br />
<br />
<pre><br />
<p>Sugar is commonly sold in 5 <abbr title="pound">lb.<abbr> bags.</p><br />
<p>Welcome to the <abbr title="World Wide Web">WWW</abbr>!</p><br />
</pre><br />
<br />
A Datetime as a title would not be a good use of abbr, and is using abbr in the wrong direction.<br />
<br />
== See Also ==<br />
* [[Main_Page#Design_Patterns|All microformat design patterns]]<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html discussion in microformats-discuss]<br />
* [[datetime-design-pattern]] uses [[abbr-design-pattern]]<br />
* [http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR HTML 4.01 definition]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15799genealogy-formats2007-04-19T10:16:25Z<p>SeanHayes: </p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.-[[User:SeanHayes|SeanHayes]] it might go away at any time.<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
* GEDCOM is basically a set of INDIvidual records, related by FAMily nodes the family nodes contain the HUSBand, WIFE and CHILd. The INDI records are quite similar and might be replaced by hCard records, but the graph structure is a little harder to capture; families arent strict trees, so a direct mapping to XML doesnt really work. Publishing a GEDCOM database directly to the web might not be the most logical thing to do.<br />
<br />
* Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15798GEDCOM Worked example2007-04-19T10:15:15Z<p>SeanHayes: </p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
Actually this document '''is''' the process. This is a work in progress. think of it as an extended public brainfart if it helps. It is building on some ideas from, and will go in the main [[genealogy-formats|genealogy exploration]] section when done<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<br />
The below is a pretty literal translation of the above. GEDCOM uses a hierachical record structure, which maps to XML relatively easily, and also uses links which map reasonably well to id and <a> in HTML. I've done a simple styling here which positions the family grouping. I'll try and get this up on a webserver somewhere soon. This is not really a proposal at this stage, but an exploration to see if a GEDCOM microformat even makes sense.<br />
<br />
<br />
<pre><br />
<nowiki><br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<title>Enter the title of your XHTML document here</title><br />
<style type="text/css"><br />
.CHAN { display:none }<br />
.HEAD { display:none }<br />
.INDI { font-family:'Arial'; font-size:7pt; position: absolute; width:20em; height:14; left: 0; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } .MARR { font-family:'Arial'; font-size:7pt; position: absolute; left:21em; top:4.5em; width:9.7em; height:14; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAM { font-family:'Arial'; font-size:7pt; position: absolute; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAMS { font-family:'Arial'; font-size:6pt; padding-left: 20em; } <br />
</style><br />
</head><br />
<body><br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<div id="I1" class="INDI" style="left:10em; top:10em"><br />
<div class="NAME"><br />
Edward Sean<br />
<span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"><br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I2" class="INDI" style="left:40em; top:10em"><br />
<div class="NAME"><br />
Tamsin Clare <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">25 JUL 1963</div><br />
<div class="PLAC">London</div><br />
</div><br />
<div class="OCCU">Therapist</div><br />
<div class="EDUC">School</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I3" class="INDI" style="left:10em; top:30em"><br />
<div class="NAME"><br />
Alice Rose <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">17 FEB 1986</div><br />
<div class="PLAC">Park Royal Hospital London</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">BristolCollege</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I4" class="INDI" style="left:40em; top:30em"><br />
<div class="NAME"><br />
Megan Christine <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">21 NOV 1988</div><br />
<div class="PLAC">Southmead Hospital Bristol</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">Bristol College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div class="FAM" id="F1" style="left:9em; top:8em; width:52em; height:32em; "><br />
<a class="HUSB" href="#I1"> @I1@</a><br />
<a class="WIFE" href="#I2"> @I2@</a><br />
<a class="CHIL" href="#I3"> @I3@</a><br />
<a class="CHIL" href="#I4"> @I4@</a><br />
<div class="MARR"><br />
<div class="DATE"> 25 SEP 1985</div><br />
<div class="PLAC"> London</div><br />
</div><br />
</div><br />
</div><br />
</body><br />
</html><br />
<br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
*The INDI records could be replaced by hCard records. Need to look at a tag by tag mapping here.<br />
<br />
*This example doesnt use EVENt tags, which might map to hCalendar<br />
<br />
*The FAM records are the graph structure. This is really what is needed over and above an hCard, along with the more specialised SOURce records which record documentaiton (hCite?). <br />
<br />
*It's basically a linkage structure, made slightly more complicated by the fact that an INDIvidual can appear in more than one FAMily record. e.g. if they remarry. rather than a specific geneaology microformat, maybe a general hGraph structure might be appropriate?</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15786GEDCOM Worked example2007-04-19T10:13:59Z<p>SeanHayes: /* Notes */</p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
I Know that. This is a work in progress. think of it as an extended public brainfart if it helps., it will go in the main [[genealogy-formats|genealogy exploration]] section when I'm done<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<br />
The below is a pretty literal translation of the above. GEDCOM uses a hierachical record structure, which maps to XML relatively easily, and also uses links which map reasonably well to id and <a> in HTML. I've done a simple styling here which positions the family grouping. I'll try and get this up on a webserver somewhere soon. This is not really a proposal at this stage, but an exploration to see if a GEDCOM microformat even makes sense.<br />
<br />
<br />
<pre><br />
<nowiki><br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<title>Enter the title of your XHTML document here</title><br />
<style type="text/css"><br />
.CHAN { display:none }<br />
.HEAD { display:none }<br />
.INDI { font-family:'Arial'; font-size:7pt; position: absolute; width:20em; height:14; left: 0; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } .MARR { font-family:'Arial'; font-size:7pt; position: absolute; left:21em; top:4.5em; width:9.7em; height:14; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAM { font-family:'Arial'; font-size:7pt; position: absolute; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAMS { font-family:'Arial'; font-size:6pt; padding-left: 20em; } <br />
</style><br />
</head><br />
<body><br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<div id="I1" class="INDI" style="left:10em; top:10em"><br />
<div class="NAME"><br />
Edward Sean<br />
<span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"><br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I2" class="INDI" style="left:40em; top:10em"><br />
<div class="NAME"><br />
Tamsin Clare <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">25 JUL 1963</div><br />
<div class="PLAC">London</div><br />
</div><br />
<div class="OCCU">Therapist</div><br />
<div class="EDUC">School</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I3" class="INDI" style="left:10em; top:30em"><br />
<div class="NAME"><br />
Alice Rose <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">17 FEB 1986</div><br />
<div class="PLAC">Park Royal Hospital London</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">BristolCollege</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I4" class="INDI" style="left:40em; top:30em"><br />
<div class="NAME"><br />
Megan Christine <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">21 NOV 1988</div><br />
<div class="PLAC">Southmead Hospital Bristol</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">Bristol College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div class="FAM" id="F1" style="left:9em; top:8em; width:52em; height:32em; "><br />
<a class="HUSB" href="#I1"> @I1@</a><br />
<a class="WIFE" href="#I2"> @I2@</a><br />
<a class="CHIL" href="#I3"> @I3@</a><br />
<a class="CHIL" href="#I4"> @I4@</a><br />
<div class="MARR"><br />
<div class="DATE"> 25 SEP 1985</div><br />
<div class="PLAC"> London</div><br />
</div><br />
</div><br />
</div><br />
</body><br />
</html><br />
<br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
*The INDI records could be replaced by hCard records. Need to look at a tag by tag mapping here.<br />
<br />
*This example doesnt use EVENt tags, which might map to hCalendar<br />
<br />
*The FAM records are the graph structure. This is really what is needed over and above an hCard, along with the more specialised SOURce records which record documentaiton (hCite?). <br />
<br />
*It's basically a linkage structure, made slightly more complicated by the fact that an INDIvidual can appear in more than one FAMily record. e.g. if they remarry. rather than a specific geneaology microformat, maybe a general hGraph structure might be appropriate?</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15783GEDCOM Worked example2007-04-19T10:13:25Z<p>SeanHayes: /* Notes */</p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
I Know that. This is a work in progress. think of it as an extended public brainfart if it helps., it will go in the main [[genealogy-formats|genealogy exploration]] section when I'm done<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<br />
The below is a pretty literal translation of the above. GEDCOM uses a hierachical record structure, which maps to XML relatively easily, and also uses links which map reasonably well to id and <a> in HTML. I've done a simple styling here which positions the family grouping. I'll try and get this up on a webserver somewhere soon. This is not really a proposal at this stage, but an exploration to see if a GEDCOM microformat even makes sense.<br />
<br />
<br />
<pre><br />
<nowiki><br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<title>Enter the title of your XHTML document here</title><br />
<style type="text/css"><br />
.CHAN { display:none }<br />
.HEAD { display:none }<br />
.INDI { font-family:'Arial'; font-size:7pt; position: absolute; width:20em; height:14; left: 0; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } .MARR { font-family:'Arial'; font-size:7pt; position: absolute; left:21em; top:4.5em; width:9.7em; height:14; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAM { font-family:'Arial'; font-size:7pt; position: absolute; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAMS { font-family:'Arial'; font-size:6pt; padding-left: 20em; } <br />
</style><br />
</head><br />
<body><br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<div id="I1" class="INDI" style="left:10em; top:10em"><br />
<div class="NAME"><br />
Edward Sean<br />
<span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"><br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I2" class="INDI" style="left:40em; top:10em"><br />
<div class="NAME"><br />
Tamsin Clare <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">25 JUL 1963</div><br />
<div class="PLAC">London</div><br />
</div><br />
<div class="OCCU">Therapist</div><br />
<div class="EDUC">School</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I3" class="INDI" style="left:10em; top:30em"><br />
<div class="NAME"><br />
Alice Rose <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">17 FEB 1986</div><br />
<div class="PLAC">Park Royal Hospital London</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">BristolCollege</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I4" class="INDI" style="left:40em; top:30em"><br />
<div class="NAME"><br />
Megan Christine <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">21 NOV 1988</div><br />
<div class="PLAC">Southmead Hospital Bristol</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">Bristol College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div class="FAM" id="F1" style="left:9em; top:8em; width:52em; height:32em; "><br />
<a class="HUSB" href="#I1"> @I1@</a><br />
<a class="WIFE" href="#I2"> @I2@</a><br />
<a class="CHIL" href="#I3"> @I3@</a><br />
<a class="CHIL" href="#I4"> @I4@</a><br />
<div class="MARR"><br />
<div class="DATE"> 25 SEP 1985</div><br />
<div class="PLAC"> London</div><br />
</div><br />
</div><br />
</div><br />
</body><br />
</html><br />
<br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
The INDI records could be replaced by hCard records. Need to look at a tag by tag mapping here.<br />
<br />
This example doesnt use EVENt tags, which might map to hCalendar<br />
<br />
<br />
The FAM records are the graph structure. This is really what is needed over and above an hCard, along with the more specialised SOURce records which record documentaiton (hCite?). <br />
<br />
It's basically a linkage structure, made slightly more complicated by the fact that an INDIvidual can appear in more than one FAMily record. e.g. if they remarry. rather than a specific geneaology microformat, maybe a general hGraph structure might be appropriate?</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15782GEDCOM Worked example2007-04-19T10:11:03Z<p>SeanHayes: /* Possible microformat */</p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
I Know that. This is a work in progress. think of it as an extended public brainfart if it helps., it will go in the main [[genealogy-formats|genealogy exploration]] section when I'm done<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<br />
The below is a pretty literal translation of the above. GEDCOM uses a hierachical record structure, which maps to XML relatively easily, and also uses links which map reasonably well to id and <a> in HTML. I've done a simple styling here which positions the family grouping. I'll try and get this up on a webserver somewhere soon. This is not really a proposal at this stage, but an exploration to see if a GEDCOM microformat even makes sense.<br />
<br />
<br />
<pre><br />
<nowiki><br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<title>Enter the title of your XHTML document here</title><br />
<style type="text/css"><br />
.CHAN { display:none }<br />
.HEAD { display:none }<br />
.INDI { font-family:'Arial'; font-size:7pt; position: absolute; width:20em; height:14; left: 0; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } .MARR { font-family:'Arial'; font-size:7pt; position: absolute; left:21em; top:4.5em; width:9.7em; height:14; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAM { font-family:'Arial'; font-size:7pt; position: absolute; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAMS { font-family:'Arial'; font-size:6pt; padding-left: 20em; } <br />
</style><br />
</head><br />
<body><br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<div id="I1" class="INDI" style="left:10em; top:10em"><br />
<div class="NAME"><br />
Edward Sean<br />
<span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"><br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I2" class="INDI" style="left:40em; top:10em"><br />
<div class="NAME"><br />
Tamsin Clare <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">25 JUL 1963</div><br />
<div class="PLAC">London</div><br />
</div><br />
<div class="OCCU">Therapist</div><br />
<div class="EDUC">School</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I3" class="INDI" style="left:10em; top:30em"><br />
<div class="NAME"><br />
Alice Rose <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">17 FEB 1986</div><br />
<div class="PLAC">Park Royal Hospital London</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">BristolCollege</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I4" class="INDI" style="left:40em; top:30em"><br />
<div class="NAME"><br />
Megan Christine <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">21 NOV 1988</div><br />
<div class="PLAC">Southmead Hospital Bristol</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">Bristol College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div class="FAM" id="F1" style="left:9em; top:8em; width:52em; height:32em; "><br />
<a class="HUSB" href="#I1"> @I1@</a><br />
<a class="WIFE" href="#I2"> @I2@</a><br />
<a class="CHIL" href="#I3"> @I3@</a><br />
<a class="CHIL" href="#I4"> @I4@</a><br />
<div class="MARR"><br />
<div class="DATE"> 25 SEP 1985</div><br />
<div class="PLAC"> London</div><br />
</div><br />
</div><br />
</div><br />
</body><br />
</html><br />
<br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
The INDI records could be replaced by hCard records. Need to look at a tag by tag mapping here.<br />
<br />
<br />
The FAM records are the graph structure. This is really what is needed over and above an hCard, along with the more specialised SOURce records which record documentaiton. It's basically a linkage structure, made slightly more complicated by the fact that an INDIvidual can appear in more than one FAMily record. e.g. if they remarry.</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15781GEDCOM Worked example2007-04-19T10:04:36Z<p>SeanHayes: /* Notes */</p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
I Know that. This is a work in progress. think of it as an extended public brainfart if it helps., it will go in the main [[genealogy-formats|genealogy exploration]] section when I'm done<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<pre><br />
<nowiki><br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<title>Enter the title of your XHTML document here</title><br />
<style type="text/css"><br />
.CHAN { display:none }<br />
.HEAD { display:none }<br />
.INDI { font-family:'Arial'; font-size:7pt; position: absolute; width:20em; height:14; left: 0; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } .MARR { font-family:'Arial'; font-size:7pt; position: absolute; left:21em; top:4.5em; width:9.7em; height:14; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAM { font-family:'Arial'; font-size:7pt; position: absolute; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAMS { font-family:'Arial'; font-size:6pt; padding-left: 20em; } <br />
</style><br />
</head><br />
<body><br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<div id="I1" class="INDI" style="left:10em; top:10em"><br />
<div class="NAME"><br />
Edward Sean<br />
<span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"><br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I2" class="INDI" style="left:40em; top:10em"><br />
<div class="NAME"><br />
Tamsin Clare <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">25 JUL 1963</div><br />
<div class="PLAC">London</div><br />
</div><br />
<div class="OCCU">Therapist</div><br />
<div class="EDUC">School</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I3" class="INDI" style="left:10em; top:30em"><br />
<div class="NAME"><br />
Alice Rose <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">17 FEB 1986</div><br />
<div class="PLAC">Park Royal Hospital London</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">BristolCollege</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I4" class="INDI" style="left:40em; top:30em"><br />
<div class="NAME"><br />
Megan Christine <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">21 NOV 1988</div><br />
<div class="PLAC">Southmead Hospital Bristol</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">Bristol College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div class="FAM" id="F1" style="left:9em; top:8em; width:52em; height:32em; "><br />
<a class="HUSB" href="#I1"> @I1@</a><br />
<a class="WIFE" href="#I2"> @I2@</a><br />
<a class="CHIL" href="#I3"> @I3@</a><br />
<a class="CHIL" href="#I4"> @I4@</a><br />
<div class="MARR"><br />
<div class="DATE"> 25 SEP 1985</div><br />
<div class="PLAC"> London</div><br />
</div><br />
</div><br />
</div><br />
</body><br />
</html><br />
<br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
The INDI records could be replaced by hCard records. Need to look at a tag by tag mapping here.<br />
<br />
<br />
The FAM records are the graph structure. This is really what is needed over and above an hCard, along with the more specialised SOURce records which record documentaiton. It's basically a linkage structure, made slightly more complicated by the fact that an INDIvidual can appear in more than one FAMily record. e.g. if they remarry.</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15780GEDCOM Worked example2007-04-19T10:00:47Z<p>SeanHayes: </p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
I Know that. This is a work in progress. think of it as an extended public brainfart if it helps., it will go in the main [[genealogy-formats|genealogy exploration]] section when I'm done<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<pre><br />
<nowiki><br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<title>Enter the title of your XHTML document here</title><br />
<style type="text/css"><br />
.CHAN { display:none }<br />
.HEAD { display:none }<br />
.INDI { font-family:'Arial'; font-size:7pt; position: absolute; width:20em; height:14; left: 0; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } .MARR { font-family:'Arial'; font-size:7pt; position: absolute; left:21em; top:4.5em; width:9.7em; height:14; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAM { font-family:'Arial'; font-size:7pt; position: absolute; text-align: Center; border: 1pt solid black;margin-top: 0pt; margin-bottom: 1pt } <br />
.FAMS { font-family:'Arial'; font-size:6pt; padding-left: 20em; } <br />
</style><br />
</head><br />
<body><br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<div id="I1" class="INDI" style="left:10em; top:10em"><br />
<div class="NAME"><br />
Edward Sean<br />
<span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"><br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I2" class="INDI" style="left:40em; top:10em"><br />
<div class="NAME"><br />
Tamsin Clare <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">25 JUL 1963</div><br />
<div class="PLAC">London</div><br />
</div><br />
<div class="OCCU">Therapist</div><br />
<div class="EDUC">School</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I3" class="INDI" style="left:10em; top:30em"><br />
<div class="NAME"><br />
Alice Rose <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">17 FEB 1986</div><br />
<div class="PLAC">Park Royal Hospital London</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">BristolCollege</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div id="I4" class="INDI" style="left:40em; top:30em"><br />
<div class="NAME"><br />
Megan Christine <span class="FAML">Hayes</span><br />
<div class="SEX">F</div><br />
<div class="BIRT"><br />
<div class="DATE">21 NOV 1988</div><br />
<div class="PLAC">Southmead Hospital Bristol</div><br />
</div><br />
<div class="OCCU">Student</div><br />
<div class="EDUC">Bristol College</div><br />
<a class="FAMS" href="#F1">@F1@</a><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
</div><br />
<div class="FAM" id="F1" style="left:9em; top:8em; width:52em; height:32em; "><br />
<a class="HUSB" href="#I1"> @I1@</a><br />
<a class="WIFE" href="#I2"> @I2@</a><br />
<a class="CHIL" href="#I3"> @I3@</a><br />
<a class="CHIL" href="#I4"> @I4@</a><br />
<div class="MARR"><br />
<div class="DATE"> 25 SEP 1985</div><br />
<div class="PLAC"> London</div><br />
</div><br />
</div><br />
</div><br />
</body><br />
</html><br />
<br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
The INDI records could be replaced by hCard records:</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15787genealogy-formats2007-04-18T22:07:43Z<p>SeanHayes: /* GEDCOM */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.--[[User:SeanHayes|SeanHayes]] it might go away at any time.<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
* GEDCOM is basically a set of INDIvidual records, related by FAMily nodes the family nodes contain the HUSBand, WIFE and CHILd. The INDI records are quite similar and might be replaced by hCard records, but the graph structure is a little harder to capture; families arent strict trees, so a direct mapping to XML doesnt really work. Publishing a GEDCOM database directly to the web might not be the most logical thing to do.<br />
<br />
* Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15760genealogy-formats2007-04-18T22:07:19Z<p>SeanHayes: /* GEDCOM */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.--[[User:SeanHayes|SeanHayes]] it might go away at any time.<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
* GEDCOM is basically a set of INDIvidual records, related by FAMily nodes the family nodes contain the HUSBand, WIFE and CHILd. The INDI records are quite similar and might be replaced by hCard records, but the graph structure is a little harder to capture; families arent strict trees, so a direct mapping to XML doesnt really work. Publishing a GEDCOM database directly to the web might not be the most logical thing to do. -- ~~<br />
<br />
** Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15759genealogy-formats2007-04-18T22:00:21Z<p>SeanHayes: /* External Links */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.--[[User:SeanHayes|SeanHayes]] it might go away at any time.<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
** Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
** HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15758genealogy-formats2007-04-18T21:59:59Z<p>SeanHayes: /* External Links */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.--[[User:SeanHayes|SeanHayes]] it might go away at any time.<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
** Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format) (broken?)<br />
HTML translation [http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm GEDCOM 5.5 Standard]<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15757genealogy-formats2007-04-18T21:54:03Z<p>SeanHayes: /* Genealogy Formats */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.--[[User:SeanHayes|SeanHayes]] it might go away at any time.<br />
<br />
see: The Dring tree [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
** Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format)<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15756genealogy-formats2007-04-18T21:53:34Z<p>SeanHayes: </p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working it out in real time.--[[User:SeanHayes|SeanHayes]] it might go away at any time.<br />
<br />
see: [http://www.sussexbarn.com/dring/web/dring/pafg01.htm] for an interesting family tree website.<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
** Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format)<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15776GEDCOM Worked example2007-04-18T21:50:35Z<p>SeanHayes: </p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
I Know that. This is a work in progress. think of it as an extended public brainfart if it helps., it will go in the main [[genealogy-formats|genealogy exploration]] section when I'm done<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
<br />
<div class="INDI"><br />
<div class="NAME" id="Edward-Sean-Hayes"><br />
<span class="FAML">Edward Sean</span><span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"> <br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#f1">@F1@</div><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
<br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
The INDI records could be replaced by hCard records:</div>SeanHayeshttps://microformats.org/wiki/index.php?title=Main_Page&diff=29474Main Page2007-04-18T21:50:07Z<p>SeanHayes: /* Exploratory Discussions */</p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If you haven't already done so, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[books]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat. We even have a [[spellcheck|spell-check dictionary]] of microformat-related terms.<br />
<br />
Frequently asked questions about this wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate this microformats wiki into other languages]] to make microformats globally accessible.<br />
*Find [[orphans|orphaned]] pages, and add links to them.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]], [[examples-in-the-wild]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]]<br />
* [[hresume|hResume]]<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
* alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* audio-info ([[audio-info-examples|examples]], [[audio-info-formats|formats]], [[audio-info-brainstorming|brainstorming]]) - Marking up information and metadata related to audio (speech, music, and sound in general). {{NewMarker}}<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* code [[code-examples| code examples]], [[code-brainstorming|code brainstorming]] {{NewMarker}}<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]<br />
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software {{NewMarker}}<br />
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) {{NewMarker}}<br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* file-format ([[file-format-examples|examples]], formats, brainstorming) - for the mark-up of file format information (size, type, codecs, bitrate, etc.) {{NewMarker}}<br />
* genealogy [[genealogy-formats|genealogy exploration]]<br />
* geo extensions<br />
** [[geo-extension-strawman]] - extend geo for moons, other planets, etc.<br />
** [[geo-elevation-examples]] - extend geo for representing altitude {{NewMarker}}<br />
** [[geo-waypoint-examples]] - extend geo for representing routes and boundaries, using waypoints {{NewMarker}}<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]<br />
* [[htodo|hToDo]]<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) {{UpdateMarker}}<br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]] {{UpdateMarker}}<br />
* [[operating-hours]]: [[operating-hours-examples]] ..of stores, restaurants, etc. {{UpdateMarker}}<br />
* [[payment]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] <br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[internationalization]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
* [[profile-examples-in-wild|Profile examples, in the wild]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[icons]] {{NewMarker}}<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]]<br />
* [[to-do]]<br />
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.<br />
* [[user-interface]]<br />
* [[shortcuts]] to wiki pages with long names<br />
* [[marked-for-deletion]]<br />
<br />
== microformats wiki translations in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15754GEDCOM Worked example2007-04-18T21:47:37Z<p>SeanHayes: </p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
I Know that. This is a work in progress. think of it as an extended public brainfart if it helps., it will go in the main geneaology section when I'm done<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
<br />
<div class="INDI"><br />
<div class="NAME" id="Edward-Sean-Hayes"><br />
<span class="FAML">Edward Sean</span><span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"> <br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#f1">@F1@</div><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
<br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
The INDI records could be replaced by hCard records:</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15752GEDCOM Worked example2007-04-18T21:45:43Z<p>SeanHayes: </p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
I Know that. This is a work in progress, it will go in the main geneaology section when I'm done<br />
--<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
<br />
<div class="INDI"><br />
<div class="NAME" id="Edward-Sean-Hayes"><br />
<span class="FAML">Edward Sean</span><span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"> <br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#f1">@F1@</div><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
<br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
The INDI records could be replaced by hCard records:</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15751GEDCOM Worked example2007-04-18T21:44:44Z<p>SeanHayes: /* Possible microformat */</p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
This is a work in progress, it will go in the main geneaology section when I'm done<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
<br />
<div class="INDI"><br />
<div class="NAME" id="Edward-Sean-Hayes"><br />
<span class="FAML">Edward Sean</span><span class="FAML">Hayes</span><br />
<div class="SEX">M</div><br />
<div class="BIRT"> <br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#f1">@F1@</div><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
<br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
The INDI records could be replaced by hCard records:</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15750GEDCOM Worked example2007-04-18T21:39:22Z<p>SeanHayes: /* Notes */</p>
<hr />
<div>'''This document is not following the [[process]]. Before proposing a micro(or 'mini')format, please research examples in the wild and derive and implied schema. -- RyanKing'''<br />
<br />
This is a work in progress, it will go in the main geneaology section when I'm done<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
<br />
<div class="INDI"><br />
<div class="NAME" id="Edward-Sean-Hayes"><br />
<div class="SEX">M</div><br />
<div class="BIRT"> <br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#f1">@F1@</div><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
<br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==<br />
<br />
<br />
The INDI records could be replaced by hCard records:</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15748GEDCOM Worked example2007-04-18T21:38:27Z<p>SeanHayes: /* Possible miniformat */</p>
<hr />
<div>This is a work in progress, it will go in the main geneaology section when I'm done<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible microformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
<br />
<div class="INDI"><br />
<div class="NAME" id="Edward-Sean-Hayes"><br />
<div class="SEX">M</div><br />
<div class="BIRT"> <br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#f1">@F1@</div><br />
<div class="CHAN"><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
</div><br />
<br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15747GEDCOM Worked example2007-04-18T21:36:24Z<p>SeanHayes: /* Possible miniformat */</p>
<hr />
<div>This is a work in progress, it will go in the main geneaology section when I'm done<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible miniformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
<br />
<div class="INDI"><br />
<div class="NAME" id="Edward-Sean-Hayes"><br />
<div class="SEX M"></div><br />
<div class="BIRT"></div><br />
<div class="DATE"> 1 DEC 1961</div><br />
<div class="PLAC"> Royal Free Hospital London</div><br />
<div class="OCCU"> Program Manager</div><br />
<div class="EDUC"> Westfield College</div><br />
<a class="FAMS" href="#f1">@F1@</div><br />
<div class="CHAN"></div><br />
<div class="DATE"> 18 APR 2007</div><br />
</div><br />
<br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
== Notes ==</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15746GEDCOM Worked example2007-04-18T21:33:40Z<p>SeanHayes: </p>
<hr />
<div>This is a work in progress, it will go in the main geneaology section when I'm done<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible miniformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
<br />
<div class="INDI"><br />
<div class="NAME Edward Sean /Hayes/<br />
<div class="SEX M<br />
<div class="BIRT<br />
<div class="DATE 1 DEC 1961<br />
<div class="PLAC Royal Free Hospital London<br />
<div class="OCCU Program Manager<br />
<div class="EDUC Westfield College<br />
<div class="FAMS @F1@<br />
<div class="CHAN<br />
<div class="DATE 18 APR 2007<br />
</div><br />
<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
<br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
<br />
<br />
== Notes ==</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15745GEDCOM Worked example2007-04-18T21:30:27Z<p>SeanHayes: /* What it looks like */</p>
<hr />
<div>This is a work in progress, it will go in the main geneaology section when I'm done<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible miniformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
<br />
<br />
== Notes ==</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15755genealogy-formats2007-04-18T21:29:06Z<p>SeanHayes: /* Genealogy Formats */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working htis out in real time.--[[User:SeanHayes|SeanHayes]]<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
** Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format)<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15743genealogy-formats2007-04-18T21:28:39Z<p>SeanHayes: /* Genealogy Formats */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this [[GEDCOM Worked example]]. This is very sketchy right now, but I'm working htis out in real time.--[[User:SeanHayes|SeanHayes]] 14:28, 18 Apr 2007 (PDT)<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
** Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format)<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15742genealogy-formats2007-04-18T21:27:59Z<p>SeanHayes: /* Genealogy Formats */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
I'm not sure whether it makes sense to do GEDCOM as its own format, or as an extention of some kind to [[hcard|hCard]], I'm working out some ideas in this[[GEDCOM Worked example]]. This is very sketchy right now, but I'm working htis out in real time.<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
** Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format)<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15744GEDCOM Worked example2007-04-18T21:22:14Z<p>SeanHayes: /* Example GEDCOM file */</p>
<hr />
<div>This is a work in progress, it will go in the main geneaology section when I'm done<br />
<br />
== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible miniformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
== What it looks like ==<br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<br />
<br />
== Notes ==</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15740GEDCOM Worked example2007-04-18T21:21:05Z<p>SeanHayes: </p>
<hr />
<div>== Example GEDCOM file ==<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible miniformat ==<br />
<pre><br />
<nowiki><br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<br />
</nowiki><br />
</pre><br />
<br />
== What it looks like ==<br />
<br />
<div class="gedcom"><br />
<div class="HEAD"><br />
<a class="SOUR" href="www.seanhayes.tv/geneaology/testapp">TESTAPP</a><br />
<span class="VERS"> V0.1</span><br />
<a class="CORP" href="www.seanhayes.tv/geneaology">Test Data</a><br />
<a class="DEST" href="www.seanhayes.tv/geneaology/reunion">REUNION</a><br />
<div class="DATE">18 APR 2007</div><br />
<div class="FILE">Master Database</div><br />
<div class="GEDC"><br />
<span class="VERS">5.01 </span><br />
<span class="CHAR">ASCII </span><br />
</div><br />
</div><br />
<br />
<br />
== Notes ==</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15739GEDCOM Worked example2007-04-18T21:20:44Z<p>SeanHayes: </p>
<hr />
<div>This is a work in progress. It will go in the main geneaology page when I'm done<br />
<br />
<br />
Example GEDCOM file:<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible miniformat ==<br />
<pre><br />
<nowiki><br />
</nowiki><br />
</pre><br />
<br />
<br />
== Notes ==</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15737GEDCOM Worked example2007-04-18T21:05:36Z<p>SeanHayes: </p>
<hr />
<div>Example GEDCOM file:<br />
<pre><br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre><br />
<br />
== Possible miniformat ==<br />
<pre><br />
<nowiki><br />
</nowiki><br />
</pre><br />
<br />
<br />
== Notes ==</div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15736GEDCOM Worked example2007-04-18T21:03:35Z<p>SeanHayes: </p>
<hr />
<div>Example GEDCOM file:<br />
<pre><nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki><br />
</pre></div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15735GEDCOM Worked example2007-04-18T21:02:40Z<p>SeanHayes: </p>
<hr />
<div>Example GEDCOM file:<br />
<nowiki><pre><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</pre><br />
</nowiki></div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15734GEDCOM Worked example2007-04-18T20:58:34Z<p>SeanHayes: </p>
<hr />
<div>Example GEDCOM file:<br />
<nowiki><br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR<br />
</nowiki></div>SeanHayeshttps://microformats.org/wiki/index.php?title=GEDCOM_Worked_example&diff=15733GEDCOM Worked example2007-04-18T20:55:50Z<p>SeanHayes: Worked example of a GEDCOM microformat</p>
<hr />
<div>Example GEDCOM file:<br />
<br />
0 HEAD<br />
1 SOUR TESTAPP<br />
2 VERS V0.1<br />
2 CORP Test Data<br />
1 DEST REUNION<br />
1 DATE 18 APR 2007<br />
1 FILE Master Database<br />
1 GEDC<br />
2 VERS 5.01<br />
1 CHAR ASCII<br />
0 @I1@ INDI<br />
1 NAME Edward Sean /Hayes/<br />
1 SEX M<br />
1 BIRT<br />
2 DATE 1 DEC 1961<br />
2 PLAC Royal Free Hospital London<br />
1 OCCU Program Manager<br />
1 EDUC Westfield College<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I2@ INDI<br />
1 NAME Tamsin Clare /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 25 JUL 1963<br />
2 PLAC London<br />
1 OCCU Therapist<br />
1 EDUC School<br />
1 RELI None<br />
1 FAMS @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I3@ INDI<br />
1 NAME Alice Rose /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 17 FEB 1986<br />
2 PLAC Park Royal, London<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @I4@ INDI<br />
1 NAME Megan Christine /Hayes/<br />
1 SEX F<br />
1 BIRT<br />
2 DATE 21 NOV 1986<br />
2 PLAC Bristol<br />
1 RELI None<br />
1 FAMC @F1@<br />
1 CHAN<br />
2 DATE 18 APR 2007<br />
0 @F1@ FAM<br />
1 HUSB @I1@<br />
1 WIFE @I2@<br />
1 CHIL @I3@<br />
1 CHIL @I4@<br />
1 MARR<br />
2 DATE 25 SEP 1985<br />
2 PLAC London<br />
0 TRLR</div>SeanHayeshttps://microformats.org/wiki/index.php?title=genealogy-formats&diff=15741genealogy-formats2007-04-18T20:53:38Z<p>SeanHayes: /* Genealogy Formats */</p>
<hr />
<div>= Genealogy Formats =<br />
<br />
I started this page because someone (Bob Jonkman apparently) added a bunch of stuff to the [http://developers.technorati.com/wiki/MicroFormats Technorati microformats page] on genealogy, and I moved it here. -[http://tantek.com/log/ Tantek]<br />
<br />
[[GEDCOM Worked example]] pasted here<br />
<br />
== GEDCOM ==<br />
<br />
* Coding the GEDCOM standard into hGEDCOM. I don't know of any projects working on this, but nominate [http://www.starkeffect.com/ged2html/3.6a/ Gene Stark's GED2HTML translator] (esp. the [http://www.starkeffect.com/ged2html/3.6a/templates.html modifiable output program]) as a suitable candidate for hGEDCOM hacking. See also [http://homepages.rootsweb.com/~pmcbride/genweb.html#gedcom Paul McBride's links] to GEDCOM standards and resources. --[mailto:bjonkman@sobac.com Bob Jonkman]<br />
<br />
* Had a look at some examples of what GEDCOM creates [http://en.wikipedia.org/wiki/GEDCOM#Example]. Basically, seems to be [[xfn|XFN]] relationships (siblings, spouses etc.) and [[hcard|hCard]] information (could genealogy be inferred from existing XFNs regardless of a hGED format?). The only additional information we do not currently hold in a format is that of gender. GEDCOM specifies male or female for each individual. Creating something using these formats would be quite straightforward, but not sure its takeup would be good unless someone was interested in creating a hGEDCOM2GEDCOM. -- [[user:Phae|Frances Berriman]]<br />
<br />
** Genealogical information has date-of-death, which is also missing in hCard format (although hCard does have date-of-birth). Much of genealogical information is event based: Date of birth, date of death, dates of marriages and divorces, and many other significant events such as religious observances (Baptisms, Bar/Bat Mitzvahs) and migrations ("Moved to Canada from the Netherlands"). This all translates wonderfully to [[hCalendar]]. Additionally, a properly researched family tree will cite sources for all the data listed, and so could use [[citation|hCite]]. The biggest problem I see in using hCalendar is that genealogical data allows approximate dates, specifically "ABT 4 July 1776", "BEF 25 Dec 1903", "AFT 11 Nov 1918". It also also allows ambiguous dates, "July 1867" or just "1886", or even "4 July". And these in combination, (Approximately ambiguous dates? Ambiguously approximate dates?), eg. "BEF Feb 2007", "AFT 1945". The most ambiguous entries I've seen for dates are "DECEASED" when date-of-death is unknown, and "NOT MARRIED" for couples who have not had a wedding ceremony. (Info from ''Guidelines for event dates'' in the PAF Help File).<br />
<br />
::The only relationship links in GEDCOM are HUSBand, WIFE and CHILd. All other relationships (brother, sister, grandparents, grandchildren, uncles, aunts, nieces, nephews, cousins) can be inferred by traversing family records. This does mean that any collection of genealogical pages need some way to cross-reference to each other. This isn't a problem for all pages on a single Web site, which use RIN (Record Identifier) or REFN (User Reference Number). However, different Web pages maintained by different genealogists may have conflicting RINs and REFNs. There is a globally-unique AFN (Ancestral File Number) issued by the Church of Jesus Christ of Latter-Day Saints (LDS), but I don't know how they're issued and most genealogical sites don't use them anyway. <br />
<br />
::The GEDCOM format contains much other data specific to the LDS, but I don't know how widespread it is, nor how appropriate it would be to code it into a microformat intended to reach well beyond the LDS.<br />
<br />
::Regardless of whether an hGED microformat is developed, it would still be valuable to mark up genealogical information with microformats on Web pages for the semantic value.<br />
<br />
::[[User:Bob Jonkman|Bob Jonkman]] 07:58, 9 Feb 2007 (PST)<br />
<br />
==Wikipedia's Persondata==<br />
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:04, 28 Jan 2007 (PST)<br />
<br />
== External Links ==<br />
*GEDCOM specifications are documented on the FamilySearch website: [http://www.familysearch.org/Eng/Home/FAQ/faq_gedcom.asp]<br />
** [http://www.familysearch.org/GEDCOM/GEDCOM55.EXE GEDCOM 5.5 Standard] (Executable file in Envoy format)<br />
** [http://www.familysearch.org/GEDCOM/GedXML60.pdf Draft Specification for GEDCOM XML 6.0] (PDF)<br />
*Personal Ancestral File (PAF)<br />
**[http://en.wikipedia.org/wiki/Personal_Ancestral_File Personal Ancestral File]<br />
**[http://productsupport.familysearch.org/supportroot/eng/frameset_products.asp PAF support page]<br />
**[http://en.wikipedia.org/wiki/Ancestral_File_Number Ancestral File Number]<br />
<br />
==See also==<br />
*[[genealogy-brainstorming]]<br />
*[[hcard|hCard]]</div>SeanHayes