ITU-T T 808 AMD 1-2006 Information technology C JPEG 2000 image coding system Interactivity tools APIs and protocols Amendment 1 APIs metadata and editing (Study Group 16)《信息技术-JPE.pdf

1、 International Telecommunication Union ITU-T T.808TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1(05/2006) SERIES T: TERMINALS FOR TELEMATIC SERVICES Information technology JPEG 2000 image coding system: Interactivity tools, APIs and protocols Amendment 1: APIs, metadata and editing ITU-

2、T Recommendation T.808 (2005) Amendment 1 ITU-T Rec. T.808 (2005)/Amd.1 (05/2006) i INTERNATIONAL STANDARD ISO/IEC 15444-9 ITU-T RECOMMENDATION T.808 Information technology JPEG 2000 image coding system: Interactivity tools, APIs and protocols Amendment 1 APIs, metadata and editing Summary Amendment

3、 1 to ITU-T Rec. T.808 (01/2005) | ISO/IEC 15444-9:2005 adds support for JPIP over secure HTTP protocol (HTTPS), for serving JPM (15444-6) files over JPIP, and for serving Motion JPEG 2000 (15444-3) over JPIP. Using JPIP over HTTPS was a requirement for the DICOM medical imaging community. They are

4、in the process of adopting JPIP for image data transfers but often require transfers to be done over a secure channel, so HTTPS was a requirement for the inclusion of JPIP in the DICOM standard. The other two items simply define additional JPIP syntax and parameters for the efficient browsing of Mot

5、ion JPEG 2000 and JPM files over a networked connection. Source Amendment 1 to ITU-T Recommendation T.808 (2005) was approved on 29 May 2006 by ITU-T Study Group 16 (2005-2008) under the ITU-T Recommendation A.8 procedure. An identical text is also published as ISO/IEC 15444-9, Amendment 1. ii ITU-T

6、 Rec. T.808 (2005)/Amd.1 (05/2006) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical,

7、operating and tariff questions and 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 tur

8、n, produce Recommendations on these 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

9、 In this Recommendation, the expression “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.

10、g. interoperability or applicability) 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 su

11、ggest that compliance with the Recommendation 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 ev

12、idence, validity or applicability 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

13、 may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2006 All rights reserved. No part of this publication may be reproduced, by any means wha

14、tsoever, without the prior written permission of ITU. ITU-T Rec. T.808 (2005)/Amd.1 (05/2006) iii CONTENTS Page 1) Subclause 5.1. 1 2) Annex C.5.1 1 3) Annex C.2.1 2 4) Annex C.3.3 2 5) Annex C.4.7 2 6) Annex F.1 . 4 7) Annex F.3 . 4 ISO/IEC 15444-9:2005/Amd.1:2006 (E) ITU-T Rec. T.808 (2005)/Amd.1

15、(05/2006) 1 INTERNATIONAL STANDARD ITU-T RECOMMENDATION Information technology JPEG 2000 image coding system: Interactivity tools, APIs and protocols Amendment 1 APIs, metadata and editing 1) Subclause 5.1 Add after TOKEN definition: TEXT-LABEL = DQUOTE TOKEN DQUOTE 2) Annex C.5.1 Replace the last s

16、entence: This Recommendation | International Standard does not advise on what constitutes the implicit MJ2 metadata for view-window requests, however, this may be defined in a future standard. with: For MJ2 files, the following metadata elements shall be considered to be requested along with the vie

17、w-window: JP2 signature (“jP“) File type (“ftyp“) “mvhd“ For tracks that are relevant with the view-window request: “tkhd“ edts0. Only the TBox field is useful, and a placeholder signals that no access is provided to the original content of the box. “mdhd“ “hdlr“ “vmhd“ if present in the original MJ

18、2 file. “stsd“ “stts“ either: a placeholder for “stco“ or “stco64“ (depending on which of them is present in the original MJ2 file) indicating that the content of the box is provided by one or more incremental codestreams; or the entire “stsc“, “stsz“ and “stco“ or “stco64“ boxes. ISO/IEC 15444-9:20

19、05/Amd.1:2006 (E) 2 ITU-T Rec. T.808 (2005)/Amd.1 (05/2006) 3) Annex C.2.1 Rewrite the 3rd sentence of the 3rd paragraph as follows (with the changes underlined): If the Target field is not specified and the request is carried over HTTP (or HTTPS), then the JPIP request shall be directed to the reso

