ITU-T T 808 AMD 4-2010 Information technology C JPEG 2000 image coding system Interactivity tools APIs and protocols Amendment 4 JPIP server and client profiles (Study Group 16)《信息.pdf

《ITU-T T 808 AMD 4-2010 Information technology C JPEG 2000 image coding system Interactivity tools APIs and protocols Amendment 4 JPIP server and client profiles (Study Group 16)《信息.pdf》由会员分享，可在线阅读，更多相关《ITU-T T 808 AMD 4-2010 Information technology C JPEG 2000 image coding system Interactivity tools APIs and protocols Amendment 4 JPIP server and client profiles (Study Group 16)《信息.pdf（28页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T T.808TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 4(05/2010) 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、4: JPIP server and client profiles Recommendation ITU-T T.808 (2005) Amendment 4 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 codi

3、ng T.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

4、T.150T.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.429 Document transfer and manipulation T.430T.449 Document application profile T.500T.509 Communication application profile

5、T.510T.559 Telematic services Equipment characteristics T.560T.649 Still-image compression JPEG 2000 T.800T.829Still-image compression JPEG XR T.830T.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 (200

6、5)/Amd.4 (05/2010) i INTERNATIONAL STANDARD ISO/IEC 15444-9 RECOMMENDATION ITU-T T.808 Information technology JPEG 2000 image coding system: Interactivity tools, APIs and protocols Amendment 4 JPIP server and client profiles Summary Amendment 4 to Recommendation ITU-T T.808 (2005) | ISO/IEC 15444-9:

7、2005 defines the framework, concepts and methodology for establishing JPIP interoperability and the criteria to be achieved to claim compliance to Recommendation ITU-T T.808 | ISO/IEC 15444-9. This amendment defines JPIP profiles and variants. Profiles define the fields that a JPIP server is expecte

8、d to implement and support beyond parsing and interpretation; profiles also limit the requests a client can expect a server within this profile to support and fully implement. Variants define which features of the JPIP standard are used to request and transmit data between client and server. Servers

9、 are classified according to the highest level profile they support, and all the variants they implement. Clients are classified according to all the variants they implement, and according to the highest level profile they support. A new annex is also included in this amendment that defines a method

10、ology for testing compliance within the set of defined profiles and variants. Test data and scripts for JPIP testing are provided as an integral part of this amendment. This amendment has an electronic attachment containing test data and scripts for JPIP testing. This attachment is also available on

11、line from the ITU-T Test Signal Database at http:/itu.int/net/ITU-T/sigdb/speimage/Tseries-s.htm#T.808. History Edition Recommendation Approval Study Group 1.0 ITU-T T.808 2005-01-08 16 1.1 ITU-T T.808 (2005) Amend. 1 2006-05-29 16 1.2 ITU-T T.808 (2005) Cor. 1 2007-01-13 16 1.3 ITU-T T.808 (2005) A

12、mend. 2 2007-08-29 16 1.4 ITU-T T.808 (2005) Cor. 2 2008-06-13 16 1.5 ITU-T T.808 (2005) Amend. 3 2008-06-13 16 1.6 ITU-T T.808 (2005) Amend. 4 2010-05-22 16 ii Rec. ITU-T T.808 (2005)/Amd.4 (05/2010) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency i

13、n 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 and issuing Recommendations on them with a view to s

14、tandardizing 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 these topics. The approval of ITU-T Recommendations i

15、s 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 expression “Administration“ is used for conciseness to

16、 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 applicability) and compliance with the Recommendation is a

17、chieved 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 Recommendation is required of any party. INTELLECT

18、UAL 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 of claimed Intellectual Property Rights, whethe

19、r 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 this Recommendation. However, implementers are caut

20、ioned 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 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of

21、ITU. Rec. ITU-T T.808 (2005)/Amd.4 (05/2010) iii CONTENTS Page 1) Clause 2, Normative references 1 2) Clause 5.1 . 1 3) Clause C.2.4 . 1 4) Clause C.3.2 . 1 5) Clause L.1 . 1 6) Clause L.2 . 2 7) Clause 6.2 . 3 8) Clause 7 3 9) Clause 3.3 . 3 10) Clause 5.1 . 4 11) Clause 5.2 . 4 12) Clause A.3.6.2

