Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
CAN/CSA-ISO/IEC 11179-6:16 – Metadata Registration Procedures: Scope, Requirements, and Compliance
A comprehensive guide to the Canadian adoption of ISO/IEC 11179-6:2015 for authoritative metadata registry administration
Scope of CAN/CSA-ISO/IEC 11179-6:16
CAN/CSA-ISO/IEC 11179-6:16 is the Canadian adoption of the international standard ISO/IEC 11179-6:2015, which forms part of the ISO/IEC 11179 series on Information technology — Metadata registries (MDR). This part defines the administrative and procedural framework for registering metadata items in a metadata registry that conforms to the ISO/IEC 11179 model. The standard addresses the lifecycle of metadata items—from initial submission through review, approval, maintenance, and eventual supersession—ensuring that metadata is uniquely identified, quality-controlled, and governed by clear policies.
Intended for organizations that must share metadata across systems and domains, CAN/CSA-ISO/IEC 11179-6:16 establishes four distinct roles (Registrar, Registering Authority, Steward, and Submitter) and a set of registration states (Candidate, Recorded, Qualified, Standard, Deprecated, Superseded) that form the backbone of any compliant registration process. The standard is identical in technical content to ISO/IEC 11179-6:2015 and includes only a Canadian foreword.
Note: The ISO/IEC 11179 series consists of several parts. Part 6 focuses purely on registration procedures; to build a complete metadata registry system, Parts 3 (Metamodel) and 4 (Formulation of data definitions) are also essential.
Technical Requirements
Registration Roles and Responsibilities
The standard mandates a clear separation of duties to ensure accountability and integrity in the registration process. The four roles are:
- Registrar – The body that manages the day-to-day operation of the registry, including receiving submissions, performing completeness checks, and maintaining the registry infrastructure.
- Registering Authority – The authoritative body that assigns registration statuses and unique identifiers, ensuring that only properly reviewed items reach higher states.
- Steward – The organization or individual responsible for the semantic quality and content of a metadata item. The steward performs content reviews and recommends state transitions.
- Submitter – The entity that proposes new metadata items or changes to existing items for entry into the registry.
Registration States and Transitions
Each metadata item in the registry must have a current registration state. Transitions between states are governed by specific quality checks and approvals. The table below summarizes the states, their meaning, and the required action for entry.
| State | Description | Required Action | Responsible Role |
|---|---|---|---|
| Candidate | Item submitted but not yet reviewed | Submitter provides metadata | Submitter |
| Recorded | Basic metadata recorded after a completeness check | Registrar verifies mandatory fields | Registrar |
| Qualified | Item meets quality criteria (definitions, precision) | Steward conducts semantic review | Steward |
| Standard | Approved for general use after wider review | Registering Authority gives final approval | Registering Authority |
| Deprecated | Still present but not recommended for new use | Steward recommends based on usage analysis | Steward / Registrar |
| Superseded | Replaced by another item (version or alternative) | Registering Authority assigns supersession relationship | Registering Authority |
Identifier Structure
To guarantee global uniqueness, the standard requires that each registered metadata item bear an identifier composed of three parts:
- Registration Authority Identifier (RAI) – a globally unique code assigned to each Registering Authority (e.g., by an international maintenance agency).
- Data Identifier (DI) – a unique code within the scope of the Registering Authority.
- Version Identifier (VID) – a version number that increments with each change to the item.
The recommended format is RAI-DI-VID. The standard also specifies administrative procedures for requesting, modifying, and retiring identifiers.
Implementation caution: The identifier scheme must be supported by the registry’s database and user interface. Versioning is particularly critical for tracking changes and ensuring that references to metadata items remain valid over time.
Implementation Highlights
Adopting CAN/CSA-ISO/IEC 11179-6:16 requires more than just documental compliance; organizations must integrate the registration procedure into their data governance practices. Key considerations include:
- Role assignment: Clearly designate individuals or teams for each role and document their authority and responsibilities.
- Workflow automation: Build or procure a registry system that supports state transitions, notifications, and audit trails.
- Quality criteria: Define explicit rules for moving from Candidate to Recorded (completeness) and from Recorded to Qualified (semantic quality).
- Training: Ensure that all participants understand the states, the meaning of each transition, and the importance of metadata definitions (see Part 4).
- Interoperability: Align the registry’s metamodel with Part 3 to ensure that metadata items can be exchanged with other ISO/IEC 11179-compliant registries.
Best practice: Start with a pilot registration process for a small set of high-value data elements. Use the lessons learned to refine workflows before scaling up. This approach reduces resistance and demonstrates tangible benefits.
Compliance Notes
Organizations seeking to claim compliance with CAN/CSA-ISO/IEC 11179-6:16 must demonstrate that their registration procedures meet all mandatory (shall) requirements of the standard. Recommendations (should) and permissions (may) are optional but encouraged for full alignment. Key compliance criteria include:
- Documented procedures: Written policies for each role, state transition, and identifier management.
- Audit capability: The ability to reconstruct the history of every registered item, including who performed each action and when.
- Status visibility: The current registration state must be clearly visible to all registry users.
- Periodic review: Regular audits of registered items to identify stale, deprecated, or misclassified entries.
While the standard is voluntary in Canada, it is often referenced in government and industry contracts that require metadata consistency across partners. In regulated sectors (healthcare, finance, aerospace), compliance may be mandated indirectly through other data governance frameworks such as CAN/CSA-BIO- or industry-specific standards.
Risk: Failure to follow the registration procedure can lead to duplicate, conflicting, or untrustworthy metadata. This undermines data integration efforts and can cause costly errors in data exchange and reporting.
Frequently Asked Questions
Q: How does CAN/CSA-ISO/IEC 11179-6:16 differ from the original ISO standard?
A: Technically, there is no difference. CAN/CSA-ISO/IEC 11179-6:16 is an identical adoption of ISO/IEC 11179-6:2015 for use in Canada. It includes a national foreword but retains all normative content unchanged.
A: Technically, there is no difference. CAN/CSA-ISO/IEC 11179-6:16 is an identical adoption of ISO/IEC 11179-6:2015 for use in Canada. It includes a national foreword but retains all normative content unchanged.
Q: Who in Canada should use this standard?
A: Any organization that maintains a metadata registry—including government agencies, healthcare providers, financial institutions, and research data centers—can benefit from adopting this standard to improve metadata quality and interoperability.
A: Any organization that maintains a metadata registry—including government agencies, healthcare providers, financial institutions, and research data centers—can benefit from adopting this standard to improve metadata quality and interoperability.
Q: Does the standard prescribe specific software or database schemas?
A: No. It defines administrative procedures, roles, and states. The technical implementation of the registry (e.g., database design, APIs, user interface) is left to the implementer, though alignment with Part 3 of the series is recommended for interoperability.
A: No. It defines administrative procedures, roles, and states. The technical implementation of the registry (e.g., database design, APIs, user interface) is left to the implementer, though alignment with Part 3 of the series is recommended for interoperability.
Q: Where can I obtain the full text of CAN/CSA-ISO/IEC 11179-6:16?
A: The standard is published by the CSA Group and available from their online store. It may also be accessible via university libraries or through corporate standards licenses.
A: The standard is published by the CSA Group and available from their online store. It may also be accessible via university libraries or through corporate standards licenses.