architectural governance & oversight global justice xml data model aka: justice xml data...

ARCHITECTURAL GOVERNANCE & OVERSIGHT

Global Justice XML Data Modelaka: Justice XML Data Dictionary (JXDD)

PA Driver History JXDD 3.0 Model Validation

January 8-9, 2004National Governors Association

More about JNET www.pajnet.state.pa.us

PA Driver History XML Model

The Pennsylvania JNET XML Vision

Collaborative Effort:

JNET – an integrated criminal justice network governed by representatives from 15 state and 2 county agencies with one common goal: exchange critical and useful information efficiently.

JXDD 3.0-based Driver History message the most recent example of continuing inter-agency cooperation. Developed by JNET and PA Department of Transportation, deployed August 2003.

Driver History initiative selected by DOJ as one of several validation projects. JNET / DOT receive technical support from GA Tech Research Institute (GTRI) scientists – designers of JXDD 3.0.



Overall Advantages:

JXDD 3.0’s object model is a ready-made source of data objects common to the criminal justice community that are highly reusable.

JXDD 3.0’s flexible object structure allows extension of data elements to meet local requirements (optional, multiple).

JXDD 3.0 minimizes data conflicts (some standardized codes).

Reliance on JXDD 3.0 to develop subsequent applications will result in long term resource and cost savings.

JXDD 3.0’s wider domain coverage will enable justice and public safety agencies to more effectively share information at all levels (Enforcement, Courts, Corrections, Probation, Driver/Vehicles, etc.).



Lessons Learned:

There is a learning curve. JXDD 3.0 has been vastly upgraded over version 2.1 and is still a work in progress. JNET has been using version 3.0 prerelease. Global / GTRI expects to release 3.0 Initial Operating Capacity (IOC) by mid-January 2004.

IOC version will stabilize JXDD, requiring minor changes to existing documentation developed using 3.0 prerelease.

Agencies working in a collaborative manner need to agree on protocol for implementing JXDD 3.0.

GTRI technical support invaluable. Development and training tools for searching JXDD and building schema set for release in early 2004.



Implementation Issues:

The JXDD 3.0 full schema is very large. Customized subset / partial schema development strategy recommended by GTRI works well.

Properly partitioned applications will enhance implementation flexibility: Business data in XML format Presentation in HTML format

Upcoming JXDD 3.0 search tool, schema design tool, and repository/ registry will enhance utility. GTRI presently developing these tools.

Future version(s) of JXDD will present new development options. It’s the direction the technology is heading (from structure to semantic).



Improved Information Sharing Efficiency and Effectiveness:

Same set of XML data will service different applications: On-line web applications External systems Mobile applications

XML data can be translated to meet local needs.

Business Case for using JXDD 3.0 XML:

More reusable data objects defined in JXDD 3.0.

Customized subset / partial schema approach resolves flexibility and extendibility issues (reuse of JXDD data objects, eliminates unnecessary attributes,

multiplicity defined accurately based on local needs, constraints refined).



Policy Considerations:

Interoperability is XML technology’s greatest benefit. XML is a text file and does not rely on any one platform.

JXDD 3.0 will not give you everything. Keep expectations realistic.

With the proper architecture, JXDD 3.0 extendibility will enable agencies to structure their own approach.

PA Driver History – 80% JXDD, 20% extended PA Sentencing Guidelines – 60% JXDD, 40% extended

Executive level understanding and leadership key. JNET’s Executive Director Linda Rosenberg the driving force behind JXDD 3.0 project implementations – benefits that will be realized Commonwealth-wide.



Technician and Vendor Considerations:

Greatest benefit derived from JXDD 3.0 when there is a demonstrated need to share information across agencies. Still useful intra-agency, but most useful inter-agency.

Define your business goals and requirements – what type of participants will be involved in the information sharing effort:

Federated – independent model, each agency going their own way[e.g. health care sector, finance sector, criminal justice agency]

VS. Centralized – single authority model, consolidated control

[e.g. NASA, criminal justice authority]

JNET’s collaborative effort falls somewhere in the middle.


The original JNET blueprint, published during late 1997, defined an XML based “electronic interchange of data” concept.

JNET’s blueprint established a requirement for the usage of “a standard criminal justice file format to support the electronic interchange of data”.

The blueprint further stated “XML provides information about the data itself and how it relates to other data. In essence, XML is emerging as a standard for web-based delivery of data in agreed- upon name-value pairs.”



