Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
CAN/CSA-ISO/IEC 11179-1-16: Foundational Framework for Metadata Registries
A technical deep dive into the Canadian adoption of the international standard for metadata registry structure, data element specification, and semantic interoperability.
The increasing volume of data across enterprise systems demands a rigorous approach to data governance. The CAN/CSA-ISO/IEC 11179-1-16 standard, the Canadian adoption of the international standard ISO/IEC 11179-1:2015, provides the foundational framework for creating and managing Metadata Registries (MDR). This article provides a technical examination of its scope, core structural requirements, practical implementation strategies, and critical compliance considerations for data architects and standards professionals.
1. Scope and Applicability
Part 1 of the ISO/IEC 11179 series specifically defines the framework for a Metadata Registry. It establishes the essential concepts and terminology used across all other parts of the series (Parts 2-6). The scope includes:
- Defining the fundamental purpose of an MDR as a standardized, authoritative source of metadata for unambiguous data interpretation.
- Introducing the key conceptual building blocks: Data Element Concept (DEC), Conceptual Domain, Value Domain, and the Data Element.
- Providing the context for describing data within a specific subject area, allowing for semantic consistency.
- Serving as the top-level specification for the type of metadata that can be stored and managed within an MDR.
This standard is applicable to any organization that needs to describe data formally. It is heavily utilized in government administration, healthcare informatics, statistical agencies, and scientific research.
Tip: CAN/CSA-ISO/IEC 11179-1-16 is fundamentally a framework standard (a conceptual model). It does not specify a physical database schema for an MDR but provides the logical blueprint that any compliant MDR must follow.
2. Core Technical Requirements and the MDR Structure
The standard’s primary technical contribution is the formal structure it imposes on metadata. It outlines a clear hierarchy for data specification. The core requirement is the separation of a data element’s conceptual meaning from its representational form.
2.1 The Core Metamodel Framework
The framework defines a strict conceptual model. The relationship between these four levels is critical for compliance:
| Level | Component | Definition |
|---|---|---|
| 1 | Data Element Concept (DEC) | A concept that can be represented by a data element. Note: It is independent of any specific representation. Example: “Person Date of Birth”. |
| 2 | Conceptual Domain | A set of conceptual value meanings (e.g., a classification of types, a context for a date). |
| 3 | Value Domain | A set of permissible values for a Data Element (e.g., a specific date format: `YYYY-MM-DD`). |
| 4 | Data Element | A unit of data that combines a DEC with a specific Value Domain. Example: “Person Date of Birth” (DEC) expressed as “YYYY-MM-DD” (Value Domain). |