The NIEM Conformance Specification introduces 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.
The Conformance Specification is currently out of date, with references to NIEM 3.0 and NDR 3.0. The information is still valid, but the 4.0 version of the NDR should be used where appropriate.
The term conformance is often used very broadly, but it has a very specific meaning within NIEM. Artifacts, like schemas and IEPDs, can conform to a specific conformance target.
System, tools, or databases may have capabilities designed to specifically support the development of NIEM-conformant artifacts, but those systems art not, themselves, NIEM-conformant. Such tools or systems are considered NIEM-aware or NIEM-supporting.
NIEM-conformance does not imply NIEM compliance. Compliance indicates enforcement and the existence of an official certification process that verifies conformance or level of conformance. NIEM does not currently define compliance.
conformance target is a special class of artifact, defined by a NIEM specification, with an applicable set of normative rules.
In addition to describing what a conformance target is, NIEM specifications assign unique IDs (conformance target identifiers) and define normative rules for each.
The images below show information about conformance target
reference schema document (REF)from the NDR 4.0 specification.
- The first image shows the definition of the conformance target and its conformance target identifier.
- The second image shows two of the normative rules for the REF conformance target. Note that the first rule is free text and must be checked manually; the second rule is written in Schematron and can be validated using ConTesA.
A NIEM artifact will declare its applicable conformance targets by referencing the associated conformance target identifier(s).
Extension schema documentconformance target from the NDR 4.0 specification.
IEPDconformance target from the MPD 3.0.1 specification.
CSV Code List Documentconformance target from the Code Lists 4.0 specification.
See the Conformance Targets Attribute Specification for more information on how this is done.
An artifact is NIEM-conformant if and only if it:
NIEM developed a set of practices for information exchanges, which include:
1. Reuse existing NIEM data components when appropriate
Reuse NIEM elements and types whenever possible rather than creating new ones.
In an IEPD extension schema, this means reference NIEM elements and types that are declared in a full NIEM release or in a NIEM subset. Do not recreate elements in the extension schema with NIEM names and definitions.
2. Extend and augment NIEM data components as needed
3. Construct new components when necessary
Construct new data components to express any concepts specific to an exchange or community which the NIEM model does not cover.
4. Use NIEM techniques for data modeling
Use NIEM techniques for common data modeling needs. For example, NIEM describes:
5. Make IEPDs precise
Make the specifications for information exchanges precise, so that tools and systems can support the use and comprehension of messages, as well as ensuring each messages obeys the rules of their specifications
6. Make IEPDs consistent and unambiguous
Construct messages so tools and systems can ensure they follow their specifications and reuse NIEM terms (namespaces and local names), so the identity and expected content of messages are consistent and unambiguous
NIEM has practices, methods, and formats for the pieces that compose an information exchange. These are expressed as a set of specifications. Specifications define the rules and procedures for creating content which is NIEM-conformant.
We encourage developers to use tools provided by the NIEM program to construct and validate their information exchanges as NIEM-conformant, including: