1 / 22

Justice XML Data Model

Justice XML Structure Task Force. Justice XML Data Model. Paul Embley 22 July 2003. 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.

arty
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 22 July 2003

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

  3. Why 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

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

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

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

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

  8. FeedbackRegistrations OrganizationAgency TypeJob / Responsibility EOUSA Federal eGovernment Federal Expert Consultant eGovernment Federal Expert Consultant IIR Federal Research Associate CrimTrac Federal Solution Sfw Architect CriMNet State Technology Consultant CriMNet State Training for XML Stds CA DOJ State DP Manager (unknown) State Maintenance Hennepin Co Atty's Ofc County IT Supervisor SDDPC / ARJIS Local Principal Analyst BearingPoint / IWG Implementer Mgr/Chair, XML Subcmte Northrop Grumman Implementer IT Project Manager VisionAir Vendor Senior Product Manager VisionAir Vendor (unknown) Vendor

  9. Other Interest in JXDM OrgPOCProject EPA Louis Sweeny (Ross & Assoc) Environ Exchange Network FBI Doug Ward terrorist watchlists (Person) FBI Greg Swanson NIBRS, incident reporting INS Tim Anderson tracking aliens (Person) OMB Ralph Hodgson (TopQuadrant) FEA, RDF+XML together GSA Marion Royale Govt namespace registration NIST Roy Morgan NIST Registy Law Intercept TC Tony Rutkowski (Verisign) OASIS LegalXML Blue Oxide Kevin Williams (CTO) registry software Yellow Dragon Matthew McKenzie (President) registry software XRI Marc LeMaitre product MetaMatrix product Booze-Allen-Hamilton partner VisionAir partner

  10. FeedbackSummary of Comments Questions about component misspellings or malformed names meaning and use of terms, names, definitions (e.g., sex vs. gender) binary objects, images, etc. enumerations, code tables, code values, and related reference schemas for standard documents/transactions methods of usage Suggestions to clarify or expand definitions modify components add components (for common requirements) compress (or normalize) the number of components modify subtyping structure (the class model) add metadata to particular components Requests for modifications to documentation format additional documentation training materials

  11. FeedbackWhat we are doing We are listening ... JXDDS is so large and slow to validate. I only need to use a small part of JXDDS. I need to search / find components easily. A component I need is missing. How can I interact with JXDD? How do I extend ... ? How do I use secondary relationships? How can I focus / package my data? Is there more documentation / training? What we are doing ... Very fast Xerces XML instance validator tool online at justicexml.gtri or ojp.gov Partial schema generator Standalone API + Java Lib JXDM Registry/Repository Schema builder Reference document schemas User/implementor guide

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

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

  14. Validation Projects Interview Summaries • 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

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

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

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

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

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

  20. Current Conditions • http://www.it.ojp.gov/ • Paul Embley • pembley@mstar2.net • 502.545.0127

More Related