So it should be obvious that omitting “” from the Individual Event structure was an oversight. The definition of EVENT_DESCRIPTOR even states that it is “Text describing a particular event pertaining to the individual or family” (emphasis added). Now why would this be? Clearly it was an oversight on the part of the authors and editors of the standard, because on page 48 of the standard, the following example is provided for an EVENT_DESCRIPTOR on an Individual Event:ġ EVEN Appointed Zoning Committee Chairperson The crucial difference is that the Individual Event structure lacks the EVENT_DESCRIPTOR. You would think that, with the exception of the HUSB and WIFE elements, the Individual Event structure would be the same, but from the partially expanded structure that follows, we can see one crucial difference:
#Geditcom 2 review full#
The partially expanded structure for a Family Event is as follows (you can find the full definition on pages 32 and 48 of the GEDCOM 5.5.1 standard): (There’s also a structure for attributes not defined in the standard, the Fact structure, but I won’t get into that in this article). Some apps try to play nice and correctly read other apps’ product-specific tags, even though the standard does not and cannot require them to.īut there’s a better way to specify events that aren’t specifically defined in the standard, and that’s to use the Event structure. The main problem with product-specific tags is that they’re product-specific, meaning data you share with other people or transfer to a different application can be misinterpreted or ignored. The GEDCOM standard allows this, calling them NEW_TAGs, and they’re supposed to begin with an underscore, but several apps incorrectly omit the underscore. However, for events not covered by these specific definitions, many apps use their own product-specific tags. The GEDCOM standard contains specific structures for many events, such as birth, marriage, death, etc. To make this question concrete, let’s take the example of the Event structure, used for both family and individual events and beginning with the tag EVEN in a GEDCOM file. However, what should apps do when there are mistakes in the standard? Should they import, export, and/or validate GEDCOM files strictly according to the standard, or according to how the standard should have been? This is a letter versus spirit of the law question, and the answer depends on the mistake in question and the purpose of the app.
#Geditcom 2 review archive#
^ Journal of Online Genealogy - Volume 3, Number 5, December 1998 - Software Trends - GEDitCOM 1.0 for the Power Macintosh, By John Nairn Wayback Archive.^ "Ancestry® | Ahnenforschung, Stammbaum und Familiengeschichte".^ "GEDitCOM II AppleScripting Tutorials".^ GEDitCOM Version History, Wayback Archive.
GEDitCOM II supports International Localization.Supported languages: English, French, Spanish, Portuguese, Finnish, Swedish. The most significant changes were the introduction of "Extensions" (or GEDitCOM II plug ins), dynamic editing in trees, and redesigned help window. GEDitCOM v1.0 was released 7 December 1998, with the final version 3.82 released on 7 June 2009 which runs on MacOS 8.1 or newer. GEDitCOM II v1.0 was released 7 June 2009 and was a complete rewrite of GEDitCOM 3.82 as a universal binary Cocoa-based application, which runs under OS X 10.4 and higher. GEDitCOM has native support of GEDCOM files, and is customizable and extensible through Applescript, Python, or Ruby. It includes options for users to produce charts depicting family relationships and web pages for publishing family history online.
#Geditcom 2 review mac os x#
GEDitCOM is genealogy software for the Mac OS X that provides methods to input, manipulate, and view information about a family history.
0 kommentar(er)
