Real-Life XML Implementation Stories

Real-Life XML Implementation Stories

Slide 1

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

APPA XML WebcastAPPA XML Webcast

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

BAJ Bureau ofJustice Assistance

1

XML and the Global Justice XML Data Model

(GJXDM)Paul Embley

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

Chair

Slide 2





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:

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

Attribution. You must give the original author credit.

• 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.

Slide 3





3

Topics• Definitions• Guidelines• Methodologies• Development Activities

Slide 4





4

GJXDM Information Exchange Package• A “GJXDM Information Exchange Package”

represents a GJXDM-conformant set of data that is transmitted for a specific business purpose

• Based on the definition of an “Information Exchange Package” in the Federal Enterprise Architecture (FEA) Data Reference Model (DRM)

• An instance of an XML document• Delivers the payload or information

Slide 5





5

GJXDM Information Exchange PackageDescription• A “GJXDM Information Exchange Package

Description” is a collection of artifacts that describe the structure and content of a GJXDM Information Exchange Package

• It does not specify other interface layers (such as web services)

• Known as GIEPD, IEPD, IEP

Slide 6





6

GJXDM Information Exchange PackageDescription - Reference• If an IEPD has been mandated, approved, endorsed,

recommended, or acknowledged by a cognizant organization, it may be referred to as a “reference”

• E.g., “GIEPD for a Reference Incident Report”

Slide 7





7

GJXDM Information Exchange PackageDescription Guidelines• Guidelines for what is included in an IEPD

• http://it.ojp.gov• http://www.ijisinstitute.org

Slide 8





8

IEPD Guidelines• 1. Purpose and Scope• 2. List of Artifacts• 3. XML Schemas

• GJXDM Subset Schema, Constraint Schema, Extension Schema, Document Schema

• 4. Additional Exchange Provisions• Minimal data set, additional business rules, etc.

• 5. Samples• XML Document Instances, XSL Style Sheets

• 6. Development• Participants, Process, Artifacts

• 7. Testing and Conformance• 8. Feedback

Slide 9





9

IEPD Development Process

• No particular process developing an IEPD is mandated

• A recommended process for developing an IEPD was released on January 2, 2005• “Exchange Document Development Process: An

Overview”• GIEPD is new name for “Exchange Document”• http://www.justiceintegration.com/whitepapers/

ExchangeDocumentProcessOverview.pdf

Slide 10





10

IEPD Development Process• Assemble a workgroup to develop the IEPD

• This group should include business experts as well as technical members familiar with domain object modeling and GJXDM

• Build a domain model• A graphical depiction of the document structure – UML encouraged• Use existing paper forms as well as business experts’ knowledge• Leverage GJXDM where appropriate without being constrained by

GJXDM• Map the entities and properties in the domain model to GJXDM

• Noting extensions where they occur• Build a GJXDM schema package from the mapping

• Use available tools (like the online subset schema generator andstylesheets) to create subset, constraint, extension, and document schemas

• Develop sample instances, document business rules• Package the artifacts in the GIEPD

Slide 11





11

Information Exchange Package Documentation Process

Slide 12





12

IEPDs Developed 2004-2005Sentencing OrderAmber AlertField Interview ReportCharging DocumentIncident ReportingUniform Rap SheetBooking/Arrest ReportTraffic Citation

Slide 13





13

• Probation/Parole/DOC to Courts: Pre-Sentence Investigation/Report

• Courts to Corrections: Judgment and Sentence• Corrections to Parole/Probation: Parole Board

Reports/ Offender Accountability• Corrections to Public Safety: Offender Information

and Status• Corrections to Victim Services: Offender

Information (movement, release, etc)

Corrections IEPDs

Slide 14





14

• Public Safety to Corrections: Arrest Reports, Warrants, Criminal History, Criminal DV Protection Orders

• Corrections to INS: Alien Information (SCAAP Grant also)

• Corrections to Corrections: Offender Record• Corrections to Courts: Financial Information• Corrections to Human Services: Child support

offender information

Corrections IEPDs (cont.)

Slide 15





15

Information Exchange Package DocumentationInmate NotificationThis document is intended to serve as a Reference IEP for inmate notifications.

It was produced by the New York City Department of Correction in order to notify interested parties of inmate admissions, releases and updates.

Purpose and ScopeThe business purpose of the Inmate Notification IEP, hereinafter referred to as

“the IEP,” is as follows:To define a data structure describing an inmate notification, including

admission to a correctional facility, discharge from a correction facility and updates to data of previously admitted inmates.

To describe a model for electronic exchange of inmate notification data among justice entities (including District Attorneys, police, courts) as well as to victims and to the public.

This IEP is intended to serve as a Reference IEP once approved by criminal justice agencies, especially those within the City and state of New York.

New York Inmate Notification IEPD

Slide 16





16

SRFERS - State, Regional & FederalEnterprise Retrieval System

Slide 17





17

ALEISS

