These are the major sections of this website. Expand each sub-section to see the pages within.


NIEM training information, tailored to specific user roles.

Domain Modeler (1)

A domain modeler creates and manages the content in a NIEM domain.

IEPD Developer (12)

An Information Exchange Package Documentation (IEPD) Developer designs, builds, and validates the components (artifacts) of an Information Exchange Package (IEP).

IEPD Implementer (3)

An IEPD implementer exchanges information based on the format, rules, and guidance provided by an existing IEPD specification.


Learn more about NIEM, including the model, IEPDs, tools, and specifications.

Artifacts (4)

Learn about the kinds of files that make up NIEM releases and IEPDs.

  • Code Lists

    NIEM Code Lists are special files that support the use of enhanced code lists in NIEM, beyond the basic capabilities provided by XML and JSON schema enumerations.

  • JSON-LD Context

    A JSON-LD context file is a file that can be used to associate namespace prefixes with the full URIs that they represent.

  • XML Catalog

    An XML catalog is a XML document that assigns locations to files. This can be used to override the file locations assigned by NIEM XML schema import statements without having to modify the original schema itself.

Concepts for data modeling (24)

Learn about properties, types, augmentations, and other building blocks used to construct the model.

Content (1)

A high-level perspective on the kinds of content that appear in Core and the domains.

IEPDs (19)

An Information Exchange Package Documentation (IEPD) is a collection of NIEM artifacts. They define and describe the context, content, semantics, and structure of one or more implementable information exchanges.

  • IEPD Lifecycle

    An Information Exchange Package Documentation (IEPD) developer designs, builds, and validates the components (artifacts) of an Information Exchange Package(IEP). The process consists of a six-phase lifecycle.

    • Scenario Planning

      Review background information related to your information exchange, assess resource impact, understand business context, and identify information exchange business scenarios.

    • Analyze Requirements

      Further elaborate on the information exchange scenario to understand and document the data requirements and business rules.

    • Map and Model

      Review the data requirements captured during the previous phase and discover if there are similar components in NIEM. Document results in a mapping spreadsheet. Begin modeling the data requirements without a match in NIEM; these will be later added to the IEPD as extensions.

    • Build and Validate

      Create subset schemas, and extension schemas, and sample instances based on the previous mapping and modeling work. Verify that schemas and instances are valid and that they meet NIEM conformance requirements described by the NIEM Naming and Design Rules (NDR) specification.

    • Assemble and Document

      Create any additional documentation needed for the IEPD, fill out the IEPD catalog, assemble all of the artifacts, and bundle the files into the final IEPD zip file package.

    • Publish and Implement

      Publish the IEPD for search, discovery, and reuse, and implement the IEPD for production.

  • IEPD Artifacts

    Each IEPD is a package that contains schemas and other supporting files.

    • Subset Schemas

      A subset schema is a customized version of a NIEM schema that contains only the properties, types, and codes that are needed for a particular information exchange, plus any of their required dependencies.

    • Extension Schema

      In an extension schema, an IEPD developer can create new NIEM-conformant properties and types to represent message data requirements that are not available in a NIEM release. Extensions schemas are used in combination with NIEM subset schemas to define the structure and meaning of a message.

    • IEPD Catalog

      An IEPD Catalog is an XML document that contains basic information about the package (name, description, purpose, etc.) and a listing of the package's key artifacts. It is a required artifact in an IEPD.

    • Conformance Report

      A conformance report specifies how and to what degree the IEPD is NIEM-conformant.

    • Mapping Spreadsheet

      A mapping spreadsheet can be used to explicitly document mappings from data requirements to properties and types in NIEM. It can also be used to model extensions for requirements that do not exist in NIEM.

  • IEPD Starter Kit

    Learn about NIEM IEPD conformance, view sample IEPDs, and more.

  • IEPD Version Control

    Best practices for NIEM IEPD change control and version management.

Releases (5)

A NIEM release is a coherent set of schemas and supporting artifacts representing a specific version of the NIEM data model, published by the NIEM Management Office. Release schemas contain reusable properties and types meant for use in information exchanges. These schemas include NIEM Core, domains, and code tables.

  • Core Supplement

    A Core Supplement is an incremental NIEM release that contains new or updated components for the NIEM Core namespace. These changes are published in separate schemas that can be used in addition to the original Core namespace. Core Supplements are used as a way of 'adjusting' Core content while it is locked between major releases.

  • Domain Update

    A domain update is one or more schemas that constitute changes to a NIEM domain outside of the standard NIEM release cycle.

  • Release Artifacts

    Each NIEM release comes bundled as a zip file containing schemas and other supporting files.

  • Release Version Control

    Information about NIEM release change control and version management.

Specifications (13)

NIEM specifications provide rules and guidance in order to design consistent and well-defined information exchanges. Specifications are managed by the NIEM Technical Architecture Committee (NTAC).

  • /reference/specifications/rule-browser/

  • NIEM Naming and Design Rules (NDR) Specification

    The NIEM Naming and Design Rules (NDR) describe the architecture of the NIEM data model and its representation in XML. It specifies principles and enforceable rules for NIEM data components and schemas.

    • Naming and Design Rules Change History

      The NIEM Naming and Design Rules Specification is updated with major NIEM releases, occurring every three years. The following highlights the changes that have been made.

    • Reference vs. Extension Schema

      The NIEM Naming and Design Rules defines two classes of conformant XML Schema documents: reference schema documents (REF) and extension schema documents (EXT). View the key rule differences between the two conformance targets.

  • NIEM Information Exchange Package Documentation (IEPD) Specification

    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 IEPD catalogs; and recommends how the package should be structured.

    • IEPD Specification Change History

      The NIEM Information Exchange Package Documentation (IEPD) Specification can be updated with major NIEM releases, occurring every three years. The following highlights the changes that have been made.

  • NIEM JSON Specification

    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 message specifications.

  • NIEM Conformance Specification

    The Conformance Specification specifies general conformance guidance, principles, and rules for NIEM.

  • NIEM Conformance Targets Attribute Specification

    The Conformance Targets Attribute Specification (CTAS) defines how NIEM XML documents classify what kind of artifact they are through the use of a conformance targets attribute.

  • NIEM Code Lists Specification

    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.

  • NIEM High-Level Version Architecture (HLVA) Specification

    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.

Tools (13)

NIEM tools provide support for searching and exploring NIEM content and developing NIEM domains and exchanges.

  • Schema Subset Generation Tool (SSGT)

    The Schema Subset Generation Tool (SSGT) enables users to search and view the content of the NIEM model, and build XML Schema subsets for use in exchanges.

  • Conformance Testing Assistant (ConTesA)

    The Conformance Testing Assistant (ConTesA) enables users to test NIEM XML schemas against the automated rules from the NIEM Naming and Design Rules (NDR).

  • Movement

    Movement provides a user-friendly interface and smarter search results for the latest NIEM release. Movement is also open source so the community who inspired its creation can contribute to it.

  • Migration Tool

    The Migration Tool enables you to upgrade a NIEM XML Schema subset generated by the SSGT to the next release.

  • NIEM resources for the Oxygen XML Editor

    The Oxygen XML Editor is a commercial multi-platform XML editor. NIEM provides some additional information and resources for this tool that may assist with domain and IEPD schema development and conformance testing.

    • Check NDR Conformance Using Schematron Validation

      Use Oxygen to test a XML schema for NDR conformance.

    • NIEM Snippets

      NIEM XML follows a regular, well-defined syntax. Snippets can be used to quickly and consistently fill in standard syntax, leaving users to fill in the blank or partially-filled in values for fields like name and definition.

    • Using XML Catalogs with Oxygen

      Use XML catalog files in Oxygen to specify or override schema file locations.

  • NIEM resources for XMLSpy

    XMLSpy is a proprietary XML editor and integrated development environment developed by Altova. NIEM provides some additional information for this tool that may assist with domain and IEPD schema development and testing.

NIEM Domain Modeling Guide (1)

How to design a Community of Interest


An easy introduction to the purpose of NIEM, the reasons to use NIEM with JSON data, and the developer knowledge needed to put NIEM JSON into practice.

