GJXDM/NIEM Presentation - PowerPoint PPT Presentation

GJXDM/NIEM Presentation

Global has and continues to participate on NIEM governance, ConOps, architecture, and outreach materials.

Global members have heard the concerns re: future relationship between GJXDM and NIEM – such as, “what do I invest in?”

XSTF heretofore has not managed the justice namespace, but will assume this responsibility with 4.0.

XSTF will manage the justice namespace

renamed in NIEM as jxdm

XSTF will have governance responsibility (within current Global structure)

XSTF is represented on the NIEM governing body (NIEM Business Architecture Committee, or “NBAC”) for “Common” and “Universal.”

Governance of “Common” and “Universal” is now NBAC’s responsilbility.

Development cycle of 3.1

Time (calendar)

Resources

Convergence of GJXDM and NIEM is at GJXDM 4.0/NIEM 1.1 (slated for Q2 ‘07).

• 3.0.3
• Implements only generic relationships
• Roles are not supported
• All metadata inherits from Supertype
• Proxy schemas are used to implement code types
• 3.1
• Implements associations and roles with metadata
• Implements flexible metadata containers
• PropertyType and ActivityType completely refactored
• No proxy schemas are used for code lists

• 3.0.3
• Contains many deprecations accumulated from 3.0.x series
• 3.1
• Removed deprecations accumulated in 3.0.x series
• Incorporates many new association and role types
• Motor vehicle crash data
• New security components for TWPDES and Intelligence community
• Updated NCIC tables
• Many other component changes applied per feedback through Bugzilla

NIEM 1.0:

• Partitioned into multiple NIEM domains (including Justice)
• Includes Universal, Common, and Structures namespaces (Core)
• Refactors data components across all namespaces
• Implements type augmentation
• Implements more flexible code lists
• uses abstract code elements and substitution groups
• does not use dot notation
• Implements a URI for each component
• Refactors some specialization occurrences into augmentation, associations, roles, and metadata
• Uses original GJXDM 3.0.3 PropertyType and ActivityType(GJXDM 3.1 implements substantive structural and content changes to PropertyType and ActivityType)

NIEM 1.0 adds (in addition to Justice):

• Immigration and Customs Enforcement
• Customs and Border Protection / International Trade
• Intelligence
• Emergency Management
• Infrastructure Protection
• Person Screening
• External standards (Geospatial, EDXL)

NIEM 1.0:

• Partitioned into multiple NIEM domains (including Justice)
• Includes Universal, Common, and Structures namespaces (Core)
• Refactors data components across all namespaces
• Implements
• Associations
• Roles
• Metadata
• Implements a URI for each component
• Based on GJXDM 3.0.3 PropertyType and ActivityType
• Implements a URI for each component
• Refactors some specialization occurrences into augmentation, associations, roles, and metadata
• Uses original GJXDM 3.0.3 PropertyType and ActivityType

• Type augmentation
• Abstract code elements

NIEM 1.0 adds (in addition to Justice):

• Immigration and Customs Enforcement
• Customs and Border Protection / International Trade
• Intelligence
• Emergency Management
• Infrastructure Protection
• Person Screening
• External standards (Geospatial, EDXL)

4.0/1.1 will converge GJXDM 3.0.3, GJXDM 3.1 features, and NIEM 1.0 into one release with built-in migration support to subsequent NIEM releases.

GJXDM 4.0/NIEM 1.1 summary: Multi-domain, refactored PropertyType and ActivityType; associations, roles, metadata, type augmentation, flexible code lists, URI for each component, database export, and three integrated support tools

NIEM Naming and Design Rules (NDR) compliance

Version independence

Lessons learned from NIEM 1.0 implementations

Commitment from NIEM PMO to support local and state pilots

XSTF will continue to have governance oversight within the justice domain

XSTF and Global are participating in the NIEM governance structure

Convergence/Interlocking will occur with simultaneous 4.0/1.1 releases

“Interlocking” means:

NDRs and toolsets are consistent

IEPDs will be developed using both

The two data models are complementary and efficient (data is not duplicated) and allow seamless interoperability via toolsets