22、4 13) Clause A.3.6.3 4 14) Clause C.1.1 . 5 15) Clause C.1.2 . 5 16) Clause C.2.1 . 5 17) Clause C.2.3 . 5 18) Clause C.3.5 . 6 19) Clause C.4.2 . 6 20) New clause C.5.2.10 . 6 21) Clause C.6.1 . 6 22) Clause C.7.1 . 7 23) Clause C.10.2.1 7 24) Clause C.10.2.2 7 25) Clause C.10.2.3 8 26) Clause C.10

23、.2.4 9 27) New clause C.10.2.8 . 9 28) Clause D.1.2 . 9 29) Clause D.1.3.5 10 30) New clause D.1.4 10 31) Clause D.2.2 . 10 32) Clause D.2.3 . 10 33) Clause D.2.6 . 10 34) Clause D.2.8 . 11 35) Clause D.2.9 . 11 36) Clause D.2.10 . 11 37) Clause D.2.23 . 11 38) New clause D.2.24 11 39) New clause D.

24、2.25 11 40) Clause D.3 11 41) New Annex J 12 iv Rec. ITU-T T.808 (2005)/Amd.4 (05/2010) Page Annex J Profiles and variants for interoperability and testing 12 J.1 Introduction . 12 J.2 Definition of variants 12 J.3 Definition of profiles . 13 J.4 Testing methodology . 15 42) Bibliography . 19 Electr

25、onic attachment = JPIP test data and scripts ISO/IEC 15444-9:2005/Amd.4:2010 (E) Rec. ITU-T T.808 (2005)/Amd.4 (05/2010) 1 INTERNATIONAL STANDARD RECOMMENDATION ITU-T Information technology JPEG 2000 image coding system: Interactivity tools, APIs and protocols Amendment 4 JPIP server and client prof

26、iles 1) Clause 2, Normative references Add the following reference to clause 2: Recommendation ITU-T T.803 (2002) | ISO/IEC 15444-4:2004, Information technology JPEG 2000 image coding system: Conformance testing. 2) Clause 5.1 a) Replace the definition of TOKEN by: TOKEN = 1*(ALPHA / DIGIT / “.“ / “

27、_“ / “-“) b) Add the following token at the end of the ABNF-rules: IDTOKEN = 1*(TOKEN / “;“) 3) Clause C.2.4 Replace the definition of the target-id by the following: target-id = IDTOKEN 4) Clause C.3.2 Replace the definition of the channel-id by the following: channel-id = IDTOKEN 5) Clause L.1 Add

28、 to the list of fields in L.1 the following: ;= ; C.4.5 Frame Size for Variable Dimension Data (fvsiz) ;= fvsiz = “fvsiz“ “=“ 1#UINT “,“ round-direction round-direction = “round-up“ / “round-down“ / “closest“ ;= ; C.4.7 Offset for Variable Dimension Data (rvoff) ;= rvoff = “rvoff“ “=“ 1#UINT ;= ISO/

29、IEC 15444-9:2005/Amd.4:2010 (E) 2 Rec. ITU-T T.808 (2005)/Amd.4 (05/2010) ; C.4.8 Region Size for Variable Dimension Data(rvsiz) ;= rvsiz = “rvsiz“ “=“ 1#UINT 6) Clause L.2 a) Replace the list of jpip-response headers by the following: jpip-response-header = / JPIP-tid ; D.2.2 / JPIP-cnew ; D.2.3 /

30、JPIP-qid ; D.2.4 / JPIP-fsiz ; D.2.5 / JPIP-rsiz ; D.2.6 / JPIP-roff ; D.2.7 / JPIP-fvsiz ; D.2.8 / JPIP-rvsiz ; D.2.9 / JPIP-rvoff ; D.2.10 / JPIP-comps ; D.2.11 / JPIP-stream ; D.2.12 / JPIP-context ; D.2.13 / JPIP-roi ; D.2.14 / JPIP-layers ; D.2.15 / JPIP-srate ; D.2.16 / JPIP-metareq ; D.2.17 /

31、 JPIP-len ; D.2.18 / JPIP-quality ; D.2.19 / JPIP-type ; D.2.20 / JPIP-mset ; D.2.21 / JPIP-cap ; D.2.22 / JPIP-pref ; D.2.23 / JPIP-align ; D.2.24 / JPIP-subtarget ; D.2.25 b) Add respectively the following items to the list of JPIP Response BNF: ;= ; D.2.8 Frame Size for Variable Dimension Data (J

32、PIP-fvsiz) ;= JPIP-fvsiz = “JPIP-fvsiz“ “:“ LWSP 1#UINT ;= ; D.2.9 Region Size for Variable Dimension Data(JPIP-rvsiz) ;= ISO/IEC 15444-9:2005/Amd.4:2010 (E) Rec. ITU-T T.808 (2005)/Amd.4 (05/2010) 3 JPIP-rvsiz = “JPIP-rvsiz“ “:“ LWSP 1#UINT ;= ; D.2.10 Offset for Variable Dimension Data (JPIP-rvoff

