Common Model Format Specification

This repository is part of the NIEM Open Project. It contains the NIEMOpen Common Model Format Specification (CMF).

CMF is a NIEM message specification for data models, In all versions of NIEM through version 5, data models are expressed in XML Schema (XSD). CMF offers an equivalent expression, one that is more suitable for developers not working in XML and is easier to support with developer tools. Using CMF, a data model can be expressed as XML or JSON or any other data serialization that NIEM supports, and the data described by the CMF data model can also be expressed in any supported serialization.

CMF is extensively described in the NIEM Naming and Design Rules, Version 6.0.

For more information on NIEMOpen, see the project's website at www.niemopen.org.

General questions about OASIS Open Projects may be directed to OASIS staff at [email protected]

Examples

This specification is itself a CMF example! model.cmf is a CMF message representing a NIEM model; model.xsd is the equivalent model representation in XML Schema. message.xsd is a simplified message schema for validating CMF messages.

The Crash Driver Report message specification is designed to test and describe the features of the NIEM technical architecture. It contains a NIEM model in equivalent CMF and XSD representations.

Where are the original versions of CMF?

The pre-OASIS history of CMF is at NIEM-Metamodel (github.com)

Other assets

In addition to this GitHub repository, this project also makes use of other assets.

• The NIEMOpen website is at www.niemopen.org. The website contains news, announcements, and other information of interest about the project.

• The General purpose mailing list. To subscribe, send an empty email message to [email protected]. Anyone interested is welcome to subscribe and send email to the list. The list maintains an archive.

• The Project Governing Board mailing list. This is the discussion list for use by the members of the PGB. To subscribe, send an empty email message to [email protected]. Anyone interested is welcome to subscribe read-only. Only PGB members can post. The list maintains an archive.

• NBAC Technical Steering Committee mailing list. This is the discussion list for use by the members of the NIEM Business Architecture Committee TSC. To subscribe, send an empty email message to [email protected]. Anyone interested is welcome to subscribe read-only. The list maintains an archive.

• NTAC Technical Steering Committee mailing list. This is the discussion list for use by the members of the NIEM Technical Architecture Committee TSC. To subscribe, send an empty email message to [email protected]. Anyone interested is welcome to subscribe read-only. The list maintains an archive.

Contributing

Please read CONTRIBUTING.md for details how to join the project, contribute changes to our repositories and communicate with the rest of the project contributors. Please become familiar with and follow the code of conduct.

Governance

NIEM Open operates under the terms of the Open Project Rules and the applicable license(s) specified in LICENSE.md. Further details can be found in GOVERNANCE.md, GOVERNANCE-NBAC.md, and GOVERNANCE-NTAC.md.

CLA & Non-assert signatures required

All technical contributions must be covered by a Contributor's License Agreement. This requirement allows our work to advance through OASIS standards development stages and potentially be submitted to de jure organizations such as ISO. You will get a prompt to sign this document when you submit your first pull request to a project repository, or you can sign here. If you are contributing on behalf of your employer, you must also sign the ECLA here.