20、urce specified through the path component of the JPIP request URL. 4) Annex C.3.3 Rewrite the 1st sentence of the second paragraph as follows (with the changes underlined): The value string identifies the names of one or more transport protocols that the client is willing to accept. This Recommendat

21、ion International Standard defines only the transport names, “http“, “https“ and “http-tcp,“ although it is anticipated that other transports, such as “udp“, may be defined elsewhere. 5) Annex C.4.7 a) Rewrite line 2 as follows (new portions underlined): context-range = jpxl-context-range / mj2t-con

22、text / jpm-context / reserved-context b) Add the following after the line beginning “reserved context“: jpm-context = “jpmp“ “ jpm-objects jpm-pages = jpm-page-collection “:“ jpm-sampled-range jpm-objects = “ jpm-object-range “ jpm-page-collection = object-id jpm-sampled-range = page-object-range “:

23、“ sampling-factor page-object-range = 1#(object-id “-“ object-id ) jpm-object-range = UINT-RANGE “:“ jpm-object-type / UINT-RANGE /“:“ jpm-object-type jpm-object-type = “mask“ / “image“ / “nostrm“ object-id = UINT / TEXT-LABEL c) Rewrite the first line of paragraph 4 as follows (with the changes und

24、erlined): This Recommendation | International Standard defines two three specific types of context-range, which are intended to address the needs of the JPX and MJ2, MJ2, and JPM file formats. d) Add the following after the paragraph beginning “NOTE 2“: The third type of context-range described by t

25、his Recommendation | International Standard, jpm-context, allows clients to request specific layout objects from a JPM file. The simplest usage allows a request to be made for all the items needed to render a single page. More complex usage allows only some of the layout objects or only one type of

26、object to be requested. The jpm-context always contains a request for specific pages, it may also contain a specification for page collections, a list of layout objects, and object types. If jpm-context has no jpm-page-collection item then the main page collection is assumed. If TEXT-LABEL is specif

27、ied in the jpm-page-collection item it must correspond to a label of a page collection box in the target JPM file. If UINT is specified in the jpm-page-collection item it indicates the page collection box in that position in file, where page collection boxes are numbered from 0. A range of pages is

28、a required part of the jpm-context. The page range could be “0-“ which would specify all the pages in the page collection. Pages are numbered by following the page collections and pages in the JPM file, and assigning the number 0 to the first page in a depth first tree walk. The root of the tree is

29、given by the jpm-page-collection item or the main page collection if no jpm-page-collection is part of the request. Loops in the page collection tree should be detected and an error condition returned. If a “sampling-factor“ is used as part of the jpm-sampled-range, the client desires pages starting

30、 with the first number in each range, and less than or equal to the last number in the range, and at all integer multiples of the sampling-factor plus the initial page number. Thus two sampling ranges it is possible to request even and odd number pages using a sampling-factor of 2, by starting each

31、range with an even or odd number. If the jpm-context has no jpm-object-range item then it is considered to be “1-“ which corresponds to all objects on the page except the thumbnail. If the thumbnail image for a page is needed then the jpm-object-range item shall ISO/IEC 15444-9:2005/Amd.1:2006 (E) I

32、TU-T Rec. T.808 (2005)/Amd.1 (05/2006) 3 include zero. The jpm-object-range indicates which of the layout objects on all pages in the jpm-page-range are requested. If the jpm-context has no jpm-object-type then all types are used. If the jpm-object-type is “mask“ only mask objects are of interest fo

33、r the request. If the jpm-object-type is “image“ only image objects are of interest. If the jpm-object-type is “nostrm“ then boxes for both mask and image are of interest. If the jpm-context parameter appears in a request without a Frame Size request (fsiz) then the Frame Size values fx and fy are s

34、et to the page width and page height. If the jpm-context parameter appears in a request without a Region Size request (rsiz) then the Region Size values rx and ry are set to the frame size values fx and fy (after fx and fy have been set to the page width and height if necessary). When the jpm-contex

35、t parameter is used, the requested corresponds to the view-window applied to each page independently. The Frame Size values fx and fy are mapped to the page width and height as specified by the Pwidth and Pheight elements of the Page Header Box of the JPM standard ISO/IEC 15444-6. A layout object wi

