I can understand your point, but respectfully disagree.
I agree that all vendors have different data models, but when a vendor adds functionality to their product that extends the basic Gedcom data model, it is, in my opinion, in their best interest (and that of their customers) to see how other vendors handle similar data model extensions so that their customers can best exchange data, unless, of course, they wish to take on a proprietary business model and make it difficult for their customers to exchange data with researchers who use other products.
The fact that Legacy and RootsMagic use similar Gedcom for Shared events is a positive informal collaboration that benefits both company's customers.
The issue with Child Status is that Legacy has chosen to export the data as an attribute of Family instead of Person as is done by all other vendors who export this type of data.
By placing the data in what the industry has deemed the wrong place - and which on a reasonable review most folks would agree is the wrong place - I would say Legacy should change their implementation.
As no one else (that I have researched) has a child status, some other companies may not be able to receive the data (and that is their problem), but a company that has a flexible approach to custom events, like TNG has, will be able to receive the data. Most importantly, the data is organized as the "common wisdom" feels it should be.
john.
At 02:58 PM 3/31/2015, Jay Wilpolt wrote:
On Tue, Mar 31, 2015 at 10:00 AM, John Lisle <[email protected]> wrote:
- What is a problem with Legacy is when Legacy does not export any of its data OR it exports the data in a fashion that cannot be accepted by the receiving software.
John ,
In regards to
What is a problem with Legacy is when Legacy does not export any of its data OR it exports the data in a fashion that cannot be accepted by the receiving software.
I agree with
What is a problem with Legacy is when Legacy does not export any of its data
BUT not with
it exports the data in a fashion that cannot be accepted by the receiving software.
You cannot blame Legacy or any manufacturer for what happens to their data by SOMEONE ELSE's process.... they have no control or "mind reading" capability to know how someone else code will manage the data.
And therein lies the problem currently with so many variations of genealogy software all which may or may not import/ export properly process any data outside of standardize gedcom data.
Jay
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://support.legacyfamilytree.com
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
