Justice XML Data Model
Paul Embley
08 August 2003
Importance of Standards
Standards exponentially increase value to
everyone (critical mass)
 Electrical outlets & plugs
 Ethernet, TCP/IP, HTTP, HTML
Open standards, not organization, allowed the
Web to grow so fast
XML is the data standard
August 2003
Data is Data
Connectedness
Intelligence
Patterns
Information
Relationships
Data
Understanding
August 2003
What is XML?

A structured language for describing a electronic document sent by one
agency to another (e.g. Arrest/ Incident Report)

Sets a standard for exchanging information electronically

Establishes an organizing template for the electronic document

Facilitates standards-based data exchange
August 2003
What is XML?

XML specifications do not dictate how the data is stored
in sending or receiving systems

Specifications are broad enough to accommodate
jurisdictional differences

Specifications are shared among states and federal
justice agencies
August 2003
Header (Metadata)
Case Object
Person Object
Activity Object
(Offense)
Activity Object
(Disposition)
Activity Object
(Commitment)
August 2003
Justice XML Data Dictionary Schema Evolution
RDD
1.0
Document
Instances
Applications
JDD
3.0
JDD
4.0
Normative DD Schema
Reconcile:
RISS, Rap,
CF, AAMVA
Std Doc
Schemas
Standard Data Dictionary
DDS
2.0
RISS1.0
.xsd
CF1.1
.xsd
Rap2.2
.xsd
RISS
.xml
CF
.xml
Rap
.xml
1.0
Apps
Upper
Camel
Case
2.0
Apps
Object
Oriented
+ RDF
Block
.xsd
2.1
.xsd
2.0
.xml
2.0
DDS
2.1
.xsl
2.0-2.1
.xml
2.1
2.1
Apps
? .xsl
2.1-3.0
DDS
3.0
RDF
DD.rdfs
4.0
.xsd
3.0
.rdfs
4.0
.xml ? .xsl
3.0 3.0-4.0
.rdf
4.0
3.0
Apps
4.0
Apps
August 2003
JXDD Version 3.0
•
•
•
•
•
•
•
•
•
Aligned with standards (some were not available to RDD)
Model-based  consistent
Requirements-based – data elements, processes, documents
Object-oriented  efficient extension and reuse
Expanded domain (courts, corrections, juvenile, etc.)
Extensions to activity objects / processes
Relationships (to improve exchange information context)
Can evolve / advance with emerging technology (RDF/OWL)
Basis for an XML component registry that can provide
• Searching / browsing components and metadata
• Assistance for schema development / generation
• Reference / cache XML schemas for validation
• Interface (via std specs) to external XML registries
August 2003
What Standards Are Being Applied?
XML.gov
Draft Federal XML Schema Developer’s Guide (04/02)
ISO / IEC
11179 Specification & Standardization of Data Elements
UN / CEFACT ebXML Core Components Technical Spec 1.85 (09/02)
FBI
Electronic Fingerprint Transmission Spec v7 (01/99)
ANSI / NIST
Data Format for Interchange of Fingerprint, Facial, & SMT
OASIS
XML Common Biometrics Format Committee (09/02)
Dept of Navy Draft XML Registry Requirements (09/02)
DoD
DoD 5015.2-STD Design Criteria Std for E-RMS Apps (06/02)
W3C
XML Schema Specification (05/01)
W3C
RDF and RDF Schema Specification (02/99)
August 2003
What Sources of Requirements Are Being Used?
SPONSOR
SOURCE DOCUMENTS / SPECIFICATIONS
Global ISWG
JTF for ICHTS
RISS
LegalXML
AAMVA
Reconciliation Data Dictionary (RDD) v1.0.0
Rap Sheet v2.2 schema
RISSIntel v2.0 schema
CourtFiling v1.1 DTD
Driver History v1.02 schema
NIJ
LA County CA
InfoTech v2.0 Data Dictionary and schema
Incident Report schema
SEARCH
LegalXML
LegalXML
LegalXML
Minnesota
Justice Info Exchange Model (JIEM) data sets
Arrest Warrant schema
Charging Document schema
Sentencing Order schema
CriMNet v1.0 Data Dictionary and schema
NCSC
Maricopa Co AZ
CISA
FBI
NIBRS
Data element spreadsheets (civil, criminal, juvenile)
ICJIS Data Dictionary v1.3
Southwest Border States DD (TX, AZ, NM)
NCIC 2000 Data Dictionary and Code Tables
Incident Report schema
August 2003
JXDD v3.0.0.0
PreRelease
Content
Miscellaneous
general properties
and support types
Objects
Components
Activity
1092
Person
478
Property
308
Location
162
Document
107
Miscellaneous
99
Organization
86
ContactInformation 34
TOTALS
2366
%
46.2
20.2
13.0
6.9
4.5
4.2
3.6
1.4
100.0
Activity
107
99
86
34
Person
Property
162
1092
Location
Document
Miscellaneous
308
Organization
ContactInformation
478
August 2003
JXDM v3.0 Schedule
2003
Jan
Feb
Mar
Build Pre-Release
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
JXDM Pre-Release v3 for public review
Public review, vet, and refine
XSTF face-face
JXDM IOC v3 Decision
...
IOC Release
...
Reference document schemas
Refinement and maintenance
Maintenance releases
IOC = Initial Operational Capability
August 2003
Criteria for JXDM Validation Projects
Technical 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 & 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., intra-state exchanges involving
state, county, tribal, and local agencies.
August 2003
Validation Projects
• Colorado
• Washington
• Pennsylvania J-Net
potentially
15 states represented
(over ¼ of the U.S.)
• Criminal Information Sharing Alliance
(CISANet – CA, NM, AZ, TX, ID, GA)
• Minnesota CriMNet (MN, IA, IL, MI, ND, WI)
August 2003
Validation Projects
• WA Courts (Tom Clarke) – plans for Rap Sheet, Charging,
Citation, and Disposition documents
• PA J-Net (Linda Rosenberg) – plans for Driver History
• CISANet (Glen Gillum) – upgrade (in progress) will use
JXDD as target exchange format; will also design and
explore applicability of Justice Query Language (JQL)
• MN CriMNet (Tom Kooy) – will use JXDD for external
exchanges as required
August 2003
Other 3.0 Projects
• NLETS (Steve Correll) – Driver History, Rap Sheet
• CapWIN (George Ake) – integrated transportation and
criminal justice information wireless network
• Syracuse PD (Pete Small) – Three PD’s and Prosecutor’s
office
• LA County Sheriff – Incident Report
• Many others
August 2003
Reference Document Schemas
The Short List ~15
REFERENCE SCHEMA
Arrest/Incident Report
Common Alerting Protocol (CAP)
Inmate Record
Criminal History (Rap Sheet)
Arrest Warrant
Charging Document
Citation
Court Disposition / Disposition Rpt
Court Filing / Document v1.1
Court Order
Driver History
Filed Motion
Incident Status Summary (ICS-209)
Probation Report
Protection Order
Sentence Order
JUSTIFICATION
OASIS, LASD, NIBRS, MD
LASD, CAP
CriMNet
IL, WI, WA, MD
OASIS, WI
OASIS, LASD, WA
LASD, WA
OASIS, WA
OASIS (large spec)
has multiple types
AAMVA, PA JNet
has multiple types
DHS, NIMS
LASD
OASIS
OASIS, WA
August 2003
Reference Document Schemas
The Long List ~100+
• The Ultimate List may be ~150.
• Likely many more local schemas.
+
Common Alerting Protocol
Incident Status Sum (ICS209)
Court Filing and Document (v1.1)
August 2003
Justice XML Data Dictionary Registry/Repository Model
Data Requirements,
Business Processes, Models,
…
ebXML
compliant
LM = Lifecycle Mgt
QM = Query Mgt
Map
Other J/PS artifacts
Justice Data Dictionary
Model and Repository
Justice
Registry LM
Server
QM
Justice XML Repository
ebXML
compliant
EPA
QM
Registry
Server
DoD
QM
Registry
Server
Registry Client
Web Server
Registry Client
COTS Application
Browsers
August 2003
Justice Reference Model
Justice
Process
Model
Business
Architecture
• Business
Reference Model
Sequence
Sequenceof
ofEvents
Eventsin
inthe
theCriminal
CriminalJustice
JusticeSystem
System
Criminal
CriminalJustice
JusticeSystem
SystemModel
Model
Justice
Service
Model
Applications Architecture
• Conceptual/Process Model
• Interoperability Model
Data Architecture
Technology Architecture
• Technical Models
• Technical Reference Model
• Standards
Federal Enterprise Architecture (FEA)
(Architectures and Models)
Justice XML Data Model + Dictionary v3
XML, RDF, XMI / UML, SOAP
ebXML, UDDI, WSDl, WSCL,
WSFL, JAVA, J2EE, .Net
August 2003
What Else / What Next?
Additional requirements
• justice query language (jql)
• Security / sensitivity / privacy
• Web services
XSTF
• Reference document schemas
• Reviewing feedback
• Next scheduled meeting late Aug / early Sep
• Weekly teleconference to review feedback
• Work plan
• Technical Assistance Steering Cmte
IWG
• JXDM presentation 29 April 2003
• List of test requirements
• 1-page summary format for test results/feedback
• Will solicit help with reference document schemas
• Providing feedback through Mike Hulme
• Vendor contact
August 2003