The JNET blueprint established a strategic direction for sharing information among JNET participating organizations.

A globally accepted, criminal justice focused, XML data standard is essential to accomplishing the strategy.

JNET is, and has always been, in 100% support of “Facilitating information sharing and integrated justice by reducing impediments, such as standards, cost, and time.”

JNET is committed to being part of the enablement process to more effectively provide information sharing and communications among the many justice/public-safety agencies at the local, state, and federal levels.



Reliable Messaging Infrastructure

XML Syntax, DTD, JNET Messages

Justice XML Data Model and Schema

Service/Process Definition - ebXML

Justice RDF/OWL

Semantic Web

We are here

XML Technical Strategy


Identify, Analyze Data Source and object modeling

Understand Justice Data Model

Map data source object model to Justice data model

Fill the gap:•Add extensions and restrictions•Add local elements

Define data mapping between data source and XML

Define transformation rules between XML and web presentations

Start

End

XML Design Approach


Message Structure

DriverHistory

Driver

jxdd3:PersonGivenNamejxdd3:PersonMiddleNamejxdd3:PersonSurNamejxdd3:PersonSuffixNamejxdd3:PersonBirthDate

jxdd3:PersonName

jxdd3:PersonAssignedIDDetails jxdd3:PersonDriverLicenseID

jxdd3:PersonPhysicalDetails jxdd3:PersonSexTextjxdd3:PersonSexCode

DriverRecordTypeElement

jxdd3:Address jxdd3:StreetFullTextjxdd3:AddressCityName

jxdd3:AddressStreet

jxdd3:AddressStateCodeusps:USStateCodeTypeElement

jxdd3:AddressPostalCodeID

DLAuthorizationCDLAuthorizationOLLAuthorizationPLAuthorization

jxdd3:DriverAuthorizationIssueDatejxdd3: DriverAuthorizationExpirationDatejxdd3: DriverAuthorizationEndorsementCode

DriverLicenseClassCode

jxdd3:DriverAuthorizationRestriction

jxdd3: DrivingRestrictionDescriptionText

DriverOriginalAuthorizationIssueDate

DriverLicenseLearnerPermitClassCode

DriverLicenseStatusElement

DriverLicenseSchoolBusEndorsementDescdriptionText

DriverAccident

jxdd3: ActivityDate

jxdd3: IncidentLocation

jxdd3: LocationDescriptionTextVehicleType

DriverLicenseStatusCodeDriverLicenseStatusDescriptionText

DriverRecordTypeCodeDriverRecordTypeDescriptionText

ViolationIncidentMedicalIncident

jxdd3: ActivityTypeText jxdd3: ActivityDescriptionTextjxdd3: ActivityDate

ActionPLActionOLLActionResponseAction

jxdd3: ActivityDate

jxdd3:Incident

jxdd3: ActivityCommentText

jxdd3: Conviction

jxdd3: CourtActivity

ProcessDate

Consequence

Act143Disclaimer

jxdd3: ActivityResultText


Data Element MappingDL 2020 Element XML Sub Node XML Path Compliant

CUS001 DLNumber Driver DriverHistory/Driver/jxdd3:PersonAssignedIDDetails/jxdd3:PersonDriverLicenseID Y

LastName Driver DriverHistory/Driver/jxdd3:PersonName/jxdd3:PersonSurName Y

FirstName Driver DriverHistory/Driver/jxdd3:PersonName/jxdd3:PersonGivenName Y

MiddleName Driver DriverHistory/Driver/jxdd3:PersonName/jxdd3:PersonMiddleName Y

Suffix Driver DriverHistory/Driver/jxdd3:PersonName/jxdd3:PersonSuffixName Y

CUS002 AddressLine1 Address DriverHistory/jxdd3:Address/jxdd3:AddressStreet/jxdd3:/StreetFullText Y

AddressLine2 Address DriverHistory/jxdd3:Address/jxdd3:AddressStreet/jxdd3:/StreetFullText Y

City Address DriverHistory/jxdd3:Address/jxdd3:AddressCityName Y

State Address DriverHistory/jxdd3:Address/jxdd3:AddressStateCode/usps:USStateCodeTypeElement Y

ZipCode Address DriverHistory/jxdd3:Address/jxdd3:AddressPostalCodeID Y

CUS003 DateOfBirth Driver DriverHistory/pajnet:Driver/jxdd3:PersonBirthDate Y

Sex Driver DriverHistory/pajnet:Driver/jxdd3:PersonPhysicalDetails/jxdd3:PersonSexText Y

DriverHistory/pajnet:Driver/jxdd3:PersonPhysicalDetails/jxdd3:PersonSexCode

RecordType Driver DriverHistory/Driver/DriverRecordTypeElement/DriverRecordTypeCode N

Driver DriverHistory/Driver/DriverRecordTypeElement/DriverRecordTypeDescriptionText

CUS004 DLLicenseClass DLAuthorization DriverHistory/DLAuthorization/DriverLicenseClassCode Y

DLIssueDate DLAuthorization DriverHistory/DLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationIssueDate Y

DLOrgIssueDate DLAuthorization DriverHistory/DLAuthorization/DriverOriginalAuthorizationIssueDate N

DLExpireDate DLAuthorization DriverHistory/DriverAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationExpirationDate Y

DLMedRestrictions DLAuthorizationDriverHistory/DLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationRestriction/jxdd3:DrivingRestrictionDescriptionText Y

DLLearnerPermit DLAuthorization DriverHistory/DLAuthorization/DriverLicenseLearnerPermitClassCode Y

DLStatus DLAuthorization DriverHistory/DLAuthorization/DriverLicenseStatusElement/DriverLicenseStatusCode N

DLAuthorization DriverHistory/DLAuthorization/DriverLicenseStatusElement/DriverLicenseStatusDescriptionText

CUS005 CDLClass CDLAuthorization DriverHistory/CDLAuthorization/DriverLicenseClassCode Y

CDLIssueDate CDLAuthorization DriverHistory/CDLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationIssueDate Y

CDLExpireDate CDLAuthorization DriverHistory/CDLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationExpirationDate Y

CDLEndorsements CDLAuthorization DriverHistory/CDLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationEndorsementText Y

CDLRestricitons CDLAuthorizationDriverHistory/CDLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationRestriction/jxdd3:DrivingRestrictionDescriptionText Y

CDLLearnerPermit CDLAuthorization DriverHistory/CDLAuthorization/DriverLicenseLearnerPermitClassCode Y

CDLStatus CDLAuthorization DriverHistory/CDLAuthorization/DriverLicenseStatusElement/DriverLicenseStatusCode N

CDLAuthorization DriverHistory/CDLAuthorization/DriverLicenseStatusElement/DriverLicenseStatusDescriptionText

CDLSBEndorsements CDLAuthorization DriverHistory/CDLAuthorization/DriverLicenseSchoolBusEndorsementDescriptionText N

CDLEndorsements2 CDLAuthorization

CUS006 PLLicenseClass PLAuthorization DriverHistory/PLAuthorization/DriverLicenseClassCode Y

PLIssueDate PLAuthorization DriverHistory/PLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationIssueDate Y

PLExpireDate PLAuthorization DriverHistory/PLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationExpirationDate Y

PLStatus PLAuthorization DriverHistory/PLAuthorization/DriverLicenseStatusElement/DriverLicenseStatusCode N

PLAuthorization DriverHistory/PLAuthorization/DriverLicenseStatusElement/DriverLicenseStatusDescriptionText

CUS007 OLLLicenseClass OLLAuthorization DriverHistory/OLLAuthorization/DriverLicenseClassCode Y

OLLIssueDate OLLAuthorization DriverHistory/OLLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationIssueDate Y

OLLExpireDate OLLAuthorization DriverHistory/OLLAuthorization/jxdd3:DriverAuthorization/jxdd3:DriverAuthorizationExpirationDate Y

OLLStatus OLLAuthorization DriverHistory/OLLAuthorization/DriverLicenseStatusElement/DriverLicenseStatusCode N

OLLAuthorization DriverHistory/OLLAuthorization/DriverLicenseStatusElement/DriverLicenseStatusDescriptionText

VAC (Violation) ACTION ViolationIncident DriverHistory/ViolationIncident/Consequence/Action/jxdd3:ActivityResultText Y

VCD (Violation) CONVICTION DATE ViolationIncident DriverHistory/ViolationIncident/jxdd3:Conviction/jxdd3:ActivityDate Y

VCI (Violation) COURT INFO ViolationIncident DriverHistory/ViolationIncident/Consequence/jxdd3:CourtActivity/jxdd3:ActivityCommentText Y

VDS (Violation) DESCRIPTION ViolationIncident DriverHistory/ViolationIncident/jxdd3:Incident/jxdd3:ActivityDescriptionText Y

