Re: [LegacyUG] changed to Gedcom history/future

2009-08-25 Thread RICHARD SCHULTHIES
Gedcom does not belong to LDS, nor anyone else. It was created by a committee 
of interested parties, of which LDS was represented. What needs to happen is to 
create a new committee, containing all (or most) of the major program writers, 
database companies, descendant societies; if not actully participating, but 
giving tacit approval in abstentia. Then it would take at least a year. Don't 
hold your breath.
ich in LA CA

--- On Tue, 8/25/09, Chick Lewis cglewi...@gmail.com wrote:

 From: Chick Lewis cglewi...@gmail.com
 Subject: Re: [LegacyUG] combining/replacing sources
 To: LegacyUserGroup@legacyfamilytree.com
 Date: Tuesday, August 25, 2009, 2:53 PM
 OK, I'm confused.  I realize the
 GEDCOM standard is old, but it is
 still the only method available for transferring data
 between
 programs.  If the new SourceWriter data and ESM's
 templates do not
 transfer well by gedcom, what is the alternative? Should we
 stop using
 SW until a new gedcom standard is developed?  That may
 never happen
 because as far as I know, LDS has no plans to update the
 gedcom.
 Chick Lewis




Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp





Re: [LegacyUG] changed to Gedcom history/future

2009-08-25 Thread Chick Lewis
I beg to differ. The Family History Department of the Church of Jesus
Christ of Latter Day Saints is the creator and owner of the GEDCOM
specification. The current version, 5.5, came out in January of 1996.

http://www.rootsworks.com/genart13.htm

and

http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcint.htm

The question still remains... Should SourceWriter be used if you want
to be compatible with other genealogical programs?



On Tue, Aug 25, 2009 at 4:35 PM, RICHARD
SCHULTHIESfourpa...@verizon.net wrote:
 Gedcom does not belong to LDS, nor anyone else. It was created by a committee 
 of interested parties, of which LDS was represented. What needs to happen is 
 to create a new committee, containing all (or most) of the major program 
 writers, database companies, descendant societies; if not actully 
 participating, but giving tacit approval in abstentia. Then it would take at 
 least a year. Don't hold your breath.
 ich in LA CA

 --- On Tue, 8/25/09, Chick Lewis cglewi...@gmail.com wrote:

 From: Chick Lewis cglewi...@gmail.com
 Subject: Re: [LegacyUG] combining/replacing sources
 To: LegacyUserGroup@legacyfamilytree.com
 Date: Tuesday, August 25, 2009, 2:53 PM
 OK, I'm confused.  I realize the
 GEDCOM standard is old, but it is
 still the only method available for transferring data
 between
 programs.  If the new SourceWriter data and ESM's
 templates do not
 transfer well by gedcom, what is the alternative? Should we
 stop using
 SW until a new gedcom standard is developed?  That may
 never happen
 because as far as I know, LDS has no plans to update the
 gedcom.
 Chick Lewis




 Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
 Archived messages:
   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
 Online technical support: http://www.LegacyFamilyTree.com/Help.asp
 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp







Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp