NIEM 5.1 will be a minor release and is currently under development. Publication is scheduled for Fall 2021.
Download the full draft release package as a zip file
View schemas and documentation on GitHub
Submit a new issue (see info for help) or email feedback to niem-comments@lists.gatech.edu
View a list of all 5.1 issues or track progress via the 5.1 project board
This schedule is subject to change.
| Draft | Date | Issues | Description |
|---|---|---|---|
| Alpha 1 | Mar 2021 | Major domain content submissions due. | |
| Alpha 2 | June 2021 | Additional updates to domain content. | |
| Beta 1 | July 2021 | Harmonize and refine alpha changes. Smaller content submissions, code table updates, and new requests may still be addressed during this time. | |
| Release Candidate (RC) 1 | Aug 2021 | QA and preparations for the release. Only bug fixes are considered during this stage; other requests will be queued for the following release. | |
| Release | Fall 2021 | Publish release and update tools (SSGT, Movement, Migration Tool) |
Additional phases (e.g., Beta 2) may be added as needed during the development process.
The following changes are expected to appear in NIEM 5.1:
Cyber domain (new) - add Federal Incident Reporting Requirements (FIRR) and Cybercrime Support Network (CSN) requirements
Biometrics domain - add new DNA content (#152)
Emergency Management domain - add flood damage claim content from OpenFEMA (#208)
Military Operations domain - add content from the Joint Non-Kinetic Effectiveness (JNKE) IEPD (cyber-related)
Statistics domain (new) - add content from the Census Bureau and merge the Generic Statistic Information Model (GSIM) auxiliary content added to 5.0
Update code sets
The following are the NIEM specifications that can be used with this release:
The NIEM Naming and Design Rules specifies the data model XML Schema components and XML data for use with the National Information Exchange Model (NIEM). Learn more...
The NIEM Information Exchange Package Documentation (IEPD) Specification specifies normative rules and non-normative guidance for building NIEM information exchange messages. It defines IEPD artifacts like subset schemas, extension schemas, and MPD catalogs; and recommends how the package should be structured. Learn more...
The NIEM JSON Specification establishes the technical basis for using JavaScript Object Notation (JSON) as a data format for exchange of information consistent with NIEM-conformant schemas and information exchange package documentations (IEPDs). Learn more...
The NIEM Conformance Specification introduces the idea of NIEM conformance and provides a general normative definition for its meaning, how it applies, and to what it does and does not apply. It describes the benefits of conformance, and refers to sources of information, tools, and help. Learn more...
The Code Lists Specification adds support for new capabilities of NIEM code lists beyond the basic enumeration representations provided by XML and JSON schema. Key features include the definition of codes in CSV or Genericode files, dynamic code lists via run-time binding, and multi-column code table support. Learn more...
The Conformance Targets Attribute Specification (CTAS) defines how NIEM XML documents indicate what kind of artifact they are through the use of a conformance targets attribute. Learn more...
The NIEM High-Level Version Architecture (HLVA) Specification identifies the processes, artifacts, and responsibilities required to produce new releases of the NIEM model. It also establishes a regular release cycle for predictable and manageable NIEM updates. Learn more...