advertisement

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

Area Summary

People with the surname "Restriction" have various records marked with the restriction notice RESN subrecord. According to the GEDCOM 5.5.1 specification, "the restriction notice is defined for Ancestral File usage", but several programs export the RESN subrecord to mark private or confidential records.

GEDCOM 5.5.1 defines three values for RESN:

confidential
"This data was marked as confidential by the user. In some systems data marked as confidential will be treated differently, for example, there might be an option that would stop confidential data from appearing on printed reports or would prevent that information from being exported."
locked
"Some records in Ancestral File have been satisfactorily proven by evidence, but because of source conflicts or incorrect traditions, there are repeated attempts to change this record. By arrangement, the Ancestral File Custodian can lock a record so that it cannot be changed without an agreement from the person assigned as the steward of such a record. The assigned steward is either the submitter listed for the record or Family History Support when no submitter is listed."
privacy
"Indicate that information concerning this record is not present due to rights of or an approved request for privacy. For example, data from requested downloads of the Ancestral File may have individuals marked with ‘privacy’ if they are assumed living, that is they were born within the last 110 years and there isn’t a death date. In certain cases family records may also be marked with the RESN tag of privacy if either individual acting in the role of HUSB or WIFE is assumed living."

Given the definitions above are mostly focused on Ancestral File operations, it's not clearly defined how other programs should implement the restrictions.

For the purposes of these tests, the "confidential" and "privacy" values are considered synonyms that identify sensitive data that must not be shared with other users without the consent of the end-user.

For the purposes of these tests, the "locked" value is considered inert and the target application should not omit or suppress locked data. Whether or how to implement a data locking scheme is left to the target application. End users can edit GEDCOM files and remove the locking mechanism, and for that and other reasons, GEDCOM Assessment does not require target applications to implement locking mechanism.

01-FAM Confidential

This test includes a FAM record with a RESN subrecord that has the value confidential. The FAM record should be omitted from output intended to be shared with other people.

Test Result Criteria

  1. If the target application omits the confidential FAM record in output intended to be shared with other people such as exports, reports, charts, and web sites, set the test result to "Supported".

    It is acceptable to include the confidential data if the target application has an output option specifically intended to override restriction directives.

  2. If a target application rejects the RESN record with a message in its import log, set the test result to "Rejected".
  3. If a target application ignores the RESN record and does not issue an error message, set the test result to "Ignored".
  4. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I244@ and @I245@

0 @I244@ INDI
1 NAME 01-FAM Confidential1 /Restriction/
1 SEX M
1 FAMS @F244@
0 @I245@ INDI
1 NAME 01-FAM Confidential2 /Restriction/
1 SEX F
1 FAMS @F244@
0 @F244@ FAM
1 RESN confidential
1 HUSB @I244@
1 WIFE @I245@
1 MARR
2 DATE 01 JAN 2000

02-FAM Locked

This test includes a FAM record with a RESN subrecord that has the value locked. The FAM record should be included in output intended to be shared with other people.

Test Result Criteria

  1. If the target application includes the locked FAM record in output intended to be shared with other people such as exports, reports, charts, and web sites, set the test result to "Supported".

    Target applications that include data editing capabilities (edit, delete, etc.) may indicate that a record is locked, but that feature is not required.

  2. If the target application ignores or appears to ignore the RESN record, that is acceptable. Set the test result to "Supported".
  3. If the target application rejects the RESN record with a message in its import log, set the test result to "Rejected".
  4. If a target application suppresses the FAM data in response to the RESN record, set the test result to "Imported Incorrectly".
  5. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment. This should be rare.

GEDCOM Records for @I246@ and @I247@

0 @I246@ INDI
1 NAME 02-FAM Locked1 /Restriction/
1 SEX M
1 FAMS @F246@
0 @I247@ INDI
1 NAME 02-FAM Locked2 /Restriction/
1 SEX F
1 FAMS @F246@
0 @F246@ FAM
1 RESN locked
1 HUSB @I246@
1 WIFE @I247@
1 MARR
2 DATE 02 JAN 2000

03-FAM Private

This test includes a FAM record with a RESN subrecord that has the value privacy. The FAM record should be omitted from output intended to be shared with other people.

Test Result Criteria

  1. If the target application omits the privacy FAM record in output intended to be shared with other people such as exports, reports, charts, and web sites, set the test result to "Supported".

    It is acceptable to include the privacy data if the target application has an output option specifically intended to override restriction directives.

  2. If a target application rejects the RESN record with a message in its import log, set the test result to "Rejected".
  3. If a target application ignores the RESN record and does not issue an error message, set the test result to "Ignored".
  4. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I248@ and @I249@

0 @I248@ INDI
1 NAME 03-FAM Private1 /Restriction/
1 SEX M
1 FAMS @F248@
0 @I249@ INDI
1 NAME 03-FAM Private2 /Restriction/
1 SEX F
1 FAMS @F248@
0 @F248@ FAM
1 RESN privacy
1 HUSB @I248@
1 WIFE @I249@
1 MARR
2 DATE 03 JAN 2000

04-INDI Confidential

This test includes an INDI record with a RESN subrecord that has the value confidential. The INDI record should be omitted from output intended to be shared with other people.

Test Result Criteria

  1. If the target application omits the confidential INDI record in output intended to be shared with other people such as exports, reports, charts, and web sites, set the test result to "Supported".

    It is acceptable to include the confidential data if the target application has an output option specifically intended to override restriction directives.

  2. If a target application rejects the RESN record with a message in its import log, set the test result to "Rejected".
  3. If a target application ignores the RESN record and does not issue an error message, set the test result to "Ignored".
  4. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I250@

0 @I250@ INDI
1 NAME 04-INDI Confidential /Restriction/
1 SEX M
1 RESN confidential
1 BIRT
2 DATE 04 JAN 2000

05-INDI Locked

This test includes an INDI record with a RESN subrecord that has the value locked. The INDI record should be included in output intended to be shared with other people.

Test Result Criteria

  1. If the target application includes the locked INDI record in output intended to be shared with other people such as exports, reports, charts, and web sites, set the test result to "Supported".

    Target applications that include data editing capabilities (edit, delete, etc.) may indicate that a record is locked, but that feature is not required.

  2. If the target application ignores or appears to ignore the RESN record, that is acceptable. Set the test result to "Supported".
  3. If the target application rejects the RESN record with a message in its import log, set the test result to "Rejected".
  4. If a target application suppresses the INDI data in response to the RESN record, set the test result to "Imported Incorrectly".
  5. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment. This should be rare.

GEDCOM Records for @I251@

0 @I251@ INDI
1 NAME 05-INDI Locked /Restriction/
1 SEX M
1 RESN locked
1 BIRT
2 DATE 05 JAN 2000

06-INDI Private

This test includes an INDI record with a RESN subrecord that has the value privacy. The INDI record should be omitted from output intended to be shared with other people.

Test Result Criteria

  1. If the target application omits the privacy INDI record in output intended to be shared with other people such as exports, reports, charts, and web sites, set the test result to "Supported".

    It is acceptable to include the privacy data if the target application has an output option specifically intended to override restriction directives.

  2. If a target application rejects the RESN record with a message in its import log, set the test result to "Rejected".
  3. If a target application ignores the RESN record and does not issue an error message, set the test result to "Ignored".
  4. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I252@

0 @I252@ INDI
1 NAME 06-INDI Private /Restriction/
1 SEX M
1 RESN privacy
1 BIRT
2 DATE 06 JAN 2000

07-BIRT Confidential

This test includes a BIRT record with a RESN subrecord that has the value confidential. The BIRT record should be omitted from output intended to be shared with other people.

Test Result Criteria

  1. If the target application omits the confidential BIRT record in output intended to be shared with other people such as exports, reports, charts, and web sites, set the test result to "Supported".

    It is acceptable to include the confidential data if the target application has an output option specifically intended to override restriction directives.

  2. If a target application rejects the RESN record with a message in its import log, set the test result to "Rejected".
  3. If a target application ignores the RESN record and does not issue an error message, set the test result to "Ignored".
  4. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I253@

0 @I253@ INDI
1 NAME 07-BIRT Confidential /Restriction/
1 SEX M
1 BIRT
2 DATE 07 JAN 2000
2 RESN confidential

08-BIRT Locked

This test includes a BIRT record with a RESN subrecord that has the value locked. The BIRT record should be included in output intended to be shared with other people.

Test Result Criteria

  1. If the target application includes the locked BIRT record in output intended to be shared with other people such as exports, reports, charts, and web sites, set the test result to "Supported".

    Target applications that include data editing capabilities (edit, delete, etc.) may indicate that a record is locked, but that feature is not required.

  2. If the target application ignores or appears to ignore the RESN record, that is acceptable. Set the test result to "Supported".
  3. If the target application rejects the RESN record with a message in its import log, set the test result to "Rejected".
  4. If a target application suppresses the BIRT data in response to the RESN record, set the test result to "Imported Incorrectly".
  5. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment. This should be rare.

GEDCOM Records for @I254@

0 @I254@ INDI
1 NAME 08-BIRT Locked /Restriction/
1 SEX M
1 BIRT
2 DATE 08 JAN 2000
2 RESN locked

09-BIRT Private

This test includes a BIRT record with a RESN subrecord that has the value privacy. The BIRT record should be omitted from output intended to be shared with other people.

Test Result Criteria

  1. If the target application omits the privacy BIRT record in output intended to be shared with other people such as exports, reports, charts, and web sites, set the test result to "Supported".

    It is acceptable to include the privacy data if the target application has an output option specifically intended to override restriction directives.

  2. If a target application rejects the RESN record with a message in its import log, set the test result to "Rejected".
  3. If a target application ignores the RESN record and does not issue an error message, set the test result to "Ignored".
  4. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I255@

0 @I255@ INDI
1 NAME 09-BIRT Private /Restriction/
1 SEX M
1 BIRT
2 DATE 09 JAN 2000
2 RESN privacy

Letters N and S indicating non-standard 10-NAME Confidential

This test includes a NAME record with a RESN subrecord that has the value confidential. The NAME record should be omitted from output intended to be shared with other people.

GEDCOM 5.5.1 does not support the RESN record as a subrecord of the NAME record. Target applications are free to ignore or reject it.

Test Result Criteria

  1. If the target application omits or obscures the confidential NAME record in output intended to be shared with other people such as exports reports, charts, and web sites, set the test result to "Supported".

    It is acceptable to include the confidential data if the target application has an output option specifically intended to override restriction directives.

  2. For any other outcome, set the test result to "Not Supported (non-standard)" and describe the outcome in the comment.

Non-Standard Content

This test includes non-standard records or values.

GEDCOM Records for @I256@

0 @I256@ INDI
1 NAME 10-NAME Confidential /Restriction/
2 RESN confidential
1 SEX M
1 BIRT
2 DATE 10 JAN 2000

Letters N and S indicating non-standard 11-NAME Locked

This test includes a NAME record with a RESN subrecord that has the value locked. The NAME record should be included in output intended to be shared with other people.

Test Result Criteria

  1. If the target application includes the locked NAME record in output intended to be shared with other people such as reports, charts, and web sites, set the test result to "Supported".

    Target applications that include data editing capabilties (edit, delete, etc.) may indicate that a record is locked, but that feature is not required.

  2. If the target application ignores or appears to ignore the RESN record, that is acceptable. Set the test result to "Supported".
  3. If a target application suppresses the NAME data in response to the RESN record, set the test result to "Imported Incorrectly".
  4. For any other outcome, set the test result to "Not Supported (non-standard)" and describe the outcome in the comment.

Non-Standard Content

This test includes non-standard records or values.

GEDCOM Records for @I257@

0 @I257@ INDI
1 NAME 11-NAME Locked /Restriction/
2 RESN locked
1 SEX M
1 BIRT
2 DATE 11 JAN 2000

Letters N and S indicating non-standard 12-NAME Private

This test includes a NAME record with a RESN subrecord that has the value privacy. The NAME record should be omitted from output intended to be shared with other people.

GEDCOM 5.5.1 does not support the RESN record as a subrecord of the NAME record. Target applications are free to ignore or reject it.

Test Result Criteria

  1. If the target application omits or obscures the privacy NAME record in output intended to be shared with other people such as exports reports, charts, and web sites, set the test result to "Supported".

    It is acceptable to include the privacy data if the target application has an output option specifically intended to override restriction directives.

  2. For any other outcome, set the test result to "Not Supported (non-standard)" and describe the outcome in the comment.

Non-Standard Content

This test includes non-standard records or values.

GEDCOM Records for @I258@

0 @I258@ INDI
1 NAME 12-NAME Private /Restriction/
2 RESN privacy
1 SEX M
1 BIRT
2 DATE 12 JAN 2000
On This Page