1、 International Telecommunication Union ITU-T T.808TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 3(06/2008) SERIES T: TERMINALS FOR TELEMATIC SERVICES Still-image compression JPEG 2000 Information technology JPEG 2000 image coding system: Interactivity tools, APIs and protocols Amendment
2、3: JPIP extensions to 3D data Recommendation ITU-T T.808 (2005) Amendment 3 ITU-T T-SERIES RECOMMENDATIONS TERMINALS FOR TELEMATIC SERVICES Facsimile Framework T.0T.19 Still-image compression Test charts T.20T.29 Facsimile Group 3 protocols T.30T.39 Colour representation T.40T.49 Character coding T.
3、50T.59 Facsimile Group 4 protocols T.60T.69 Telematic services Framework T.70T.79 Still-image compression JPEG-1, Bi-level and JBIG T.80T.89 Telematic services ISDN Terminals and protocols T.90T.99 Videotext Framework T.100T.109 Data protocols for multimedia conferencing T.120T.149 Telewriting T.150
4、T.159 Multimedia and hypermedia framework T.170T.189 Cooperative document handling T.190T.199 Telematic services Interworking T.300T.399 Open document architecture T.400T.429Document transfer and manipulation T.430T.449 Document application profile T.500T.509 Communication application profile T.510T
5、559 Telematic services Equipment characteristics T.560T.649 Still-image compression JPEG 2000 T.800T.849 Still-image compression JPEG-1 extensions T.850T.899 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T T.808 (2005)/Amd.3 (06/2008) i INTERNATIONAL STANDARD ISO/
6、IEC 15444-9 RECOMMENDATION ITU-T T.808 Information technology JPEG 2000 image coding system: Interactivity tools, APIs and protocols Amendment 3 JPIP extensions to 3D data Summary Amendment 3 (2008) to Recommendation ITU-T T.808 (2005) | ISO/IEC 15444-9:2005 extends the fields in JPIP for use with 3
7、D and higher dimensional data. All fields related to the frame and region of the requested image are extended to multiple dimensions, as part of this amendment. This work item (ISO/IEC Project) was formerly referred to as “Amendment 4“. Subsequent to the renumbering of Amendment 3 approved in 2007
8、as Amendment 2 for publication purposes, all subsequent work items were renumbered by ISO/IEC JTC1 SC29 decreasing the numbering by one. Hence, the attached text went to the approval process as Amendment 3 (2008), in order to maintain the sequential numbering of attachments. Source Amendment 3 to Re
9、commendation ITU-T T.808 (2005) was approved on 13 June 2008 by ITU-T Study Group 16 (2005-2008) under Recommendation ITU-T A.8 procedure. An identical text is also published as ISO/IEC 15444-9, Amendment 3. ii Rec. ITU-T T.808 (2005)/Amd.3 (06/2008) FOREWORD The International Telecommunication Unio
10、n (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions an
11、d issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on the
12、se topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expr
13、ession “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicabil
14、ity) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Re
15、commendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability
16、 of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement thi
17、s Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced, by any means what
18、soever, without the prior written permission of ITU. Rec. ITU-T T.808 (2005)/Amd.3 (06/2008) iii CONTENTS Page 1) Subclause 3.3. 1 2) Subclause 3.4. 1 3) Subclause A.3.2.1. 1 4) Subclause C.4.1 1 5) Subclause C.4.1 2 6) Subclause C.4.5 3 7) Subclauses C.4.6 and C.4.7. 3 8) Subclause C.4.5 4 9) Subcl
19、ause C.4.7 4 10) Subclause C.4.11 4 11) Subclause D.2 4 ISO/IEC 15444-9:2005/Amd.3:2008 (E) Rec. ITU-T T.808 (2005)/Amd.3 (06/2008) 1 INTERNATIONAL STANDARD RECOMMENDATION ITU-T Information technology JPEG 2000 image coding system: Interactivity tools, APIs and protocols Amendment 3 JPIP extensions
20、to 3D data 1) Subclause 3.3 Add the following item: 3.3.23 slice: A subset of voxels in a volumetric image with constant Z coordinates. 2) Subclause 3.4 Add the following items: fz z-axis frame size for client request view-window fz z-axis frame size for suitable codestream resolution fz modified jp
21、x z-axis frame size for suitable resolution oz z-axis offset for client request view-window oz z-axis offset for suitable codestream/component region oz modified z-axis offset for suitable region sz z-axis size of client request view-window sz z-axis size for suitable codestream region sz modified j
22、px z-axis size for suitable region 3) Subclause A.3.2.1 After the third paragraph, add the following: For volumetric images encoded in JP3D (Rec. ITU-T T.809 | ISO/IEC 15444-10), the sequence number of precincts within a tile-component is computed as follows: All precincts of the lowest resolution l
23、evel, i.e., those containing only the L|XL|XL|X samples are sequenced first, starting from zero, following a raster scan order as defined by 3.11 of Rec. ITU-T T.809 | ISO/IEC 15444-10. The precincts from each successive resolution level are sequenced in turn, again following the raster scan order o
24、f 3.11. The precinct with sequence number 0 thus refers to the front most, upper left hand precinct of the lowest resolution sub-band of the image component 0 in tile 0. 4) Subclause C.4.1 Replace the third paragraph with: Codestream image regions are described using 3 n-dimensional parameters where
25、 n is the number of dimensions required to describe this image. The size parameters and offset parameters specify the extent and location of the desired codestream image region with respect to a whole image that has the given frame size. Figure C.1 demonstrates this set-up for regular images with n
26、 2, but the construction carries over naturally to a higher number of dimensions. For the rest of this subclause, we will consider only this case, naming the frame size fx and fy, the offset of the region ox and oy and its size sx and sy as indicated in Figure C.1. ISO/IEC 15444-9:2005/Amd.3:2008 (
27、E) 2 Rec. ITU-T T.808 (2005)/Amd.3 (06/2008) 5) Subclause C.4.1 At the end of C.4.1, add the following: The above considerations for two dimensional images carry over naturally to images of higher dimensionality, e.g., to the case n = 3 where a third coordinate is added to each group of parameters.
28、Specifically, the frame size is then represented by three numbers fx, fy and fz, the offset by ox, oy and oz and the region size by sx, sy and sz. In that case, Equation C-1 extends to: =rr2ZsizzZsi2ZOsizzZOsi where ZOsiz and Zsiz specify the original image offset and canvas size in the Z direction,
29、 respectively. Equation C-2 extends to: zofzzfoz)(szzsfzzfozzo += For images represented within Rec. ITU-T T.809 | ISO/IEC 15444-10 codestream, ZOsiz and Zsiz are taken from the relevant NSI marker segment. In addition, a server may choose to identify a Rec. ITU-T T.801 | ISO/IEC 15444-2 codestream
30、making use of wavelet transformations as a multi-component transformation with a volume image using generated components to represent the third (Z) dimension. The identification by which generated components constitute which slice is then at the discretion of the server, and so is the choice of suit
31、able values for ZOsiz and Zsiz. In this situation, clients may either choose to use the two-dimensional or three-dimensional request syntax to fetch data from the client. For two-dimensional requests, it is up to the client to identify slices with components and make the necessary requests; for thre
32、e-dimensional requests, it is the duty of the server to find the relevant components for the requested image volume. In the latter case, servers are not required to honour the comp and mctres fields, see C.4.5 and C.4.11, and their usage is discouraged in this case. Application Note: In case servers
33、 have to identify a Rec. ITU-T T.801 | ISO/IEC 15444-2 encoded image with volumetric data, they are recommended to use the following choices for ZOsiz and Zsiz to provide an efficient and consistent definition of resolution levels in the Z direction: ZOsiz shall be taken identical to the minimum of
34、all Omcci values in all MCC markers within the codestream identified by the request, see Annex A.3.8 of Rec. ITU-T T.801 | ISO/IEC 15444-2. This choice ensures a reasonable definition of the resolution levels in the Z direction compatible to the origin of the wavelet transformation, and eases the ex
35、traction of lower-resolution images from the stream. Zsiz is to be taken identical to the number of slices identified by methods described below plus ZOsiz as computed by the procedure above. It is recommended to use the following procedure to identify the generated components that make up a slice i
36、n case a Rec. ITU-T T.801 | ISO/IEC 15444-2 conforming file format is available for the target of the request: Identify all compositing layers of the file that use the codestream the request targets at. Each compositing layer in this set defines exactly one slice of the volumetric image. The Z coord
37、inate to be assigned to the first compositing layer in this set is to be ZOsiz, as defined above, and all following slices are assigned continuously ascending Z coordinates in the order they appear in the file. Within each compositing layer, scan for a channel definition box. If there is a channel d
38、efinition box, identify the channels that are associated to a colour by testing the Asoc field of the cdef box for that channel and perform the next step. Otherwise, apply the next step to all channels. Identify within the compositing layer the generated components providing the data for the channel
39、s found in the step above. For direct mapping, this is a 1:1 relation, but for palette mapped images, the component mapping box must be parsed. If no Rec. ITU-T T.801 | ISO/IEC 15444-2 conforming file format is available, other metadata outside the scope of this Recommendation | International Standa
40、rd might be available to identify which generated components define which slice. In this case, servers are expected to use whatever metadata is available and be consistent with the specifications made there. ISO/IEC 15444-9:2005/Amd.3:2008 (E) Rec. ITU-T T.808 (2005)/Amd.3 (06/2008) 3 In case no add
41、itional meta-data, neither inside 15444 nor outside of it, is available, the following algorithm can be used as a last resort to come to a reasonable definition of slices: A codestream is identified as grey scale volume image if each generated component is reconstructed by exactly one transformation
42、 stage in the sense of Annex J of Rec. ITU-T T.801 | ISO/IEC 15444-2, and if that type of the transformation stage is a wavelet transformation. A codestream is identified as colour volume image, if each generated component is reconstructed by exactly two transformation stages of which the first one,
43、 which is applied to the spatial components of the codestream, is a wavelet transformation, and of which the second one is not a wavelet transformation, but a decorrelation or dependency transformation. All other set-ups cannot be handled. The Z coordinate of the slice a generated component contribu
44、tes to is identified as follows: For generated component g, identify the MCC marker MCCithat describes the wavelet transformation step taken to compute g from the spatial components of the canvas system. According to the above definition, there should be exactly one such marker. If the image is a gr
45、ey-scale image, find the index j in the output component collection of that marker such that Wmccijequals g, i.e., find the output slot in the transformation generating this component. Then generated component g contributes then to the slice with Z = j + Omcci. This will define a Z coordinate for th
46、e component g based on the ordering of the output of the wavelet transformation step. For colour images, first identify all intermediate input components of the dependency or decorrelation transformation required to reconstruct the generated component g, and find for each of them its Z coordinate as
47、 described above. It is required that this Z coordinate does not depend on which of the intermediate components required to reconstruct generated component g has been chosen; otherwise, this algorithm fails. 6) Subclause C.4.5 Insert the following after C.4.4 and update the following subclause numbe
48、rs accordingly: C.4.5 Frame size for variable dimension data (fvsiz) fvsiz = “fvsiz“ “=“ 1#UINT “,“ round-direction round-direction = “round-up“ / “round-down“ / “closest“ This request takes a variable number of arguments. There shall be as many numerical arguments as there are dimensions in the sou
49、rce codestream. Specifically, if the image is a regular two-dimensional image, this request field is equivalent to the fsiz field with the first argument defining fx and the second defining fy. If the source stream represents volumetric data, there shall be three numerical arguments, specifying the view-window extents fx, fy and fz, in that order. This field is used to identify the resolution associated with the requested view-window. The numerical arguments specify