A NIEM-JSON tutorial (1)

This tutorial walks the reader through a small example of implementing an information exchange using NIEM-JSON. It begins with a small set of data requirements, constructs a NIEM information exchange model, expresses data for that model as JSON, then constructs a JSON schema for that data.

NIEM and JSON Frequently Asked Questions (5)

Explains what NIEM and JSON each are and do and why they are useful together.

A NIEM-JSON Reference Guide (20)

Provides normative and non-normative guidance on how NIEM and JSON are used, including lots of examples.

Community Activities

NIEM community activities

Biometrics Domain (9)

A dedicated group that supports information sharing and promotes interoperability between mission-based organizations engaged in activities such as homeland security, national defense, border management, immigration benefits, and global law enforcement through the joint development and alignment of Extensible Markup Language (XML) Biometric Standards.

Cyber Domain (1)
A common understanding of grant data (1)

There are approximately 24 federal agencies that manage grants ranging from health to disasters to education and many other issue areas. A team within the NIEM community is working to identify the common terms, standardize them, and harmonize/unify the grants management systems.

Health Care and NIEM (14)

The NIEM Health Community's primary objective is to identify ways to use existing health IT standards to meet the needs of the NIEM community, all while providing education and awareness about the specific requirements for protecting sensitive health data.

Military Operations Domain (10)

The MilOps Domain provides a catalogue of data components necessary to support improved data interoperability between DOD and mission partners for operations.

State, Local, Tribal, and Territorial Tiger Team (18)

A dedicated group to advance information sharing at the state, local, tribal, and territorial level to help protect, support, and respond to community needs.

Geospatial Integration

There is a growing need for information exchanges to include geospatial elements and capabilities—NIEM provides this functionality.

Geo4NIEM Part 1 (2013) (1)

Geo4NIEM Part 1 (2013) was a collaborative, hands-on rapid prototype development and testing initiative in accordance with the Open Geospatial Consortium (OGC)'s Interoperability Program. The partnership included NGA, Department of Defense (DoD), Defense Information Systems Agency (DISA), U.S. Geological Survey (USGS), the Army Geospatial Center and numerous participants and supporters from the public and private sector.

Geo4NIEM Part 2 (2015) (1)

Geo4NIEM Part 2 (2015) was one of four threads in OGC’s Testbed 11—a scenario-based test and demonstration of Geo4NIEM work. It focused on enhancing NIEM’s geospatial exchange capabilities to include Intelligence Community (IC) data encoding specifications, along with OASIS standards to enable granular data object level access authorization and/or denial aligned to OCG web services.

NIEM Releases

Information and resources for each NIEM release.

NIEM 6.0 Version (Draft) (1)

An overview of the draft NIEM 6.0 version, currently under development.

NIEM 5.2 Release (Current) (1)

An overview of the draft NIEM 5.2 release.

NIEM 5.1 Release (1)

An overview of the NIEM 5.1 release.

NIEM 5.0 Release (1)

An overview of the NIEM 5.0 release.

NIEM 4.2 Release (1)

An overview of the NIEM 4.2 release.

NIEM 4.1 Release (1)

An overview of the NIEM 4.1 release.

NIEM 4.0 Release (1)

An overview of the NIEM 4.0 release.

NIEM 3.2 Release (1)

An overview of the NIEM 3.2 release.

NIEM 3.1 Release (1)

An overview of the NIEM 3.1 release.

NIEM 3.0 Release (1)

An overview of the NIEM 3.0 release.

NIEM 2.1 Release (1)

An overview of the NIEM 2.1 release.

NIEM 2.0 Release (1)

An overview of the NIEM 2.0 release.

NIEM 1.0 Release (1)

An overview of the NIEM 1.0 release.

Domain Timeline (1)

The following is a timeline that shows when new domains were added to NIEM or underwent significant changes.

Release Statistics (1)

Summary and detailed counts of properties, types, and codes across NIEM releases.

Page index

Active pages

This site has 206 active pages. Expand to view the list.


This site has 82 redirect pages. Expand to view the list.