Gedcom version need to go to 7

[Delcour]

Hello, when exporting my data to an online website I loose information because the Gedcom version is quite old. Is there any chance version 7 will be implemented?

[Blaise A. Darveaux]

Version 5.5.1 is the current standard and is the most widely used version in the industry. Differences of opinion of how that specification is implemented is responsible for losses of data, not necessarily the age of the specification. I doubt if Leister Productions will say one way or the other if they will implement 7.0 in the next version of Reunion, but even if they came out with a 7.0 compatible version of Reunion tomorrow and was able to WRITE a GEDCOM in 7.0, there is absolutely no guarantee that any other software will be able to READ that GEDCOM yet.

Probably what needs to be done is for the big data warehouses in the industry (Ancestry.com and FamilySearch.com) to implement 7.0 and then the smaller application developers would follow suit. This would ensure that if data was OUTPUT in 7.0 by the smaller apps, there would at least be someplace for the data to be IMPORTED. There probably will be a period of time when both standards will be acceptable until everyone is on board with 7.0.

Wikipedia is very informative. https://en.wikipedia.org/wiki/GEDCOM.

[B Jansen]

Reunion has stubbornly refused to implement changes for the GEDCOM standard from many, many versions ago (look at dates for an easy example). Based on their history, there is about a zero percent chance Reunion will be compliant. That said, Reunion is very customizable, and users can do a lot to do it themselves (for many parts of it anyway).

FamilySearch announced they were implementing it over a year ago, and many software companies have too.

[Gregg]

The problem is not always the supported GEDCOM version, sometimes Reunion’s dataset is not the same as the other software’s dataset. IOW: There are cases where data from one app has nowhere to go in another app. For example: Reunion doesn’t support source repositories and others may not support connections or child statuses.

Can you be more specific about what data is lost?

[Delcour]

Sorry for my late response.
Thnx for responding.

I post my genealogy results at www.genealogieonline.nl
If you look here for instance you see a character issue: https://www.genealogieonline.nl/delc...ogie/I1625.php
Maybe that is not a Gedcom issue?
Also, media is not coming through, something about links not being right.
But that also may not be Gedcom issue.
I'm just trying to find out where glitches in the transfer occur and how to avoid or improve them.

[Gregg]

Thanks for the clarification.

When you export a GEDCOM file from Reunion, make sure you have select a GEDCOM character set of 'UTF-8' - from the looks of the web page it looks to me like you probably did. However, there may be some characters that are not being rendered properly to HTML. GEDCOM 7 would not make a difference here.

As far as images go, it doesn't look like genealogieonline.nl supports GEDCOM 7 yet, so how do they want images passed to them?

[B Jansen]

Reunion doesn’t support source repositories

Will Reunion support source repositories?

[Gregg]

No, Reunion 14 does not support repositories.