33、) ;= JPIP-rvoff = “JPIP-rvoff“ “:“ LWSP 1#UINT ;= ; D.2.24 Alignment (JPIP-align) ;= JPIP-align = “JPIP-align“ “:“ LWSP “yes“ / “no“ ;= ; D.2.25 Subtarget (JPIP-subtarget) ;= JPIP-subtarget = “JPIP-subtarget“ “:“ LWSP byte-range / src-codestream-specs 7) Clause 6.2 a) Replace the third point of the

34、second paragraph by the following: Annex C defines the client request syntax. The client shall produce compliant requests and the server shall be able to parse, interpret and respond to all compliant requests. b) Add the following to 6.2: Server and client conformance is further structured into prof

35、iles and variants. Profiles define which fields servers must support and implement beyond simply parsing and interpreting. Variants define the operating modes and features of the JPIP standard a client and server use to transmit data. Clients and servers must provide a common subset of variants in o

36、rder to interoperate. See Annex J for details about conformance and testing for conformance. 8) Clause 7 Change clause 7 to: Conformance with this Recommendation | International Standard by a client means that the clients JPIP requests are well structured, valid and conformant to the JPIP client req

37、uests as defined by this Recommendation | International Standard, and that it is able to parse the JPIP responses defined by this Recommendation | International Standard. Conformance with this Recommendation | International Standard by a server means that the servers JPIP responses are well structur

38、ed, valid and conformant to the JPIP server response signalling as defined by this Recommendation | International Standard, and is able to parse the JPIP requests defined by this Recommendation | International Standard. Servers shall parse and interpret all normative request types and shall respond

39、to all compliant requests. Compliance to a profile requires servers furthermore to support and implement all mandatory fields within that profile to the extent defined in Annex J. Conformance, profiles and conformance testing methodologies of this Recommendation | International Standard are defined

40、in Annex J. It is expected that server applications may reduce efficiency by sending additional data not explicitly requested for or redundant data depending on the network quality-of-service. Such implementation decisions are application specific and provide the JPIP system with high utility. 9) Cl

41、ause 3.3 Add the following definitions: 3.3.24 profile: Conformance is structured according to profiles; a profile defines the set of request fields that a server is expected to support and implement and a client communicating with a server in this profile may issue expecting the ISO/IEC 15444-9:200

42、5/Amd.4:2010 (E) 4 Rec. ITU-T T.808 (2005)/Amd.4 (05/2010) server to support them. A server is conforming to a profile if it supports and implements all request fields within this profile to the extent defined in Annex J. 3.3.25 variant: Variants define the operating modes and features of the JPIP s

43、tandard that a client and a server use to exchange requests and data. Clients and servers must provide a common subset of variants in order to interoperate. 10) Clause 5.1 In 5.1, delete the definition of ENCODED-CHAR, and insert the following definition instead, and replace all occurrences of ENCOD

44、ED-CHAR by OCTAL-ENCODED-CHAR: OCTAL-ENCODED-CHAR = “ QUADDIG OCTDIG OCTDIG QUADDIG = “0“ / “1“ / “2“ / “3“ OCTDIG = “0“ / “1“ / “2“ / “3“ / “4“ / “5“ / “6“ / “7“ 11) Clause 5.2 Replace all occurrences of ENCODED-CHAR by OCTAL-ENCODED-CHAR and replace the first paragraph of 5.2 by the following: box

45、-type specifies the four characters of the box type. For each character in the box type, if the character is alpha-numeric (AZ, az or 09), the character is written directly into the string. If the character is a space (040), then that character shall be encoded as the underscore character (“_“) or b

46、y octal encoding. For any other character, a 4-character string is written in its place, consisting of a backslash character (“) followed by three octal digits representing the value of the character from the box type in octal. The compatibility-code is encoded the same way that a box-type is encode

47、d. 12) Clause A.3.6.2 At the end of A.3.6.2, replace the example Figure A.10 by the following: 13) Clause A.3.6.3 a) After the last paragraph of A.3.6.3, add a Note: NOTE The above definition implies that the placeholder box may be truncated after the last used field, but intermediate fields, even if unused, must be present. b) In Table A.3, row five the description of