Question GEDCOM tags QUAY and TYPE

Hi there,
When I import a GEDCOM file generated with Heredis 2025, I get two unrecognized tags : SOUR:QUAY and SOUR:TYPE.
It seems to me that these tags are standard GEDCOM 5.5 tags, why won't they not be recognized?

SOUR.QUAY is used in source citations (i.e. where you reference the source), not in the source record itself.

I've not seen SOUR.TYPE before. I don't see it in the GEDCOM specification.

You can read the specification here: webtrees.net/downloads/gedcom-5-5-1.pdf

The policy of webtrees is to create only valid GEDCOM, but to also display invalid GEDCOM. For this, we have a list of invalid tags created by various other applications.

I will add these two to the list of invalid tags created by Heredis.

fisharebest wrote:

The policy of webtrees is to create only valid GEDCOM, but to also display invalid GEDCOM. For this, we have a list of invalid tags created by various other applications.

I know it is one of the strengths of webtrees to display GEDCOM derivatives of other programs without loss, even if they deviate from the standard. But would it still make sense to mark invalid, non-standard tags in the user interface? This would make incorrect GEDCOM tags visible to the user. 

Perhaps we should also discuss whether it makes sense to optionally exclude incorrect GEDCOM structures during export or to move them to NOTEs. Today it looks to receiving programs as if webtrees would generate these incorrect structures.

Peter_S wrote:

Perhaps we should also discuss whether it makes sense to optionally exclude incorrect GEDCOM structures during export or to move them to NOTEs. Today it looks to receiving programs as if webtrees would generate these incorrect structures.

That is a totally different discussion. But I'd vote for the GIGO approach. If the user wants non-standard GEDCOM for whatever reason (imported from, or to be imported into another program) then transfer it transparently.

Displaying it in red is a good indication that there is an issue at hand.

If some cases the incorrect (non-standard) GEDCOM reflects data that can be correctly changed to another standard GEDCOM tag.  Noting to a user who can correct the use would be very helpful to people transitioning away from their previous application.  

Many applications that create a NOTE tag for incoming tags they don’t understand is used because they don’t support the tag in their schema design!  This messes with both correct GEDCOM tags and can still promote incorrect GEDCOM tags!  I think it is a good idea for webtrees to not automatically change a tag or create a NOTE tag for incorrect tags which are still visible to users!

I sent this problem, along with the invalid "DATE -44" (instead of "DATE 44 B.C.") problem, to Heredis's technical support. However, I have no expectation that they will solve their GEDCOM problems soon.