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 VERSIONA system is con<strong>for</strong>mant to this standard if it is capable of generating or using transactionsthat are morphologically, syntactically and semantically con<strong>for</strong>mant to the requirements ofthis standard. Transactions shall consist of one Type-1 record and one or more of the Type-2to Type-99 records. For the structure of a transaction, see Section 5.1. For a description ofthe Record Types, see Section 5.3. Prior versions of the standard only required a Type-1record.2.2 Morphological 4 (Level 1) con<strong>for</strong>manceMorpohological con<strong>for</strong>mance deals with the <strong>for</strong>m and structure of the internal content andverifies data structures exist and have allowable values. Specifically, it checks <strong>for</strong> thestructure and value of each field, subfield and in<strong>for</strong>mation item in a transaction.A transaction con<strong>for</strong>ms morphologically to this standard if it satisfies all of the normativemorphological requirements related to its data structure and data values, as specifiedthroughout Section 7 In<strong>for</strong>mation associated with several records and Section 8 Recordtype specifications. If the system claims con<strong>for</strong>mance with a particular encoding, then itshall satisfy the requirements of either Annex B: Traditional encoding or Annex C:NIEM-con<strong>for</strong>mant encoding rules, as appropriate.Table 1 Excerpt from Table 24: Type-4 record layoutFieldNumberMnemonic Content Description CondcodeTypeCharacterMIn#Max#ValueConstraintsOccurrenceMIn#Max#4.004 FGPFRICTION RIDGEGENERALIZED POSITIONMNT=1X=1T=1X=30 < FGP < 15 orFGP = 255 integerSee Table 86 6The excerpt above is taken from Table 24 Type-4 record layout. Notice the “ValueConstraints” column. See Section 8 Record type specifications <strong>for</strong> an explanation of theentries in this type of table.This example illustrates con<strong>for</strong>mance of the data values.• Valid values <strong>for</strong> Field 4.004: Friction ridge generalized position / FGP areshown in Table 24. Testing this type of con<strong>for</strong>mance <strong>for</strong> Field 4.004 involvesverifying that the value <strong>for</strong> FGP is zero or that it is a positive integer less than orequal to 15 or that it is equal to 255. A value of 10 is con<strong>for</strong>mant; however, a4[2013e>] Morphogological and Syntactical header labels were reversed in thesesections in the <strong>2011</strong> text. The explanatory text was correct. [

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

Saved successfully!

Ooh no, something went wrong!