Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Understanding IEC 13522-4-01 – Registration Procedure for Multimedia and Hypermedia Objects (MHEG)
A comprehensive technical guide to the structure, implementation, and compliance of the ISO/IEC 13522-4:2001 registration scheme
1. Scope and Purpose
IEC 13522-4-01 (also adopted as CAN/CSA-ISO/IEC 13522-4:01) is the Canadian adoption of the international standard ISO/IEC 13522-4:2001, which defines the registration procedure for multimedia and hypermedia information objects encoded according to the MHEG (Multimedia and Hypermedia information coding Experts Group) standard. The standard establishes a formal mechanism to assign unique identifiers to MHEG objects and object classes, ensuring global interoperability across platforms and applications. It primarily addresses the needs of implementers, registration authorities, and conformance testers who require a structured system for object identification without overlap or ambiguity.
The standard applies to any object defined in other parts of the ISO/IEC 13522 family (e.g., MHEG-1, MHEG-5), including scripts, scenes, and resources. Its goal is to avoid identifier collision, streamline interchange, and simplify the maintenance of object libraries in multimedia and hypermedia systems.
Key Insight: IEC 13522-4-01 does not define the syntax or semantics of MHEG objects; it only specifies the administrative framework for obtaining unique object identifiers. Implementers must refer to the respective MHEG parts for content encoding rules.
2. Technical Requirements and Registration Framework
2.1 Registration Identification Structure
The core requirement of IEC 13522-4-01 is the use of a two-level identifier hierarchy: an organization identifier and an object identifier. The organization identifier is a globally unique string assigned to the entity requesting registration (e.g., a company, consortium, or standards body). The object identifier is a local value chosen by that entity to unambiguously denote a specific MHEG object within its domain. The full registration identifier is concatenated as <org-id>/<obj-id>.
The standard mandates that the organization identifier must be obtained from a recognized national or international registration authority as defined in the standard’s administrative annexes. Object identifiers within each domain must be unique and should not be reused for different object types. Implementers are required to follow the rules for both initial assignment and subsequent extensions.
2.2 Registration Authority and Procedures
The standard designates the Registration Authority (RA) for MHEG identifiers, responsible for maintaining the central registry of organization identifiers and verifying compliance with the naming rules. The RA may delegate sub‑registration to national bodies (e.g., CSA for Canada). Requests must be submitted in writing or electronically, accompanied by a statement of intended use and the applicant’s contact details. The RA is required to respond within 30 working days.
Table 1 below summarizes the record field structure that the RA maintains for each registration:
| Field | Description | Example |
|---|---|---|
| Organization ID | Unique string (alphanumeric + hyphens) assigned by RA | MHEG-ORG-1042 |
| Organization Name | Full legal name of the requesting entity | ABC Multimedia Corp. |
| Contact Information | Postal address, email, and phone of the responsible person | j.doe@abcmm.com |
| Object Prefix | Designated prefix (first part of the object identifier) | MMNGR- |
| Last Object Serial | Last assigned serial number in the prefix range | 002047 |
| Registration Date | Date when the organization ID was issued | 2025-03-15 |
| Status | Active, Suspended, or Revoked | Active |
2.3 Registration Record Format and Metadata
Each registered object must be accompanied by a minimal set of metadata including the object type (e.g., scene, script, resource), a human-readable name, version, and the date of last modification. The standard recommends (but does not require) that implementers include a digital signature over this metadata to ensure integrity. The registration record must be stored in an XML‑based format (as defined in Annex C of ISO/IEC 13522‑4:2001) for machine‑readability. The schema enforces the uniqueness of the full <org-id>/<obj-id> pair across the global namespace.
Implementation Note: When generating object identifiers locally, use a scheme that incorporates a timestamp or random component to avoid collisions even within the same organization. Prefixes can be reserved for well-known object categories (e.g.,
P- for presentation objects, R- for resources). 3. Implementation Highlights
Implementers of IEC 13522-4-01 should follow these best practices to align with the standard’s spirit and legal requirements:
- Obtain an Organization ID early – The registration process can take several weeks; plan ahead for product development cycles.
- Establish an internal naming policy – Define conventions for object identifier formats (e.g., length, allowed characters) to minimize conflicts and facilitate automatic generation.
- Maintain a local registry – Keep a copy of all assigned object identifiers along with their metadata, version history, and lifecycle status to aid debugging and conformance testing.
- Use version numbers – The standard allows extending an object identifier with a version or sub‑type indicator; however, the base identifier must remain stable.
- Leverage XML schemas – The registration format is XML‑based; use validated XML processing to ensure interoperability when exchanging object declarations between systems.
Caution: Reassigning an object identifier that was previously used for a different object (even if retired) can break existing applications or archives. Always retire identifiers permanently and never reuse them.
4. Compliance and Conformance Notes
Conformance to IEC 13522-4-01 is assessed at two levels: conformant implementations (software and hardware that handle MHEG objects) and conformant registrations (the registration process itself). For implementation conformance, a system must correctly parse and generate registration identifiers according to the syntax defined in the standard, and must reject any identifier that does not follow the <org-id>/<obj-id> structure. For registration conformance, the registration authority must follow the administrative procedures outlined in Clauses 6 and 7 of the standard, including record keeping, response times, and dispute resolution.
Implementers seeking formal conformance should submit their product for testing at an accredited laboratory. The standard does not define a test suite, but conformance can be verified by checking that the product correctly handles a set of sample identifiers including edge cases (e.g., maximum length, special characters). Common pitfalls include:
- Using characters outside the allowed set (alphanumeric, hyphen, underscore, period allowed; others forbidden).
- Case sensitivity – Organization IDs are case‑insensitive, but object IDs are case‑sensitive. Implementations must respect this distinction.
- Misinterpreting the intended uniqueness scope – Two identical object identifiers from different organizations are permitted; only the tuple (organization ID, object ID) must be unique.
Critical: An implementation that silently duplicates an existing combination (OrgID+ObjectID) is non‑conformant. The standard requires that a new object must not overwrite or alias an already registered object unless explicitly versioned.
Compliance with the Canadian adoption (CAN/CSA-ISO/IEC 13522-4:01) may require additional conformance marks or registration with CSA Group. International adopters should refer directly to ISO/IEC 13522‑4:2001 and note that the registration authority’s contact details have been updated in the recent corrigenda.
Frequently Asked Questions
Q: Is IEC 13522-4-01 identical to ISO/IEC 13522-4:2001?
A: Yes, the Canadian standard CAN/CSA-ISO/IEC 13522-4:01 is an identical adoption of ISO/IEC 13522-4:2001, with only minor editorial changes for national labeling requirements. All technical requirements are the same.
A: Yes, the Canadian standard CAN/CSA-ISO/IEC 13522-4:01 is an identical adoption of ISO/IEC 13522-4:2001, with only minor editorial changes for national labeling requirements. All technical requirements are the same.
Q: How long does it take to obtain an organization ID?
A: The standard mandates a 30‑working‑day response target for the Registration Authority. In practice, most requests are processed within two to three weeks.
A: The standard mandates a 30‑working‑day response target for the Registration Authority. In practice, most requests are processed within two to three weeks.
Q: Can an individual developer register an organization ID?
A: Yes, the standard does not restrict registration to legal entities; any individual or organization that needs to assign MHEG object identifiers can apply, as long as they provide verifiable contact information and commit to the naming rules.
A: Yes, the standard does not restrict registration to legal entities; any individual or organization that needs to assign MHEG object identifiers can apply, as long as they provide verifiable contact information and commit to the naming rules.
Q: What happens if an organization ceases to exist?
A: The registration authority may suspend or revoke the organization ID, but any object identifiers already assigned remain valid for interchange purposes. The standard recommends that the organization’s successor or a designated custodian assume responsibility for maintaining the numeric range.
A: The registration authority may suspend or revoke the organization ID, but any object identifiers already assigned remain valid for interchange purposes. The standard recommends that the organization’s successor or a designated custodian assume responsibility for maintaining the numeric range.
Article prepared for technical documentation use based on IEC 13522-4-01 / CAN/CSA-ISO/IEC 13522-4:01. © 2026 – All rights reserved.