1 / 23

Justice XML Data Model

Justice XML Structure Task Force. 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

keefer
Download Presentation

Justice XML Data Model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Justice XML Structure Task Force Justice XML Data Model Paul Embley 08 August 2003

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

  3. Intelligence Patterns Information Relationships Data is Data Connectedness Data Understanding

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

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

  6. Header (Metadata) Case Object Person Object Activity Object (Offense) Activity Object (Disposition) Activity Object (Commitment)

  7. Reconcile: RISS, Rap, CF, AAMVA RISS1.0.xsd CF1.1 .xsd Std Doc Schemas Rap2.2 .xsd JDD 3.0 RDD 1.0 JDD 4.0 RISS.xml CF .xml Document Instances Rap .xml 1.0 Apps Applications Justice XML Data Dictionary Schema Evolution Standard Data Dictionary Normative DD Schema Object Oriented + RDF Block Upper Camel Case DDS 2.0 DDS 2.1 DDS 3.0 DD.rdfs 4.0 RDF .xsd 2.1 .xsd 3.0 .rdfs 4.0 .xsd 2.0 .xml 2.1 .xml 3.0 .rdf 4.0 .xml 2.0 ? .xsl 2.1-3.0 ? .xsl 3.0-4.0 .xsl 2.0-2.1 2.1 Apps 3.0 Apps 4.0 Apps 2.0 Apps

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

  9. 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)

  10. What Sources of Requirements Are Being Used? SPONSORSOURCE DOCUMENTS / SPECIFICATIONS Global ISWG Reconciliation Data Dictionary (RDD) v1.0.0 JTF for ICHTS Rap Sheet v2.2 schema RISS RISSIntel v2.0 schema LegalXML CourtFiling v1.1 DTD AAMVA Driver History v1.02 schema NIJ InfoTech v2.0 Data Dictionary and schema LA County CA Incident Report schema SEARCH Justice Info Exchange Model (JIEM) data sets LegalXML Arrest Warrant schema LegalXML Charging 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 DD (TX, AZ, NM) FBI NCIC 2000 Data Dictionary and Code Tables NIBRS Incident Report schema

  11. ObjectsComponents % Activity 1092 46.2 Person 478 20.2 Property 308 13.0 Location 162 6.9 Document 107 4.5 Miscellaneous 99 4.2 Organization 86 3.6 ContactInformation 34 1.4 TOTALS 2366 100.0 JXDD v3.0.0.0PreRelease Content Miscellaneous general properties and support types

  12. JXDM v3.0 Schedule 2003 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec JXDM Pre-Release v3 for public review Build Pre-Release 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

  13. Criteria for JXDM Validation ProjectsTechnical 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.

  14. Validation Projects • Colorado • Washington • Pennsylvania J-Net • Criminal Information Sharing Alliance(CISANet – CA, NM, AZ, TX, ID, GA) • Minnesota CriMNet (MN, IA, IL, MI, ND, WI) potentially 15 states represented (over ¼ of the U.S.)

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

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

  17. Reference Document SchemasThe Short List ~15 REFERENCE SCHEMAJUSTIFICATION Arrest/Incident Report OASIS, LASD, NIBRS, MD Common Alerting Protocol (CAP) LASD, CAP Inmate Record CriMNet Criminal History (Rap Sheet) IL, WI, WA, MD Arrest Warrant OASIS, WI Charging Document OASIS, LASD, WA Citation LASD, WA Court Disposition / Disposition Rpt OASIS, WA Court Filing / Document v1.1 OASIS (large spec) Court Order has multiple types Driver History AAMVA, PA JNet Filed Motion has multiple types Incident Status Summary (ICS-209) DHS, NIMS Probation Report LASD Protection Order OASIS Sentence Order OASIS, WA

  18. Reference Document SchemasThe 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)

  19. Data Requirements, Business Processes, Models, … LM = Lifecycle Mgt QM = Query Mgt ebXMLcompliant Map Other J/PS artifacts JusticeRegistryServer Justice Data Dictionary Model and Repository LM QM Justice XML Repository EPARegistryServer QM Registry ClientCOTS Application Registry Client Web Server DoDRegistryServer QM Browsers ebXMLcompliant Justice XML Data Dictionary Registry/Repository Model

  20. Justice Reference Model Justice Process Model • Business • Architecture • Business Reference Model JusticeService Model • Applications Architecture • Conceptual/Process Model • Interoperability Model Data Architecture • Technology Architecture • Technical Models • Technical Reference Model • Standards Justice XML Data Model + Dictionary v3 XML, RDF, XMI / UML, SOAPebXML, UDDI, WSDl, WSCL, WSFL, JAVA, J2EE, .Net Federal Enterprise Architecture (FEA) (Architectures and Models)

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

More Related