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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION'user-defined' in the character type column of the record layout tables.C.4.2 Grayscale dataBinary data so constructed as to represent a grayscale image shall be converted to ASCIIcharacters prior to transmission using Base-64 encoding. See Annex A A.3: Base-64encoding.C.4.3 Binary dataBinary image data may be constructed in either compressed or uncompressed <strong>for</strong>m, thenshall be converted to ASCII characters prior to transmission using Base-64 encoding. SeeAnnex A A.3: Base-64 encoding. Binary data fields, other than image data, in the Type-4, 7,and 8 records have been given conventional XML element tags. For XML encoding, thesedata elements and their content shall be represented as ASCII characters.C.5 Data Conventions Specific to XMLC.5.1 Record <strong>for</strong>matAn exchange package shall consist of two or more logical records. See Section 5.1Structure of a transaction. For each logical record contained in the package, severalin<strong>for</strong>mation elements appropriate to that record type shall be present. Complex elementsmay contain one or more complex or simple elements according to the rules of well-<strong>for</strong>medXML. Taken together, these items are used to convey different aspects of the data containedin a data in<strong>for</strong>mation object. To the extent possible, the objects used have been defined as apart of the National In<strong>for</strong>mation Exchange Model (NIEM). Some in<strong>for</strong>mation objects maybe repeated multiple times.The XML schema referenced <strong>for</strong> this encoding define the structure and order of the elementsin the in<strong>for</strong>mation exchange package. To the extent possible, the schema define data typesand constraints that en<strong>for</strong>ce the allowable content rules of the base standard. Nevertheless,the XML schema may not strictly en<strong>for</strong>ce the allowable content. The base standard definesallowable content, and its requirements shall be met by implementers regardless of encodingmethod.May, 2013 DRAFT VERSION UPDATE 2013 Page 459

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

Saved successfully!

Ooh no, something went wrong!