22

Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

Embed Size (px)

Citation preview

Page 1: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case
Page 2: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

Justice XML Data ModelJustice XML Data Model

Paul Embley

22 July 2003

Page 3: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

DDS2.1

DDS2.1

.xsd2.1

.xsd2.1

.xml2.1

.xml2.1

2.1Apps2.1

Apps

.xsl2.0-2.1

UpperCamelCase

Justice XML Data Dictionary Schema EvolutionJustice XML Data Dictionary Schema Evolution

DD.rdfs4.0

DD.rdfs4.0

.rdfs4.0

.rdfs4.0

.rdf4.0.rdf4.0

4.0Apps4.0

Apps

JDD4.0

JDD4.0

RDFDDS3.0

DDS3.0

.xsd3.0

.xsd3.0

.xml3.0

.xml3.0

3.0Apps3.0

Apps

JDD3.0

JDD3.0

ObjectOriented

+ RDFBlock

? .xsl2.1-3.0

DDS2.0

DDS2.0

.xsd2.0

.xsd2.0

.xml2.0

.xml2.0

2.0Apps2.0

Apps

Normative DD Schema

Standard Data DictionaryRDD1.0

RDD1.0

Std DocSchemas

DocumentInstances

Applications

RISS1.0.xsdRISS1.0.xsd

1.0Apps1.0

Apps

CF1.1.xsdCF1.1.xsdRap2.2

.xsdRap2.2.xsd

RISS.xmlRISS.xmlCF.xmlCF.xmlRap

.xmlRap.xml

Reconcile: RISS, Rap,

CF, AAMVA

? .xsl3.0-4.0

Page 4: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

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

Page 5: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

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)

Page 6: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

What Sources of Requirements Are Being Used?What Sources of Requirements Are Being Used?

SPONSOR SOURCE DOCUMENTS / SPECIFICATIONS

Global 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 schema

NIJ InfoTech v2.0 Data Dictionary and schemaLA County CA Incident Report schema

SEARCH Justice Info Exchange Model (JIEM) data setsLegalXML Arrest Warrant schemaLegalXML Charging Document schemaLegalXML Sentencing Order schemaMinnesota CriMNet v1.0 Data Dictionary and schema

NCSC 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

Page 7: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

JXDD v3.0.0.0PreRelease

Content

JXDD v3.0.0.0PreRelease

Content

Objects Components %Activity 1092 46.2Person 478 20.2Property 308 13.0Location 162 6.9Document 107 4.5Miscellaneous 99 4.2Organization 86 3.6ContactInformation 34 1.4TOTALS 2366 100.0

Objects Components %Activity 1092 46.2Person 478 20.2Property 308 13.0Location 162 6.9Document 107 4.5Miscellaneous 99 4.2Organization 86 3.6ContactInformation 34 1.4TOTALS 2366 100.0

Miscellaneousgeneral properties and support types

Miscellaneousgeneral properties and support types

Page 8: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

JXDM Pre-Release v3 for public review

JXDM IOC v3 Decision

2003

IOC Release... ...

JXDM v3.0 ScheduleJXDM v3.0 Schedule

IOC = Initial Operational Capability

Reference document schemas

Maintenance releases

Build Pre-Release

Refinement and maintenance

XSTF face-facePublic review, vet, and refine

Page 9: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

Organization Agency Type Job / ResponsibilityEOUSA FederaleGovernment Federal Expert ConsultanteGovernment Federal Expert ConsultantIIR Federal Research AssociateCrimTrac Federal Solution Sfw ArchitectCriMNet State Technology ConsultantCriMNet State Training for XML StdsCA DOJ State DP Manager(unknown) State MaintenanceHennepin Co Atty's Ofc County IT SupervisorSDDPC / ARJIS Local Principal AnalystBearingPoint / IWG Implementer Mgr/Chair, XML

SubcmteNorthrop Grumman Implementer IT Project ManagerVisionAir Vendor Senior Product ManagerVisionAir Vendor(unknown) Vendor

Organization Agency Type Job / ResponsibilityEOUSA FederaleGovernment Federal Expert ConsultanteGovernment Federal Expert ConsultantIIR Federal Research AssociateCrimTrac Federal Solution Sfw ArchitectCriMNet State Technology ConsultantCriMNet State Training for XML StdsCA DOJ State DP Manager(unknown) State MaintenanceHennepin Co Atty's Ofc County IT SupervisorSDDPC / ARJIS Local Principal AnalystBearingPoint / IWG Implementer Mgr/Chair, XML

SubcmteNorthrop Grumman Implementer IT Project ManagerVisionAir Vendor Senior Product ManagerVisionAir Vendor(unknown) Vendor

FeedbackRegistrations

FeedbackRegistrations

Page 10: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

Org POC Project

EPA Louis Sweeny (Ross & Assoc) Environ Exchange NetworkFBI Doug Ward terrorist watchlists (Person)FBI Greg Swanson NIBRS, incident reporting INS

Tim Anderson tracking aliens (Person)OMB Ralph Hodgson (TopQuadrant) FEA, RDF+XML togetherGSA Marion Royale Govt namespace registrationNIST Roy Morgan NIST RegistyLaw Intercept TC Tony Rutkowski (Verisign) OASIS LegalXMLBlue Oxide Kevin Williams (CTO) registry softwareYellow Dragon Matthew McKenzie (President) registry softwareXRI Marc LeMaitre productMetaMatrix productBooze-Allen-Hamilton partnerVisionAir partner

Org POC Project

EPA Louis Sweeny (Ross & Assoc) Environ Exchange NetworkFBI Doug Ward terrorist watchlists (Person)FBI Greg Swanson NIBRS, incident reporting INS

Tim Anderson tracking aliens (Person)OMB Ralph Hodgson (TopQuadrant) FEA, RDF+XML togetherGSA Marion Royale Govt namespace registrationNIST Roy Morgan NIST RegistyLaw Intercept TC Tony Rutkowski (Verisign) OASIS LegalXMLBlue Oxide Kevin Williams (CTO) registry softwareYellow Dragon Matthew McKenzie (President) registry softwareXRI Marc LeMaitre productMetaMatrix productBooze-Allen-Hamilton partnerVisionAir partner

Other Interest in JXDMOther Interest in JXDM

Page 11: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

FeedbackSummary of Comments

FeedbackSummary of Comments

Questions aboutcomponent misspellings or malformed namesmeaning and use of terms, names, definitions

(e.g., sex vs. gender)binary objects, images, etc.enumerations, code tables, code values, and relatedreference schemas for standard documents/transactions methods of usage

Suggestions to clarify or expand definitionsmodify components add components (for common requirements)compress (or normalize) the number of componentsmodify subtyping structure (the class model)add metadata to particular components

Requests formodifications to documentation formatadditional documentationtraining materials

Page 12: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

FeedbackWhat we are doing

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 generatorStandalone API + Java LibJXDM Registry/Repository Schema builderReference document schemasUser/implementor guide

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 generatorStandalone API + Java LibJXDM Registry/Repository Schema builderReference document schemasUser/implementor guide

Page 13: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

Criteria for JXDM Validation ProjectsTechnical Considerations

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.

Page 14: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

Validation ProjectsValidation 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)

potentially15 states represented

(over ¼ of the U.S.)

potentially15 states represented

(over ¼ of the U.S.)

Page 15: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

Validation ProjectsInterview Summaries

Validation ProjectsInterview 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

Page 16: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

REFERENCE SCHEMA JUSTIFICATIONArrest/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, WACourt 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

REFERENCE SCHEMA JUSTIFICATIONArrest/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, WACourt 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

Reference Document SchemasThe Short List ~15

Reference Document SchemasThe Short List ~15

Page 17: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

Common Alerting ProtocolIncident Status Sum (ICS209)Court Filing and Document (v1.1)

Common Alerting ProtocolIncident Status Sum (ICS209)Court Filing and Document (v1.1)

Reference Document SchemasThe Long List ~100+

Reference Document SchemasThe Long List ~100+

• The Ultimate List may be ~150.• Likely many more local schemas.

• The Ultimate List may be ~150.• Likely many more local schemas.

+

Page 18: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

Justice XML Data Dictionary Registry/Repository ModelJustice XML Data Dictionary Registry/Repository Model

JusticeRegistryServer

JusticeRegistryServer

