The Development of the Global Justice XML Data Model

1
The Development of the Global Justice XML Data
Model

• Robin Gibson
• Missouri Office of the State Courts Administrator
• Global XML Structure Task Force

2
The Business Case for Justice Information Sharing

• Criminal activity is not confined to a single
  county or state
• Criminals today can move much faster than
  information about them
• Information is needed nationwide, not just
  locally or even statewide
• Paper cannot move information far enough or fast
  enough to meet justice system needs

3
The Business Case for Justice Information Sharing

• Justice system officials do not have the
  information they need to make informed decisions
• Justice and public safety is an
  information-dependent enterprise that often
  operates (at a cost of billions of dollars) with
  little or no information
• The information that we do have often does not
  arrive in time to make a difference

4
The Business Case for Justice Information Sharing

• Consequences
• We treat career criminals as first-time offenders
• We release persons who should not be released due
  to previous behavior
• We hire employees with criminal records that
  would otherwise disqualify them
• Inappropriate charging, plea agreement,
  disposition, sentencing, classification,
  treatment, placement, and other decisions

5
How did the Justice XML initiative get started
and why is it needed?

• 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 termsuniversal dictionary
• Flexible content images, summary offender
  profile, location data, status, etc.

6
What is Justice XML?
Purpose Facilitate information sharing and
integrated justice by reducing impediments such
as conflicting systems, high development cost and
time.
XML A set of rules that specify syntax for
information exchange.
Justice XML Extends XML to the justice and
public safety communities by providing a standard
vocabulary and semantic building blocks that can
be reused and extended by practitioner,
integrator, and vendor communities.
7
Information Sharing is supported by
Interoperability and Component Reuse

• Horizontal and vertical information sharing
  between business lines
• Re-use and integration of data, as opposed to
  duplication
• Enabler to support cross-agency collaboration
• Facilitates cross-agency information exchanges
• Consistent means to categorize and classify data

Integrated Enterprise
Agency 1
Agency 2
FEA-DRM
State
Local
Agency 3
Agency 4
8
Who created the GJXDM?
Global XML Structure Task Force of the Global
Infrastructure/Standards Working Group
9
Representation on the XSTF

• Corrections Administrators
• AAMVA
• Probation and Parole
• IWG
• IACP
• Federal CIO Council

• FBI
• NTIA
• SEARCH
• Georgia Tech Research Institute
• JTFRSS

10
Representation on the XSTF

• State/Local Law Enforcement
• NLETS
• RISS
• CISA
• CriMNet
• NM, MN, IL, WI, MO, MT, VA, WA, GA, PA, OK, AL,
  CO, AZ
• Vendors

• Courts
• Joint Technology Committee of COSCA and NACM
• National Center for State Courts
• OASIS LegalXML Member Section Technical
  Committees
• National Association of Court Managers

11
Justice XML Combining Parallel Efforts into
Similar Goals
Document Instances
Complex Components
Simple Components
Support Data Components
12
XML Standards Development

• World Wide Web Consortium (W3C)
• OASIS Organization for the Advancement of
  Structured Information Standards (LegalXML Member
  Section)
• Federal CIO Council (XML.gov)
• Global Justice Information Sharing Initiative
• XML Reconciliation Effort ?
• XML Structure Task Force (XSTF)

13
Data Element and Object Sources
SPONSOR SOURCE DOCUMENTS / SPECIFICATIONS Global
ISWG Reconciliation Data Dictionary (RDD)
v1.0.0 JTF for RSS Rap Sheet v2.2
schema RISS RISSIntel v2.0 schema LegalXML CourtFi
ling v1.1 DTD AAMVA Driver History v1.02
schema NIJ InfoTech v2.0 data dictionary and
schema LA County, CA Incident Report
schema LegalXML Arrest Warrant schema LegalXML Cha
rging Document schema LegalXML Sentencing Order
schema Minnesota CriMNet v1.0 data dictionary and
schema NCSC Data element spreadsheets (civil,
criminal, juvenile) Maricopa Co AZ ICJIS Data
Dictionary v1.3 CISA Southwest Border States Data
Dictionary (TX, AZ, NM) FBI NCIC 2000 data
dictionary and code tables NIBRS Incident Report
schema SEARCH Justice Information Exchange Model
(JIEM) data sets
14
GJXDM 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, document specs
• Object-oriented efficient extension and reuse
  (inheritance)
• Extendable enables local additions of data
  components
• Expanded domain includes courts, corrections,
  juvenile, etc.
• Provides 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 Global Justice Data
  Dictionary (GJXDD) that facilitates standard
  information exchange
• Generalize GJXDD for the justice and public
  safety do NOT target specific applications or
  systems
• Over-inclusive and Optional
• Provide reference-able schema components

16
GJXDM Design Criteria

• 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
• Requirements, solutions, and time constraints
  require rational compromises

17
GJXDM Design Criteria

• Develop reference architecture and namespaces for
  a standard Justice XML DD Schema (JXDDS)
  specification
• Use object-oriented data model, named types,
  extensions
• Use ISO 11179 - Specification Standardization
  of Data Elements and other applicable standards
• Metadata for content, registry support, and
  infrastructure

18
GJXDM Design Criteria

• Enable value constraints codes / enumerations,
  special semantics
• Utilize primary (IS-A, HAS-A) and secondary
  (domain) relationships
• Build from functional requirements, reference
  documents, use cases, business context components
  and containers
• Provide migration paths for evolution to new
  technologies

19
GJXDM Design Criteria Goals

• Enable forms-based maintenance / reconfiguration
  of JXDD model
• Automatic generation of XML Schema for the JXDDS
• Automatically generate equivalent RDF Schema.
• Store and map data element requirements from any
  data source (schema, DTD, data table, or data
  dictionary) to JXDD components.
• Enables measurement by source, of number of data
  requirements covered and number left to implement
  in the JXDD.
• Provide search filters, forms, and tools to
  quickly analyze data requirements and build
  initial draft object models for vetting

20
Assumptions

• Re-usable, 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 reference-able schema components for
  schema developers
• Justice XML DD and Schema 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

21
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 Developers
  Guide (04/02)
• ISO/IEC 11179 Specification Standardization
  of Data Elements
• UN/CEFACT ebXML Core Components Technical Spec
  1.9 (12/02)
• DC Dublin Core metadata for documents
• US DoD DoD 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)

22
ISO Standard 11179Data Element Naming Syntax
Property Term (follows object class term)
Object Class Term (left-most)
Representation Term (right-most)
23
What does the GJXDM Contain??
GJXDM v3.0 (Jan 2004) Complex types (approx)
400 Simple types (approx) 150 Properties
(approx) 2,200
Total components 2,750
Source requirement references 34 Source
requirement components 16,000
According to one government data consultant, all
branches and departments of a typical state
government use about 20,000 unique data elements.
24
What do These Contents Represent??
2754 Total data
components (545 types
2209 properties)
Metadata 116
Misc 177
Org 94
Location 178
Activity 1216
Property 397
Person 543
25
GJXDD Spreadsheet
jxdm-3.0.xls
26
The Development of the Global Justice XML Data
Model

• Robin Gibson
• Missouri Office of the State Courts Administrator
• Global XML Structure Task Force