ISO/IEC 15444-4:2002
(Main)Information technology — JPEG 2000 image coding system — Part 4: Conformance testing
Information technology — JPEG 2000 image coding system — Part 4: Conformance testing
ISO/IEC 15444-4:2002 specifies the framework, concepts, methodology for testing, and criteria to be achieved to claim compliance to ITU-T Recommendation T.800 | ISO/IEC 15444-1. It provides a framework for specifying abstract test suites and for defining the procedures to be followed during compliance testing. ISO/IEC 15444-4:2002 specifies compliance testing procedures for encoding and decoding using JPE 2000 Part 1 (ITU-T Recommendation T.800 | ISO/IEC 15444-1); specifies codestreams, decoded images, and error metrics to be used with the testing procedures; specifies abstract test suites; provides guidance for creating an encoder compliance test. ISO/IEC 15444-4:2002 does not include the following tests: Acceptance testing: the process of determining whether an implementation satisfies acceptance criteria and enables the user to determine whether or not to accept the implementation. This includes the planning and execution of several kinds of tests (e.g. functionality, quality, and speed performance testing) that demonstrate that the implementation satisfies the user requirements. Performance testing: measures the performance characteristics of an Implementation Under Test (IUT) such as its throughput, responsiveness, etc., under various conditions. Robustness testing: the process of determining how well an implementation processes data which contains errors.
Technologies de l'information — Système de codage d'image JPEG 2000 — Partie 4: Essais de conformité
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 15444-4
First edition
2002-11-01
Information technology — JPEG 2000
image coding system —
Part 4:
Conformance testing
Technologies de l'information — Système de codage d'image
JPEG 2000 —
Partie 4: Essais de conformité
Reference number
ISO/IEC 15444-4:2002(E)
©
ISO/IEC 2002
---------------------- Page: 1 ----------------------
ISO/IEC 15444-4:2002(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO/IEC 2002
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body
in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO/IEC 2002 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 15444-4:2002(E)
CONTENTS
Foreword. vii
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . v iii
1 Scope.1
2 References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
3 Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
5 Symbols.6
6 General description . . . . . . . . . . . . . . . . . . . . . . . . . . .7
6.1 Profiles and compliance classes. . . . . . . . . . . . . . . . . . . . .7
6.2 Decoders.8
6.3 Encodersand codestreams. . . . . . . . . . . . . . . . . . . . . . .8
6.4 Implementation compliance statement. . . . . . . . . . . . . . . . . . .8
6.5 Abstracttestsuites.8
6.6 Encoder compliancetesting procedure . . . . . . . . . . . . . . . . . . .8
6.7 Decodercompliancetesting procedure . . . . . . . . . . . . . . . . . . .9
7 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
8 Copyright.9
9 Compliance filesavailabilityandupdates. . . . . . . . . . . . . . . . . . . .9
AnnexA Decoder ComplianceClasses . . . . . . . . . . . . . . . . . . . . . . . .10
A.1 Compliance classparameter definitions. . . . . . . . . . . . . . . . . . .10
A.2 Compliance classdefinitions . . . . . . . . . . . . . . . . . . . . . .13
A.3 Lossless encoding and decoding . . . . . . . . . . . . . . . . . . . . .14
AnnexB Decoder ComplianceTesting Procedures. . . . . . . . . . . . . . . . . . . .15
B.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
B.2 Decodertestprocedure.15
AnnexC Compliance Tests . . . . . . . . . . . . . . . . . . . . . . . . . . .20
C.1 Abstracttest suite(informative). . . . . . . . . . . . . . . . . . . . .20
C.2 Executabletestsuite(ETS) .22
AnnexD Encoder Compliance Test Procedure . . . . . . . . . . . . . . . . . . . . . .30
D.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
D.2 Referencedecoder . . . . . . . . . . . . . . . . . . . . . . . . .30
D.3 Compliance requirement andacceptance. . . . . . . . . . . . . . . . . .30
D.4 Encoding compliance test procedure. . . . . . . . . . . . . . . . . . . .30
AnnexE Decoder ImplementationCompliance Statement . . . . . . . . . . . . . . . . . .33
E.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
E.2 Decoderimplementationcompliancestatement . . . . . . . . . . . . . . . .33
E.3 Extended support . . . . . . . . . . . . . . . . . . . . . . . . . .33
© ISO/IEC 2002 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 15444-4:2002(E)
AnnexF Encoder Implementation Compliance Statement . . . . . . . . . . . . . . . . . .37
F.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
F.2 Encoder description . . . . . . . . . . . . . . . . . . . . . . . . .38
AnnexG JP2File Format Reader Compliance Testing Procedure. . . . . . . . . . . . . . . .47
G.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
G.2 Compliance requirement andacceptance. . . . . . . . . . . . . . . . . .47
G.3 Readinga JP2 file compliance testprocedure . . . . . . . . . . . . . . . . .47
G.4 JP2fileformat test codestreams and images . . . . . . . . . . . . . . . . .48
iv © ISO/IEC 2002 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 15444-4:2002(E)
LISTOFFIGURES
FigureB-1 Decodercompliancetestflow chart . . . . . . . . . . . . . . . . . . . . . .15
FigureD-1 Encoder compliancetest block diagram . . . . . . . . . . . . . . . . . . . . .31
FigureG-1 JP2fileformat reader compliance test block diagram . . . . . . . . . . . . . . . . .48
© ISO/IEC 2002 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 15444-4:2002(E)
LISTOFTABLES
TableA-1 Definitions of complianceclasses(Cclass). . . . . . . . . . . . . . . . . . . .14
TableC-1 Class0 Profile0 referenceimagesand allowable errors. . . . . . . . . . . . . . . .23
TableC-2 ItemstestedbyProfile0codestreams.24
TableC-3 Profile 0codestream0 contents. . . . . . . . . . . . . . . . . . . . . . . .24
TableC-4 Class0 Profile1 referenceimagesand allowable errors. . . . . . . . . . . . . . . .26
TableC-5 ItemstestedbyProfile1codestreams.26
TableC-6 Class1 Profile0 referencefilesand maximumerror . . . . . . . . . . . . . . . . .27
TableC-7 Class1 Profile1 referenceimagesand allowable error . . . . . . . . . . . . . . . .29
TableE-1 ICSfor profilesand Cclass . . . . . . . . . . . . . . . . . . . . . . . . .33
TableE-2 Extended capabilitiesfor Cclass0. . . . . . . . . . . . . . . . . . . . . . .34
TableE-3 Extended capabilitiesfor Cclass1. . . . . . . . . . . . . . . . . . . . . . .35
TableE-4 Extended capabilitiesfor Cclass2. . . . . . . . . . . . . . . . . . . . . . .36
TableF-1 Encoder Implementation Marker Usage . . . . . . . . . . . . . . . . . . . . .37
TableF-2 Delimitingmarkersandmarkersegments. . . . . . . . . . . . . . . . . . . .39
TableF-3 Fixedinformation markersegments . . . . . . . . . . . . . . . . . . . . . .39
TableF-4 Functional marker segments . . . . . . . . . . . . . . . . . . . . . . . .41
TableF-5 Pointer marker segments. . . . . . . . . . . . . . . . . . . . . . . . . .45
TableF-6 Inbitstreammarkersandmarkersegments. . . . . . . . . . . . . . . . . . . .46
TableF-7 Informational marker segments. . . . . . . . . . . . . . . . . . . . . . . .46
TableG-1 JP2referenceimages and allowable error. . . . . . . . . . . . . . . . . . . .49
vi © ISO/IEC 2002 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 15444-4:2002(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the
specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the
development of International Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In
the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by
the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires
approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this part of ISO/IEC 15444 may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 15444-4 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 29,
Coding of audio, picture, multimedia and hypermedia information, in collaboration with ITU-T, but is not published as common
text at this time.
ISO/IEC 15444 consists of the following parts, under the general title Information technology — JPEG 2000 image coding
system:
— Part 1: Core coding system
— Part 2: Extensions
— Part 3: Motion JPEG 2000
— Part 4: Conformance testing
— Part 5: Reference software
— Part 6: Compound image file format
— Part 7: Guideline of minimum support function of ISO/IEC 15444-1
Annexes B and C form a normative part of this part of ISO/IEC 15444. Annexes A, D, E, F and G are for information only.
© ISO/IEC 2002 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO/IEC 15444-4:2002(E)
Introduction
ITU-TT.800|ISO/IEC15444-1isaspecificationthatdescribesanimagecompressionsystemthatallowsgreat
flexibility, not only for the compression of images but also for access into the codestream. The codestream provides a
number of mechanisms for locating and extracting portions of the compressed image data for the purpose of
retransmission,storage,display,orediting.Thisaccessallowsstorageandretrievalofcompressedimagedataappropriate
foragivenapplicationwithoutdecoding.
This Recommendation | International Standard provides the framework, concepts, and methodology for testing and the
criteriatobeachievedtoclaimcompliancetoITU-T T.800| ISO/IEC15444-1standard.Theobjectiveofstandardization
in this field is to promote interoperability between JPEG 2000 encoders and decoders and to test these systems for
compliance to this specification. Compliance testing is the testing of a candidate product for the existence of specific
characteristics required by a standard. It involves testing the capabilities of an implementation against both the
compliance requirementsin therelevant standard andthe statement of the implementation’scapability.
The purpose of this Recommendation | International Standard is to define a common test methodology, to provide a
framework for specifying abstract test suites (ATS), and to define the procedures to be followed during compliance
testing.
Any organization contemplating the use of test methods defined in this Recommendation | International Standard should
carefully consider the constraints on their applicability. Compliance testing does not include robustness testing,
acceptancetesting, and performancetesting.
viii © ISO/IEC 2002 – All rights reserved
---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO/IEC 15444-4:2002(E)
INFORMATIONTECHNOLOGY–
JPEG2000IMAGECODINGSYSTEM —
PART 4: CONFORMANCETESTING
1Scope
This Recommendation | International Standard specifies the framework, concepts, methodology for testing, and criteria
to be achieved to claim compliance to ITU-T Recommendation T.800 | ISO/IEC 15444-1. It provides a framework for
specifying abstract test suitesandfor defining the procedurestobefollowed duringcompliancetesting.
ThisRecommendation |InternationalStandard
— specifies compliance testing procedures for encoding and decoding using JPEG 2000 Part 1 (ITU-T
Recommendation T.800| ISO/IEC 15444-1);
— specifiescodestreams,decoded images,anderrormetricstobeusedwith thetesting procedures;
— specifiesabstracttest suites;
— providesguidancefor creating an encodercompliancetest.
ThisRecommendation |InternationalStandard doesnotincludethe following tests:
Acceptance testing: the process of determining whether an implementation satisfies acceptance criteria and enables the
usertodeterminewhether or not toaccept theimplementation.Thisincludestheplanning andexecutionof severalkinds
oftests(e.g.,functionality,quality,andspeed performance testing)thatdemonstratethatthe implementationsatisfiesthe
user requirements.
Performance testing: measures the performance characteristics of an Implementation Under Test (IUT) such as its
throughput,responsiveness,etc.,undervariousconditions.
Robustness testing: the processof determininghow well an implementation processesdatawhichcontains errors.
2References
The following references document the technical details and legal codestream syntax that serve as a basis for this
Recommendation | International Standard. At the time of publication, the editions indicated were valid. All
Recommendations and Standards are subject to revision, and parties to agreements based on this Recommendation |
International Standard are encouraged to investigate the possibility of applying the most recent edition of the
Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently valid
International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently valid
ITU-T Recommendations.
— ITU-T Recommendation T.800 | ISO/IEC 15444-1, Information technology — JPEG 2000 Image
Coding System.
— ITU-T Recommendation T.800 | ISO/IEC 15444-1 Amendment 1, Information technology — JPEG
2000ImageCoding System,Amendment 1.
— ITU-T Recommendation T.800 | ISO/IEC 15444-1 Amendment 2, Information technology — JPEG
2000ImageCoding System,Amendment 2.
1
© ISO/IEC 2002 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 15444-4:2002(E)
— ITU-T Recommendation T.800 | ISO/IEC 15444-1 Corrigendum 1, Information technology — JPEG
2000ImageCoding System.
— ITU-T Recommendation T.800 | ISO/IEC 15444-1 Corrigendum 2, Information technology — JPEG
2000ImageCoding System.
— ITU-T Recommendation T.800 | ISO/IEC 15444-1 Corrigendum 3, Information technology — JPEG
2000ImageCoding System.
3 Definitions
For the purposes of this Recommendation | International Standard, the following definitions apply. The definitions from
ITU-T T.800| ISO/IEC 15444-1clause3 also apply tothisRecommendation| International Standard.
3.1 abstracttestsuite: Genericcompliancetesting concepts and proceduresfor a givenrequirement.
3.2 arithmetic coder: An entropy coder that converts variable length strings to variable length codes (encoding)
and vice versa (decoding).
3.3 bigendian:Anorderofbyteswiththemostsignificantbytefirst.
3.4 bit:Acontraction ofthe term“binarydigit”;aunitofinformationrepresentedbya zero ora one.
3.5 bit-depth: Thenumber of bitsrequired torepresent anoriginal component of an image.
3.6 bit-plane: A two-dimensional arrayof bits.InthisRecommendation |InternationalStandardabit-planerefers
to all the bits of the same magnitude in all coefficients or samples. This could refer to a bit-plane in a component, tile-
component, code-block,regionof interest,or other.
3.7 bitstream:Theactual sequenceof bitsresultingfrom thecodingof asequenceofsymbols.It doesnotinclude
the markers or marker segments in the main and tile-part headers or the EOC marker. It does include any packet headers
and instreammarkersandmarkersegments notfoundwithinthemain ortile-partheaders.
3.8 box: A portion of the file format defined by a length and unique box type. Boxes of some types may
containotherboxes.
3.9 byte:Eightbits.
3.10 Cclass: Defines a level of performance for a decoder. Also provides guidance for encoders to produce
codestreams that are easilydecodable by compliant decoders.
3.11 code-block:Arectangulargroupingofcoefficientsfromthesame subbandofatile-component.
3.12 coder: An embodiment of either anencoding or decoding process.
3.13 codestream: A collection of one or more bitstreams and the main header, tile-part headers, and the EOC
required for their decoding and expansion into image data. This is the image data in a compressed form with all of the
signalling needed todecode. This doesnot includethe file format.
3.14 coding pass: A procedure accessing coefficients in a code-block where the context and bit are determined.
Typically there are 3 different coding passes for each bitplane, each coefficient will be represented in exactly one of the
three passes. For an encoder a coding pass examines coefficinets and agments a bitstream. For a decoder a coding pass
readsabitstream and updates coefficients.
3.15 coefficient: Thevaluesthat arethe result of atransformation.
3.16 component: A two-dimensional array of samples. An image typically consists of several components (e.g.,
red, green,andblue).
3.17 compressed image data:Partorallofacodestream.Canalsorefertoacollectionofbitstreamsinpartorall
of a codestream.
3.18 compliance: Fulfillment of the specified requirements, as defined in thisspecification, for a given Profileand
Cclass.
© ISO/IEC 2002 – All rights reserved
2
---------------------- Page: 10 ----------------------
ISO/IEC 15444-4:2002(E)
3.19 compliancetestprocedure:Theprocessofassessingcompliance.
3.20 context: Function of coefficients previously decoded and used to condition the decoding of the present
coefficient.
3.21 decoder: Anembodiment of adecoding process,and optionallyacolour transformationprocess.
3.22 decoding process: A process that takes as its input all or part of a codestream and outputs all or part of a
reconstructed image.
3.23 decompositionlevel:A collection ofwavelet subbands where each coefficienthas the same spatial impactor
span with respect to the source component samples. These include all subbands of the same two-dimensional subband
decomposition. For thelast decomposition level, theLL subbandisalso included.
3.24 discrete wavelettransformation(DWT): A transformation that iteratively transforms one signal into two or
more filtered and decimated signals corresponding to different frequency bands. This transformation operates on
spatiallydiscretesamples.
3.25 encoder: Anembodiment of an encodingprocess, and optionallya colour transformation process.
3.26 encodingprocess:Aprocessthattakesasitsinputallorpartofasourceimagedataandoutputsacodestream.
3.27 executabletestsuite:Set of executabletest casesthat support the abstract test cases.
3.28 fileformat: A codestream and additional support data and information not explicitly required for the
decoding of the codestream. Examples of such support data include text fields providing titling, security and historical
information, data to support placement of multiple codestreams within a given data file, and data to support exchange
betweenplatformsorconversiontootherfileformats.
3.29 fully decode: Applying ITU-T T.800 | ISO/IEC 15444-1 to produce an image from a codestream where all
codeddatainthecodestreamhasbeenusedtoproducetheimage.
3.30 guardbits:Additionalmostsignificantbitsthathave beenadded tosampledata.
3.31 header:Eitherapartofthecodestreamthatcontainsonlymarkersandmarkersegments(mainheaderandtile
part header) or the signalling part of apacket (packet header).
3.32 image: Thesetofallcomponents.
3.33 imagedata: The component samples making up an image. Image data can refer to either the source image
data orthe reconstructed image data.
3.34 implementation:Arealizationofaspecification.
3.35 Implementation Compliance Statement (ICS): Statement of specification options and the extent to which
they havebeen implementedbya implementationundertest.
3.36 ImplementationUnderTest(IUT):An implementationthatisbeingevaluated forcompliance.
3.37 irreversible: A transformation, progression, system, quantization, or other process that, due to systemic or
quantization error,prevents losslessrecovery.
3.38 JP2 file:Thenameofafileinthefileformatdescribedinthisspecification.Structurally,aJP2fileisa
contiguoussequence ofboxes.
3.39 JPEG: Joint Photographic Experts Group - The joint ISO/ITU committee responsible for developing
standards for continuous-tone still picture coding. It also refers to the standards produced by this committee: ITU-T.81 |
ISO/IEC 10918-1,ITU-T T.83| ISO/IEC 10918-2, ITU-T T.84 |ISO/IEC 10918-2and ITU-T T.87 |ISO/IEC 14495.
3.40 LL subband: The subband obtained by forward horizontal low-pass filtering and vertical low-pass filtering.
Thissubbandcontributestoreconstructionwithinverse vertical low-passfilteringandhorizontal low-passfiltering.
3.41 layer: A collection of compressed image data from coding passes of one, or more, code-blocks of a tile-
component. Layershave anorderforencodinganddecoding thatmustbepreserved.
3
© ISO/IEC 2002 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 15444-4:2002(E)
3.42 lossless: A descriptive term for the effect of the overall encoding and decoding processes in which the output
of thedecodingprocessisidentical to theinput to theencodingprocess.Distortion-free restorationcanbeassured.Allof
thecodingprocessesorstepsusedforencodinganddecoding arereversible.
3.43 lossy: A descriptive term for the effect of the overall encoding and decoding processes in which the output of
the decoding processis not identical to the input to the encodingprocess. There is distortion (measured mathematically).
Atleastoneofthecoding processesorstepsusedforencodinganddecoding is irreversible.
3.44 main header: A group of markers and marker segments at the beginning of the codestream that describe the
image parametersandcoding parametersthat can apply toevery tileand tile-component.
3.45 marker:Atwo-bytecodeinwhichthefirstbyteishexadecimalFF(0xFF)andthesecondbyteisavalue
between1(0x01)andhexadecimalFE(0xFE).
3.46 markersegment: A marker and associated(not empty) set of parameters.
3.47 packet:Apartofthecodestreamcomprisingapacketheaderandthecompressedimagedatafromonelayerof
oneprecinct of one resolution level of onetile-component.
3.48 packetheader:Portionof thepacket that containssignalling necessaryfor decodingthat packet.
3.49 parser:Readsandidentifiescomponentsofthecodestreamdown to the code-block level.
3.50 partialdecoding:Producinganimagefromasubsetofanentirecodestream.
3.51 precinct:Arectangularregionofatransformedtile-component,withineachresolutionlevel,usedforlimiting
thesize of packets.
3.52 precision: Number of bits allocated to a particular sample, coefficient, or other binary numerical
representation.
3.53 progression: The order of a codestream where the decoding of each successive bit contributes to a “better”
reconstruction of the image. What metrics make the reconstruction “better” is a function of the application. Some
examplesofprogressionare increasingresolutionorimproved sample fidelity.
3.54 profile: A subset of technology, from ITU-T T.800 | ISO/IEC 15444-1 Amendment 1, that meets the needs of
agivenapplicationwithlimitsonparameterswithinaselectedtechnology.Thisisacodestreamlimitation.
3.55 quantization: A method of reducing the precision of the individual coefficients to reduce the number of bits
used to represent them. This is equivalent to division while compressing and multiplying while decompressing.
Quantizationcanbeachievedbyanexplicitoperationwithagivenquantizationvalue(scalarquantization)orby
dropping (truncating) coding passesfrom thecodestream.
3.56 reconstructedimage:Animagethatistheoutputofadecoder.
3.57 reference grid: A regular rectangular array of points used to define other rectangular arrays of data. The
referencegrid isusedto determine thenumber of samples in tile-componentsfor example.
3.58 regionofinterest(ROI): A collection of coefficientsthat areconsidered of particular relevanceby some user
definedmeasure.
3.59 reversible: A transformation, progression, system, or other process that does not suffer systemic or
quantization errorandtherefore allowsforlosslesssignalrecovery.
3.60 reversiblefilter:Aparticularfilterpairusedinthewavelettransformationwhichallowslosslesscompression.
3.61 sample:One element in the two-dimensional arraythat comprisesacomponent.
3.62 selectivearithmeticcodingbypass:Acodingstylewheresomeof thecode-blockpassesarenotcodedbythe
arithmeticcoder. Instead,the bitstobecoded areappended directly to the bitstream without coding.
3.63 shift:Multiplicationordivisionofanumberbypowersoftwo.Divisionofanintegerviashiftimplies
truncationtowardminusinfinity of the non-integer portion.
3.64 signbit:Abitthatindicates whether anumberis positive (zero value)ornegative (one value).
4
© ISO/IEC 2002 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC 15444-4:2002(E)
3.65 sign-magnitudenotation: A binary representation of an integer where the distance from the origin is
expressedwithapositivenumberandthedirectionfromtheorigin(positiveornegative)isexpressedwithaseparate
single sign bit.
3.66 sourceimage:Animageusedasinputtoanencoder.
3.67 subband: A group of transform coefficients resulting from the same sequence of low-pass and high-pass
filtering operations, both vertically and horizontally.
3.68 testing: The processof evaluating compliance.
3.69 tile:Arectangulararrayofpointsonthereferencegrid,registeredwithanoffsetfrom thereferencegridorigin
and definedbya widthand height.
3.70 tile-component:Allthesamplesofagivencomponentinatile.
3.71 tile-part:Aportionofthecodestreamwithcompressedimagedataforsome,orall,ofatile.Thetile-partmay
includeoneor more packetsthat make up thecoded tile.
3.72 tile-part header: A group of markers and marker segments at the beginning of each tile-part in the
codestream that describethetile-part coding parameters.
3.73 transformation: A mathematical mapping from onesignal space to another.
3.74 transformcoefficient:Avaluethatis theresultofatransformation.
4 Abbreviations
For the purposes of this Recommendation | International Standard, the following abbreviations apply. The abbreviations
definedin ITU-T T.800| ISO/IEC 15444-1 subclause4.1also applyto this Recommendation |International Standard.
ATS:Abstract Test Suite
CCITT:InternationalTelegraph andTelephoneConsultativeCommittee,nowITU-T
ETS: ExecutableTest Suite
ICC: InternationalColorConsortium
ICT: IrreversibleColour Transformation
ICS: Implementation Compliance Statement
IEC: International Electrotechnical Commission
ISO: International Organizationfor Standardization
ITU: International Telecommunication Union
ITU-T: International Telecommunication Union – Telecommunication Standardization Sector (formerly the
CCITT)
IUT: Implementation Under Test
JPEG:Joint PhotographicExperts Group
MSE:MeanSquaredError
RCT:ReversibleColourTransformation
ROI:RegionOfInterest
TCS:Test Codestream
5
© ISO/IEC 2002 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 15444-4:2002(E)
5Symbols
For the purposes of this Recommendation | International Standard, the following symbols apply. The symbols defined in
ITU-T T.800| ISO/IEC15444-1subclause4.2also applyto thisRecommendation |InternationalStandard.
0x----:
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.