QMQM

LMLM

LM = Lifecycle MgtQM = Query MgtLM = Lifecycle MgtQM = Query Mgt

ebXMLcompliant

ebXMLcompliant

EPARegistryServer

QMQM

DoDRegistryServer

QMQMebXML

compliantebXML

compliant

Registry Client

COTS Application

Registry Client

COTS Application

Registry Client

Web Server

Registry Client

Web 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,

Page 19: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

Justice Reference ModelJustice Reference Model

Applications Architecture• Conceptual/Process Model• Interoperability Model

Data Architecture

Federal Enterprise Architecture (FEA)(Architectures and Models)

Justice Process

Model

Justice Process

Model

Justice XML Data Model + Dictionary v3Justice XML Data Model + Dictionary v3

JusticeService Model

JusticeService Model

XML, RDF, XMI / UML, SOAPebXML, UDDI, WSDl, WSCL,

WSFL, JAVA, J2EE, .Net

XML, RDF, XMI / UML, SOAPebXML, UDDI, WSDl, WSCL,

WSFL, JAVA, J2EE, .Net

December 2002Ctrl

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 2002Ctrl

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

Sequence of Events in the Criminal Justice SystemSequence of Events in the Criminal Justice SystemSequence of Events in the Criminal Justice SystemSequence of Events in the Criminal Justice System Criminal Justice System ModelCriminal Justice System ModelCriminal Justice System ModelCriminal Justice System Model

December 2002Ctrl

Local_Instance.xmlLocal_Instance.xmlStandard_Instance.xmlStandard_Instance.xml

xmlns:xsi

W3C XMLInstance

W3C XMLInstance

namespace references

Schema Reference ArchitectureSchema Reference Architecture

W3C XMLSchema

W3C XMLSchema Support

TypesSupportTypes

Element and Relationship Names

Element and Relationship Names

EntityTypesEntityTypes

xmlns:Justice

xmlns:Local

Standard Tag NamesStandard

Tag NamesData Typesthat do not fit into the class hierarchy

Data Typesthat do not fit into the class hierarchy

Primary Data Model -- Class Hierarchy

Primary Data Model -- Class Hierarchy

import+ ns ref

ns ref

Reference Documentse.g. Arrest Warrant

Reference Documentse.g. Arrest Warrant

LocalExtension

LocalExtension

import+ ns ref

import+ ns ref

xmlns:xsd

December 2002Ctrl

Local_Instance.xmlLocal_Instance.xmlStandard_Instance.xmlStandard_Instance.xml

xmlns:xsi

W3C XMLInstance

W3C XMLInstance

namespace references

Schema Reference ArchitectureSchema Reference Architecture

W3C XMLSchema

W3C XMLSchema Support

TypesSupportTypes

Element and Relationship Names

Element and Relationship Names

EntityTypesEntityTypes

xmlns:Justice

xmlns:Local

Standard Tag NamesStandard

Tag NamesData Typesthat do not fit into the class hierarchy

Data Typesthat do not fit into the class hierarchy

Primary Data Model -- Class Hierarchy

Primary Data Model -- Class Hierarchy

import+ ns ref

ns ref

Reference Documentse.g. Arrest Warrant

Reference Documentse.g. Arrest Warrant

LocalExtension

LocalExtension

import+ ns ref

import+ ns ref

xmlns:xsd

December 2002Ctrl

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 Client

COTS Application

Registry Client

COTS Application

Registry Client

Web Server

Registry Client

Web 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 2002Ctrl

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 Client

COTS Application

Registry Client

COTS Application

Registry Client

Web Server

Registry Client

Web 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, …

Technology Architecture• Technical Models• Technical Reference Model• Standards

BusinessArchitecture• Business

Reference Model

Page 20: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

What Else / What Next?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

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

Page 21: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case

July 2003

http://www.it.ojp.gov/

Paul Embley [email protected] 502.545.0127

Current ConditionsCurrent Conditions

Page 22: Justice XML Data Model Paul Embley 22 July 2003 July 2003 DDS 2.1 DDS 2.1.xsd 2.1.xsd 2.1.xml 2.1.xml 2.1 Apps 2.1 Apps.xsl 2.0-2.1 Upper Camel Case