justice xml data dictionary jxdd version 3
TRANSCRIPT
Justice XML Data Dictionary JXDD Version 3.0
Justice XML Data Dictionary JXDD Version 3.0
Status of Design & DevelopmentStatus of Design & Development
17 December 2002
DAY
December 2002
“I love it when a plan comes together!”– COL Hannibal Smith, The A-Team
“I love it when a plan comes together!”– COL Hannibal Smith, The A-Team
ArrestWarrant.xsdArrestWarrant.xsd
IncidentReport.xsdIncidentReport.xsd
SentenceOrder.xsdSentenceOrder.xsd
ChargeDoc.xsdChargeDoc.xsd
RapSheet.xsdRapSheet.xsd
DriverHistory.xsdDriverHistory.xsd
RISSIntel.xsdRISSIntel.xsd
CourtFiling.dtdCourtFiling.dtd
Justice XMLData Dictionary,
Schema, andRegistry
Justice XMLData Dictionary,
Schema, andRegistry
DocumentSpec.xsdDocumentSpec.xsdDocumentSpec.xsdDocumentSpec.xsd
OtherDocSpecs.xsdOtherDocSpecs.xsdOtherDocSpecs.xsdOtherDocSpecs.xsd
SEARCH Justice InfoExchange Model (JIEM)SEARCH Justice Info
Exchange Model (JIEM)
ReconcilData
Dictionary(RDD)
XML Object RepositoryXML Object Repository
W3C XML SchemaW3C XML Schema
Support Data ComponentsSupport Data ComponentsSimple ComponentsSimple Components
Complex ComponentsComplex ComponentsDocument / TransactionsDocument / Transactions
Other DDs&
Data Sets
RequirementsMethodologyFormal Rules
Ref ArchitectureStandards
RequirementsMethodologyFormal Rules
Ref ArchitectureStandards
InfoTech
CriMNet
December 2002
Why JXDD Version 3.0?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
December 2002
What Sources of Requirements Are Being Used?What Sources of Requirements Are Being Used?
SPONSOR SOURCE DOCUMENTS / SPECIFICATIONSGlobal ISWG Reconciliation Data Dictionary (RDD) v1.0.0JTF for ICHTS Rap Sheet v2.2 schemaRISS RISSIntel v2.0 schemaLegalXML CourtFiling v1.1 DTDAAMVA Driver History v1.02 schemaNIJ InfoTech v2.0 Data Dictionary and schemaLA County CA Incident Report schemaSEARCH Justice Info Exchange Model (JIEM) data setsLegalXML Arrest Warrant schemaLegalXML Charging Document schemaLegalXML Sentencing Order schemaMinnesota CriMNet v1.0 Data Dictionary and schemaNCSC Data element spreadsheets (civil, criminal, juvenile)Maricopa Co AZ ICJIS Data Dictionary v1.3CISA Southwest Border States DD (TX, AZ, NM)FBI NCIC 2000 Data Dictionary and Code TablesNIBRS Incident Report schema
December 2002
What Standards Are Being Applied?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)
December 2002
Justice Data Dictionary ViewJustice Data Dictionary View
Activity ~60% (other objects ~30%)Activity ~60% (other objects ~30%)LocationLocation
ContactInfoContactInfo
PropertyProperty
???10%???10%
DocumentDocumentRelationshipsRelationships
ReferenceDocument.xsdReferenceDocument.xsd
ContentMetadataRegistry
Metadata
InfrastructureMetadata
PersonPersonOrganizationOrganization
IS-A
December 2002
Typical Activity ObjectsTypical Activity Objects
Doc.xsdDoc.xsd
IncidentRpt
IncidentRpt
BookingRpt
BookingRpt Charge
DocCharge
Doc
CaseFile
CaseFile
ArrestWarrantArrest
WarrantArrest
RptArrest
Rpt
ProtectOrder
ProtectOrder
SentenceOrder
SentenceOrder
ActivityActivity
PersPers
LocLocCntCnt
PropPropOrgOrg
??????DocDocRelateRelate
IncidentIncident
ActivityActivity
InvestigateInvestigate
ArrestArrest
BookBook ConfineConfine
ProsecuteProsecute
IndictIndict AdjudicateAdjudicate SentenceSentence
IncarcerateIncarcerate
BondBond
SuperviseSupervise
ReleaseRelease
ChargeCharge
PardonPardonParoleParole
FineFine
December 2002
Justice Data Dictionary v3.0 Database StatisticsJustice Data Dictionary v3.0 Database Statistics
Elements or Relationships
JDD v3.0 (December 2002)Complex types 104Properties (core) 688Properties (Activity) 854
JDD v3.0 (December 2002)Complex types 104Properties (core) 688Properties (Activity) 854 1542
Total components 1646Total components 1646
RDD v1.0.1 (October 2002)Complex properties 30Simple properties 250
RDD v1.0.1 (October 2002)Complex properties 30Simple properties 250
Total components 280Total components 280
According to one Government data consultant, all branches and departments of a typical State Government use about 20,000 unique data elements.
According to one Government data consultant, all branches and departments of a typical State Government use about 20,000 unique data elements.
Source Requirement References = 33Source Requirement Components = 15,951Source Requirement References = 33Source Requirement Components = 15,951
December 2002
Validation of JXDDS V3.0 RFCDecember 2002
Validation of JXDDS V3.0 RFCDecember 2002
Complete PersonOrganizationLocationContactInformation(personal)Property
and enough Activity objects to build …
Rap Sheet RDD / NLETS Sentence Order CourtFilingIncident Report InfoTechDriver History RDD / AAMVA
December 2002
What Work Remains To Be Done?What Work Remains To Be Done?
• Implement objects: Activity, property• Map source data requirements• Define data components (definitions)• Identify / install internal enumerations• Define / implement special constraints
(e.g. partial values, nulls, etc.)• Implement metadata (content, registry, infrastructure)• Implement or refine user tools for database• Document user interface, design, etc.• Implement interface to an ebXML registry • Designate namespaces (naming policy)• Define policies, procedures, CONOPS
December 2002
Where Are We Going and Why? How Does It All Fit Together?
The Big Picture – An XML Registry/Repository
Where Are We Going and Why? How Does It All Fit Together?
The Big Picture – An XML Registry/Repository
December 2002
Why a Justice XML Registry/Repository?Why a Justice XML Registry/Repository?
History shows that long term success of data exchange within and between communities of interest is facilitated by:
Discovery and re-use of standard vocabulariesDiscovery and re-use of componentsde facto standards due to voting “by feet”
How is this different from the Justice Standards Registry?
Different scope, objectives, functional requirements, specifications, management scheme, and operational guidelines
December 2002
Basic Overview of Using a Metadata RegistryBasic Overview of Using a Metadata Registry
Justice XMLMetadata Registry
DeveloperQueriesJustice
MetadataRegistry
2
Justice XMLComponentRepository
Results returned
based on thecomponents
stored in repositories
3
Domain BRepository
Domain ARepository
Developer needsXML tags, schema,
stylesheet, etc.
1
Developer eitheruses an existingcomponent, orbuilds a new
component andregisters it forothers to use
4
UDDIRegistry
December 2002
Justice XML Data Dictionary Registry/Repository ModelJustice XML Data Dictionary Registry/Repository Model
JusticeRegistryServer
QMQM
LMLM
LM = Lifecycle MgtQM = Query MgtLM = Lifecycle MgtQM = Query Mgt
ebXMLcompliant
ebXMLcompliant
EPARegistryServer
QMQM
DoDRegistryServer
QMQMebXML
compliantebXML
compliant
Registry ClientCOTS Application
Registry ClientCOTS Application
Registry ClientWeb Server
Registry ClientWeb Server
BrowsersBrowsers
Other J/PS artifactsOther J/PS artifacts
Justice Data DictionaryModel and Repository
Justice Data DictionaryModel and Repository
Justice XML Repository
Map
Data Requirements, Business Processes, Models, …
Data Requirements, Business Processes, Models, …
December 2002
XML Development Using the Registry
Standards Developer
Creates SchemaUsing Objects from Registry
DevelopsBusiness Process
Documents
Information Provider
Establishes Collaboration
Protocol Agreementwith User
Establishes Collaboration
Protocol Agreementwith Provider
XML Registry
CreatesCollaboration
Protocol Profile
Searches Registryfor Provider ofNeeded Info
Information User
December 2002
Potential Issues for I/SWG
Prioritize and evaluate registry features.Establish validation/approval processes
New componentsModifications of componentsCriteria for different approval schemes
Recommend operational oversight bodyProposing and maintaining a stablefunding process
Implementation, operation, maintenanceNamespace management recommendations