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 VERSIONFN : value Ua S… value bGSIf subfield count = 1FN : value aGS[
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONMSB LSB MSB LSBFirst ByteLast ByteMost Significant ByteLeast Significant ByteMost Significant Byte Least Significant ByteMost Significant Byte Within a Block Transmitted FirstMostSignificantBitByte of DataLeastSignificantBitMost Significant Bit Within a Byte Transmitted FirstB.1.2Date formatDates shall appear as eight digits in the format YYYYMMDD. The YYYY characters shallrepresent the year of the transaction; the MM characters shall be the tens and units values ofthe month; and the DD characters shall be the day in the month. For example, “20070103”represents January 3, 2007. See Section 7.7.2 Date and time.B.1.3Agency CodesThe 2007 version of the standard included only agency identifier fields (See Section 7.6).The 2008 version added the option of entering an organization name. This capability of the2008 version is retained in this version of the standard by adding new fields (Field 1.017Agency names / ANM and Fields xx.993 Source agency name / SAN)B.1.4GMT/UTC Date/Time formatGMT/UTC shall be represented as YYYYMMDDHHMMSSZ, a 15-character string that isthe concatenation of the date with the time and concludes with the character “Z”. The YYYYcharacters shall represent the year of the transaction. The MM characters shall be the tensand units values of the month. The DD characters shall be the tens and units values of theday of the month. The HH characters represent the hour; the MM the minute; and the SSrepresents the second. See Section 7.7.2.2 Greenwich mean time (coordinated universaltime – UTC) / GMT.B.1.5Record layoutFor the Type-1, Type-2, Type-9 through Type-99 records, each information field that is usedshall be numbered in accordance with this standard. The format for each field shall consistof the logical record type number followed by a period “.”, a field number followed by acolon “:”, followed by the information appropriate to that field. The field number may beany one to nine-digit number occurring between the period “.” and the colon “:”. It shall beinterpreted as an unsigned integer field number. This implies that a field number of “2.123:”is equivalent to and shall be interpreted in the same manner as a field number of448
- 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
- Page 474 and 475: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 476 and 477: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 478 and 479: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 480 and 481: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 483 and 484: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 485 and 486: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 487: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 491 and 492: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 493 and 494: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 495 and 496: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 497 and 498: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 499 and 500: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 501 and 502: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 503 and 504: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 505 and 506: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 507 and 508: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 509 and 510: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 511 and 512: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 513 and 514: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 515 and 516: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 517 and 518: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 519 and 520: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 521 and 522: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 523 and 524: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 525 and 526: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 527 and 528: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 529 and 530: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 531 and 532: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 533 and 534: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 535 and 536: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 537 and 538: ANSI/NIST-ITL 1-2011 - UPDATE 2013
ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSIONMSB LSB MSB LSBFirst ByteLast ByteMost Significant ByteLeast Significant ByteMost Significant Byte Least Significant ByteMost Significant Byte Within a Block Transmitted FirstMostSignificantBitByte of DataLeastSignificantBitMost Significant Bit Within a Byte Transmitted FirstB.1.2Date <strong>for</strong>matDates shall appear as eight digits in the <strong>for</strong>mat YYYYMMDD. The YYYY characters shallrepresent the year of the transaction; the MM characters shall be the tens and units values ofthe month; and the DD characters shall be the day in the month. For example, “20070103”represents January 3, 2007. See Section 7.7.2 Date and time.B.1.3Agency CodesThe 2007 version of the standard included only agency identifier fields (See Section 7.6).The 2008 version added the option of entering an organization name. This capability of the2008 version is retained in this version of the standard by adding new fields (Field 1.017Agency names / ANM and Fields xx.993 Source agency name / SAN)B.1.4GMT/UTC Date/Time <strong>for</strong>matGMT/UTC shall be represented as YYYYMMDDHHMMSSZ, a 15-character string that isthe concatenation of the date with the time and concludes with the character “Z”. The YYYYcharacters shall represent the year of the transaction. The MM characters shall be the tensand units values of the month. The DD characters shall be the tens and units values of theday of the month. The HH characters represent the hour; the MM the minute; and the SSrepresents the second. See Section 7.7.2.2 Greenwich mean time (coordinated universaltime – UTC) / GMT.B.1.5Record layoutFor the Type-1, Type-2, Type-9 through Type-99 records, each in<strong>for</strong>mation field that is usedshall be numbered in accordance with this standard. The <strong>for</strong>mat <strong>for</strong> each field shall consistof the logical record type number followed by a period “.”, a field number followed by acolon “:”, followed by the in<strong>for</strong>mation appropriate to that field. The field number may beany one to nine-digit number occurring between the period “.” and the colon “:”. It shall beinterpreted as an unsigned integer field number. This implies that a field number of “2.123:”is equivalent to and shall be interpreted in the same manner as a field number of448