ARJISTUSCON

PD

SPOKANE

PD

Mission: To seamlessly share justice Mission: To seamlessly share justice information across state boundariesinformation across state boundaries

Slide 18





18

1. Booking Info & Photos•

•

•

•

•

User requirements demonstrate the need for sharing booking photos across states

Current method is manual,time consuming and ineffective

Proposed:

Predicate-based, subject query on name,date of birth, and/or identification number

Photos will be sent via web services

Slide 19





19

2nd Annual Global Justice XML Data Model(Global JXDM) Users' Conference

September 2006San Diego or Phoenix

Slide 20





20

Paul Embley [email protected] Chair

Thank you!Thank you!

Slide 1

Implementing GJXML in Wisconsin

Mo WestWIJIS Business AnalystSeptember 8, 2005

P&P Conditions Exchange

APPA XML Webcast II

Slide 2

Describe the Information Exchange Package Document Process

Learn how to develop and implement your own exchange

Provide tools and strategies to help you!

Objectives

Slide 3

XML: Why Should I Care? Recap

XML is highly scalableTranscends database configurations GJXML is designed by and for the Justice CommunityFunding requirement from BJAEveryone else is doing it!

Slide 4

The Roots of Information Sharing

AnalysisJustification…“Going Paperless”Sept. 11th

Share across jurisdictions and domainsTimely accessPrevention

Slide 5

The WI Landscape: A Strong Foundation

Statewide SystemsDistrict Attorney Case Management (PROTECT)Consolidated Court Automation Program (CCAP)Integrated Corrections System (ICS)Criminal History Repository (CIB) and TIMEStatistical Analysis Center (SAC)

There is currently no mechanism to share incident information among Law Enforcement agencies!!!

Slide 6

Still Have Problems

Technical Term: Hairball

GJXML

Slide 7

Wisconsin’s Approach

Purpose: Build capacity for information sharing among justice and other public safety agencies at local, state, tribal and federal levelsVision: The Justice Gateway will be a single secure point of access, via GJXML, to ‘read only’ information from the justice community.

WIsconsin Justice Information Sharing Program

Slide 8

Getting StartedMay ‘04

Project Executive (and Staff)

Business Advisory

Committee

Technical Advisory

Committee

Policy Advisory Group

Justice Partners

Legislature

Requirements

MOU/Contracts

Privacy/Open Records

Public Information

Operational Management

Security

Technical ArchitectureUser Groups

Working Groups

Slide 9

The Hard Work Begins

Identified ExchangesIncidentsArrestsCharging DecisionsVehicle Registrations (for partial plate searches)Supervision Conditions

The IEPD Process Begins!

Slide 10

IEPD Goals and Objectives

Define IEPDs (Information Exchange Package Documentation) to support interoperability among justice systemsExpand and refine GJXDM/DD through experienced feedback; resolve vague definitionsRestrict to key choices to support interoperability

Slide 11

IEPD Process

•

•

•

•

•

•

•

•

•

Group OrganizationJIEM/Exchange RequirementsDomain Modeling (object modeling)GJXDM MappingSubset Schema (SSGT)Extension, Constraint, Document SchemasSample XML InstancePackagingHorizontal Analysis/Reuse

Slide 12

Step 1: Get the Right People

Subject Matter Expertise is crucialWelcome IT StaffDon’t Be Shy!FacilitationProvide DocumentationKeep the number manageable

Slide 13

Step 2: JIEM Analysis

Justice Information Exchange Modeling Tool is useful to identify the type, partners, conditions and data involved in one exchange. This is a great way to set parameters around the exchangeLet’s see what it looks like…

Slide 14

JIEM Tool

Slide 15

Step 3: Domain Modeling

Graphic depiction of an exchange (in case schemas aren’t your cup of tea).Defines terms and relationships between data and documents the thought processInteractive; could even be fun…Different approaches for the same result; a smorgasbord of tools available!

Slide 16

Criminal Filing

CaseCourt

Case

CaseParticipants

CaseJudgeCaseProsecutionAttorney

CaseDefendantParty

CaseChargeArrest/Detention/Citation

ArrestingAgency

Booking

Investigating Officer

BookingAgency

CaseCourtClerk

1,*

1

1

1,*

1

10,*

0,1

0,1

1,*

1

1

1

1

Reference

1

CaseDefenseAttorney

1,*

1,*

ArrestSubject

1

1,*

1

Bail

0,*

Sample Domain Model

Source: Search Consortium-Charging IEPD

Slide 17

Source: Search Consortium-Sentence Order

Sample Domain Model

Slide 18

Argo UML: One Tool

Class:Object title

AttributesRoot Object

Slide 19

Step 4: Mapping to GJXDM

Class and attribute definitionsSpreadsheet generationLooking through the data modelReconciliation or extensionTools for documenting

Slide 20

Example Spreadsheet

Source: SEARCH Consortium

Sentence Order IEPD

Slide 21

