ISO/IEC 15444-1:2000/Cor 2:2002

Information technology — JPEG 2000 image coding system — Part 1: Core coding system — Technical Corrigendum 2

Technologies de l'information — Système de codage d'image JPEG 2000 — Partie 1: Système de codage de noyau — Rectificatif technique 2

General Information

• Status: Withdrawn
• Publication Date: 23-Jan-2002
• Withdrawal Date: 23-Jan-2002
• ICS: 35.040 - Information coding
• ICS: 35.040.30 - Coding of graphical and photographical information
• Technical Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Drafting Committee: ISO/IEC JTC 1/SC 29/WG 1 - JPEG Coding of digital representations of images
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 23-Sep-2004

Relations

• Corrects: ISO/IEC 15444-1:2000 - Information technology — JPEG 2000 image coding system — Part 1: Core coding system
• Effective Date: 06-Jun-2022
• Child: ISO/IEC 15444-1:2000 - Information technology — JPEG 2000 image coding system — Part 1: Core coding system
• Effective Date: 15-Apr-2008
• Revised: ISO/IEC 15444-1:2004 - Information technology — JPEG 2000 image coding system: Core coding system — Part 1:
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL STANDARD ISO/IEC 15444-1:2000
TECHNICAL CORRIGENDUM 2
Published 2002-01-15

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION  •  МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ  •  ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE


Information technology — JPEG 2000 image coding system —
Part 1:
Core coding system
TECHNICAL CORRIGENDUM 2
Technologies de l'information — Système de codage d'image JPEG 2000 —
Partie 1: Système de codage de noyau
RECTIFICATIF TECHNIQUE 2
Technical Corrigendum 2 to International Standard ISO/IEC 15444-1:2000 was prepared by Joint Technical
Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and
hypermedia information.


ICS 35.040 Ref. No. ISO/IEC 15444-1:2000/Cor.2:2002(E)
©  ISO/IEC 2002 – All rights reserved
Printed in Switzerland

---------------------- Page: 1 ----------------------
ISO/IEC 15444-1:2000/Cor.2:2002(E)

INFORMATION TECHNOLOGY – JPEG 2000 IMAGE CODING SYSTEM:
CORE CODING SYSTEM
TECHNICAL CORRIGENDUM 2
1) In the List of Tables, Table A-16 and Table A-15, change the order of Table A-15 and Table A-16.
2) In the List of Tables, Table A-16, change
“Progression order for the SPcod, SPcoc, and Ppoc parameters”
to
“Progression order for the SGcod, SPcoc, and Ppoc parameters”
3) In Annex A.6.1, Table A-17, change
“Multiple component transformation for the SPcod parameters”
to
“Multiple component transformation for the SGcod parameters”
4) In List of Tables, add “Table J-25 Recommended frequency weighting for multiple component (colour) images”
5) In clause 3.99, change
“tile-part index: The index of the current tile-part ranging from zero to the number of tile-parts minus in a given tile.”
to
“tile-part index: The index of the current tile-part ranging from zero to the number of tile-parts minus one in a given
tile.”
6) In Annex A.2, Table A-2, the footnotes markers in the table do not correspond to the footnotes. The correct
table has the below footnoting.
Table A-2 — List of markers and marker segments
Symbol Code Main header Tile-part header
Delimiting markers and marker segments
Start of codestream
a
SOC 0xFF4F not allowed
required
Start of tile-part
SOT 0xFF90 not allowed required
Start of data
SOD 0xFF93 not allowed last marker
End of codestream
EOC 0xFFD9 not allowed not allowed
Fixed information marker segments
Image and tile size
SIZ 0xFF51 required not allowed
©  ISO/IEC 2002 – All rights reserved 1

---------------------- Page: 2 ----------------------
ISO/IEC 15444-1:2000/Cor.2:2002(E)

Table A-2 — List of markers and marker segments (continued)
a
Symbol Code Main header Tile-part header
Functional marker segments
Coding style default
COD 0xFF52 required optional
Coding style component
COC 0xFF53 optional optional
Region-of-interest
RGN 0xFF5E optional optional
Quantization default
QCD 0xFF5C required optional
Quantization component
QCC 0xFF5D optional optional
b
Progression order change
POC 0xFF5F optional optional
Pointer marker segments
Tile-part lengths
TLM 0xFF55 optional not allowed
Packet length, main header
PLM 0xFF57 optional not allowed
Packet length, tile-part header
PLT 0xFF58 not allowed optional
c
Packed packet headers, main header
PPM 0xFF60 optional not allowed
c
Packed packet headers, tile-part header
PPT 0xFF61 not allowed optional
In bit stream markers and marker segments
not allowed in tile-
Start of packet SOP 0xFF91 not allowed part header, optional
in bit stream
optional inside PPT
optional inside PPM
End of packet header EPH 0xFF92 marker segment or in
marker segment
bit stream
Informational marker segments
Component registration
CRG 0xFF63 optional not allowed
Comment
COM 0xFF64 optional optional
a. Required means the marker or marker segment shall be in this header, optional means it may be used.
b. The POC marker segment is required if there are progression order changes.
c. Either the PPM or PPT marker segment is required if the packet headers are not distributed in the bit stream. If the PPM marker
segment is used then PPT marker segments shall not be used, and vice versa.
7) In Annex A.4.2, Table A-5, Psot value, correct
32
“12 — (2 -1)”
to
32
“0, or 14 — (2 -1)”
2 ©  ISO/IEC 2002 – All rights reserved

