acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...
acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ... acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONseparated by a comma between values. An example is “14,23.3” or “22.1,23.3”.• The third information item is the genotype numerical weight / GNW. It is anon-negative real number up to 5 characters (including a period) ranging from 0to 1. An example is “0.114”.8.18.22 Field 18.022: Comment / COMThis is an optional field. See Section 7.4.4 for details.8.18.23 Field 18.023: Electropherogram ladder / EPLThis optional field contains a repeating subfield for a ladder / control sample. This field isonly present if Field 18.011: Sample typing information / STI has a subfield with thevalue 3. Each subfield is comprised of the following information items, the first four ofwhich are mandatory if this field is used:• The first information item is the ladder image reference / LIR. It shall containan alphanumeric reference up to 8 characters, which is unique for each image. Ifnone has been assigned, enter 999. This is a unique identifier.• The second information item is the ladder storage type / LST. This is a string ofup to 4 characters, representing the file type suffix for the electropherogram. Thedata is stored in “fsa”, “hid” or “----“ The dashes may be substituted withcharacter strings for other format types as they become available.• The third information item is the ladder image data descriptor / LDD of theelectropherogram contained in this subfield. If the data is stored externally, enterthe filename. This is an alphanumeric string with special characters allowed. Anexample is “NIST Run 5 Well A07 12 Jan 11”• The fourth information item is the ladder electropherogram data/ LEPD. Thisshall be stored in base-64 format.• The fifth information item is optional. It is the ladder electropherogramscreenshot / LES. This may be an image captured during the analysis. This shallbe stored in base-64 format.8.18.24 Fields 18.200-18.900: user-defined fields / UDFThese fields are user-defined fields. Their size and content shall be defined by the user and be inaccordance with the receiving agency.8.18.25 Field 18.902: Annotation information / ANNThis is an optional field, listing the operations performed on the original source in orderto prepare it for inclusion in a biometric record type. See Section 7.4.1.May, 2013 DRAFT VERSION UPDATE 2013 Page 383
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION[2013n>]8.18.26 Field 18.992: Type-2 Record Cross Reference / T2CThis is an optional field. When used, it contains the IDC value of the Type-2 record thatcontains relevant biographic information and other data concerning the subject of thisinstance of the record, who may be differenct from the subject of the transaction. SeeSection 7.3.1.1 Type-2 Record Cross reference / T2C.[
- Page 374 and 375: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 376 and 377: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 378 and 379: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 380 and 381: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 382 and 383: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 384 and 385: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 386 and 387: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 388 and 389: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 390 and 391: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 392 and 393: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 394 and 395: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 396 and 397: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 398 and 399: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 400 and 401: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 402 and 403: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 404 and 405: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 406 and 407: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 408 and 409: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 410 and 411: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 412 and 413: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 414 and 415: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 416 and 417: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 418 and 419: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 420 and 421: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 422 and 423: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 426 and 427: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 428 and 429: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 430 and 431: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 432 and 433: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 434 and 435: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 436 and 437: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 438 and 439: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 440 and 441: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 442 and 443: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 444 and 445: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 446 and 447: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 448 and 449: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 450 and 451: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 452 and 453: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 454 and 455: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 456 and 457: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 458 and 459: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 460 and 461: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 462 and 463: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 464 and 465: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 466 and 467: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 468 and 469: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 470 and 471: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 472 and 473: ANSI/NIST-ITL 1-2011 - UPDATE 2013
ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSIONseparated by a comma between values. An example is “14,23.3” or “22.1,23.3”.• The third in<strong>for</strong>mation item is the genotype numerical weight / GNW. It is anon-negative real number up to 5 characters (including a period) ranging from 0to 1. An example is “0.114”.8.18.22 Field 18.022: Comment / COMThis is an optional field. See Section 7.4.4 <strong>for</strong> details.8.18.23 Field 18.023: Electropherogram ladder / EPLThis optional field contains a repeating subfield <strong>for</strong> a ladder / control sample. This field isonly present if Field 18.011: Sample typing in<strong>for</strong>mation / STI has a subfield with thevalue 3. Each subfield is comprised of the following in<strong>for</strong>mation items, the first four ofwhich are mandatory if this field is used:• The first in<strong>for</strong>mation item is the ladder image reference / LIR. It shall containan alphanumeric reference up to 8 characters, which is unique <strong>for</strong> each image. Ifnone has been assigned, enter 999. This is a unique identifier.• The second in<strong>for</strong>mation item is the ladder storage type / LST. This is a string ofup to 4 characters, representing the file type suffix <strong>for</strong> the electropherogram. Thedata is stored in “fsa”, “hid” or “----“ The dashes may be substituted withcharacter strings <strong>for</strong> other <strong>for</strong>mat types as they become available.• The third in<strong>for</strong>mation item is the ladder image data descriptor / LDD of theelectropherogram contained in this subfield. If the data is stored externally, enterthe filename. This is an alphanumeric string with special characters allowed. Anexample is “<strong>NIST</strong> Run 5 Well A07 12 Jan 11”• The fourth in<strong>for</strong>mation item is the ladder electropherogram data/ LEPD. Thisshall be stored in base-64 <strong>for</strong>mat.• The fifth in<strong>for</strong>mation item is optional. It is the ladder electropherogramscreenshot / LES. This may be an image captured during the analysis. This shallbe stored in base-64 <strong>for</strong>mat.8.18.24 Fields 18.200-18.900: user-defined fields / UDFThese fields are user-defined fields. Their size and content shall be defined by the user and be inaccordance with the receiving agency.8.18.25 Field 18.902: Annotation in<strong>for</strong>mation / ANNThis is an optional field, listing the operations per<strong>for</strong>med on the original source in orderto prepare it <strong>for</strong> inclusion in a biometric record type. See Section 7.4.1.May, 2013 DRAFT VERSION UPDATE 2013 Page 383