GEDCOM for mac GEDitCOM.com



Link: http://www.downloadatoz.com/file-extensions/download,genealogy+data.html
File Extensions for Genealogical Data.
  • .ged
  • .data
  • .gedcom
  • .acc
  • ..... list goes on....





Link: http://genealogy.about.com/gi/o.htm?zi=1/XJ&zTi=1&sdn=genealogy&cdn=parenting&tm=899&f=10&su=p284.9.336.ip_p504.1.336.ip_&tt=2&bt=0&bts=0&zu=http%3A//bettergedcom.wikispaces.com./
Building a better GEDCOM Wiki




Link: http://genealogy.about.com/od/family_tree_software/a/Genealogy-Gedcom.htm
GEDCOM 101



Link: http://en.wikipedia.org/wiki/GEDCOM

GEDCOM, an acronym for GEnealogical Data COMmunication, is a proprietary and open de facto[1] specification for exchanging genealogical data between different genealogy software. GEDCOM was developed by The Church of Jesus Christ of Latter-day Saints as an aid to genealogical research.[2]
A GEDCOM file is plain text (usually either ANSEL or ASCII) containing genealogical information about individuals, andmeta data linking these records together. Most genealogy software supports importing from and/or exporting to GEDCOM format.[3] However, some genealogy software programs incorporate the use of proprietary extensions to the GEDCOM format, which are not always recognized by other genealogy programs, for example the GEDCOM 5.5 EL (Extended Locations) specification

Alternatives to GEDCOM
Commsoft, the authors of the Roots[56] series of genealogy software and Ultimate Family Tree, defined a version called Event-Oriented GEDCOM (also known as "Event GEDCOM" and originally called InterGED[57]),[58] which included events as first class (zero-level) items. Although it is event based, it is still a model built on assumed reality rather than evidence. Event GEDCOM was more flexible, as it allowed some separation between believed events and the participants. However, Event GEDCOM was not widely adopted by other developers due to its semantic differences.[//citation needed//] With Roots and Ultimate Family Tree no longer available, very few people today are using Event GEDCOM.[59]


Link: http://www.raynorshyn.com/gedclean/DefGEDCOM.asp


All genealogical database programs are designed to be able to share information in a common format. The GEDCOMspecification defines a format that all such programs can create and understand.
GEDCOM is short for Genealogical Data Communication.
GEDCOM files contain only plain (ASCII) text. This means you can read them with any text editor or word processor (Notepad, Wordpad, or MS-Word, for example).
Each line of a GEDCOM file starts with a "level" number, which indicates whether the piece of data on that line starts a new record, or is part of the record above.
For example, a level "0" line might indicate the start of an "individual" record. The next line might be level "1", and contain the "name" of that individual:
0 @I2@ INDI
1 NAME John  /Doe/
1 SEX M
 
This is a section of the record about an individual with the first name "John", and last name "Doe". Reading this, we see that he isMale, and in this database the ID of his record is I2.
The true power of the GEDCOM format, however, is that it also contains the relationships between records. For example, further along in the file, we find something like this:
1 FAMS @F3@
1 FAMC @F1@
 
This says that this individual is a Spouse in family F3, and a Child in family F1.
Further along, we should expect to find a record that defines each of these families. Family records will contain information such as the IDs of the members of the family, and the date and place of the parents' marriage.
Armed with this basic information, you can now browse your GEDCOM file with confidence.
In a GEDCOM, all the information about an individual is together, but to find out about that individual's spouse, children or parents requires that you read the entire GEDCOM file into a database, to restore the pointers and links.
This is why GEDClean cannot, for example, know that an individual whose child was born 200 years ago is not likely to be still living. All GEDClean can know is what's in the INDI record.


link: http://helpdesk.rootsweb.com/FAQ/wcsubmit8.html
Protecting the Privacy of the living

You determine how (or if) the WorldConnect Project displays living individuals by the options you choose on the advanced user setup/edit form.

When uploading a GEDCOM to WorldConnect, you can choose to clean or remove the records of living individuals from display. (The records will still be in your file. Only what is displayed on the Internet is altered.) Living in this case is defined as anyone in your family tree born (or christened) in 1930 or later, that does not have a death or burial year included, unless you change the default settings. The year 1930 was used as the default setting because the 1930 U.S. census has been released as public information. You can change the default to any year prior to 1930 if you wish. For example, if you have a person in your file who was born in 1921 and is still living, you can change the default to 1920 so that their full name will not be displayed When there are no birth or christening dates, the WorldConnect program attempts to approximate the year of birth from other information in the GEDCOM file.
  • Clean means the entries for living individuals will be displayed in WorldConnect but the given names will be replaced with the word "living." The advanced user setup/edit form gives you a multitude of ways to protect the privacy of the living in your file. Included are the choices to treat tags as notes or to remove specific tags. You will find a listing of common tags here.
  • Remove means your family tree will not display entries for any living individuals. You will still need to determine how you want notes, source information, and tags to be shown for those who are not living.
You have additional options to protect the privacy of the living, including removing notes or source information from display.
You may also remove specific GEDCOM tags or request the program's living finder to treat specific tags as notes. If you list more than one tag, separate them with a comma, but leave no spaces (for example, CAUS,BAPM,BAPT).

Excluding specific individuals

Other researchers may ask you to remove their name(s) from your file. You can remove specific individuals from your file, remove specific individuals and their descendants, or mark specific individuals as living by using the "individuals to remove" section of the advanced user setup/edit form.

Go into your file and locate the individual's number, then list that number in this section listing one entry per line. If you want to remove an individual and all his/her descendants, you will need to do two entries (two lines) as in the fourth example shown below.

Removal of an individual, or his descendants, has no effect on the display of a spouse; they must be removed (listed) separately.


Example
Results In
I0001
removes individual I0001
I0001,R*
removes descendants of I0001
I0001,R*#
removes descendants of I0001, and adds a comment to the entry — for example, a comment reading "this person requested that they be removed"
I0001
I0001,R*
removes individual I0001 (top line), and his/her descendants (second line)
I0001,L
marks individual I0001 as living
I0001,L*
marks descendants of I0001 as living

If you wish, you can add a message that will be attached to each of the living individuals in your file. For example, "Living individual, some details withheld."

If you are changing the options for an existing file, leave the location of your file blank on the user setup/edit form. You only need to upload your file when you have made a change to the content of the file.