gjxdm niem presentation n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
GJXDM/NIEM Presentation PowerPoint Presentation
Download Presentation
GJXDM/NIEM Presentation

Loading in 2 Seconds...

play fullscreen
1 / 16

GJXDM/NIEM Presentation - PowerPoint PPT Presentation


  • 229 Views
  • Uploaded on

GJXDM/NIEM Presentation. Background: GJXDM and NIEM. Global has been and continues to focus on development of NIEM in parallel to GJXDM Global has and continues to participate on NIEM governance, ConOps, architecture, and outreach materials

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'GJXDM/NIEM Presentation' - violet


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
background gjxdm and niem
Background: GJXDM and NIEM
  • Global has been and continues to focus on development of NIEM in parallel to GJXDM
  • Global has and continues to participate on NIEM governance, ConOps, architecture, and outreach materials
  • Global members have heard the concerns regarding future relationship between GJXDM and NIEM—such as, “what do I invest in?”
  • GXSTF heretofore has not managed the justice namespace but will assume this responsibility with 4.0
gjxdm niem governance
GJXDM/NIEM Governance
  • GJXDM will continue in relevancy, existence
  • GXSTF will manage the justice namespace
    • Renamed in NIEM as jxdm
    • GXSTF will have governance responsibility (within current Global structure)
  • GXSTF is represented on the NIEM governing body (NIEM Business Architecture Committee (NBAC)) for “Common” and “Universal”
  • Governance of “Common” and “Universal” is now NBAC’s responsilbility
gjxdm 3 1 0 why not
GJXDM 3.1.0: Why not?
  • Differences between GJXDM 3.1.0 and NIEM 1.0
  • Development cycle of 3.1
    • Time (calendar)
    • Resources
  • Convergence of GJXDM and NIEM is at GJXDM 4.0/NIEM 1.1 (slated for Q2 2007)
making decisions 3 03 and niem 1 0 and 4 0 1 1
Making Decisions:3.03 and NIEM 1.0 and 4.0/1.1
  • This will not affect current IEPDs ever
gjxdm 3 0 3 vs gjxdm 3 1 structure
GJXDM 3.0.3 vs GJXDM 3.1 Structure
  • 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
gjxdm 3 0 3 vs gjxdm 3 1 content
GJXDM 3.0.3 vs GJXDM 3.1 Content
  • 3.0.3
    • Contains many deprecations accumulated from 3.0.x series
  • 3.1
    • Removes deprecations accumulated in 3.0.x series
    • Incorporates many new association and role types
    • Includes motor vehicle crash data
    • Includes new security components for TWPDES and Intelligence community
    • Updates NCIC tables
    • Includes many other component changes applied per feedback through Bugzilla
gjxdm 3 1 vs niem 1 0 structure
GJXDM 3.1 vs NIEM 1.0 Structure
  • 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)
gjxdm 3 1 vs niem 1 0 content
GJXDM 3.1 vs NIEM 1.0 Content
  • 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)
gjxdm 3 0 3 vs niem 1 0 structure
GJXDM 3.0.3 vs NIEM 1.0 Structure
  • 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
gjxdm 3 0 3 vs niem 1 0 content
GJXDM 3.0.3 vs NIEM 1.0 Content
  • 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)
gjxdm 4 0 niem 1 1 q2 2007
GJXDM 4.0/NIEM 1.1 (Q2 2007)
  • 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—multidomain, refactored PropertyType and ActivityType; associations, roles, metadata, type augmentation, flexible code lists, URI for each component, database export, and three integrated support tools
requirements for 4 0 1 1 release
Requirements for 4.0/1.1 Release
  • 3.1 functionality
  • 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
wrap up
Wrap-Up
  • GJXDM is alive and well—investments, to date, will be preserved
  • GXSTF will continue to have governance oversight within the justice domain
  • GXSTF 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