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

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

General Information

Status
Withdrawn
Publication Date
23-Jan-2002
Withdrawal Date
23-Jan-2002
Current Stage
9599 - Withdrawal of International Standard
Completion Date
23-Sep-2004
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 15444-1:2000/Cor 1:2002
English language
5 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL STANDARD ISO/IEC 15444-1:2000
TECHNICAL CORRIGENDUM 1
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 1
Technologies de l'information — Système de codage d'image JPEG 2000 —
Partie 1: Système de codage de noyau
RECTIFICATIF TECHNIQUE 1
Technical Corrigendum 1 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.1:2002(E)
©  ISO/IEC 2002 – All rights reserved
Printed in Switzerland

---------------------- Page: 1 ----------------------
ISO/IEC 15444-1:2000/Cor.1:2002(E)
INFORMATION TECHNOLOGY – JPEG 2000 IMAGE CODING SYSTEM –
PART 1: CORE CODING SYSTEM
TECHNICAL CORRIGENDUM 1
1) In the List of Figures (p. viii, Figure I-12) change
“Channel Definition box”
to
“Component Mapping box”
2) In subclause A.1.3 (p. 14), add to the end of the list of rules
— Some marker segments have values assigned to groups of bits within a parameter. In some cases there
are bits, denoted by “x,” that are not assigned a value for any field within a parameter. The codestream
shall contain a value of zero for all such bits. The decoder shall ignore these bits.
3) In subclause A.5.1 (p. 26, Ssiz description) change
(Ssiz AND 0x7F)-1 (Ssiz AND 0x7F)-1
“-2 ≤ component sample value ≤ 2 - 1”
to
(Ssiz+1 AND 0x7F)-1 (Ssiz+1 AND 0x7F)-1
“-2 ≤ component sample value ≤ 2 - 1”
4) In subclause A.6.1 (Table A-13, p. 30, seventh row) change
“EPH marker may be used”
to
“EPH marker shall be used”
5) In subclause A6.6 (Table A-32, p. 43, sixth and seventh row) change
i
16 0 — 65 534
LYEpoc
i i
8
REpoc RSpoc — 33
to
i
16 1 — 65 535
LYEpoc
i i
8
REpoc (RSpoc + 1) — 33
6) In subclause A.6.6 (Table A-32, p. 43, eighth row, CEpoc value) change
i
“CSpoc — 255; if Csiz < 257
i
CSpoc — 16 383; Csiz ≥ 257”
to
i
“(CSpoc + 1) — 255, 0; if Csiz < 257
i
(CSpoc + 1) — 16 384; Csiz ≥ 257
(0 is interpreted as 256)”
©  ISO/IEC 2002 – All rights reserved   1

---------------------- Page: 2 ----------------------
ISO/IEC 15444-1:2000/Cor.1:2002(E)
7) In subclause A.8.2 (p. 53, Usage first and second paragraph) change
“Usage: Optionally used in the bit stream or in the PPM or PPT marker segments. Shall only be used if indicated in
the proper COD marker segment (see Annex A.6.1). Appears immediately after a packet header.
If EPH markers are allowed (by signalling in the COD marker segment, see Annex A.6.1), each packet header in any
given tile-part may or may not be postpended with an EPH marker segment (see Annex A.8.1). If the packet headers
are moved to a PPM or PPT marker segments (see Annex A.7.4 and Annex A.7.5), then the EPH markers may appear
after the packet headers in the PPM or PPT marker segments.”
to
“Usage: Shall be used if and only if indicated in the proper COD marker segment (see Annex A.6.1). Appears
immediately after a packet header.
If EPH markers are required (by signalling in the COD marker segment, see Annex A.6.1), each packet header in any
given tile-part shall be postpended with an EPH marker segment. If the packet headers are moved to a PPM or PPT
marker segments (see Annex A.7.4 and Annex A.7.5), then the EPH markers shall appear after the packet headers in
the PPM or PPT marker segments.”
8) In subclause B.6 (Equation B.16, p. 64) change
trx trx try try
1 0 1 0
numprecinctswide = – numprecintshigh = –
---------- ---------- ---------- ----------
PPx- PPx- PPy- PPy-
2 2 2 2
to
trx trx try try
 
1 0 1 0
– trx > trx – try > try
---------- ---------- ---------- ----------
 1 0  1 0
- - - -
PPx PPx PPy PPy
numprecinctswide = numprecintshigh =
 2 2  2 2
 
0 trx = trx 0 try = try
 
1 0 1 0
and add to the beginning of the next paragraph
“Even if Equation B.16 indicates that both numprecinctswide and numprecinctshigh are nonzero, some, or all,
precincts may still be empty as explained below.”
9) In subclause B.11 (p. 74, sixth paragraph) change
“If EPH markers are allowed (by signalling in the COD marker segment, see Annex A.6.1), each packet header in any
given tile-part may be postpended with an EPH marker segment (see Annex A.8.1). If the packet headers are moved to
a PPM or PPT marker segments (see Annex A.7.4 and Annex A.7.5), then the EPH markers may appear after the
packet headers in the PPM or PPT marker segments.”
to
“If EPH markers are required (by signalling in the COD marker segment, see Annex A.6.1), each packet header in any
given tile-part shall postpended with an EPH marker segment (see Annex A.8.2). If the packet headers are moved to a
PPM or PPT marker segments (see Annex A.7.4 and Annex A.7.5), then the EPH markers shall appear after the packet
headers in the PPM or PPT marker segments.”
10)In subclause B.12.1.3 (p. 76, fifth equation) change
PPy()r, i + N – r
L
“if (y = ty or y divisible by YRsiz()i ⋅ 2 )”
0
to
PPy()r, i + N ()i – r N ()i – r
L L
“if ((y divisible by YRsiz()i ⋅ 2 ) OR ((y = ty) AND (try ⋅ 2 NOT divisible by
0 0
PPy()r, i + N ()i –r
L
2 ))”
©  ISO/IEC 2002 – All rights reserved
2

---------------------- Page: 3 ----------------------
ISO/IEC 1544
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.