| The rapsheet transmission standard. Follow this link for materials and information on the work of the Joint Task Force for Rapsheet Standardization. |
| The Justice Data Dictionary -- |
04/29/2003 From John Terry
The Justice Extensible Markup Language (XML) Data Model (JXDM)
effort was organized to explore and facilitate information sharing and
technology integration in the justice and public safety communities. The
prerelease version of the Justice XML
Data Dictionary (JXDD) version 3.0 is now available for review by
government and industry persons with technical and practical expertise in
the justice and public safety domains. For the next phase of this effort,
applications are being solicited to participate in a series of validation
projects to test the data model over as broad a range of conditions as
possible. The following criteria apply to these validation projects:
Criteria for JXDM Validation ProjectsTechnical Considerations Validation projects should exercise and test: * Range (of features) - including local extension, code tables, secondary relationships * Scope of domain - component coverage (What new JXDD components are necessary, unnecessary, or never used?) * Scope of application - capability to adequately support both formal document and ad hoc transaction oriented applications * Scale - volume, size, and speed of information exchanges (Are partial schemas needed to compensate for slower validation or processing?) * Platforms and Tools - range of implementation platforms and development tools * Horizontal interoperability - exchanges with external agencies or jurisdictions at similar levels (e.g., multi-state) * Vertical interoperability - (e.g., intrastate exchanges involving local, county, tribal, and state agencies) Programmatic Considerations Validation projects must satisfy the following criteria: * Self-supported funding * Available technical staff versed in XML * Ability to start as soon as possible * Ability to demonstrate some level of product as soon as possible * Willingness to provide feedback * Willingness to sign an MOA to participate * Ability to exercise the broad range of technical criteria * Participation in the Justice XML Model (outlined in the above introduction) is considered advantageous If you meet the above criteria and are interested in being selected as a validation site or have any questions, please contact me as soon as possible. Thank you. John Terry Institute for Intergovernmental Research P.O. Box 12729 Tallahassee, FL 32317 Tel. (850) 385-0600 ext 291 Fax (850) 422-3529 E-mail: jterry@iir.com
|
09/05/2002 Notes:
With sponsorship from the USDOJ, Office of Justice Programs, the Georgia Tech Research Institute has become the custodian of the justice XML data dictionary. The Justice XML Data Subcommittee (part of the Global project) has assumed oversight of the dictionary. The chair of the subcommittee is Jim Roggero, michael_j_roggero@osca.state.mo.us.
The Georgia Tech Research Institute is developing the object-oriented version of the dictionary that will be published as version 3.0.
Revisions to the dictionary are being considered by an XML Schema Task Team headed by Paul Embley, pembley@mstar2.net. The team is looking at how the dictionary is represented (with an eye towards RDF), how "types" are used, how namespaces are used, and implementing an object-oriented approach to grouping elements and creating relationships between elements. A [gtri-xstf] listserve has been created for task team members to contribute to the dictionary's evolution. Mark Kindl, mark.kindl@gtri.gatech.edu, is the list manager.
| AAMVA National Standard Driver History Record |
The American Association of Motor Vehicle Administrators (AAMVA) has been working with the JTF, NLETS, and others to create an XML Standard Driver Record. September, 2002.
| XML implementation of Wisconsin's law enforcement network. |
See also the eTIME Project thread.
Here are DTD's currently in production: eTIME Initiators. eTIME Responses. eTIME Summary Page. And here is the stylesheet currently used for vehicle responses: eTIME Vehicle Response Stylesheet.
The above materials are "as of 2/2002."
Use this directory of files for direct access to attached materials without regard to how your browser manipulates them.
It is possible to define XML formatted input and output messages for all transactions used for law enforcement message exchange on state systems. Here is an example of a conventional teletype message as looks on today's systems.
Here is an example of the same law enforcement response message coded in XML and translated to HTML by a linked XSL stylesheet. While looking at the graphic display, use your browser's View | Source to see how the data has been formatted using XML. The XSL stylesheet can be downloaded from the directory of files. Your browser uses the two files together to create the display you see on your screen.
The advantage of separating the data (XML) from the display format (XSL) is that the data can be sent in a single XML format to any agency for any purpose: insertion in a database, pre-filling a form, printout on a laser printer, summary on a mobile terminal, or display on a hand-held palm device. Stylesheets can be written in XSL to build a customized display for any purpose, or the XML can be imported directly into a local database.
Here is a draft of specifications for XML formatted response messages on Wisconsin's law enforcement system. These include all responses from NCIC, NLETS, the CIB hot files, and Wisconsin agencies DOT, DOC, and DNR. This is a Microsoft WORD document.
The above specifications include a spreadsheet listing the XML tags contained in the above document. The sheet includes "token" references. Tokens are what we call the labels currently used by NCIC and other data services to tag fields in standard teletype responses. For example, NCIC uses the token "OCA" as a label for an agency case number. In the specification, this might map to an XML tag named <agencyCaseNumber>. This publication is a Microsoft EXCEL spreadsheet.