You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the GEDCOM 5.5.1 standard a source can have a subordinate DATA tag storing additional informations:
n @<XREF:SOUR>@ SOUR {1:1}
+1 DATA {0:1}
+2 EVEN <EVENTS_RECORDED> {0:M}
+3 DATE <DATE_PERIOD> {0:1}
+3 PLAC <SOURCE_JURISDICTION_PLACE> {0:1}
+2 AGNC <RESPONSIBLE_AGENCY> {0:1}
+2 <<NOTE_STRUCTURE>> {0:M}
...
At the moment this DATA tag and its subordinates are not included in the object model.
I'd like to submit a pull request to fix.
I have created a SourceData class and a DataEvent class.
But now I have a doubt: in SourceData is it better to define a single DataEvent or a List<DataEvent>?
In the real world of GEDCOMs is there usually only one EVEN under DATA?
Or is it actually common to have multiple EVEN, in accordance to the standard?
The text was updated successfully, but these errors were encountered:
Receiving no response I will opt for what I think is best.
I will follow the GEDCOM 5.5.1 standard, that is the possibility to add multiple EVEN under DATA.
According to the GEDCOM 5.5.1 standard a source can have a subordinate DATA tag storing additional informations:
At the moment this DATA tag and its subordinates are not included in the object model.
I'd like to submit a pull request to fix.
I have created a
SourceData
class and aDataEvent
class.But now I have a doubt: in
SourceData
is it better to define a singleDataEvent
or aList<DataEvent>
?In the real world of GEDCOMs is there usually only one EVEN under DATA?
Or is it actually common to have multiple EVEN, in accordance to the standard?
The text was updated successfully, but these errors were encountered: