ISO/IEC 19794-14:2013/Amd 1:2016
(Amendment)Information technology — Biometric data interchange formats — Part 14: DNA data — Amendment 1: Conformance testing and clarification of defects
Information technology — Biometric data interchange formats — Part 14: DNA data — Amendment 1: Conformance testing and clarification of defects
Technologies de l'information — Formats d'échange de données biométriques — Partie 14: Données ADN — Amendement 1: Essais de conformité et clarification des défauts
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 19794-14
First edition
2013-03-15
AMENDMENT 1
2016-08-15
Information technology — Biometric
data interchange formats —
Part 14:
DNA data
AMENDMENT 1: Conformance testing
and clarification of defects
Technologies de l’information — Formats d’échange de données
biométriques —
Partie 14: Données ADN
AMENDEMENT 1: Essais de conformité et clarification des défauts
Reference number
ISO/IEC 19794-14:2013/Amd.1:2016(E)
©
ISO/IEC 2016
---------------------- Page: 1 ----------------------
ISO/IEC 19794-14:2013/Amd.1:2016(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2016, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2016 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide standardization.
National bodies that are members of ISO or IEC participate in the development of International
Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. ISO and IEC technical committees collaborate in fields of
mutual interest. Other international organizations, governmental and non-governmental, in
liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO
and IEC have established a joint technical committee, ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2
(see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such
patent rights. Details of any patent rights identified during the development of the document
will be in the Introduction and/or on the ISO list of patent declarations received (see
www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and
does not constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO's adherence to the World Trade Organization
(WTO) principles in the Technical Barriers to Trade (TBT) see the following
URL: www.iso.org/iso/foreword.html.
The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 37,
Biometrics.
© ISO/IEC 2016 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
Information technology — Biometric data interchange
formats — Part 14 - DNA data –
Amendment 1 : Conformance testing and clarification
of defects
Page v, Introduction
Add the following text to the "Introduction":
"The definition of conformance testing in Annex A is distinct from the ISO/IEC 29109, which
addressed conformance testing only of the first edition of ISO/IEC 19794. This annex
addresses the ISO/IEC 19794-14:2013 revision conformance testing.
Additionally, this part of the ISO/IEC 19794 supports XML encoding, to support a spectrum of
user requirement. With XML, this part will meet the requirements of modern IT architectures.
Annex B specifies the schema that XML encoded DNA data records must conform to, and
Annex E provides an example of a valid XML encoded finger image record. "
Page 1, Clause 1, Scope
Add the following text to the "Scope":
"This part of ISO/IEC 19794 also specifies elements of conformance testing methodology, test
assertions, and test procedures as applicable to this part of ISO/IEC 19794. It establishes test
assertions pertaining to the structure of the DNA data format (Type A Level 1 as defined in
ISO/IEC 19794-1:2011/Amdt. 1:2013), test assertions pertaining to internal consistency of the
types of values that may be contained within each field (Type A Level 2 as defined in ISO/IEC
19794-1:2011/Amdt. 1:2013).
The conformance testing methodology specified in this part of ISO/IEC 19794 does not
establish:
tests of other characteristics of biometric products or other types of testing of biometric
products (e.g. acceptance, performance, robustness, security),
tests of conformance of systems that do not produce or consume data records not
conforming to the requirements of this part of ISO/IEC 19794.
The conformance testing level 1 and level 2 are defined in this Amendment, and the
conformance testing level 3 will be defined in ISO/IEC 19794-14/Amdt 2."
Page 1, Clause 2, Conformance
Add the following text to the "Conformance" Clause:
"Biometric data interchange format conformance tests conform to this part of ISO/IEC 19794 if
they satisfy all of the normative requirements set forth in Clause 6.
The description of the conformance testing methodology for ISO/IEC 19794-14 DNA data
should reflect the general characteristics of a BDIR structure as specified in the ISO/IEC
19794-1/Amdt. 1. However, the implementations of ISO/IEC 19794-14 DNA data may include
© ISO/IEC 2016 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
examples in conformance testing with biometric data record (BDB) embedded in a patron
format, e.g. CBEFF in this part of ISO/IEC 19794.
The included implementations do not necessarily need to conform to all possible aspects of this
part of ISO/IEC 19794, but only to those requirements supported by an Implementation
Conformance Statement (ICS) in accordance with Clause A.3 of ISO/IEC 19794-1:2011 Amdt.
1:2013 and Table A.1 of Annex A of this part of ISO/IEC 19794.“
Page 4, subclause 6.3, 5th paragraph
Replace:
“The CBEFF_BDB_format_type shall be specified by the CBEFF BDB format type identifier
assigned by ISO/IEC JTC1/SC37 to this DNA record format. This value is the sixteen bit value
0x0008."
With:
“The CBEFF_BDB_format_type shall be specified by the CBEFF BDB format type identifier
assigned by ISO/IEC JTC1/SC37 to this DNA record format. This value is the sixteen bit value
0x0020."
Page 13, 6.4.3.2.1, "STR DNA Profile"
Add the following text to the "STR DNA Profile" subclause:
"Because "allele call number #1" contain float number only, in case of the locus marker is
"Amelogenin", the value of "allele call number #1" shall be "0" instead of "X" or "1" instead of
"Y"."
Page 19, Annex A
Replace Annex A with the following one.
Annex A
(normative)
Conformance Testing Methodology
The testing methodology specified in Clauses A.1, A.2 and A.3 of ISO/IEC 19794-1/Amdt. 1
shall apply. The content of the tables below is based on the conformance testing methodology
outlined in 19794-1/Amdt. 1 and shall only be used in the context of that testing methodology.
A.1. Table of requirements in the base standard for conformance testing
level 1 and 2
The normative requirements of ISO/IEC 19794-14 Biometric Data Interchange Format – Part 14
DNA Data are listed in Table A.1. The supplier of the IUT shall explain which optional
components of the standard are supported and the testing laboratory shall note the results of
the test.
This table, A.1, may extend over multiple pages.
2 © ISO/IEC 2016 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
Table A.1 – Table of Requirements of the Base Standard (19794-14)
Requirement Reference in Supported Test XML
Requirement Summary Level Status IUT Support
ID Base Standard Range Result Applicability
R-1 6.3 BDB The biometric data record represented using the DNA record format may be 2 O-x No
embedded in the biometric data block (BDB) of the CBEFF patron format
compliant with ISO/IEC 19785-1:2004. If a CBEFF header is used, the following
specifications apply:
The CBEFF patron format requests to specify both CBEFF_BDB_format_owner
and CBEFF_BDB_format_type as mandatory elements in the CBEFF Header.
The CBEFF_BDB_format_owner shall be specified by the CBEFF biometric
organization identifier issued by the CBEFF registration authority to ISO/IEC
JTC1/SC37. This value is the sixteen bit value 0x0101.
The CBEFF_BDB_format_type shall be specified by the CBEFF BDB format type
identifier assigned by ISO/IEC JTC1/SC37 to this DNA record format. This value
is the sixteen bit value 0x0008
R-2 6.3 BDIR The structure of a BDIR consisting of one mandatory General Header and one or 2 M Yes
more Representation parts
R-3 6.4.1.1 The format identifier field shall be the string "DNA" 2 M Yes
R-4 6.4.1.2 The version field shall be the Major version 3 and Minor version 0 2 M Yes
R-5 6.4.1.3 The communication direction field shall contain a string listed in Table 2 of this 2 M Yes
standard.
The NationalityCode of sending party field shall contain a valid ISO 3166-2
R-6 6.4.1.4 2 M Yes
code entry.
The Name of Entity of sending party field shall contain a valid ISO 3166-2 code
R-7 6.4.1.4 1 M Yes
entry.
R-8 6.4.1.4 The Name of Person of sending party field shall contain a valid ISO 3166-2 1 M Yes
code entry.
R-9 6.4.1.5 The NationalityCode of receiving party field shall contain a valid ISO 3166-2 2 M Yes
code entry.
R-10 6.4.1.5 The Name of Entity of receiving party field shall contain a valid ISO 3166-2 1 M Yes
code entry.
R-11 6.4.1.5 The Name of Person of receiving party field shall contain a valid ISO 3166-2 1 M Yes
code entry.
R-12 6.4.1.6 The entity type field shall be in accordance with clause 6.4.1.6 2 M Yes
R-13 6.4.1.7 The date and time of data exchange field shall be in accordance with 19794-1 2 M Yes
AMD2
© ISO/IEC 2016 – All rights reserved 3
---------------------- Page: 6 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
R-14 6.4.2.1 The sample collection date field shall be in accordance with 19794-1 AMD2 2 M Yes
The sample category field shall be in accordance with Table 5.
R-15 6.4.2.2. 2 M Yes
R-16 6.4.2.3. The sample cellular type field shall be in accordance with Table 6. 2 M Yes
R-17 6.4.2.4 The sample typing technology field shall be in ccordance with Table 7. 2 M Yes
R-18 6.4.2.5 The specimen contributor field shall be in accordance with Table 8. 2 M Yes
R-19 6.4.2.6 The sample collection method field shall be in string 1 M Yes
R-20 6.4.2.7 The sample collection location field shall be in string 1 M Yes
The sample collection Geo-Location fields shall be in accordance with Table 9
R-21 6.4.2.8 2 M Yes
and WGS 84.
R-22 6.4.2.9 The pedigree tree field shall be in accordance with clause 6.4.2.9 2 M Yes
The date and time field shall be in accordance with 19794-1 AMD2
R-23 6.4.3.1.1 2 M Yes
R-24 6.4.3.1.2 The batch ID field shall be in string 1 M Yes
R-25 6.4.3.1.3 The dna profile ID field shall be in string 1 M Yes
The kit ID field shall be in string
R-26 6.4.3.1.4 1 M Yes
R-27 6.4.3.1.5 The lab certification field shall be in accordance with clause 6.4.3.1.5 and 2 M Yes
contain values from Table 15.
R-28 6.4.3.1.6 The scope of accreditation field shall be in accordance with clause 6.4.3.1.6 2 M Yes
and contain values from table 17.
R-29 6.4.3.1.7 The request type field shall be in accordance with clause 6.4.3.1.7 and contain 2 M Yes
values from Table 19.
R-30 6.4.3.1.7 The request type field shall be mandatory when the communication direction is 2 M Yes
“R” (request), otherwise optional.
R-31 6.4.3.1.8 The result field shall be in accordance with clause 6.4.3.1.8 and contain values 2 M Yes
from Table 21.
R-32 6.4.3.1.8 The result type field shall be mandatory when the communication direction is “A” 2 M Yes
(Answer), otherwise optional.
R-33 6.4.3.1.9 The error message field shall be in string 1 M
The supplementary message field shall be in string
R-34 6.4.3.1.10 1 M
R-35 6.4.3.2.1 The STR DNA profile field shall be in accordance with clause 6.4.3.2.1. 2 M Yes
R-36 6.4.3.2.1 The STR DNA profile field shall mandatory when the sample typing technology 2 M Yes
is “STR”, otherwise optional. See Table 22.
4 © ISO/IEC 2016 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
R-37 6.4.3.2.2 The Y-STR DNA profile field shall be in accordance with clause 6.4.3.2.2 2 M Yes
R-38 6.4.3.2.2 The Y-STR DNA profile field shall mandatory when the sample typing 2 M Yes
technology is “Y-STR”, otherwise optional. See Table 22.
R-39 6.4.3.2.3 The mitochondrial DNA data field shall be in accordance with clause 6.4.3.2.3 2 M Yes
R-40 6.4.3.2.3 The mitochondrial DNA data type field shall mandatory when the sample 2 M Yes
typing technology is “mtDNA”, otherwise optional. See Table 22.
R-41 6.4.3.2.4 The electropherogram data field shall be in accordance with clause 6.4.3.2.4 2 M Yes
R-42 6.4.3.2.4 The electropherogram data field shall mandatory when the sample typing 2 M Yes
technology is “Electropherogram”, otherwise optional. See Table 22.
R-43 6.4.3.2.5 The user defined DNA Data field shall be in accordance with table 42. 2 M Yes
Note. For R-1 requirement, ‘O-x’ means that CBEFF conformance testing is out of scope of this document.
A.2. Table Conformance Test Assertions
The XML encoded conformance test assertions are listed in the order in that the corresponding fields are required to appear, if present, in a conforming
record.
This table, A.1, may extend over multiple pages.
Table A.2 – XML Encoded Conformance Test Assertions
Test No. Section Requirement Level Field Name Operator Operand Test Note Status IUT Supported Test
ID Support Range Result
1 6 DNA format R-2 2 Entire field EQ BDIR has one general header and at
specification least one representation
2 6.4.1 DNA Record R-3 2 Format Identifier EQ "DNA"
General Header
3 6.4.1 DNA Record R-4 2 Version – Major version EQ 3
General Header
© ISO/IEC 2016 – All rights reserved 5
---------------------- Page: 8 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
4 6.4.1 DNA Record R-4 2 Version – Minor version EQ 0
General Header
5 6.4.1 DNA Record R-5 2 Communication Direction EQ "Request" or "Answer"
General Header
6 6.4.1 DNA Record R-6 2 Sending Party : EQ Nationality code defined in
General Header Nationality Code ISO 3166-2
7 6.4.1 DNA Record R-7 1 Sending Party : GTE Length ≥ 0
General Header Name of Entity
8 6.4.1 DNA Record R-8 1 Sending Party : GTE
Length ≥ 0
General Header Name of Person
9 6.4.1 DNA Record R-9 2 Receiving Party : EQ Nationality code defined in
General Header Nationality Code ISO 3166-2
10 6.4.1 DNA Record R-10 1 Receiving Party : GTE
Length ≥ 0
General Header Name of Entity
11 6.4.1 DNA Record R-11 1 Receiving Party : GTE Length ≥ 0
General Header Name of Person
12 6.4.1 DNA Record R-12 2 Entity Type EQ "G", "GM", "GR",
General Header "I", "IM", "IR",
"O", "OM", "OR",
"U", "UM" or "UR"
13 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 1 to 65534
General Header Processing : Year
14 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 1 to 12
General Header Processing: Month
15 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 1 to 31
General Header Processing : Day
16 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 0 to 23
General Header Processing : Hour
17 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 0 to 59
General Header Processing : Minute
18 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 0 to 59
General Header Processing : Second
6 © ISO/IEC 2016 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
19 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 0 to 999
General Header Processing : Millisecond
20 6.4.2 Representation R-14 2 Sample Collection Date : EQ 1 to 65534
Metadata Year
21 6.4.2 Representation R-14 2 Sample Collection Date : EQ 1 to 12
Metadata Month
22 6.4.2 Representation R-14 2 Sample Collection Date : EQ 1 to 31
Metadata Day
23 6.4.2 Representation R-14 2 Sample Collection Date : EQ 0 to 23
Metadata Hour
24 6.4.2 Representation R-14 2 Sample Collection Date : EQ 0 to 59
Metadata Minute
25 6.4.2 Representation R-14 2 Sample Collection Date : EQ 0 to 59
Metadata Second
26 6.4.2 Representation R-14 2 Sample Collection Date : EQ 0 to 999
Metadata Millisecond
© ISO/IEC 2016 – All rights reserved 7
---------------------- Page: 10 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
27 6.4.2 Representation R-15 2 Sample Category EQ "Arrestee",
Metadata "Claimed Biological Child",
"Claimed Biological Father",
"Claimed Biological Mother",
"Claimed Biological Sibling",
"Claimed Biological Spouse",
"Actual Biological Child",
"Actual Biological Father",
"Actual Biological Mother",
"Actual Biological Sibling",
"Actual Biological Spouse",
"Adoptive Biological Child",
"Adoptive Biological Father",
"Adoptive Biological Mother",
"Adoptive Biological Sibling",
"Adoptive Biological Spouse",
"Convicted Offender",
"Forensic, Unknown",
"Insurgent",
"Known Suspected Terrorist",
"Maternal Relative",
"Missing Person",
"Paternal Relative",
"Suspect, Known",
"Unidentified Living",
"Unidentified Dead",
"Victim, Known",
"Detainee",
"Other" or
"Unspecified"
8 © ISO/IEC 2016 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
28 6.4.2 Representation R-16 2 Sample Cellular Type EQ "Blood",
Metadata "Bone",
"Commingled Biological Material",
"Hair",
"Saliva",
"Semen",
"Skin",
"Sweat/Fingerprint",
"Tissue",
"Tooth (including Pulp)",
"Other",
"Unknown" or
"Unspecified"
29 6.4.2 Representation R-17 2 Sample Typing EQ "STR",
Metadata Technology "Y-STR",
"mtDNA",
"Electropherogram" or
"User Defined Typing"
30 6.4.2 Representation R-18 2 Specimen Contributor EQ "Known" or "Unknown"
Metadata
31 6.4.2 Representation R-19 1 Sample Collection Method GTE
Length ≥ 0
Metadata
32 6.4.2 Representation R-20 1 Sample Collection GTE Length ≥ 0
Metadata Location
33 6.4.2 Representation R-21 2 Sample Collection Geo- EQ -90.0 ≤ latitude ≤ +90.0
Metadata Location : Latitude
34 6.4.2 Representation R-21 2 Sample Collection Geo- EQ -180.0 ≤ longitude ≤ +180.0
Metadata Location : Longitude
Pedigree Tree :
35 6.4.2 Representation R-22 2 GT 0
Pedigree Member ID
Metadata
Pedigree Tree :
36 6.4.2 Representation R-22 2 LTE Length ≤ 24
Specimen ID
Metadata
Pedigree Tree :
37 6.4.2 Representation R-22 2 GT 0
Mother ID
Metadata
Pedigree Tree :
38 6.4.2 Representation R-22 2 GT 0
Father ID
Metadata
© ISO/IEC 2016 – All rights reserved 9
---------------------- Page: 12 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
Pedigree Tree :
39 6.4.2 Representation R-22 2 EQ "Known" or "Unknown"
Specimen ID
Metadata
Pedigree Tree :
40 6.4.2 Representation R-22 2 EQ "Male" or "Female"
Specimen ID
Metadata
41 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 1 to 65534
Analysis : Year
42 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 1 to 12
Analysis : Month
43 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 1 to 31
Analysis : Day
44 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 0 to 23
Analysis : Hour
45 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 0 to 59
Analysis : Minute
46 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 0 to 59
Analysis : Second
47 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 0 to 999
Analysis : Millisecond
48 6.4.3.1 DNA Typing Data R-24 1 Batch ID GTE
Length ≥ 0
49 6.4.3.1 DNA Typing Data R-25 1 DNA Profile ID GTE
Length ≥ 0
50 6.4.3.1 DNA Typing Data R-26 1 Kit ID GTE Length ≥ 0
51 6.4.3.1 DNA Typing Data R-27 2 Lab Certification EQ "No validation",
"ISO/IEC 17025 (KOLAS) certification",
"GLP validation",
"AABB certification",
"ISO/ILAC Guild 19 accreditation",
"Unknown" or
"Unspecified"
52 6.4.3.1 DNA Typing Data R-28 2 Scope of Accreditation EQ "Nuclear",
"Mitochondrial",
"Database",
"Other" or
"Unspecified"
10 © ISO/IEC 2016 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
53 6.4.3.1 DNA Typing Data R-29 2 Request Type EQ "Data submission",
"Data submission and Search",
"Search",
"User Defined"
54 6.4.3.1 DNA Typing Data R-30 2 (Request Type field == C Communication direction,
Mandatory) “Request”
55 6.4.3.1 DNA Typing Data R-31 2 Result EQ "Unable to Process",
"No Hit",
"Hit User Defined",
"User Defined"
56 6.4.3.1 DNA Typing Data R-32 2 (Result field == C Communication direction,
Mandatory) “answer"
57 6.4.3.1 DNA Typing Data R-33 1 Error Message GTE Length ≥ 0
58 6.4.3.1 DNA Typing Data R-34 1 Supplementary Message GTE
Length ≥ 0
59 6.4.3.2 DNA Typing R-35 2 STR DNA Profile : EQ Name of Locus marker in Annex D
Locus infomation :
Locus header :
Name of Locus marker
60 6.4.3.2 DNA Typing R-35 2 STR DNA Profile : EQ ”Normal”,
Locus infomation : “Silent allele”,
Locus header : “Not determined”, or
Status “Not analyzed”
61 6.4.3.2 DNA Typing R-35 2 STR DNA Profile : EQ "Equal",
Locus infomation : "Lower-limit",
Allele call : "Upper-limit" or
Operator "Range"
62 6.4.3.2 DNA Typing R-35 1 STR DNA Profile :
Locus infomation :
Allele call :
Allele call number #1
63 6.4.3.2 DNA Typing R-35 2 STR DNA Profile : C STR DNA Profile : Locus infomation :
Locus infomation : Allele call : Operator,
Allele call : “Range”
Allele call number #2
© ISO/IEC 2016 – All rights reserved 11
---------------------- Page: 14 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
64 6.4.3.2 DNA Typing R-36 2 (STR DNA Profile field == C Sample Typing Technology,
Mandatory) “STR”
65 6.4.3.2 DNA Typing R-37 2 Y-STR DNA Profile : EQ Name of Locus marker in Annex D
Locus infomation :
Locus header :
Name of Locus marker
66 6.4.3.2 DNA Typing R-37 2 Y-STR DNA Profile : EQ Normal”,
Locus infomation : “Silent allele”,
Locus header : “Not determined”, or
Status “Not analyzed”
67 6.4.3.2 DNA Typing R-37 2 Y-STR DNA Profile : EQ "Equal",
Locus infomation : "Lower-limit",
Locus header : "Upper-limit" or
Operator "Range"
68 6.4.3.2 DNA Typing R-37 1 Y-STR DNA Profile :
Locus infomation :
Allele call :
Allele call number #1
69 6.4.3.2 DNA Typing R-37 2 Y-STR DNA Profile : C STR DNA Profile : Locus infomation :
Locus infomation : Allele call : Operator,
Allele call : “Range”
Allele call number #2
70 6.4.3.2 DNA Typing R-38 2 (Y-STR DNA Profile field C Sample Typing Technology,
== Mandatory) “Y-STR”
71 6.4.3.2 DNA Typing R-39 2 mtDNA Data : EQ string consists only the character listed
Mito control region1 in Table 28
72 6.4.3.2 DNA Typing R-39 2 mtDNA Data : EQ string consists only the character listed
Mito control region2 in Table 28
73 6.4.3.2 DNA Typing R-39 1 mtDNA Data :
Mito DNA Quality 1
74 6.4.3.2 DNA Typing R-39 1 mtDNA Data :
Mito DNA Quality 2
75 6.4.3.2 DNA Typing R-40 2 (mtDNA data field == C Sample Typing Technology
Mandatory) “mtDNA”
12 © ISO/IEC 2016 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
Electropherogram data :
76 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Run Name
Electropherogram data :
77 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Sample File Name
Electropherogram data :
78 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Electropherogram Dye
Data:
Dye name
Electropherogram data :
79 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Electropherogram Time
Data:
Time in the run
Electropherogram data :
80 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Electropherogram Time
Data:
Fluorescence strenth
Electropherogram data :
81 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Base Pair
Correspondence Data :
Correspondence Data :
Run Name
Electropherogram data :
82 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Base Pair
Correspondence Data :
Correspondence Data :
Sample File Name
© ISO/IEC 2016 – All rights reserved 13
---------------------- Page: 16 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
Electropherogram data :
83 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Base Pair
Correspondence Data :
Correspondence Data :
Time in the run
Electropherogram data :
84 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Base Pair
Correspondence Data :
Correspondence Data :
Base Pair Size
Electropherogram data :
85 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Panel Data :
Primer Set Name
Electropherogram data :
86 6.4.3.2 DNA Typing R-41 2 EQ Name of Locus marker in Annex D
Electropherogram Data :
Panel Data :
Panel Allele Data :
Locus Name
Electropherogram data :
87 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Panel Data :
Panel Allele Data :
Dye Name
Electropherogram data :
88 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Panel Data :
Panel Allele Data :
Minimun Allele Size
Electropherogram data :
89 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Panel Data :
Panel Allele Data :
Maximum Allele Size
Electropherogram data :
90 6.4.3.2 DNA Typing R-41 2 EQ 0.0 to 1.0
Electropherogram Data :
Panel Data :
Panel Allele Data :
Noise Ratio
Electropherogram data :
91 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Bin Data :
Primer Set Name
14 © ISO/IEC 2016 – All rights reserved
---------------------- Page: 17 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
Electropherogram data :
92 6.4.3.2 DNA Typing R-41 2 EQ Name of Locus marker in Annex D
Electropherogram Data :
Bin Data :
Bin Locus Data :
Locus Name
Electropherogram data :
93 6.4.3.2 DNA Typing R-41 2 See Test
Electropherogram Data :
54 to 56.
Bin Data :
Bin Locus Data :
Bin Call Data :
Allele Call
Electropherogram data :
94 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Bin Data :
Bin Locus Data :
Bin Call Data :
Average Base Pair Size
Electropherogram data :
95 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Bin Data :
Bin Locus Data :
Bin Call Data :
Minus Deviation Base Pair
Size
Electropherogram data :
96 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Bin Data :
Bin Locus Data :
Bin Call Data :
Plus Deviation Base Pair
Size
Electropherogram data :
97 6.4.3.2 DNA Typing R-41 2 See Test
Reference
69 to 73.
Electropherogram Data :
Time and Fluorescence
Strength Data
Electropherogram data :
98 6.4.3.2 DNA Typing R-41 2 See Test
Electropherogram Data
69 to 73.
Mitocondrial Sequence
Data :
Time and Fluorescence
Strength Data
© ISO/IEC 2016 – All rights reserved 15
---------------------- Page: 18 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
Electropherogram data :
99 6.4.3.2 DNA Typing R-41 1
Electropherogram Data
Mitocondrial Sequence
Data :
Dye assignment for Base :
Dye Name
Electropherogram data :
100 6.4.3.2 DNA Typing R-41 2 EQ string consists only the character listed
Electropherogram Data
in Table 28
Mitocondrial Sequence
Data :
Dye assignment for Base :
Base type
101 6.4.3.2 DNA Typing R-42 2 (Electropherogram data C Sample Typing Technology
field == Mandatory) “Electropherogram”
User Defined DNA Data :
102 6.4.3.2 DNA Typing R-43 2 GTE Length ≥ 0
TypeCode
User Defined DNA Data :
103 6.4.3.2 DNA Typing R-43 2 EQ Base 64 Encoding
Data
Note: Operator 'C' means the following: If the value of the field that corresponds to the first operand is equal to the value of the second operand, this field is
mandatory. For example, when operator 'C' is set and the operands are "Communication direction" and "Answer", this is interpreted as follows. If the value
of "Communication direction" field is the same as "Answer", this field is mandatory.
16 © ISO/IEC 2016 – All rights reserved
---------------------- Page: 19 ----------------------
ISO/IEC 19794-14:2013/AMD.1:2016(E)
A.3. Sample XML
DRAFT AMENDMENT
ISO/IEC 19794-14: DAM 1
ISO/IEC JTC 1/SC 37 Secretariat: ANSI
Voting begins on: Voting terminates on:
2015-05-04 2015-08-04
Information technology — Biometric data interchange
formats —
Part 14:
DNA data
AMENDMENT 1: Conformance testing and clarification defects
Technologies de l’information — Formats d’échange de données biométriques —
Partie 14: Données ADN
AMENDEMENT 1:
ICS: 35.040
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/IEC 19794-14:2013/DAM 1:2015(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
©
PROVIDE SUPPORTING DOCUMENTATION. ISO/IEC 2015
---------------------- Page: 1 ----------------------
ISO/IEC 19794-14:2013/DAM 1:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2015
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2015 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19794-14 DAM 1
Foreword
ISO (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide standardization.
National bodies that are members of ISO or IEC participate in the development of International
Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. ISO and IEC technical committees collaborate in fields of
mutual interest. Other international organizations, governmental and non-governmental, in
liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO
and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives,
Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft
International Stand-ards adopted by the joint technical committee are circulated to national
bodies for voting. Publication as an International Standard requires approval by at least 75 % of
the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such
patent rights.
Amendment 2 to ISO/IEC 19794-14:2013 was prepared by Joint Technical Committee ISO/IEC
JTC 1, Information technology, Subcommittee SC 37, Biometrics.
3
---------------------- Page: 3 ----------------------
ISO/IEC 19794-14 DAM 1
Information Technology — Biometric Data Interchange
Formats — Part 14 - DNA Data – Amendment 1 :
Conformance Testing and Clarification of Defects
1. The following text is to be added to the "Introduction" clause of ISO/IEC 19794-14:
The definition of conformance testing in annex A is distinct from the ISO/IEC 29109, which
addressed conformance testing only of the first version of the ISO/IEC 19794 standard. This
annex addresses the ISO/IEC 19794-14:2013 revision conformance testing.
Additionally, this part of the ISO/IEC standard supports XML encoding, to support a spectrum of
user requirement. With XML, this part will meet the requirements of modern IT architectures.
Annex B specifies the schema that XML encoded DNA data records must conform to, and
Annex E provides an example of a valid XML encoded finger image record.
2. The following text is to be added to the "Scope" clause of ISO/IEC 19794-14:
This part of ISO/IEC 19794 also specifies elements of conformance testing methodology, test
assertions, and test procedures as applicable to this part of ISO/IEC 19794. It establishes test
assertions pertaining to the structure of the DNA data format (Type A Level 1 as defined in
ISO/IEC 19794-1:201X AMD 1), test assertions pertaining to internal consistency of the types
of values that may be contained within each field (Type A Level 2 as defined in ISO/IEC
19794-1:201X AMD 1), and semantic test assertions (Type A Level 3 as defined in ISO/IEC
19794-1:201X AMD 1).
The conformance testing methodology specified in this part of ISO/IEC 19794 does not
establish:
tests of other characteristics of biometric products or other types of testing of
biometric products (e.g. acceptance, performance, robustness, security),
tests of conformance of systems that do not produce or consume data records not
conforming to the requirements of this part of ISO/IEC 19794.
The conformance testing level 1 and level 2 defined in ISO/IEC 19794-14:201X AMD 1, and the
conformance testing level 3 defined in ISO/IEC 19794-14:201X AMD 2.
3. The following text is to be added to the "Conformance" clause of ISO/IEC 19794-14:
Biometric data interchange format conformance tests conform to this part of ISO/IEC 19794 if
they satisfy all of the normative requirements set forth in clauses X, Y, and Z. In consideration
of the semantic specifics in different parts of 19794, all level 1, level 2, and level 3 tests shall
use the assertions defined in Table N of clause M in this part of 19794 in conformity with the
concept and rules set in 19794-1/AMD1
The description of the conformance testing methodology for ISO/IEC 19794-14 DNA data
should reflect the general characteristics of a BDIR structure as specified in the ISO/IEC
19794-1/AMD1. However, the implementations of ISO/IEC 19794-14 DNA data may include
examples in conformance testing with biometric data record (BDB) embedded in a patron
4
---------------------- Page: 4 ----------------------
ISO/IEC 19794-14 DAM 1
format, e.g. CBEFF in this part of ISO/IEC 19794.
The included implementations do not necessarily need to conform to all possible aspects of this
part of ISO/IEC 19794, but only to those requirements supported by an Implementation
Conformance Statement (ICS) in accordance with Clause K of ISO/IEC 19794-1:201x AMD 1
and Table K of Clause R of this part of ISO/IEC 19794.
4. The following text is to be added to the " STR DNA Profile“ clause of ISO/IEC 19794-14.
Because "allele call number #1" contain float number only, in case of the locus marker is
"Amelogenin", the value of "allele call number #1" shall be "0" instead of "X" or "1" instead of
"Y".
5. The following text is to be replaced in clause 6.3 of ISO/IEC 19794-14.
Replace :
“The CBEFF_BDB_format_type shall be specified by the CBEFF BDB format type identifier
assigned by ISO/IEC JTC1/SC37 to this DNA record format. This value is the sixteen bit value
0x0008.“
With
“The CBEFF_BDB_format_type shall be specified by the CBEFF BDB format type identifier
assigned by ISO/IEC JTC1/SC37 to this DNA record format. This value is the sixteen bit value
0x0020.“
6. Replace Annex A of ISO/IEC 19794-14:2013 with the following one
Annex A. Conformance Testing Methodology
(normative)
The testing methodology specified in Clauses A.1, A.2 and A.3 of ISO/IEC 19794-1/AMD1 shall
apply. The content of the tables below is based on the conformance testing methodology
outlined in 19794-1/AMD1 and shall only be used in the context of that testing methodology
A.1. Table of requirement in the base standard for conformance testing
level 1 and 2
The normative requirements of ISO/IEC 19794-14 Biometric Data Interchange Format – Part 14
DNA Data are listed in Table A.1. The supplier of the IUT shall explain which optional
components of the standard are supported and the testing laboratory shall note the results of
the test.
This table, A.1, may extend over multiple pages.
5
---------------------- Page: 5 ----------------------
Table A.1 – Table of Requirements of the Base Standard (19794-14)
Requirement Reference in Supported Test XML
Requirement Summary Level Status IUT Support
ID Base Standard Range Result Applicability
R-1 6.3 BDB The biometric data record represented using the DNA record format may be 2 O-x No
embedded in the biometric data block (BDB) of the CBEFF patron format
compliant with ISO/IEC 19785-1:2004. If a CBEFF header is used, the following
specifications apply:
The CBEFF patron format requests to specify both CBEFF_BDB_format_owner
and CBEFF_BDB_format_type as mandatory elements in the CBEFF Header.
The CBEFF_BDB_format_owner shall be specified by the CBEFF biometric
organization identifier issued by the CBEFF registration authority to ISO/IEC
JTC1/SC37. This value is the sixteen bit value 0x0101.
The CBEFF_BDB_format_type shall be specified by the CBEFF BDB format type
identifier assigned by ISO/IEC JTC1/SC37 to this DNA record format. This value
is the sixteen bit value 0x0008
R-2 6.3 BDIR The structure of a BDIR consisting of one mandatory General Header and one or 2 M Yes
more Representation parts
R-3 6.4.1.1 The format identifier field shall be the string "DNA" 2 M Yes
R-4 6.4.1.2 The version field shall be the Major version 3 and Minor version 0 2 M Yes
R-5 6.4.1.3 The communication direction field shall contain a string listed in Table 2 of this 2 M Yes
standard.
R-6 6.4.1.4 The NationalityCode of sending party field shall contain a valid ISO 3166-2 2 M Yes
code entry.
R-7 6.4.1.4 The Name of Entity of sending party field shall contain a valid ISO 3166-2 code 1 M Yes
entry.
R-8 6.4.1.4 The Name of Person of sending party field shall contain a valid ISO 3166-2 1 M Yes
code entry.
R-9 6.4.1.5 The NationalityCode of receiving party field shall contain a valid ISO 3166-2 2 M Yes
code entry.
R-10 6.4.1.5 The Name of Entity of receiving party field shall contain a valid ISO 3166-2 1 M Yes
code entry.
R-11 6.4.1.5 The Name of Person of receiving party field shall contain a valid ISO 3166-2 1 M Yes
code entry.
R-12 6.4.1.6 The entity type field shall be in accordance with clause 6.4.1.6 2 M Yes
R-13 6.4.1.7 The date and time of data exchange field shall be in accordance with 19794-1 2 M Yes
AMD2
6
---------------------- Page: 6 ----------------------
ISO/IEC 19794-14 DAM 1
R-14 6.4.2.1 The sample collection date field shall be in accordance with 19794-1 AMD2 2 M Yes
R-15 6.4.2.2. The sample category field shall be in accordance with Table 5. 2 M Yes
R-16 6.4.2.3. The sample cellular type field shall be in accordance with Table 6. 2 M Yes
R-17 6.4.2.4 The sample typing technology field shall be in ccordance with Table 7. 2 M Yes
R-18 6.4.2.5 The specimen contributor field shall be in accordance with Table 8. 2 M Yes
R-19 6.4.2.6 The sample collection method field shall be in string 1 M Yes
R-20 6.4.2.7 The sample collection location field shall be in string 1 M Yes
R-21 6.4.2.8 The sample collection Geo-Location fields shall be in accordance with Table 9 2 M Yes
and WGS 84.
R-22 6.4.2.9 The pedigree tree field shall be in accordance with clause 6.4.2.9 2 M Yes
R-23 6.4.3.1.1 The date and time field shall be in accordance with 19794-1 AMD2 2 M Yes
R-24 6.4.3.1.2 The batch ID field shall be in string 1 M Yes
R-25 6.4.3.1.3 The dna profile ID field shall be in string 1 M Yes
R-26 6.4.3.1.4 The kit ID field shall be in string 1 M Yes
R-27 6.4.3.1.5 The lab certification field shall be in accordance with clause 6.4.3.1.5 and 2 M Yes
contain values from Table 15.
R-28 6.4.3.1.6 The scope of accreditation field shall be in accordance with clause 6.4.3.1.6 2 M Yes
and contain values from table 17.
R-29 6.4.3.1.7 The request type field shall be in accordance with clause 6.4.3.1.7 and contain 2 M Yes
values from Table 19.
R-30 6.4.3.1.7 The request type field shall be mandatory when the communication direction is 2 M Yes
“R” (request), otherwise optional.
R-31 6.4.3.1.8 The result field shall be in accordance with clause 6.4.3.1.8 and contain values 2 M Yes
from Table 21.
R-32 6.4.3.1.8 The result type field shall be mandatory when the communication direction is “A” 2 M Yes
(Answer), otherwise optional.
R-33 6.4.3.1.9 The error message field shall be in string 1 M
R-34 6.4.3.1.10 The supplementary message field shall be in string 1 M
R-35 6.4.3.2.1 The STR DNA profile field shall be in accordance with clause 6.4.3.2.1. 2 M Yes
R-36 6.4.3.2.1 The STR DNA profile field shall mandatory when the sample typing technology 2 M Yes
is “STR”, otherwise optional. See Table 22.
7
---------------------- Page: 7 ----------------------
ISO/IEC 19794-14 DAM 1
R-37 6.4.3.2.2 The Y-STR DNA profile field shall be in accordance with clause 6.4.3.2.2 2 M Yes
R-38 6.4.3.2.2 The Y-STR DNA profile field shall mandatory when the sample typing 2 M Yes
technology is “Y-STR”, otherwise optional. See Table 22.
R-39 6.4.3.2.3 The mitochondrial DNA data field shall be in accordance with clause 6.4.3.2.3 2 M Yes
R-40 6.4.3.2.3 The mitochondrial DNA data type field shall mandatory when the sample 2 M Yes
typing technology is “mtDNA”, otherwise optional. See Table 22.
R-41 6.4.3.2.4 The electropherogram data field shall be in accordance with clause 6.4.3.2.4 2 M Yes
R-42 6.4.3.2.4 The electropherogram data field shall mandatory when the sample typing 2 M Yes
technology is “Electropherogram”, otherwise optional. See Table 22.
R-43 6.4.3.2.5 The user defined DNA Data field shall be in accordance with table 42. 2 M Yes
Note. For R-1 requirement, ‘O-x’ means that CBEFF conformance testing is out of scope of this document.
A.2. Table Conformance Test Assertions
The XML encoded conformance test assertions are listed in the order in that the corresponding fields are required to appear, if present, in a conforming
record.
This table, A.1, may extend over multiple pages.
Table A.2 – XML Encoded Conformance Test Assertions
Test No. Section Requirement Level Field Name Operator Operand Test Note Status IUT Supported Test
ID Support Range Result
1 6 DNA format R-2 2 Entire field EQ BDIR has one general header and at
specification least one representation
2 6.4.1 DNA Record R-3 2 Format Identifier EQ "DNA"
General Header
3 6.4.1 DNA Record R-4 2 Version – Major version EQ 3
General Header
8
---------------------- Page: 8 ----------------------
ISO/IEC 19794-14 DAM 1
4 6.4.1 DNA Record R-4 2 Version – Minor version EQ 0
General Header
5 6.4.1 DNA Record R-5 2 Communication Direction EQ "Request" or "Answer"
General Header
6 6.4.1 DNA Record R-6 2 Sending Party : EQ Nationality code defined in
General Header Nationality Code ISO 3166-2
7 6.4.1 DNA Record R-7 1 Sending Party : GTE Length ≥ 0
General Header Name of Entity
8 6.4.1 DNA Record R-8 1 Sending Party : GTE
Length ≥ 0
General Header Name of Person
9 6.4.1 DNA Record R-9 2 Receiving Party : EQ Nationality code defined in
General Header Nationality Code ISO 3166-2
10 6.4.1 DNA Record R-10 1 Receiving Party : GTE
Length ≥ 0
General Header Name of Entity
11 6.4.1 DNA Record R-11 1 Receiving Party : GTE Length ≥ 0
General Header Name of Person
12 6.4.1 DNA Record R-12 2 Entity Type EQ "G", "GM", "GR",
General Header "I", "IM", "IR",
"O", "OM", "OR",
"U", "UM" or "UR"
13 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 1 to 65534
General Header Processing : Year
14 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 1 to 12
General Header Processing: Month
15 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 1 to 31
General Header Processing : Day
16 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 0 to 23
General Header Processing : Hour
17 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 0 to 59
General Header Processing : Minute
18 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 0 to 59
General Header Processing : Second
9
---------------------- Page: 9 ----------------------
ISO/IEC 19794-14 DAM 1
19 6.4.1 DNA Record R-13 2 Date and Time of Data EQ 0 to 999
General Header Processing : Millisecond
20 6.4.2 Representation R-14 2 Sample Collection Date : EQ 1 to 65534
Metadata Year
21 6.4.2 Representation R-14 2 Sample Collection Date : EQ 1 to 12
Metadata Month
22 6.4.2 Representation R-14 2 Sample Collection Date : EQ 1 to 31
Metadata Day
23 6.4.2 Representation R-14 2 Sample Collection Date : EQ 0 to 23
Metadata Hour
24 6.4.2 Representation R-14 2 Sample Collection Date : EQ 0 to 59
Metadata Minute
25 6.4.2 Representation R-14 2 Sample Collection Date : EQ 0 to 59
Metadata Second
26 6.4.2 Representation R-14 2 Sample Collection Date : EQ 0 to 999
Metadata Millisecond
10
---------------------- Page: 10 ----------------------
ISO/IEC 19794-14 DAM 1
27 6.4.2 Representation R-15 2 Sample Category EQ "Arrestee",
Metadata "Claimed Biological Child",
"Claimed Biological Father",
"Claimed Biological Mother",
"Claimed Biological Sibling",
"Claimed Biological Spouse",
"Actual Biological Child",
"Actual Biological Father",
"Actual Biological Mother",
"Actual Biological Sibling",
"Actual Biological Spouse",
"Adoptive Biological Child",
"Adoptive Biological Father",
"Adoptive Biological Mother",
"Adoptive Biological Sibling",
"Adoptive Biological Spouse",
"Convicted Offender",
"Forensic, Unknown",
"Insurgent",
"Known Suspected Terrorist",
"Maternal Relative",
"Missing Person",
"Paternal Relative",
"Suspect, Known",
"Unidentified Living",
"Unidentified Dead",
"Victim, Known",
"Detainee",
"Other" or
"Unspecified"
11
---------------------- Page: 11 ----------------------
ISO/IEC 19794-14 DAM 1
28 6.4.2 Representation R-16 2 Sample Cellular Type EQ "Blood",
Metadata "Bone",
"Commingled Biological Material",
"Hair",
"Saliva",
"Semen",
"Skin",
"Sweat/Fingerprint",
"Tissue",
"Tooth (including Pulp)",
"Other",
"Unknown" or
"Unspecified"
29 6.4.2 Representation R-17 2 Sample Typing EQ "STR",
Metadata Technology "Y-STR",
"mtDNA",
"Electropherogram" or
"User Defined Typing"
30 6.4.2 Representation R-18 2 Specimen Contributor EQ "Known" or "Unknown"
Metadata
31 6.4.2 Representation R-19 1 Sample Collection Method GTE
Length ≥ 0
Metadata
32 6.4.2 Representation R-20 1 Sample Collection GTE Length ≥ 0
Metadata Location
33 6.4.2 Representation R-21 2 Sample Collection Geo- EQ -90.0 ≤ latitude ≤ +90.0
Metadata Location : Latitude
34 6.4.2 Representation R-21 2 Sample Collection Geo- EQ -180.0 ≤ longitude ≤ +180.0
Metadata Location : Longitude
Pedigree Tree :
35 6.4.2 Representation R-22 2 GT 0
Pedigree Member ID
Metadata
Pedigree Tree :
36 6.4.2 Representation R-22 2 LTE Length ≤ 24
Specimen ID
Metadata
Pedigree Tree :
37 6.4.2 Representation R-22 2 GT 0
Mother ID
Metadata
Pedigree Tree :
38 6.4.2 Representation R-22 2 GT 0
Father ID
Metadata
12
---------------------- Page: 12 ----------------------
ISO/IEC 19794-14 DAM 1
Pedigree Tree :
39 6.4.2 Representation R-22 2 EQ "Known" or "Unknown"
Specimen ID
Metadata
Pedigree Tree :
40 6.4.2 Representation R-22 2 EQ "Male" or "Female"
Specimen ID
Metadata
41 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 1 to 65534
Analysis : Year
42 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 1 to 12
Analysis : Month
43 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 1 to 31
Analysis : Day
44 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 0 to 23
Analysis : Hour
45 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 0 to 59
Analysis : Minute
46 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 0 to 59
Analysis : Second
47 6.4.3.1 DNA Typing Data R-23 2 Date and Time of EQ 0 to 999
Analysis : Millisecond
48 6.4.3.1 DNA Typing Data R-24 1 Batch ID GTE
Length ≥ 0
49 6.4.3.1 DNA Typing Data R-25 1 DNA Profile ID GTE Length ≥ 0
50 6.4.3.1 DNA Typing Data R-26 1 Kit ID GTE Length ≥ 0
51 6.4.3.1 DNA Typing Data R-27 2 Lab Certification EQ "No validation",
"ISO/IEC 17025 (KOLAS) certification",
"GLP validation",
"AABB certification",
"ISO/ILAC Guild 19 accreditation",
"Unknown" or
"Unspecified"
52 6.4.3.1 DNA Typing Data R-28 2 Scope of Accreditation EQ "Nuclear",
"Mitochondrial",
"Database",
"Other" or
"Unspecified"
13
---------------------- Page: 13 ----------------------
ISO/IEC 19794-14 DAM 1
53 6.4.3.1 DNA Typing Data R-29 2 Request Type EQ "Data submission",
"Data submission and Search",
"Search",
"User Defined"
54 6.4.3.1 DNA Typing Data R-30 2 (Request Type field == C Communication direction,
Mandatory) “Request”
55 6.4.3.1 DNA Typing Data R-31 2 Result EQ "Unable to Process",
"No Hit",
"Hit User Defined",
"User Defined"
56 6.4.3.1 DNA Typing Data R-32 2 (Result field == C Communication direction,
Mandatory) “answer"
57 6.4.3.1 DNA Typing Data R-33 1 Error Message GTE Length ≥ 0
58 6.4.3.1 DNA Typing Data R-34 1 Supplementary Message GTE
Length ≥ 0
59 6.4.3.2 DNA Typing R-35 2 STR DNA Profile : EQ Name of Locus marker in Annex D
Locus infomation :
Locus header :
Name of Locus marker
60 6.4.3.2 DNA Typing R-35 2 STR DNA Profile : EQ ”Normal”,
Locus infomation : “Silent allele”,
Locus header : “Not determined”, or
Status “Not analyzed”
61 6.4.3.2 DNA Typing R-35 2 STR DNA Profile : EQ "Equal",
Locus infomation : "Lower-limit",
Allele call : "Upper-limit" or
Operator "Range"
62 6.4.3.2 DNA Typing R-35 1 STR DNA Profile :
Locus infomation :
Allele call :
Allele call number #1
63 6.4.3.2 DNA Typing R-35 2 STR DNA Profile : C STR DNA Profile : Locus infomation :
Locus infomation : Allele call : Operator,
Allele call : “Range”
Allele call number #2
14
---------------------- Page: 14 ----------------------
ISO/IEC 19794-14 DAM 1
64 6.4.3.2 DNA Typing R-36 2 (STR DNA Profile field == C Sample Typing Technology,
Mandatory) “STR”
65 6.4.3.2 DNA Typing R-37 2 Y-STR DNA Profile : EQ Name of Locus marker in Annex D
Locus infomation :
Locus header :
Name of Locus marker
66 6.4.3.2 DNA Typing R-37 2 Y-STR DNA Profile : EQ Normal”,
Locus infomation : “Silent allele”,
Locus header : “Not determined”, or
Status “Not analyzed”
67 6.4.3.2 DNA Typing R-37 2 Y-STR DNA Profile : EQ "Equal",
Locus infomation : "Lower-limit",
Locus header : "Upper-limit" or
Operator "Range"
68 6.4.3.2 DNA Typing R-37 1 Y-STR DNA Profile :
Locus infomation :
Allele call :
Allele call number #1
69 6.4.3.2 DNA Typing R-37 2 Y-STR DNA Profile : C STR DNA Profile : Locus infomation :
Locus infomation : Allele call : Operator,
Allele call : “Range”
Allele call number #2
70 6.4.3.2 DNA Typing R-38 2 (Y-STR DNA Profile field C Sample Typing Technology,
== Mandatory) “Y-STR”
71 6.4.3.2 DNA Typing R-39 2 mtDNA Data : EQ string consists only the character listed
Mito control region1 in Table 28
72 6.4.3.2 DNA Typing R-39 2 mtDNA Data : EQ string consists only the character listed
Mito control region2 in Table 28
73 6.4.3.2 DNA Typing R-39 1 mtDNA Data :
Mito DNA Quality 1
74 6.4.3.2 DNA Typing R-39 1 mtDNA Data :
Mito DNA Quality 2
75 6.4.3.2 DNA Typing R-40 2 (mtDNA data field == C Sample Typing Technology
Mandatory) “mtDNA”
15
---------------------- Page: 15 ----------------------
ISO/IEC 19794-14 DAM 1
Electropherogram data :
76 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Run Name
Electropherogram data :
77 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Sample File Name
Electropherogram data :
78 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Electropherogram Dye
Data:
Dye name
Electropherogram data :
79 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Electropherogram Time
Data:
Time in the run
Electropherogram data :
80 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Fluorescence
Strength Data :
Electropherogram Time
Data:
Fluorescence strenth
Electropherogram data :
81 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Base Pair
Correspondence Data :
Correspondence Data :
Run Name
Electropherogram data :
82 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Base Pair
Correspondence Data :
Correspondence Data :
Sample File Name
16
---------------------- Page: 16 ----------------------
ISO/IEC 19794-14 DAM 1
Electropherogram data :
83 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Base Pair
Correspondence Data :
Correspondence Data :
Time in the run
Electropherogram data :
84 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Time and Base Pair
Correspondence Data :
Correspondence Data :
Base Pair Size
Electropherogram data :
85 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Panel Data :
Primer Set Name
Electropherogram data :
86 6.4.3.2 DNA Typing R-41 2 EQ Name of Locus marker in Annex D
Electropherogram Data :
Panel Data :
Panel Allele Data :
Locus Name
Electropherogram data :
87 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Panel Data :
Panel Allele Data :
Dye Name
Electropherogram data :
88 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Panel Data :
Panel Allele Data :
Minimun Allele Size
Electropherogram data :
89 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Panel Data :
Panel Allele Data :
Maximum Allele Size
Electropherogram data :
90 6.4.3.2 DNA Typing R-41 2 EQ 0.0 to 1.0
Electropherogram Data :
Panel Data :
Panel Allele Data :
Noise Ratio
Electropherogram data :
91 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Bin Data :
Primer Set Name
17
---------------------- Page: 17 ----------------------
ISO/IEC 19794-14 DAM 1
Electropherogram data :
92 6.4.3.2 DNA Typing R-41 2 EQ Name of Locus marker in Annex D
Electropherogram Data :
Bin Data :
Bin Locus Data :
Locus Name
Electropherogram data :
93 6.4.3.2 DNA Typing R-41 2 See Test
Electropherogram Data :
54 to 56.
Bin Data :
Bin Locus Data :
Bin Call Data :
Allele Call
Electropherogram data :
94 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Bin Data :
Bin Locus Data :
Bin Call Data :
Average Base Pair Size
Electropherogram data :
95 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Bin Data :
Bin Locus Data :
Bin Call Data :
Minus Deviation Base Pair
Size
Electropherogram data :
96 6.4.3.2 DNA Typing R-41 1
Electropherogram Data :
Bin Data :
Bin Locus Data :
Bin Call Data :
Plus Deviation Base Pair
Size
Electropherogram data :
97 6.4.3.2 DNA Typing R-41 2 See Test
Reference
69 to 73.
Electropherogram Data :
Time and Fluorescence
Strength Data
Electropherogram data :
98 6.4.3.2 DNA Typing R-41 2 See Test
Electropherogram Data
69 to 73.
Mitocondrial Sequence
Data :
Time and Fluorescence
Strength Data
18
---------------------- Page: 18 ----------------------
ISO/IEC 19794-14 DAM 1
Electropherogram data :
99 6.4.3.2 DNA Typing R-41 1
Electropherogram Data
Mitocondrial Sequence
Data :
Dye assignment for Base :
Dye Name
Electropherogram data :
100 6.4.3.2 DNA Typing R-41 2 EQ string consists only the character listed
Electropherogram Data
in Table 28
Mitocondrial Sequence
Data :
Dye assignment for Base :
Base type
101 6.4.3.2 DNA Typing R-42 2 (Electropherogram data C Sample Typing Technology
field == Mandatory) “Electropherogram”
User Defined DNA Data :
102 6.4.3.2 DNA Typing R-43 2 GTE Length ≥ 0
TypeCode
User Defined DNA Data :
103 6.4.3.2 DNA Typing R-43 2 EQ Base 64 Encoding
Data
Note: Operator 'C' means the following: If the value of the field that corresponds to the first operand is equal to the value of the second operand,
this field is mandatory. For example, when operator 'C' is set and the operands are "Communication direction" and "Answer", this is interpreted
as follows. If the value of "Communication direction" field is the same as "Answer", this field is mandatory.
19
---------------------- Page: 19 ----------------------
A.3. Sample XML
xmlns="http://standards.iso.org/iso-iec/19794/-14/ed-1"
xmlns:cmn="http://standards.iso.org/iso-iec/19794/-1/ed-2/amd/2"
xmlns:dna="http://standards.iso.org/iso-iec/19794/-14/ed-1"
xsi:noNamespaceSchemaLocation="19794-14_amd1.xsd">
Dna
3
0
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.