36、thin a page is considered part of the request if and only if all of the following are true: ox = LHoff oy = LVoff where: ox = ox * Pwidth / fx oy = oy * Pheight / fy sx = sx * Pwidth / fx sy = sy * Pheight / fy and fx, fy, ox, oy, sx, and sy are from the view window requests, LHoff, LVoff, LHeight,

37、and LWidth are from the Layout Object Header Box of 15444-6. Layout object 0 is reserved for a thumbnail image of the page, it should be considered part of the request regardless of the view-window if and if 0 is included in jpm-object-range. The client is considered to have requested any codestream

38、 associated with the mask or image which intersects the view-window unless jpm-object-type is “nostrm“. If the codestream is not compressed with JPEG 2000 then the request is for the complete codestream. If the codestream is compressed with JPEG 2000 then an equivalent view-window can be determined

39、for the specific codestream by mapping the request window on the page to the request window on the object as follows: fx = fx * Lwidth / Pwidth fy = fy * Lheight / Pheight ox = MAX( ox - LHoff * fx / Pwidth , 0) oy = MAX( oy - LVoff * fy / Pheight, 0) sx = MIN ( ox + sx - LHoff * fx / Pwidth, Lwidth

40、 * fx / Pwidth) - ox sy = MIN ( oy + sy - LVoff * fy /Pheight, Lheight * fy / Pheight) - oy Note that it may be necessary to issue a frame-size request with values larger than the width and height of the page in order to obtain a full resolution JPEG 2000 codestream if the JPEG 2000 file contains da

41、ta at a higher resolution than the page. Alternatively, the client could determine the codestream number and issue a request directly on that codestream with a view-window chosen appropriately. e) Add after EXAMPLE 2: EXAMPLE 3: “context=jpmp1-3:mask“ In this case, the server is requested to return

42、all data corresponding to mask objects in the first three layout objects on the pages 0, 2, 4, 6, 8, 10, 21, 23, 25, 27, and 29. This request includes all boxes necessary to render the desired region, e.g. Page Boxes, Layout Object Boxes, as well as any codestreams referenced by those objects. f) Ad

43、d the following: For JPM files, the following metadata elements shall be considered to be requested along with the view-window: JP2 signature (“jP“) File type (“ftyp“) Compound Image Header (“mhdr“) ISO/IEC 15444-9:2005/Amd.1:2006 (E) 4 ITU-T Rec. T.808 (2005)/Amd.1 (05/2006) Page Collection box (“p

44、col“) Page Table box (“pagt“) Page box (“page“) For pages that are relevant with the view-window request: Page Header box (“phdr“) Layout Object box (“lobj“) Layout Object Header box (“lhdr“) Object box (“objc“) Object Header box (“ohdr“) Object Scale box (“scal“) Base Colour box (“bclr“) 6) Annex F

45、.1 Rewrite the 2nd sentence of the second paragraph as follows (with the changes underlined): Note that the text and examples in this annex describe the use of JPIP over HTTP. It is expected that tThe same binding canshall be used for secure HTTP (or HTTPS). 7) Annex F.3 Rewrite the section as follo

46、ws (with the changes underlined): A session-based HTTP (or HTTPS) session is established by using the New Channel request field with a value of “http“ (or “https“), i.e., “cnew=http“ (or “cnew=https“) as part of a request. This request is typically delivered by HTTP (or HTTPS). The request may conta

47、in a view-window request that becomes the first request in the new channel. The response to this request is returned on the same connection as the request was made. A client may open an HTTP (or HTTPS) connection and issue a request which includes the HTTP (or HTTPS) header “Connection: keep-alive“.

48、 This is useful for efficient sessions, but it is neither necessary nor sufficient to have a session. A single HTTP (or HTTPS) connection may be used for traffic for different targets, different channels, or even non-JPIP traffic, e.g. requests for HTML files. A JPIP request that is part of a sessio

49、n may arrive on HTTP (or HTTPS) connections other than the HTTP (or HTTPS) connection used to request and issue the new channel, although this is discouraged. Printed in Switzerland Geneva, 2006 SERIES OF ITU-T RECOMMENDATIONS Series A Organization of the work of ITU-T Series D General tariff principles Series E Overall network operation, telephone service, service operation and human factors Series F Non-telephone telecommunication services Series G Transmission systems and media, di