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 VERSIONuser-defined namespaces and extension schemas. The NIEM subset versions ofbiometrics.xsd, niem-core.xsd, and other NIEM schemas may be re-subsetted to facilitate useof these elements in user-defined blocks. Implementers may create constraint schemas thatadd any of the schemas used in this standard. These constraint schemas must follow the rules<strong>for</strong> NIEM constraint schemas as they are defined in the NIEM Naming and Design Rules 193 .They may only be used to add constraints and restrictions to components; they must notloosen the standard by allowing content that is not allowed by the schemas upon which theyare based.Implementers shall not introduce new elements inside the complex except <strong>for</strong> the substitutionelements described above. They shall not change the order or structure of elements definedby the standard.The root element, , may beincluded as a payload in a larger package.All of this standard’s required elements shall be present in a con<strong>for</strong>ming instance documenteven if the schema referenced by this annex do not strictly en<strong>for</strong>ce the requirement.C.4 Transmitted data conventionsC.4.1Character encodingEach XML in<strong>for</strong>mation element, tags and data content, shall be represented by a character setthat is a subset of Unicode and that is allowable by W3C XML. For compatibility withexisting implementations of the standard, implementers may wish to limit content to the 128characters that can be represented by 7-bit ASCII. (Record Type-1 is restricted to this set of128 characters).Characters shall be transmitted using a Unicode encoding. These Unicode encoding <strong>for</strong>matsare allowable: UTF-8, UTF-16, or UTF-32. Use of UTF-8 is encouraged. Nevertheless,senders and receivers of XML packages using this standard may agree on other subsets ofUnicode, including international characters. Senders and receivers of XML packages usingthis standard shall agree on an encoding <strong>for</strong>mat. XML packages shall include an XMLdeclaration that specifies the encoding, as in this example:It is recommended that the user enter Field 1.015 Character encoding / DCS with theselection <strong>for</strong> UTF-8 in order to facilitate any translation from XML to Traditional <strong>for</strong>mat <strong>for</strong>the transaction, should that need to occur.Note that even though a Unicode encoding is used <strong>for</strong> the transaction, only certain fields mayuse the full range of characters available in Unicode. These fields are marked with 'U' or193See https://www.niem.gov/documentsdb/Documents/Technical/NIEM-NDR-1-3.pdf458

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

Saved successfully!

Ooh no, something went wrong!