Gedcom 7: Planned handling of RESI #107
-
If converting my Gedcom data to Gedcom 7, some validators throw errors/warnings about the RESI tag. The background for this is that Gedcom 7 seems to require a non-empty <Text> after the RESI tag.
Do you already have some thoughts about how to handle the RESI tag in Gedcom 7? Will you copy the PLAC value to the <Text> value? This would be compliant to the standard. However, it introduces an additional redundancy to the already existing redundancy between PLAC and _LOC.
Another alternative would be to leave the <Text> empty and accept that some validators will throw errors/warnings. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
No, and this should be handled in webtrees itself, if necessary, but:
According to the spec, this shoudn't be done: "The payload text should not duplicate PLAC or ADDR information"
Leaving it empty seems to be allowed by the spec, so it's actually the validators who are in error here. |
Beta Was this translation helpful? Give feedback.
No, and this should be handled in webtrees itself, if necessary, but:
According to the spec, this shoudn't be done: "The payload text should not duplicate PLAC or ADDR information"
Leaving it empty seems to be allowed by the spec, so it's actually the validators who are in error here.