Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
A Comprehensive Guide to ISO/IEC 11179-3:2015 – Metadata Registry Metamodel and Basic Attributes
Understanding the Core Metamodel for Data Interoperability and Metadata Standardization
Scope and Purpose
The international standard ISO/IEC 11179-3:2015, also designated as IEC 11179-3-15 and adopted in Canada as CAN CSA ISO IEC 11179-3-15, defines the metamodel and basic attributes for metadata registries (MDRs). This standard is fundamental for organizations that need to manage and exchange metadata in a consistent, harmonized way across systems and domains. It provides a generic framework for describing the structure, semantics, and representation of data elements, enabling interoperability and reusability of data assets.
The scope of ISO/IEC 11179-3:2015 covers:
- The specification of a metamodel for metadata registries, detailing the classes and relationships necessary to represent metadata.
- The identification and definition of basic attributes that apply to all metadata items.
- The rules and guidelines for the creation, maintenance, and exchange of metadata registry content.
This standard is widely applied in data governance initiatives, national data exchange frameworks such as NIEM, and enterprise information management programs.
Tip: ISO/IEC 11179-3:2015 is often used together with other parts of the 11179 series, particularly Part 1 (Framework) and Part 4 (Rules and guidelines for the formulation of data definitions), to create a complete metadata management ecosystem.
Technical Requirements and Metamodel Architecture
The core of ISO/IEC 11179-3:2015 is its metamodel, which organizes metadata into three conceptual levels: conceptual, logical, and representation. Each level contains specific classes that define the structure of metadata items.
Core Classes of the Metamodel
The following table lists the primary classes defined in the metamodel, along with their abbreviated definitions:
| Class Name | Level | Description |
|---|---|---|
| Data Element Concept (DEC) | Conceptual | An abstract concept that can be represented in multiple ways, corresponding to a property of an object class. |
| Conceptual Domain (CD) | Conceptual | A set of value meanings that can be used to represent a Data Element Concept. |
| Value Meaning | Conceptual | A specific meaning within a conceptual domain. |
| Data Element (DE) | Logical | A unit of data for which the definition, representation, and permissible values are specified. |
| Value Domain (VD) | Representation | A set of permissible values for a Data Element, represented in a specific data format. |
| Permissible Value | Representation | A specific value (and its meaning) that is allowed in a Value Domain. |
| Object Class | Conceptual | A set of ideas, abstractions, or real‑world things that can be represented. |
| Property | Conceptual | A characteristic of an Object Class. |
| Representation Class | Representation | A classification of Data Elements based on the form of their representation (e.g., amount, code, identifier). |
Basic Attributes
Every metadata item in the registry must be described by a set of basic attributes, including identifier, name, definition, language, and administrative status. The standard prescribes the form and semantics for these attributes to ensure consistency across implementations.
Warning: A common mistake when implementing the metamodel is conflating the Conceptual Domain with the Value Domain. The Conceptual Domain defines possible meanings (e.g., “female”, “male”), while the Value Domain defines how those meanings are represented (e.g., “F”, “M”). Always maintain this separation to adhere to the standard.
Implementation Highlights
Adopting ISO/IEC 11179-3:2015 requires careful planning and an understanding of the organization’s metadata landscape. Key implementation considerations include:
- Tool Support: Many metadata registry tools now offer features based on the 11179‑3 metamodel. Choose a tool that fully supports the class hierarchy and relationships defined in the standard.
- Training and Governance: Establish a metadata governance board to approve the creation of Data Element Concepts, Conceptual Domains, and Value Domains. Ensure that data stewards understand the three‑level architecture.
- Integration with Existing Standards: Map your current data dictionaries and code lists to the 11179‑3 classes. This often reveals gaps or duplications that can be resolved.
- Exchange Formats: The standard can be used to generate XML or JSON schemas for metadata exchange using the representation specified in ISO/IEC 11179‑3:2015, Annex A.
Success Story: A government agency implemented ISO/IEC 11179-3:2015 to harmonize data across six departments. By aligning their data elements with the standard’s metamodel, they reduced data redundancy by 40% and achieved seamless cross‑agency reporting.
Compliance Notes and Certifications
Organizations wishing to claim compliance with ISO/IEC 11179‑3:2015 need to meet the following requirements:
- Conformance Level 1 – Minimal: The registry must contain at least the mandatory classes (Data Element, Data Element Concept, Value Domain, Conceptual Domain) and satisfy the basic attribute definitions.
- Conformance Level 2 – Full: All classes and relationships defined in the metamodel must be implemented, including the representation class, object class, and property relationships. The registry must support the complete lifecycle attributes.
- Audit and Documentation: Retain artifacts that demonstrate the registry’s structure and its mapping to the standard. Third‑party audits can validate conformance, but the standard does not offer formal certification – compliance is self‑declared.
Note that while the standard provides a metamodel, it does not prescribe specific database schemas or API formats. Compliance focuses on the conceptual fidelity of the registry to the defined classes and attributes.
Danger: Non‑compliance can lead to data misinterpretation and an inability to exchange metadata with partners who adhere to the standard. In multi‑vendor environments, this often results in costly manual reconciliation efforts.
Frequently Asked Questions
Q: What is the difference between ISO/IEC 11179‑3:2013 and the 2015 edition?
A: ISO/IEC 11179‑3 was originally published in 2003 and revised in 2008 and 2013. The 2013 edition (correctly noted as ISO/IEC 11179‑3:2013) introduced substantial changes to the metamodel. While the user reference “IEC 11179‑3‑15” points to the 2015 adoption (e.g., in Canada), the technical content is identical to the 2013 edition. The 2023 edition is now available, but many current implementations still rely on the 2015 adoption.
A: ISO/IEC 11179‑3 was originally published in 2003 and revised in 2008 and 2013. The 2013 edition (correctly noted as ISO/IEC 11179‑3:2013) introduced substantial changes to the metamodel. While the user reference “IEC 11179‑3‑15” points to the 2015 adoption (e.g., in Canada), the technical content is identical to the 2013 edition. The 2023 edition is now available, but many current implementations still rely on the 2015 adoption.
Q: How does ISO/IEC 11179‑3 relate to the “Common Data Model” (CDM) or to DCAT?
A: ISO/IEC 11179‑3 provides a foundational metamodel that can be used to map other data models such as the Common Data Model (OCDS, NIEM) and DCAT. Its core classes (Data Element Concept, Conceptual Domain, Value Domain) allow linking datasets and catalogs at the semantic level, ensuring that the meaning of data is preserved across different representation syntaxes.
A: ISO/IEC 11179‑3 provides a foundational metamodel that can be used to map other data models such as the Common Data Model (OCDS, NIEM) and DCAT. Its core classes (Data Element Concept, Conceptual Domain, Value Domain) allow linking datasets and catalogs at the semantic level, ensuring that the meaning of data is preserved across different representation syntaxes.
Q: Can a small organization implement ISO/IEC 11179‑3:2015?
A: Yes. The standard is scalable. A small organization can start with a simple registry that records Data Elements, Data Element Concepts, and Value Domains in a spreadsheet. The key is to use consistent naming, definitions, and attribute templates. As the organization grows, more classes and relationships can be introduced.
A: Yes. The standard is scalable. A small organization can start with a simple registry that records Data Elements, Data Element Concepts, and Value Domains in a spreadsheet. The key is to use consistent naming, definitions, and attribute templates. As the organization grows, more classes and relationships can be introduced.
Q: Are there any recommended tools that support the standard?
A: Several commercial and open‑source tools support the 11179‑3 metamodel, including the US NGDI Registry, the Italian DCAT‑AP profile, and some enterprise metadata management platforms. Always verify that the tool’s data model directly represents the classes listed in the standard to ensure conformance.
A: Several commercial and open‑source tools support the 11179‑3 metamodel, including the US NGDI Registry, the Italian DCAT‑AP profile, and some enterprise metadata management platforms. Always verify that the tool’s data model directly represents the classes listed in the standard to ensure conformance.
Last updated: 2026. This article provides general guidance; refer to the official text of ISO/IEC 11179‑3:2015 (IEC 11179‑3‑15 or CAN CSA ISO IEC 11179‑3‑15) for authoritative requirements.