Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 15938-1-04:2004/Amd1:2006/Cor1:2013 – MPEG-7 Systems: Multimedia Content Description Interface
Comprehensive Overview of the 2006 Amendment and 2013 Corrigendum to the MPEG-7 Systems Standard
Scope of IEC 15938-1-04 and Its Amendments
IEC 15938-1-04:2004 (also known as ISO/IEC 15938-1:2004) is the first part of the IEC 15938 series, which defines the Multimedia Content Description Interface — commonly referred to as MPEG-7. Part 1 specifies the Systems layer of MPEG-7, covering the terminal architecture, binary representation of descriptions, and the transport mechanisms for streaming or downloading multimedia content descriptions. The standard enables interoperable access to rich semantic and structural metadata for audio-visual content.
Amendment 1 (Amd1:2006) introduced several enhancements to the original standard, including updates to the binary format for more efficient encoding, improvements to descriptor schemas, and extensions for advanced multimedia applications. Corrigendum 1 (Cor1:2013) addressed technical errors discovered during widespread implementation, such as inconsistencies in attribute definitions, parsing ambiguities, and alignment with related MPEG-7 parts. Together, these revisions ensure that the Systems layer remains robust, backward-compatible, and aligned with evolving industry requirements.
Key Point: The 2006 amendment and 2013 corrigendum refine the MPEG-7 Systems standard without altering its foundational architecture. Implementers should apply both to maintain conformance with the latest official specification.
Technical Requirements Introduced by Amd1:2006 and Cor1:2013
Binary Representation Updates
The amendment improved the binary format (BiM) by adding new fragment type codes and optimizing the encoding of empty descriptors. It also introduced optional compression markers that allow decoders to skip initialization data, improving streaming performance. The corrigendum corrected mandatory flags that were mis-assigned in the amendment, ensuring correct parsing of complex descriptors.
Descriptor and Schema Extensions
Amd1:2006 extended the Multimedia Description Schemes (MDS) with additional elements for content linking, media profiling, and event-driven navigation. For example, it added the MediaInformation element to support adaptive streaming, as well as the ContentLinking type for referencing external descriptions. Cor1:2013 fixed cross-references in the schema definition for these new elements, making them consistent with Part 5 of the standard.
Transport Mechanisms
Cor1:2013 clarified the syntax of the AccessUnit structure used in MPEG-7 streams, resolving ambiguities that could cause interoperability issues between encoders and decoders from different vendors. It also aligned the payload type identifiers with those defined in ISO/IEC 14496-1 (MPEG-4 Systems).
Implementation Note: Developers relying on code from before 2013 must verify that they have applied the corrigendum corrections. Failure to do so may result in rejected description streams during conformance testing.
| Aspect | Amd1:2006 Change | Cor1:2013 Correction |
|---|---|---|
| Binary Format (BiM) | Added fragment types for new MDS elements | Fixed offset calculations for fragmented access units |
| Schema Extensions | Introduced MediaInformation, ContentLinking | Corrected namespace references to Part 5 schemas |
| Access Unit Syntax | Unchanged | Clarified ConditionField semantics and default values |
| Transport Payloads | Added payload ID for descriptor streams | Harmonized payload IDs with ISO/IEC 14496-1:2010 |
Implementation Highlights for Developers
Adopting IEC 15938-1-04:2004 with its amendment and corrigendum requires attention to several practical details:
- Backward Compatibility: The amendment was designed to be backward-compatible, but the corrigendum introduced one non-backward-compatible fix in the AccessUnit syntax. Systems that exchange data with earlier implementations may need a compatibility layer.
- Parser Updates: Binary MPEG-7 decoders must be updated to handle the new fragment type codes (0x0C–0x0F) and the corrected TypeIndicator field. The corrigendum also mandates stricter validation of reserved bits.
- Schema Validation: XML-based workflows should validate descriptions against the updated schema from the amendment, taking care to apply the namespace URI changes specified in the corrigendum.
- Testing and Verification: The MPEG-7 conformance software (ISO/IEC 15938-6) provides test sequences that cover the changes in both publications. It is recommended to rerun conformance tests after integrating the updates.
Best Practice: Maintain a single consolidated version of the specification that merges the base standard, the amendment, and the corrigendum. This eliminates confusion and ensures all team members refer to the same text.
Compliance Notes and Conformance Testing
Conformance to IEC 15938-1-04:2004/Amd1:2006/Cor1:2013 is typically evaluated in two tiers:
- Syntax Conformance: Verifies that the binary or XML description matches the formal grammar defined in the standard. Test tools from ISO/IEC 15938-6 can validate access units and schema compliance.
- Semantic Conformance: Ensures that the description faithfully represents the multimedia content according to MPEG-7 semantics. While covered by Part 5 and Part 6, the Systems part must correctly transport these semantics.
Compliance requirements are particularly strict for applications that claim interoperability, such as digital broadcasting content annotation or media archives using MPEG-7. The corrigendum resolved several issues that were causing false negatives in conformance testing. Therefore, certification bodies now require evidence that both Amd1:2006 and Cor1:2013 have been fully adopted.
Critical Compliance Warning: Ignoring Cor1:2013 can lead to immediate non-conformance. Several test sequences from the official conformance test suite will fail if the corrigendum corrections are missing.
Regulatory and Industry Adoption
The standard, as corrected, has been adopted by various national bodies (EN, JIS) and is referenced in SMPTE guidelines for professional video archives. The EU’s ETSI has also incorporated the corrigendum into standards for digital TV metadata. Therefore, compliance is not only a technical requirement but also a regulatory one in many jurisdictions.
Q: Can I implement only the base standard without the amendment and corrigendum?
A: Yes, but your system will lack the improvements and may fail interoperability tests. Most certification programs require at least the 2006 amendment, and the 2013 corrigendum is strongly recommended to avoid known decoding errors.
A: Yes, but your system will lack the improvements and may fail interoperability tests. Most certification programs require at least the 2006 amendment, and the 2013 corrigendum is strongly recommended to avoid known decoding errors.
Q: Are there any resource consumption changes introduced by Amd1:2006?
A: The binary format enhancements generally improve efficiency, reducing stream size by 5–10% for typical descriptions. However, the added fragment types slightly increase decoder complexity. The corrigendum imposes no additional processing overhead; it fixes correctness issues without affecting performance.
A: The binary format enhancements generally improve efficiency, reducing stream size by 5–10% for typical descriptions. However, the added fragment types slightly increase decoder complexity. The corrigendum imposes no additional processing overhead; it fixes correctness issues without affecting performance.
Q: How do I verify that my implementation includes the corrigendum fixes?
A: Download the conformance test vectors from the ISO/IEC JTC 1/SC 29 website. Run the specific tests labeled “Cor1” — they will fail if your implementation does not incorporate the corrections defined in the 2013 corrigendum.
A: Download the conformance test vectors from the ISO/IEC JTC 1/SC 29 website. Run the specific tests labeled “Cor1” — they will fail if your implementation does not incorporate the corrections defined in the 2013 corrigendum.
First issued: 2004 | Amended: 2006 | Corrigendum: 2013 | This article reviewed: 2026