VIL (Violation) VIOLATION ViolationIncident DriverHistory/ViolationIncident/jxdd3:Incident/jxdd3:ActivityTypeText Y

VLD (Violation) VIOLATION DATE ViolationIncident DriverHistory/ViolationIncident/jxdd3:Incident/jxdd3:ActivityDate Y

VPD (Violation) PROCESS DATE ViolationIncident DriverHistory/ViolationIncident/ProcessDate N

ATD (Accident) VEHICLE TYPE DriverAccident DriverHistory/DriverAccident/VehicleTypeDescriptionText N

ACL (Accident) LOCATION DriverAccident DriverHistory/DriverAccident/jxdd3:IncidentLocation/jxdd3:LocationDescriptionText Y

MAC (Mdeical) ACTION MedicalIncident DriverHistory/MedicalIncident/Consequence/Action/jxdd3:ActivityResultText Y

MCD (Mdeical) CONVICTION DATE MedicalIncident DriverHistory/MedicalIncident/jxdd3:Conviction/jxdd3:ActivityDate Y

MCI (Mdeical) COURT INFO MedicalIncident DriverHistory/MedicalIncident/Consequence/jxdd3:CourtActivity/jxdd3:ActivityCommentText Y

MDS (Mdeical) DESCRIPTION MedicalIncident DriverHistory/MedicalIncident/jxdd3:Incident/jxdd3:ActivityDescriptionText Y

MIL (Mdeical) VIOLATION MedicalIncident DriverHistory/MedicalIncident/jxdd3:Incident/jxdd3:ActivityTypeText Y

MLD (Mdeical) VIOLATION DATE MedicalIncident DriverHistory/MedicalIncident/jxdd3:Incident/jxdd3:ActivityDate Y

PLA (Violation) PL ACTION ViolationIncident DriverHistory/ViolationIncident/Consequence/PLAction/jxdd3:ActivityResultText N

OLA (Violation) OL ACTION ViolationIncident DriverHistory/ViolationIncident/Consequence/OLLAction/jxdd3:ActivityResultText N


Messaging Hub

JNET

SSL

SSL

SSL

AOPC

PennDOT IMS

Web App

PSP IIMS

PennDOT Photo DB

JNET User Desktop

SSL

Wireless Middleware

Carrier Carrier Network(s)Network(s)

JNET User PDA

SSL/VPN

Police Troopers

Infrastructure for Driver Information


Project Cost Estimation

Overall cost: $350K which includes:

•JXDD research•Understanding JXDD•Strategy, methodology

•Data source analyses•Understanding data•Object Modeling•Data mapping

•XML design work •Schema•Transformation (mainframe to XML)•Presentation style sheet

•Application development•Web app•Security•Application and system integration

•Testing and deployment

* Hardware and software costs are not covered.


JNET Driver Information Query Demo

Driver Photo Lookup

Driver History Report

Driver Information Demo


Driver Photo Lookup


Driver Photo Lookup (continued)


Driver History Report


Driver History Report (continued)


Find Out More About JXDD 3.0

Website Resources:

DOJ Global Justice Information Sharing Initiative www.it.ojp.gov

Information Technology, Office of Justice Programs-DOJ

www.ijis.orgIntegrated Justice Information Systems, Industry Working Group

www.ijisinstitute.org Integrated Justice Information Systems Institute

www.it.ojp.gov/jsr/public/index.jspJustice Standards Clearinghouse

http://justicexml.gtri.gatech.eduGeorgia Tech Research Institute, Global Justice XML Information Center

More about JNET www.pajnet.state.pa.us


Find Out More About JXDD 3.0

Reference Article

U.S. Department of Justice – Office of Justice ProgramsInformation Technology Initiatives 12/17/03 http://www.it.ojp.gov (‘… More News’ link)

Pennsylvania’s JNET Crafts a Robust Online Driver History Record Tool Using Global Justice XML

“Pennsylvania's Justice Network (JNET), in cooperation with thePennsylvania Department of Transportation (PennDOT), debuts its online Driver History Record tool, JNET's first implementation using the Global Justice Information Sharing Initiative's (Global) Justice Extensible Markup Language (XML) Data Dictionary. This is the most frequently queried tool of JNET's suite of online offerings, providing digital driver photos, demographics, and driver histories to authorized users.”


Q & A

architectural governance & oversight global justice xml data model aka: justice xml data...

Documents