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 VERSIONNIEM biometrics domain. The <strong>itl</strong>.xsd copies of biometric elements have beendeprecated in favor of elements in the NIEM biometrics domain.3) XML elements have been created <strong>for</strong> all of the new features of version <strong>2011</strong>, such asnew records <strong>for</strong> DNA and plantars, and new elements <strong>for</strong> extended feature set latentencoding.4) XML elements have been removed <strong>for</strong> record types 3, 5, and 6, and field 17.018which were deprecated in version <strong>2011</strong>.5) To the extent possible, element names, data type names, and structure have beenretained from version 2-2008. Nevertheless, some changes were necessary to improvecon<strong>for</strong>mance with NIEM, or to repair errors. A list of changes expected to affect theproduction of XML instances and content can be found in the Change Log availableat http://www.<strong>nist</strong>.gov/<strong>itl</strong>/iad/ig/<strong>ansi</strong>_standard.cfm.6) Additional constraints have been added to the schema to increase the degree to whichXML schema validation will test con<strong>for</strong>mance to the base specification, such asen<strong>for</strong>cing that only certain kinds of images can appear in each record type.7) The NIEM files contained in the In<strong>for</strong>mation Exchange Package Documentation(IEPD) are a subset of NIEM, containing only those elements used by the standard.C.3 Scope, purpose, and con<strong>for</strong>manceThere are “user-defined” elements that implementers may create to extend this specificationso that it is useful in a particular application. For NIEM-con<strong>for</strong>mant XML encoding, these“user-defined” elements have been created in the schema as abstract elements. Implementersmay extend this standard by supplying substitution elements <strong>for</strong> these abstract elements:,,,,,, and/or.The implementer’s substitution elements shall be created in a separate, user-declarednamespace. The content of the substitution elements shall be well-<strong>for</strong>med XML and shallfollow NIEM rules.Implementers may modify or add namespace declarations and import elements to referenceMay, 2013 DRAFT VERSION UPDATE 2013 Page 457

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

Saved successfully!

Ooh no, something went wrong!