XML Proposal for NISTITL XML Workshop PowerPoint PPT Presentation

presentation player overlay
1 / 6
About This Presentation
Transcript and Presenter's Notes

Title: XML Proposal for NISTITL XML Workshop


1
XML Proposal for NIST-ITL XML Workshop
  • David Rodman
  • Nortel PEC Solutions

2
Summary of features
  • Usage of Global Justice XML tags where
    appropriate
  • Allow complete translation from EDI
    (NIST-ITL-2000) to XML translation. (forward
    translation)
  • Allow for all allowable EDI tags to be generated
    when translating from XML to EDI formats, but
    also recognizing that some data or metadata
    (relationships) would be lost.
  • Explicit rules for user or domain defined tags
    consistent with NIST-ITL-2000
  • Enable complex relationships and attributes
    allowed by XML that cannot be expressed in EDI.

3
Use of tag attribute fields for EDI tags, groups
and unit placement
  • XML has an ability to associate meta-data on
    tags.
  • Syntax ltxmlTagName MyAttributeNametextgt
  • GJXDM uses an ID/REF ID mechanism to associate
    tag groups that dont have a contains by
    relationship.
  • XML requires all attributes to be simple types
    (e.g. string, integer, etc) complex or aggregate
    types are not allowed.
  • Proposed meta-data attributes for all NIST-ITL
    200X xml tags
  • _at_Tag of type string Example2.02
  • _at_TagGroup of type integer Example2
  • _at_TagUnit of type integer Example3

4
NIST-ITL 200X Data Model
  • Requirements
  • A parent object should be defined to allow
    inheritance of attributes and sub-properties
  • Should follow the concepts of the NIST-ITL2000
    EDI model
  • Required Header information encompasses the
    records Equivalent to Type 1 record
  • A mandatory person (subject) record (type 2)
  • Optional biometric records (types 3-18(?))

5
NIST-ITL 200X Data Model
  • Requirement Continued
  • The data model must, at a minimum, define XML
    tags for all required fields of the NIST-ITL EDI
    format.
  • The data model must be extensible to allow user
    defined tags, and user defined organization for
    that data.
  • The data model must use tag names that conform to
    the ISO naming convention standard

6
Proposed Data Model Overview
Attributes
Tag TagGroup TagUnit
Super Object
E.g. Of Type Biometric Finger Face Palm Signatur
e
Control
Person
Biometric
The subject of the biometric samples, The
contents of the Type 2 record
The content directory, And meta-data Type 1 and
other support data
Biometric samples of All types allowed by the
Standard.
Write a Comment
User Comments (0)
About PowerShow.com