Global Justice XML Data Model (GJXDM) GJXDM Developers’ Workshop BAJ Bureau of Justice Assistance 1 The Development of the Global Justice

Global Justice XML Data Model (GJXDM)Global Justice XML Data Model (GJXDM)

GJXDM Developers’ WorkshopGJXDM Developers’ Workshop

www.it.ojp.govwww.it.ojp.gov

BAJ Bureau ofJustice Assistance

1

The Development of theGlobal Justice XML Data Model

(GJXDM)

Paul EmbleyGlobal Justice Information Sharing Initiative (Global) XML Structure Task Force (GXSTF)

Chair





2

Creative Commons

Attribution-ShareAlike 2.0 You are free:•to copy, distribute, display, and perform the work •to make derivative works •to make commercial use of the work Under the following conditions:

Attribution. You must give the original author credit.

ShareAlike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one.

• For any reuse or distribution, you must make clear to others the license terms of this work. • Any of these conditions can be waived, if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above.This is a human-readable summary of the Legal Code (the full license). Disclaimer This page is available in the following languages: Català Deutsch English Castellano Suomeksi français hrvatski Italiano 日本語 Nederlands Português 中文 ( 繁 ) Learn how to distribute your work using this license.





3

GJXDM Purpose

• To provide a consistent, extensible, maintainable XML Schema reference specification for data elements and types that represent the data requirements of the general justice and public safety communities

• Long-term goal—to provide a baseline model for the data dictionary that can be represented in advanced technologies beyond XML Schema





4

GJXDM Vision

• To significantly advance justice information sharing by providing a common language and vocabulary that reduces cost and technical barriers





5

Development of GJXDM

• Sponsored by the Global Advisory Committee• Participants from all levels—local, state, and federal• Participants across the justice domain

• Funded by the U.S. Department of Justice (DOJ) Office of Justice Programs (OJP)

• Developed primarily by the Georgia Tech Research Institute (GTRI)

• GXSTF provides guidance, review, and issue resolution for practitioners and industry





6

Business Case for Justice Information Sharing

• Criminal activity is not just a local issue because criminals can move faster than the information about them

• Justice system officials often do not have the information they need to make informed decisions in time to make a difference

• Consequently, we cannot apply the proper level of jurisprudence and concern to individual incidents





7

Justice XML Initiative Objectives

• Justice information sharing—providing complete, accurate, and timely information to justice system decision makers, when, where, and how they need it

• Cost-effective vs. unique and expensive• Reusable vs. stovepipe• Common terms—universal dictionary• Flexible content—images, summary offender profile,

location data, status, etc.





8

Who Created the GJXDM?

of the Global Infrastructure/Standards Working Group





9

Representation on the GXSTF

• Corrections Administrators• American Association of Motor

Vehicle Administrators (AAMVA)

• Probation and Parole• Industry Working Group (IWG)• International Association of

Chiefs of Police (IACP)• Federal Chief Information

Officer (CIO) Council

• Federal Bureau of Investigation (FBI)

• SEARCH, The National Consortium for Justice Information and Statistics

• Joint Task Force Regional Sharing System (JTFRSS)

• National Telecommunications and Information Association (NTIA)

• GTRI• Vendors





10

Representation on the GXSTF (continued)

• State/Local Law Enforcement• NLETS – The International

Justice and Public Safety Information Sharing Network

• Regional Information Sharing Systems® (RISS)

• Criminal Information Sharing Alliance (CISA)

• CriMNet• NM, MN, IL, WI, MO, MT, VA,

WA, GA, KY, PA, OK, AL, CO, AZ

• Courts• Joint Technology Committee of

Conference of State Court Administrators (COSCA) and National Association of Court Management (NACM)

• National Center for State Courts (NCSC)

• Organization for the Advancement of Structured Information Standards (OASIS) LegalXML Member Section Technical Committees

• NACM





11

Document InstancesComplex Components

Simple Components

Combining Parallel Efforts





12

XML Standards Development

• World Wide Web Consortium (W3C)• OASIS (LegalXML Member Section)• Federal CIO Council (XML.gov)• Global Initiative

• XML Reconciliation Effort • Global XML Structure Task Force (GXSTF)




13

Sponsor Source Documents/Specifications

GISWG Reconciliation Data Dictionary (RDD) v1.0.0JTF for RSS Rap Sheet v2.2 schemaRISS RISSIntel v2.0 schemaLegalXML CourtFiling v1.1 DTDAAMVA Driver History v1.02 schemaNIJ InfoTech v2.0 data dictionary and schema

LA County, CA Incident Report schemaLegalXML Arrest Warrant schemaLegalXML Charging Document schemaLegalXML Sentencing Order schemaMinnesota CriMNet v1.0 data dictionary and schema

NCSC Data element spreadsheets (civil, criminal, juvenile)Maricopa Co, AZ ICJIS Data Dictionary v1.3CISA Southwest Border States Data Dictionary (TX, AZ, NM)FBI NCIC 2000 data dictionary and code tablesNIBRS Incident Report schemaSEARCH Justice Information Exchange Model (JIEM) data sets