Navigating the Data Model

Excel SpreadsheetStraight to the sourceLots of data to work through

WayfarerSurfing the modelContext around the data User Friendly

GTRI Search/Viewer tool in the SSGT

Slide 22

Wayfarer

Slide 23

Step 5: Schema Generation

Schema package is a combinationGJXDM is a reference onlyTake what you need: Creating the subset (SSGT) and wantlistConstraint Schema: Applying cardinalityExtension Schema: New NamespacesDocument Schema: The RootSample XML Instance

Slide 24

Subset Schema Generation Tool

Provides a schema for the specific exchangeIncorporates requirementsValidates against the full modelEdits can be made later on the ‘wantlist’Zips up neatly

Slide 25

SSGT

Slide 26

SSGT

Slide 27

SSGT: Results<?xml version="1.0" encoding="UTF-8" ?> - <w:wantList w:release="3.0.2" xmlns:w="http://gjxdmtools.gtri.gatech.edu/wantList/1"><w:element w:prefix="j" w:name="ArrestOfficial" w:isReference="true" /> <w:element w:prefix="j" w:name="ArrestOfficial" w:isReference="false" /> <w:element w:prefix="j" w:name="ArrestSubject" w:isReference="false" /> <w:element w:prefix="j" w:name="ContactPerson" w:isReference="false" /> <w:element w:prefix="j" w:name="CriminalTraitDetails" w:isReference="false" /> <w:element w:prefix="j" w:name="Employment" w:isReference="false" /> <w:element w:prefix="j" w:name="EmploymentEmployer" w:qualifier="Organization" w:isReference="true" /> <w:element w:prefix="j" w:name="EmploymentEmployer" w:qualifier="Organization" w:isReference="false" /> <w:element w:prefix="j" w:name="EmploymentEmployer" w:qualifier="Person" w:isReference="true" /> <w:element w:prefix="j" w:name="EmploymentEmployer" w:qualifier="Person" w:isReference="false" /> <w:element w:prefix="j" w:name="EnforcementOfficialUnit" w:isReference="false" /> <w:element w:prefix="j" w:name="Image" w:isReference="false" /> <w:element w:prefix="j" w:name="IncidentArrest" w:isReference="false" /> <w:element w:prefix="j" w:name="IncidentInvolvedProperty" w:isReference="false" /> <w:element w:prefix="j" w:name="IncidentInvolvedStructure" w:isReference="false" /> <w:element w:prefix="j" w:name="IncidentLocation" w:isReference="false" /> <w:element w:prefix="j" w:name="IncidentResponse" w:isReference="false" /> <w:element w:prefix="j" w:name="IncidentResponseOrganization" w:isReference="false" /> <w:element w:prefix="j" w:name="IncidentSubject" w:isReference="false" /> <w:element w:prefix="j" w:name="IncidentSubjectOrganization" w:isReference="false" />

Source: SEARCH Field Interview Report IEPD: Subset Schema

Slide 28

Step 6: Packaging

Putting it all togetherDomain ModelMapping SpreadsheetSchemas:

• Subset • Constraint • Extension • Document

Sample XML Instance

Slide 29

Re-use and Analysis

Others will be interested in the outcomeStandardizationFirst step in an iterative processTake advantage of national resources

Slide 30

P & P in Wisconsin: Getting Started

Wouldn’t it be nice if…Funding from the National Governors’Association Center for Best PracticesProject Team formedProject Plan developed

Identify StakeholdersHigh level requirements

Assembled the committee

Slide 31

P & P Exchange Committee

Law EnforcementPatrol officersIT staff

DOCManagementProbation and Parole AgentsIT Staff

WIJIS Staff

Slide 32

Documents Provided

Sample Return from TIME System (DOJ)Name RaceDOBRelease DateConviction StatueAgent Name and Phone Number

Samples of Standard Rules (DOC Imposed) and Common Conditions (Court Ordered)

Slide 33

JIEM Analysis

Slide 34

Work in Progress

Action shots: Developing the domain model. (it does take its

toll on the facilitators)

Slide 35

P&P UML Diagram

Slide 36

The Work Continues

Scheduling Meetings to continue mapping to GJXDMSchema GenerationTechnical ImplementationApplication development/incorporationCommunication; progress reportingIterative Process

Slide 37

Resources and Tools

Everything and more at http//it.ojp.govIEPDs can be found at www.search.org“Exchange Document Development Process: An Overview”; by Justice Integration SolutionsIJIS Institute: www.ijis.orgWayfarer: www.ncsconline.org/d_tech/gjxdm/

JIEM Tool: http://www.search.org/programs/info/jiem.aspArgo UML: http://argouml.tigris.org/Wayfarer: www.ncsconline.org/d_tech/gjxdm/SSGT: http://justicexml.gtri.gatech.edu/subset_tool.html

Slide 38

Thanks!

Questions, comments:[email protected]

For more information please visit:

http://oja.state.wi.us