Office of Justice Programs Justice XML Data Model and Data Dictionary March 31, 2003 - PowerPoint PPT Presentation

1 / 18
About This Presentation
Title:

Office of Justice Programs Justice XML Data Model and Data Dictionary March 31, 2003

Description:

JXDD IOC v3. install. configure. integrate. integration tests. federated tests. Enhanced Registry ... facto standards due to voting 'by feet' March 2003. Basic ... – PowerPoint PPT presentation

Number of Views:78
Avg rating:3.0/5.0
Slides: 19
Provided by: mrk57
Category:

less

Transcript and Presenter's Notes

Title: Office of Justice Programs Justice XML Data Model and Data Dictionary March 31, 2003


1
Office of Justice ProgramsJustice XML Data
Model and Data DictionaryMarch 31, 2003
2
Justice XML Data Dictionary Evolution
Standard Data Dictionary
Normative DD Schema
Object Oriented RDF Block
Upper Camel Case
DDS 2.1
DDS 2.0
DD.rdfs 4.0
DDS 3.0
RDF
.xsd 2.1
.rdfs 4.0
.xsd 3.0
.xsd 2.0
.xml 2.1
.xml 3.0
.rdf 4.0
.xml 2.0
? .xsl 2.1-3.0
.xsl 2.0-2.1
? .xsl 3.0-4.0
2.1 Apps
4.0 Apps
3.0 Apps
2.0 Apps
3
The Initial Reconciliation Effort Expands and
Adds New Partners
Requirements Methodology Formal Rules Ref
Architecture Standards
DocumentSpec.xsd
Justice XML Data Dictionary, Schema, and Registry
DocumentSpec.xsd
OtherDocSpecs.xsd
OtherDocSpecs.xsd
CriMNet
SEARCH Justice InfoExchange Model (JIEM)
InfoTech
4
Why 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

5
What Sources of Requirements Are Being Used?
SPONSOR SOURCE DOCUMENTS / SPECIFICATIONS Global
ISWG Reconciliation Data Dictionary (RDD)
v1.0.0 JTF for ICHTS Rap Sheet v2.2
schema RISS RISSIntel v2.0 schema OASIS CourtFilin
g 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 OASIS Arrest
Warrant schema OASIS Charging Document
schema OASIS Sentencing Order schema Minnesota Cri
MNet 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
Standards Applied (Examples)
XML.GOV Draft Federal XML Schema Developers
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)
7
Justice XML Data Model
Activity 60 (other objects 30)
Person
Organization
Property
Location
??? 10
ContactInfo
Document
Relationships
IS-A
ReferenceDocument.xsd
8
Typical Activity Objects
Doc.xsd
9
Justice Data Dictionary v3.0 Database Statistics
10
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

11
XML Data Registry/Repository
2003
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Tasks
1. JXDD 3.0 XML
complete beta
JXDD Beta v3.0
vet / refine
JXDD IOC v3
...
...
id pilots, test, validate
JXDD FOC v3.1...n
...
...
2. JXDD 4.0 RDF
build 4.0 RDF
3. Justice Registry (JXR)
Operational Registry
install
configure integrate
integration tests
Enhanced Registry
user interface partial schema generation
federated tests
Federated Registry
12
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 vocabularies
  • Discovery and re-use of components
  • de facto standards due to voting by feet

13
Basic Overview of a Metadata Registry
Domain B Repository
Domain A Repository
Justice XML Metadata Registry
  • Justice XML
  • Component
  • Repository

UDDI Registry
14
Justice XML Data Registry/Repository Model
15
XML Development Using the Registry
XML Registry
Creates Schema Using Objects from Registry
Creates Collaboration Protocol Profile
Searches Registry for Provider of Needed Info
Develops Business Process Documents
Establishes Collaboration Protocol
Agreement with User
Establishes Collaboration Protocol
Agreement with Provider
Standards Developer
Information Provider
Information User
16
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)
17
Current Status
  • V3.0 Available for Review at GTRI Web Site
  • Preparing to Load Beta Version onto OJP Web Site
    for Examination and Feedback Cycle of at least 60
    Days
  • Identifying Pilot Projects for Testing v3.0 Beta
    Version
  • Anticipated Operational Capability Mid-2003
  • Examining Alternatives for XML Registry/Repository
    Capability
  • Exploring Funding Options for Operational XML
    Registry/Repository Capability

18
Office of Justice ProgramsBureau of Justice
AssistancePoints of ContactWeb Site
www.it.ojp.govJ. Patrick McCreary202-616-0532m
ccrearj_at_ojp.usdoj.govBob Greeves202-305-9317gr
eevesr_at_ojp.usdoj.gov
Write a Comment
User Comments (0)
About PowerShow.com