Data Element and Object Sources





14

GJXDM, Version 3.0, Advantages

• Standards-based—adopts several XML and data standards• Model-based—generates consistent XML schema• Requirements-based—built from existing data models,

dictionaries, processes, and document specifications• Object-oriented—efficient extension and reuse (inheritance)• Extendable—enables local additions of data components• Expanded domain—includes courts, corrections, juvenile, etc.• Provided relationships for rich exchange information context• Built to evolve/advance with emerging technologies (e.g.,

RDF)





15

GJXDM Design Criteria

• Design a common set of reusable, extendible XML data components for a GJXDD that facilitates standard information exchange

• Over-inclusive and optional• Requirements, solutions, and time constraints from

rational compromises• Use International Organization for Standardization (ISO)

11179—Specification and Standardization of Data Elements and other applicable standards





16

GJXDM Design Criteria (continued)

• GJXDD will evolve—facilitate change and extension• Extension methods should minimize impact

on prior schema and code investments• Implement and represent domain relationships so they

are globally understood• Develop reference architecture and namespaces for a

standard Justice XML DD Schema (JXDDS) specification• Use object-oriented data model, named types, extensions





17

Global and GXSTF

External Sources

BugzillaListserv Practitioners

TechnicalPractitioners

Industry

Academia

Virtual Help Desk

Development Process





18

Information Technology Initiatives Web Site

• Resources for• Integration efforts• Integration profiles• Best practices• Funding approaches• System descriptions• Telecommunications

approaches• Model integrated

systems





19

Assumptions

• Reusable, extensible data components to facilitate standard information exchange in XML within justice, the courts, public safety, and homeland security

• Generalize for the community at large—NOT specific document instances

• Provide referenceable schema components for schema developers• JXDDS will evolve, change, and require extensions—best extension

method will minimize impact on prior investments• Must represent and implement domain relationships• No silver bullets—time, technical, and requirement constraints

mandate rational trade-offs





20

What Standards Have Been Applied?

• W3C—XML Schema Specification (05/01)• W3C—RDF and RDF Schema Specification (02/99)• XML.gov—draft Federal XML Schema Developer’s Guide (04/02)• ISO/IEC—11179 Specification and Standardization of Data Elements• UN/CEFACT—ebXML Core Components Technical Spec 1.9 (12/02)• DC—Dublin Core metadata for documents• U.S. DoD—U.S. Department of Defense 5015.2-STD Design Criteria

Standard for E-RMS Applications (06/02)• IC—Intelligence Community Metadata Language (ICML)• OASIS—XML Common Biometrics Format Committee (09/02)• ASC X12—Reference Model for XML Design (10/02)




21StrategyScheduleOrganizationNetwork

Rule Specification

Timing Definition

Security Architecture

Network ArchitectureDescription

Rule DesignControl

StructurePresentation Architecture

Business Rule Model

Processing Structure

Interface Architecture

Distributed Architecture

FocusFocus

Per

spec

tive

Per

spec

tive

Technology Architecture

FunctionData

ProgramData

Definitions

System Design

Physical Data Model

Logical Applications Architecture

Logical Data Model

FunctioningEnterpriseFunctioningEnterprise

System Model(Logical)Designer

System Model(Logical)Designer

Technology Model (Physical)Builder

Technology Model (Physical)Builder

Detailed Representations (Out-of-context)Subcontractor

Detailed Representations (Out-of-context)Subcontractor

Performance Plans

Transition Strategy

Organization Chart

Workplace and

Locations

Business Functions

Conceptual Data Model

MotivationWhy

MotivationWhy

Laws, Policy Strategic

Plans

TimeWhenTimeWhen

Business Mandates

PeopleWho

PeopleWho

Organization Units

NetworkWhere

NetworkWhere

Location Types

FunctionHow

FunctionHow

Mission and Focus

DataWhatDataWhat

Scope (Contextual)Planner

Scope (Contextual)Planner

Enterprise Model (Conceptual)Owner

Enterprise Model (Conceptual)Owner

Subject Areas

Data Standards (GJXDM)





22

Potential Barriers

• Not everyone will share the vision• The GJXDM is a big compromise—everyone will find one

or more things they do not like about it• Different from what many people are used to• Appears big and complex• Lack of training and understanding can lead

to overwhelming confusion• Often seems more difficult than what you would come up

with on your own to implement a particular exchange





23

Potential Barriers (continued)

• Few information exchange schemas exist today• GJXDM-specific tools are in their infancy• GJXDM learning curve may be inconsistent with

project timeline and cost• Developers want to do what they want to do

• They may not want to use the GJXDM• They may think the GJXDM is unusable• Management guidance is important





24

Who Is Using the GJXDM?

• Alaska Department of Public Safety

• Arizona – Maricopa County ICJIS

• AAMVA• California Automated Regional

Justice Information System (ARJIS); LA County, CA DOJ

• Illinois State Police• NLETS

• Pennsylvania JNET• RISS• CriMNet• Syracuse (3 Police

Departments and Prosecutor’s Office)

• Executive Office for U.S. Attorneys (EOUSA)

• Transportation (IEEE 1512)