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

More documents

Recommendations

Info

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONIn order to ensure that the transaction description information can be read by all systems,data for all fields in Record Type-1 shall always be recorded in all encodings using thecharacters that can be represented by the 7-bit American National Standard Code forInformation Interchange (ASCII) found in Table 108 with the exception of the reservedvalues.The control characters “ F S” , “ G S”, “ R S”, “ U S”, “ STX ” and “ ETX ” are reserved characters in allencodings. Base-64 shall be used for converting non-ASCII text into ASCII form, whererequired and noted in the standard. (See Annex A: Character encoding information for adescription of Base-64).CharacterencodingindexCharacter encodingnameTable 4 Character encodingDescription0 ASCII7-bit (Default) with zero added in high bit position(See Annex A: Character encoding information)16 bit2 UTF-16 16 (See ISO/IEC 10646-1 and The Unicode standard)3 UTF-88-bit(See NWG 3629 and The Unicode standard)4 UTF-3232-bit(See The Unicode standard)5-127 ------------- Reserved for future use128-999 ------------- User-defined character encoding setsField 1.015 Character encoding / DCS is an optional field that allows the user tospecify an alternate character encoding. The default character encoding for Traditionalencoding is 7-bit ASCII. For XML, the default is UTF-8. Field 1.015 Characterencoding / DCS contains three information items: the character encoding set index /CSI, the character encoding set name / CSN, and the character encoding set version /CSV. The first two items (CSI and CSN) are selected from the appropriate columns ofTable 4. CSV specifies the specific version of the character encoding set used , such asUTF-8 version 1.0. Note that the value “1” does not appear in the table. It is a legacyvalue, which should not be used for newly generated transactions. The 2007 and 2008versions of this standard referred to it as “8-bit ASCII” and it was used to indicate theLatin-1 character set (ISO/IEC 8859-1).The 2007 version of the standard allowed users to switch any data (except that containedin the Type-1 record) to an alternative character encoding using a mechanism employingspecial control characters. This capability is retained in this version of the standard forTraditional encoding to ensure backward compatibility. See Annex B: Traditionalencoding. However, the 2007 version stated that for certain fields, UTF-8 could be used16In the 2007 and 2008 versions of the standard, this was called Unicode. It has been changed here forclarity, since Unicode can be expressed in UTF-8, UTF-16 and UTF-32 and code 2 only referred to UTF-16.May, 2013 DRAFT VERSION UPDATE 2013 Page 43
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONfor the data without having to include the special control characters. Fields where this ispossible in this version of the standard are marked with 'U' or 'user-defined' in the'character type' column of the record layout tables for each record type. Users areencouraged to choose the option of UTF-8 for 'U' and 'user-defined' character types thatdoes not require the use special control characters in Traditional Encoding. It is notpossible to switch character encodings in XML, but users are encouraged to state thecharacter encoding (normally UTF-8) and version (1.0) in Field 1.015. See Annex C.6 Implementation domain and application profilesAn implementation domain, coded in Field 1.013 Domain name / DOM of a Type-1record as an optional field, is a group of agencies or organizations that have agreed to usepre-assigned data fields with specific meanings (typically in Record Type-2) for exchanginginformation unique to their installations. The implementation domain is usually understoodto be the primary application profile of the standard. New to the 2011 version of thestandard, Field 1.016 Application profile specifications / APS allows multiple applicationprofiles to be referenced. The organization responsible for the profile, the profile name andits version are all mandatory for each application profile specified. A transaction mustconform to each profile that is included in this field. It is possible to use Field 1.016 and /or Field 1.013. It is recommended that when only one profile is applicable, that Field1.013 be used and it be called the implementation domain.An example of an implementation domain is the one maintained by the Criminal JusticeInformation Services (CJIS) Division of the Federal Bureau of Investigation (FBI). It is theNorth American Domain subscribed to by the Royal Canadian Mounted Police (RCMP), theFBI, and several state and Federal agencies in North America. The default value for thisfield shall be the North American Domain implementation and shall appear as “NORAM”.The transaction may include user-defined fields that are not described in any specifiedapplication profile or the specified domain. However, when any part of a transaction isdefined by one or more application profiles, it must conform to the requirements of all of therelevant application profiles.7 Information associated with several records7.1 Record headerThe record header appears as the first field (xx.001) in each Record Type. It containsinformation particular to the encoding format chosen, in order to enable proper reading ofthe record. In Traditional encoding, this field contains the record length in bytes (includingall information separators). In NIEM-conformant XML encoding, this field contains theRecordCategoryCode, which is the numeric representation of the Record Type.In the 2007 version of the standard, the record length was unrestricted for Record Type-1. Itwas a maximum value having up to 4-bytes in ASCII representation for Record Types 4 and44
Page 1:
NIST Special Publication 500-xxxANS
Page 5 and 6:
5.3.18 Type-18 records ............
Page 7 and 8:
8.1.4 Field 1.004 Type of transacti
Page 9 and 10:
8.9.7.18 Field 9.322: EFS core delt
Page 11 and 12:
8.11 Record Type-11: Forensic and i
Page 13 and 14:
8.14.2 Field 14.002: Information de
Page 15 and 16:
8.17 Record Type-17: Iris image rec
Page 17 and 18:
8.19.24 Field 19.902: Annotation in
Page 19:
8.24.6 Field 99.101: Biometric type
Page 22 and 23:
F.6.3 Reference points.............
Page 24 and 25:
Figure 34: Palm with carpal delta a
Page 26 and 27:
Table 31 Off-center fingerprint pos
Page 28 and 29:
Table 95 DNA sample cellular types.
Page 30 and 31:
Type-11:A new record type introduce
Page 32 and 33:
ACKNOWLEDGEMENTS FOR ANSI/NIST-ITL
Page 34 and 35: Will Graves, Rob Mungovan, Catherin
Page 36 and 37: John ManzoFBI/BIOMETRICS Center ofE
Page 38 and 39: General Editor: Brad Wing[2013a>]AC
Page 40 and 41: CANVASSEES For the 2013 UpdateTO BE
Page 42 and 43: ANSI/NIST-ITL 1-2011 - UPDATE 2013
Page 72: ANSI/NIST-ITL 1-2011 - UPDATE 2013
Page 83: ANSI/NIST-ITL 1-2011 - UPDATE 2013
Page 134 and 135:
ANSI/NIST-ITL 1-2011 - UPDATE 2013
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
Page 412 and 413:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 438 and 439:
Page 440 and 441:
Page 442 and 443:
Page 444 and 445:
Page 446 and 447:
Page 448 and 449:
Page 450 and 451:
Page 452 and 453:
Page 454 and 455:
Page 456 and 457:
Page 458 and 459:
Page 460 and 461:
Page 462 and 463:
Page 464 and 465:
Page 466 and 467:
Page 468 and 469:
Page 470 and 471:
Page 472 and 473:
Page 474 and 475:
Page 476 and 477:
Page 478 and 479:
Page 480 and 481:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
Page 501 and 502:
Page 503 and 504:
Page 505 and 506:
Page 507 and 508:
Page 509 and 510:
Page 511 and 512:
Page 513 and 514:
Page 515 and 516:
Page 517 and 518:
Page 519 and 520:
Page 521 and 522:
Page 523 and 524:
Page 525 and 526:
Page 527 and 528:
Page 529 and 530:
Page 531 and 532:
Page 533 and 534:
Page 535 and 536:
Page 537 and 538:
Page 539 and 540:
Page 541 and 542:
Page 543 and 544:
Page 545 and 546:
Page 547 and 548:
Page 549 and 550:
Page 551 and 552:
Page 553 and 554:
Page 555 and 556:
Page 557 and 558:
Page 559 and 560:
Page 561 and 562:
Page 563 and 564:
Page 565 and 566:
Page 567 and 568:
Page 569 and 570:
Page 571 and 572:
Page 573 and 574:
Page 575 and 576:
Page 577 and 578:
Page 579 and 580:
Page 581 and 582:
Page 583 and 584:
Page 585 and 586:
Page 587 and 588:
Page 589 and 590:
Page 591 and 592:
Page 593 and 594:
Page 595 and 596:
Page 597:
show all

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

Create successful ePaper yourself

Delete template?

Save as template?