advertisement

This page describes a set of tests included in version 1.04 of the GEDCOM file assess.ged (download - view). Details change between versions.

Area Summary

People with the surname "Event with TYPE" have an event record that includes the TYPE subrecord.

The GEDCOM 5.5.1 specification includes the TYPE subrecord to further classify the parent event. Some target applications reject or ignore the TYPE subrecord. Some target applications ignore the TYPE subrecord except for certain event types.

01-BIRT with TYPE

A BIRT event with TYPE BirthAlternate. Some target applications will reject or ignore the TYPE value.

Test Result Criteria

  1. If a target application imports the BIRT into an event record or equivalent and the TYPE value is used as the label for that record, and the resulting fact or event is a distinct record type, set the test result to "Supported".

    A target application must treat a BIRT record with a TYPE value as a means to create a distinct event or fact type, not to create a text value in an instance of the same fact or event record type created by BIRT without a TYPE subrecord.

  2. If a target application imports the BIRT into an event record or equivalent and the TYPE value is used as the label for that record, but the resulting fact or event uses the same record type as a BIRT record without a TYPE subrecord, set the test result to "Partially Supported" and describe the outcome in the comment.
  3. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I135@

1 BIRT
2 TYPE BirthAlternate
2 DATE 1711

02-DEAT with TYPE

A DEAT event with TYPE DeathAlternate. Some target applications will reject or ignore the TYPE value.

Test Result Criteria

  1. If a target application imports the DEAT into an event record or equivalent and the TYPE value is used as the label for that record, and the resulting fact or event is a distinct record type, set the test result to "Supported".

    A target application must treat a DEAT record with a TYPE value as a means to create a distinct event or fact type, not to create a text value in an instance of the same fact or event record type created by DEAT without a TYPE subrecord.

  2. If a target application imports the DEAT into an event record or equivalent and the TYPE value is used as the label for that record, but the resulting fact or event uses the same record type as a DEAT record without a TYPE subrecord, set the test result to "Partially Supported" and describe the outcome in the comment.
  3. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I136@

1 DEAT
2 TYPE DeathAlternate
2 DATE 1801

03-CENS with TYPE

A CENS event with TYPE 1900 Census. Some target applications will reject or ignore the TYPE value.

Test Result Criteria

  1. If a target application imports the CENS into an event record or equivalent and the TYPE value is used as the label for that record, and the resulting fact or event is a distinct record type, set the test result to "Supported".

    A target application must treat a CENS record with a TYPE value as a means to create a distinct event or fact type, not to create a text value in an instance of the same fact or event record type created by CENS without a TYPE subrecord.

  2. If a target application imports the CENS into an event record or equivalent and the TYPE value is used as the label for that record, but the resulting fact or event uses the same record type as a CENS record without a TYPE subrecord, set the test result to "Partially Supported" and describe the outcome in the comment.
  3. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I137@

1 CENS
2 TYPE 1900 Census
2 DATE 1900
On This Page