Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 15444-2:2004/Amd2:2006 – JPEG 2000 Extended Capabilities and Compliance Guide
Technical overview of the scope, new features, implementation considerations, and conformance requirements introduced by Amendment 2 to JPEG 2000 Part 2 (JPX)
Scope and Introduction
ISO/IEC 15444-2:2004/Amd2:2006 is the second amendment to the JPEG 2000 Part 2 standard (JPX – extended coding system). While the base Part 2 already extends the core JPEG 2000 codec with advanced tools such as variable DC offset, multi-component transforms, and arbitrary wavelet kernels, this amendment adds a set of optional enhancements designed to improve color management, compositing, region-based metadata, and file format flexibility. The amendment was developed by Joint Technical Committee ISO/IEC JTC 1/SC 29 and published in 2006, reflecting industry demand for richer image representation in professional broadcasting, digital cinema, medical imaging, and archival systems.
The document specifies a number of new capabilities that remain fully backward-compatible with Part 1 (ISO/IEC 15444-1) and earlier Part 2 implementations. However, decoders that wish to leverage the new features must recognise the extended marker segments and follow updated parsing rules. The amended standard retains its designation as part of the JPX profile, which is the recommended baseline for applications requiring high dynamic range, high precision, and advanced colour spaces.
Key point: Amd2:2006 does not replace or deprecate earlier amendments; it layers optional functionality on top of the existing JPX specification. All previously defined tools remain valid and unchanged.
Technical Requirements and Extended Features
1. Enhanced Colour Management
The amendment introduces additional colour space specification methods beyond those available in the base part. Key additions include:
- Embedded ICC profiles – Full ICC.1:2004 (v4) profile support, allowing precise colour reproduction without external metadata.
- Named colour systems – Colour specifications based on colourant names (e.g., Pantone, HKS) using a new
NCL(Named Colour Look-up) marker. - Extended enumerated colour spaces – Additional predefined colour spaces (e.g., sLMS, IPT) for high-end workflows.
2. Region‑Based Metadata and Compositions
Amd2:2006 formalises constructs for associating metadata with rectangular regions of an image. A new Region Set marker (RSET) and Composition Set marker (CSET) allow authors to define overlapping regions that can hold attributes such as copyright, annotations, or multilingual descriptions without altering the codestream.
3. Extended Compositing and Layer Support
The amendment standardises multi-layer compositing where independent JPX grids can be combined using alpha blending, Porter–Duff operators, and custom compositing formulas. A new Layer Description marker (LDES) defines layer properties while the Compositing Instruction Table (COIN) controls the order and operation. This enables sophisticated overlays directly inside the JPX file.
4. Additional Coding and File‑Format Features
Several minor but practical extensions were added:
- Support for more than 256 colour components (extended component count).
- New variable-length and fixed-length tags for external data references.
- Optional decoupled tile dimensions for different components.
- Clarifications on the use of the
CRG(component registration) marker with colour data.
The following table summarises the principal additions introduced by Amd2:2006.
| Feature | Marker / Construct | Mandatory for Decoder? | Primary Benefit |
|---|---|---|---|
| ICC v4 profiles | ICC (revised box) | No (optional) | Accurate colour management across devices |
| Named colours | NCL (new) | No | Support for spot colours in prepress |
| Region metadata | RSET, CSET | No | Annotations and region‑specific data |
| Compositing layers | LDES, COIN | No | Overlays and graphic compositions |
| Decoupled component tiling | SIZ template extensions | No | Flexible component placement |
Implementation tip: All new markers are self-contained within the JPX file structure. Developers can extend existing JPX parsers by adding code for each new marker class without refactoring core decoding routines.
Implementation Highlights
Because Amd2:2006 only adds optional boxes and marker segments, a conforming Part 2 implementation can ignore the new constructs and still decode the base codestream. However, to claim full JPX Extended conformance, an implementation must (a) recognise all new markers and boxes, (b) correctly resolve the composition and region structures, and (c) process the colour data according to the listed transformation chains.
Key implementation considerations:
- Colour pipeline: When an ICC profile is embedded, the decoder must apply the profile after the wavelet reconstruction and component transform. If both the base-part and Amd2 colour spaces are specified, the ICC profile takes precedence.
- Compositing order: Multiple layers are processed in the order defined by the
COINinstruction table. The default operator is “over”. Off-screen layers are allowed and must be composited at the image origin. - Region sets: Regions are described by axis-aligned rectangles; each region can carry an array of metadata items (e.g., text, XML, binary). The standard does not define access control – all regions are public and should be parsed at load time.
- Memory footprint: Because compositions can reference many layers, implementers should use lazy evaluation and on‑demand decoding to avoid loading unnecessary data into memory.
Compatibility warning: Older decoders that only support Part 1 or base Part 2 will skip the new markers and may show only the first layer or ignore region metadata. Use the
JPX Base Data box as a fallback to ensure minimal display capability. Compliance and Testing
Formal conformance is defined through the test sequences provided in ISO/IEC 15444-2/Amd2:2006 itself, supplemented by the JPEG 2000 conformance testing framework (ISO/IEC 15444-4). Compliance requires passing the following categories:
- Colour profile handling: Correct application of ICC v4 transform and metric.
- Layer composition: Pixel‑by‑pixel accuracy of combined layers for the examples in the amendment.
- Region extraction: Retrieval of metadata for each specified rectangle.
- Extended marker parsing: No fatal errors when encountering
NCL,RSET,LDES, or other new markers.
For commercial products, certification by a JPEG 2000 interoperability laboratory (e.g., based on the ISO test set) is recommended. The amendment does not modify the core codestream syntax (see Part 1), so a failure to decode these extensions does not affect baseline JPEG 2000 compliance.
Legal note: Embedding proprietary colour tables or region metadata that deviates from the standard’s marker syntax may cause interoperability failures. Always validate against the ISO test bitstreams before claiming compliance.
In summary, ISO/IEC 15444-2:2004/Amd2:2006 provides a rich set of optional extensions that make JPX suitable for demanding imaging applications. By following the implementation guidelines and conformance checks outlined here, developers and integrators can create robust, interoperable solutions that fully exploit the power of the JPEG 2000 extended coding framework.
Frequently Asked Questions
Q: Does Amd2:2006 require changes to JPEG 2000 Part 1 decoders?
A: No. The amendment only modifies Part 2 (JPX) and only adds optional boxes and marker segments. Part 1 decoders remain fully compliant without any code changes – they will simply skip the new constructs. A JPX decoder that wants to offer the extended capabilities must of course parse them correctly.
A: No. The amendment only modifies Part 2 (JPX) and only adds optional boxes and marker segments. Part 1 decoders remain fully compliant without any code changes – they will simply skip the new constructs. A JPX decoder that wants to offer the extended capabilities must of course parse them correctly.
Q: What file extension should be used for images leveraging Amd2:2006 features?
A: The standard strongly recommends the
A: The standard strongly recommends the
.jpf or .jpx extension (already defined in Part 2). Applications may continue to use .jp2 only if the extension markers are optional and the image can be reasonably decoded by a Part 1 viewer. For full JPX capabilities, use .jpf. Q: Are the ICC v4 profiles backward-compatible with ICC v2?
A: In general, ICC v4 profiles are not backward-compatible with ICC v2 due to differences in the colour engine and PCS encoding. Decoders implementing only older ICC interpretations may produce inaccurate colours when encountering a v4 profile. The amendment includes guidance on converting to v2 if needed, but full compliance requires v4 support.
A: In general, ICC v4 profiles are not backward-compatible with ICC v2 due to differences in the colour engine and PCS encoding. Decoders implementing only older ICC interpretations may produce inaccurate colours when encountering a v4 profile. The amendment includes guidance on converting to v2 if needed, but full compliance requires v4 support.
Q: Can I store animated layers using the compositing features of Amd2:2006?
A: The standard itself does not define animation or time‑varying layers – compositing is static per image instance. However, combining Amd2 layers with the Motion JPEG 2000 framework (ISO/IEC 15444-3) can produce simple animations by changing the composition set across frames. This usage is informal and not yet standardised.
A: The standard itself does not define animation or time‑varying layers – compositing is static per image instance. However, combining Amd2 layers with the Motion JPEG 2000 framework (ISO/IEC 15444-3) can produce simple animations by changing the composition set across frames. This usage is informal and not yet standardised.