11.07.2015 Views

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 ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION8.2 Record Type-2: User-defined descriptive text recordType-2 records are optional, but when present, shall contain textual in<strong>for</strong>mation relating tothe subject of the transaction. This record may include such in<strong>for</strong>mation as the state or FBInumbers, physical characteristics, demographic data, and the subject’s criminal history.Every transaction usually contains one or more Type-2 records which is dependent upon theentry in Field 1.004 Type of transaction / TOT.Table 23 Type-2 record layoutFieldNumberMnemonicContentDescriptionCondcodeCharacterTypeMIn#Max#ValueConstraintsOccurrenceMIn#Max#2.001 RECORD HEADER Mencoding specific:see Annex B:Traditionalencoding orAnnexC: NIEMcon<strong>for</strong>mantencoding rulesencoding specific:see Annex B:Traditionalencoding orAnnexC: NIEMcon<strong>for</strong>mantencoding rules1 12.002 IDCINFORMATIONDESIGNATIONCHARACTERM N 1 20 < IDC < 99integer1 12.003 andaboveUSER-DEFINEDUSER-DEFINED FIELDS O user-defined user-defined user-defined8.2.1 Field 2.001: Record headerThe content of this mandatory field is dependent upon the encoding used. See therelevant annex of this standard <strong>for</strong> details. See Section 7.1.8.2.2 Field 2.002: In<strong>for</strong>mation designation character / IDCThis mandatory field shall contain the IDC assigned to this Type-2 record as listed in thein<strong>for</strong>mation item IDC <strong>for</strong> this record in Field 1.003 Transaction content / CNT. SeeSection 7.3.1.8.2.3 Fields 2.003 and above: user-defined fieldsIndividual fields shall con<strong>for</strong>m to the specifications set <strong>for</strong>th by the agency to which thetransmission is being sent, to the domain listed in Field 1.013 Domain name / DOM, theapplication profiles listed in Field 1.016 Application profile specifications / APS and to106

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!