acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION8.1.15 Field 1.015 Character encoding / DCSThis optional field specifies the character encoding that may appear within this transactionfor data with the character type listed as “U” or 'user-defined' in the record format tables.This field shall contain one set of information items (coded as a subfield). This is consistentwith the 2008 version of the standard. The 2007 version allowed multiple characterencoding sets. See Annex B: Traditional encoding and Annex C: NIEM-conformantencoding rules for details on the use of this field.For a description of the use of alternate character encoding see Section 5.6.• The first information item (character encoding index / CSI) is the indexnumber that references an associated character encoding. See the “Characterencoding index” column of Table 4 for the valid values for this informationitem.• The second information item (character encoding name / CSN) shall be the“Character encoding name” associated with that index number, taken fromTable 4. All characters marked “A” ,“N” or “S” in the 'Type' column of Table108 Character encoding set values may be used.• The optional third information item (character encoding version / CSV) is thespecific version of the character encoding used. In the case of the use of UTF-8,the third optional information item may be used to hold the specific versionused, so that the display terminal can be switched to the correct font family. Allcharacters marked “A” ,“N” or “S” in the 'Type' column of Table 108Character encoding set values may be used.8.1.16 Field 1.016 Application profile specifications / APSUse of this optional field indicates the transaction's conformance with one or moreApplication Profile Specifications that are derived from ANSI/NIST-ITL 1-2011, such asEBTS or INT-I. There may be multiple subfields, each designating an application profile towhich this transaction conforms. If multiple Application Profile Specifications are includedin this field, the specifications must be compatible with each other: this transaction must bein conformance with all of the cited specifications. See Section 6. Each subfield shallconsist of three mandatory information items:104• The first information item (application profile organization / APO) willuniquely identify the agency or entity responsible for the specification. Allcharacters marked “A” ,“N” or “S” in the 'Type' column of Table 108Character encoding set values may be used.• The second information item (application profile name / APN) shall containthe name of the specification. All characters marked “A” ,“N” or “S” in the'Type' column of Table 108 Character encoding set values may be used.• The third information item (application profile version number / APV) shall