---------------------- Page: 3 ----------------------
ISO/IEC 15444-1:2000/Cor.2:2002(E)

8) In Annex A.5.1, Lsiz definition, Equation A.1, correct
“Lcod”
to
“Lsiz”
9) In Annex A.6.1, Table A-16, table title, change
“Progression order for the SPcod, SPcoc, and Ppoc parameters”
to
“Progression order for the SGcod, SPcoc, and Ppoc parameters”
10)In Annex A.6.1, Table A-17, table title, correct
“Multiple component transformation for the SPcod parameters”
to
“Multiple component transformation for the SGcod parameters”
i n
11)In Annex A.6.2, Figure A-11, add the definition “F -F — Precinct size”
12)In Annex A.6.6, Table A-32, correct
i
“RSpoc ”, “8”, “0 — 33"
to
i
“RSpoc ”, “8”, “0 — 32"
13)In Annex A.7.1, Table A-33, lower right cell, correct
“13 — 65 535
32
13 — (2 -1)”
to
“14 — 65 535
32
14 — (2 -1)”
14)In Annex A.8.1, Usage first paragraph, second sentence, correct
“Shall only be used if indicated in the proper COD marker segment (see Annex A.6.1).”
to
“Shall not be used unless indicated that it is allowed in the proper COD marker segment (see Annex A.6.1).”
15)In Annex B.10.3, after the first paragraph, there could be ambiguity about the functioning of the code-block
inclusion tag tree. After the last paragraph add,
“Note — If a packet is marked as empty then no code-blocks may contribute to the corresponding layer. If the next
packet is not marked as empty, the code-block inclusion information (defined in Annex B.10.4) for the previous layer
with the empty bit set has to be included. The code-block inclusion information for code-blocks which have not yet
been included in any packet is encoded using a tag tree whose entries are initialized with the layer number of the first
layer to which the code-block contributes. Thus, the tag tree will have redundant information identifying whether or
not the code-block contributes to both the current layer and the layer in which the packet was marked as empty.”
16)In Annex B.10.4, third paragraph, first sentence, change
“For code-blocks that have not been previously included in any packet, this information is signalled with a separate
tag tree code for each precinct.”
to
“For code-blocks that have not been previously included in any packet, this information is signalled with a separate
tag tree code for each precinct as confined to a subband.”
©  ISO/IEC 2002 – All rights reserved 3

---------------------- Page: 4 ----------------------
ISO/IEC 15444-1:2000/Cor.2:2002(E)

17)In Annex G.1.1, Equation G.1, change
i
Ssiz – 1
"“Ix(),y ←Ix(),y – 2
to
i
Ssiz
"“Ix(),y ←Ix(),y – 2
18)In Annex G.1.2, Equation G.2, change
i
Ssiz – 1
"“Ix(),y ←Ix(),y + 2
to
i
Ssiz
"“Ix(),y ←Ix(),y + 2
19)In Annex I.5.1, third paragraph, delete the sentence
“The control-Z character in the type stops file display under MS-DOS.”
20)In Annex I.5.3.1, BPC definition, second paragraph, change
“If the bit depth is the same for all components, then this parameter specifies that bit depth and shall be equivalent to
i
the values of the Ssiz fields in the SIZ marker in the codestream (which shall all be equal). If the components vary in
bit depth, then the value of this field shall be 255 and the JP2 Header box shall also contain a Bits Per Component box
defining the bit depth of each component (as defined in Annex I.5.3.2).”
to
“If the bit depth and the sign are the same for all components, then this parameter specifies that bit depth and shall be
i
equivalent to the values of the Ssiz fields in the SIZ marker in the codestream (which shall all be equal). If the
components vary in bit depth and/or sign, then the value of this field shall be 255 and the JP2 Header box shall also
contain a Bits Per Component box defining the bit depth of each component (as defined in Annex I.5.3.2).”
21)In Annex I.5.3.4, change "
I.5.3.4 Palette box
The palette specified in this box is applied to a single component to convert it into multiple components. The colourspace
of the components generated by the palette is then interpreted based on the values of the Colour Specification boxes in
the JP2 Header box in the file. The mapping of an actual component from the codestream through the palette is specified
in the Component Mapping box. If the JP2 Header box contains a Palette box, then it shall also contain a Component
Mapping box. If the JP2 Header box does not contain a Palette box, then it shall not contain a Component Mapping box.
The type of the Palette box shall be
...