search

FamilySearch / gedcom5-conversion

Utilities for GEDCOM 5.5 to GEDCOM X Conversion
Other
32 stars 22 forks source link

Dates aren't parsed #5

Open jralls opened 12 years ago

jralls commented 12 years ago

The Gedcom5-converter takes a Gedcom5 Date tag

2 DATE 31 DEC 1965

and produces a date structure having only a gxc:original string element

        <gxc:date>
            <gxc:original>31 DEC 1965</gxc:original>
        </gxc:date>

The GedcomX conceptual model, paragraph 5.2, specifies both an original string value and a parsed FormalValue, and includes the Gedcom 5.5 date format as "recognized". Gedcom5-converter should parse the Gedcom 5.5 date string and create the FormalValue element.

daveyse commented 12 years ago

Good catch, and I agree this is an error. Even if the values are the same, the FormalValue should be separate from Original.

stoicflame commented 12 years ago

+1