SEARCH Membership Group Systems & Technology PAC Global Justice XML Data Model (GJXDM) Update January 29, 2005

GJXDM Topics 1.Funding issues 2.Expanded areas of GJXDM/Integration collaboration 3.SEARCH efforts and projects to support practitioner implementation of the GJXDM

GJXDM/Funding Issues DOJ Special Conditions Language Requires conformance with the GJXDM DHS Special Conditions Language Mirrors the DOJ language Executive Order Establishes an Information Systems Council Focus on information sharing and interoperable systems

GJXDM Funding Issues What do we mean by Conformance? Conformance means the ability to share accurate and reliable information using the GJXDM such that the information has the same meaning for the sender as it does for the receiver

Import and reference GJXDM namespace or a correct subset If it exists, use the appropriate GJXDM component (i.e., do not create a duplicate of one that exists) Be semantically consistent Use GJXDM components in accordance with their definitions Do not use an element to represent data other than what its definition describes Apply XML Schema extension rules correctly and consistently Exchanges conform, NOT systems What you call data or how you use it in your own system does not impact conformance What counts is how you package data as XML for exchange There is no concept of partial conformance GJXDM Funding Issues

Expand GJXDM Collaboration Expanded areas of GJXDM/Integration collaboration: Emergency Management/First Responders DHS (Metadata Center of Excellence) ODP OMB Transportation Juvenile/OJJDP

January 7, 2005 Meeting Public Safety/First Responder & XML Initiatives Internal Revenue Service Department of Commerce, National Telecommunications and Information Administration ComCARE Office of Science and Technology, NIJ NLETS Department of Homeland Security Office of Domestic Preparedness Intelligent Transportation Systems Joint Program Office U.S. Department of Transportation ITS America Public Safety Advisory Group, National Emergency Number Association DHS/FEMA Disaster Management eGov Initiative Association of Public Safety Communications Officials National Association of State EMS Directors National EMS Information System National Highway Traffic Safety Administration CapWIN Intelligent Transportation Society of America Federal Highway Administration, U.S. Department of Transportation Emergency Interoperability Consortium

Expand GJXDM Collaboration Standardize metadata across DHS and Federal Government DHS Taxonomy (DHS/DRM) Data Interoperability Tiger Team of the Information Systems Council for EO Lead agency for “National” Data Reference Model (N-DRM) Working Group. Leading multiple projects to standardize information exchanges Developing a Community of Interest (COI) Strategy Document

SEARCH GJXDM Initiatives XML Structure Task Force (XSTF) GJXDM Training and Technical Assistance Committee (GTTAC) IJIS Institute XML Committee Technical Assistance and Training GJXDM User Guide Lead developer of Reference Exchange Documents

XSTF External Sources Bugzilla ListServ Practitioners Technical Practitioners Industry Academia GJXDM Development Process

Increased Collaboration Messaging Documentation Privacy Focus Group/Implementation Tools Reference Exchange Documents XSTF 2005 Focus

Reference Exchange Document Goals and Objectives Define reference exchange data packets to support interoperability among justice systems Expand and refine GJXDM/DD through experienced feedback; resolve vague definitions Constrain/restrict down to key choices to support interoperability

Reference Document Goals and Objectives Justice exchange data does not belong to only one domain Example: Protection Order is not just a court document LEA is an exchange partner FBI is an exchange partner Most important: a group of representative exchange partners working through the business and technical requirements of the exchange

Process to Build Reference Exchange Documents Assemble a team of domain + GJXDM model/schema structure expert (s)

Process to Build Reference Exchange Documents Review a variety of source examples Team builds “top down” data model Team maps objects/attributes to elements in GJXDM Team builds schema “package” and illustrative instance Team uses open source, non- proprietary tools

Process to Build Reference Exchange Documents Generate schemas based on mapping (subset, constraint, extension, document) Team reviews and packages the work product for wider review, if necessary Draft reference exchange document “package” is then vetted/validated substantively by authoritative sources Develop a governance strategy for determining when a reference document is the reference document

Courts Reference Exchange Documents SEARCH-OASIS-NCSC Workshop held June 2004 in Denver Traffic Citation Protection Order Sentencing Order Court Disposition NCSC is leveraging this work product and vetting among courts Document artifacts are posted on NCSC Bulletin Board

Law Enforcement Reference Exchange Documents SEARCH is leading this effort, with support from the Community Oriented Policing Services (COPS) office of the Department of Justice Incident Report/Incident Data/NDEx Field Investigation Report Arrest/Booking/Supplemental LEA Referral/Prosecution Charging Horizontal Analysis will be conducted following the completion of these four documents (March)

Reference Document Goals and Objectives Remember: the goal is to exchange messages, not to build databases To do this we must constrain the ways of doing things The more we standardize the container and the payload of components, the more it supports our goals

SEARCH Membership Group Systems & Technology PAC Global Justice XML Data Model (GJXDM) Update January 29, 2005