ANSI INCITS ISO IEC 12087-3-1995 Information Technology - Computer Graphics and Image Processing - Image Processing and Interchange (IPI) - Functional Specification - Part 3 Image .pdf

1、 INCITS/ISO/IEC 12087-3-1995 (R2001)(formerly ANSI/ISO/IEC 12087-3-1995 (R2001)for Information Technology -Computer Graphics andImage Processing -Image Processing andInterchange (IPI) -Functional Specification -Part 3: Image Interchange Facility (IIF)ANSI/ISO/IEC 12087-3-l 995 American National Stan

2、dard for Information Technology - Computer Graphics and Image Processing - Image Processing and Interchange (IPI) - Functional Specification - Part 3: Image Interchange Facility (IIF) Secretariat Information Technology Industry Council Approved September 6, 1996 American National Standards Institute

3、, Inc. AmericanNationalStandardApproval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgment of the ANSI Board of StandardsRevie

4、w, substantial agreement has been reached by directly and materiallyaffected interests. Substantial agreement means much more than a simplemajority, but not necessarily unanimity. Consensus requires that all views andobjections be considered, and that a concerted effort be made toward theirresolutio

5、n.The use of American National Standards is completely voluntary; their existencedoes not in any respect preclude anyone, whether he has approved the standardsor not, from manufacturing, marketing, purchasing, or using products, processes,or procedures not conforming to the standards.The American Na

6、tional Standards Institute does not develop standards and will inno circumstances give an interpretation of any American National Standard.Moreover, no person shall have the right or authority to issue an interpretation ofan American National Standard in the name of the American National StandardsIn

7、stitute. Requests for interpretations should be addressed to the secretariat orsponsor whose name appears on the title page of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that

8、 action be taken periodically to reaffirm, revise, or withdrawthis standard. Purchasers of American National Standards may receive currentinformation on all standards by calling or writing the American National StandardsInstitute.Published byAmerican National Standards Institute11 West 42nd Street,

9、New York, New York 10036Copyright 1996 by Information Technology Industry Council (ITI)All rights reserved.These materials are subject to copyright claims of International Standardization Organization (ISO),International Electrotechnical Commission (IEC), American National Standards Institute (ANSI)

10、, andInformation Technology Industry Council (ITI). Not for resale. No part of this publication may bereproduced in any form, including an electronic retrieval system, without the prior written permission of ITI.All requests pertaining to this standard should be submitted to ITI, 1250 Eye Street NW,

11、 Washington, DC20005.Printed in the United States of AmericaContents . . . Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13、 . . . . . . . . . . . . . . . . . . vi I Scope 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14、. . . . . . . . . . . . . . . . . . . . . . . . . 2 Normative references . 3 Definitions and abbreviations . 3. I Definitions . 3.2 Abbreviations . 4 The IPI-IIF architecture . 4. l The IPI-IIF Data Format and the IPI-IIF Gateway 4.2 Interworking between IPI-IIF Gateway and IPI-PIKS 5 The IIF data f

15、ormat (IIF-DF) . 5.1 Basic features of the IIF-DF 5.1.1 Objects that are expressed in the IIF-DF . 5.1.2 Syntax notation . 5.1.3 Encoding of syntax entities 5. I .4 Rules that are not formally expressed within the IIF syntax . 5.2 Structure of the IIF-DF syntax . 5.2.1 Overall structure 5.2.2 Image

16、structures . 5.2.3 Placement of pixel fields . 5.2.4 Encoding of pixel fields . 5.2.5 Attributes, annotations, and image-related data 5.3 Syntax entities of the IIF-DF . 5.3. I Entities for the description of the entire IIF-DF 5.3.2 Entities for the description of images 5.3.3 Entities for the descr

17、iption of the representation of pixel values 5.3.4 Entities for the description of image-related data 5.3.5 Entities for the description of image attributes 5.3.6 Entities for the description of image annotations 5.3.7 Entities for the description of basic data objects . 3 5 5 5 6 6 7 9 9 9 9 IO IO

18、II II 12 14 14 14 16 19 27 46 59 79 111 114 6 IPI-IIF Conformance . 121 6.1 Standardized profiles for the IIF-DF 121 6.1.1 Full PIKS profile of the IIF-DF . 122 6.1.2 Foundation profile of the IIF-DF . 125 6.2 Registered profiles for the IIF-DF . 128 6.2.1 Application-specific semantics 128 6.2.2 Co

19、nstraining methods 129 6.3 Extension methods . 130 7 IPI-IIF Gateway functionality . 131 7.1 Basic categories of IPI-IIF Gateway functions 131 7.1.1 Gateway control and error handling 7.1.2 Import and export functionality . 7.1.3 Parse and generate functionality 7.1.4 Data structure access functiona

20、lity 7.1.5 Data structure manipulation functionality . 7.1.6 Compression and decompression functionality . 7.1.7 Application-oriented functionality 7.2 IPI-IIF gateway-internal tables 7.3 Survey of IPI-IIF Gateway functions 7.4 IPI-IIF Gateway functionality by manual pages 7.5 PIKS-IIF interworking

21、protocol 131 132 132 133 134 134 137 137 138 139 _ 193 Annexes A List of IIF-DF syntax entities and component names (normative) . 194 B List of IPI-IIF Gateway function-caused errors (informative) . 208 C Typical IIF image interchange scenario (informative) . 210 D Examples of IIF-DF images (informa

22、tive) . 212 D. 1 Simple binary image . 213 D.2 Colour image with colourimetric attributes 214 D.3 Tiled image . 216 E Example program for the use of the IPI-IIF Gateway (informative) 218 F IIF-DF syntax diagrams (informative) 221 G Bibliography . 243 - Foreword (This foreword is not part of American

23、 National Standard ANSI/ISO/IEC 12087-3-1995. This document is identical to ISO/IEC 12087-3: 1995 and the following five paragraphs are the original fore- word as it appeared in that document.) IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commi

24、ssion) form the specialized system for worldwide standardization. National bodies that are members of IS0 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. IS0

25、 and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work. In the field of information technology, IS0 and IEC have established a joint technical committee, ISO

26、/IEC JTC 1. Draft International Standards adopt- ed 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. International Standard ISO/IEC 12087-3 was prepared by

27、Joint Technical Committee ISO/IEC JTC 1, information technology. ISO/IEC 12087 initially consists of three parts, under the general title Information technology - Computer graphics and image processing - Image Processing and Interchange (IPI) - Functional specification: - Part 1: Common architecture

28、 for imaging - Part 2: Programmers imaging kernel system application program interface - Part 3: Image interchange facility (/IF) Annex A forms an integral part of this part of ISO/IEC 12087. Annexes B to G are for information only. Requests for interpretation, suggestions for improvement or addenda

29、, or defect reports are welcome. They should be sent to the X3 Secretariat, Information Technology Industry Council, 1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922. This standard was processed and approved for submittal to ANSI by Accredited Standards Committee on Information Technology,

30、X3. Committee approval of the standard does not necessarily imply that all committee members voted for its approval. At the time it approved this standard, the X3 Committee had the following members: James D. Converse, Chair Donald C. Loughry, Vice-Chair Kate McMillan, Secretary Organization Represe

31、nted Name of Representative AMP, Inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ben Bennett Edward Kelly (Alt.) Apple Computer, Inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32、 . . . . . . . . . . . . . . . . . . . . . . . . . . . David K. Michael Jerry Kellenbenz (Alt.) AT the Message Oriented Text Interchange Systems (MOTIS), ISOlIEC 10021 (also known as Message Handling System (MHS), CCIlT Recommendation X.400). Thus the IIF data format could become part of application

33、-oriented OS1 communications protocols. Within the IIF data format (IIF-DF), compressed images may be specified and interchanged. For this purpose, the following standards are referenced: - CCITI Recs. T.4 and T.6 (Facsimile) - ISO/IEC 11544 (JBIG) - ISO/IEC 10918 (JPEG) - ISO/IEC 11172 (MPEG-I) Ima

34、ge data streams that conform to the encoded representation of compressed image data specified by these standards may be included in the IIF-DF. For instance, a time series image can be represented as an array of time slices, each of which is encoded according to the JPEG Standard. Furthermore, the I

35、IF-DF allows images to be represented through the combination of compressed parts with uncompressed parts. It is also possible to use multiple compression methods within a single IIF-DF-conformant image. For instance, a colour image can be represented as tiled images whereby some tiles are encoded a

36、ccording to the lossy mode of the JPEG Standard and others according to the lossless mode. For detailed information concerning compressed data streams and compression/decompression functionality, refer to 5.3.3 and 7.1.6, respectively. There are various possibilities for interaction and data exchang

37、e between the IPI-PIKS domain and the IPI- IIF domain. Both domains are controlled by the application via application program interfaces (APIs). For a detailed description of the interworking between the IPI-PIKS and the IPI-IIF refer to clause 4 (the IPI- IIF architecture) and clause 7 (the IPI-IIF

38、 Gateway functionality). For a description of the relation between the types of objects that may be interchanged by means of the IPI-IIF and those types of objects that may be processed by the IPI-PIKS, refer to clause 6 (the profiles for the IIF data format). Refer also to ISO/IEC 12087- 1. vi AMER

39、ICAN NATIONAL STANDARD ANSI/ISO/IEC 12087-3-1995 American National Standard for Information Technology - Computer Graphics and Image Processing - Image Processing and Interchange (IPI) - Functional Specification - Part 3: Image Interchange Facility (IIF) 1 Scope This part of ISO/IEC 12087 facilitate

40、s the interchange of digital images. For this purpose, conceptual, architectural, and functional definitions of the Image Interchange Facility (IPI-IIF) are established. ISO/IEC 12087-3 consists of two major parts, the: a) IIF data format (IIF-DF) definition (by means of a formal syntax, described a

41、ccording to the Abstract Syntax Notation One (ASN. 1) - refer to clause 5), and the b) IIF Gateway definition (by means of a manual page description of the functionality of an Application Program Interface (API) - refer to clause 7). An IPI-IIF-conformant implementation has to fulfill the functional

42、ity specification of the IIF Gateway, as outlined in clause 7. Besides the IIF Gateway, there may be information processing systems (software such as parsers, generators, etc.) which read an component images are accessed via an n-dimensional index. All the images stored in an array must have identic

43、al structures (including attributes, annotations, and image related data). The CompoundlmugeRecord entity is used to specify a record of images. The components are accessed via associated names, called component- identiers. In contrast to stays of images, the components are not required to have iden

44、tical image structures. The CompoundImugeList entity is used to specify a list of images of identical structure which are accessed via their position in the list. The CompoundImugeSet entity is used to specify a set of images of identical structure. The syntax of the ImageStructure entity is recursi

45、ve, i.e., the array elements, record components etc. are again of ImageStructure type. The FundumentuZImugeStructure entity specifies the structure and sequential organization of an n-dimen- sional multiband array of pixels, along with associated image-related data, such as look-up tables, histogram

46、s, etc. It and its sub-entities provide enough flexibility to specify a wide range of pixel periodicity arrangements (e.g. pixel interleaved, band interleaved, tiled images, etc.). This is specified primarily by the BandRecord and MetricArray entities as described below. The BandRecord entity is use

47、d to specify pixel arrays on a band-by-band basis; this entity is used to specify a band-interleaved image. The MetricArray entity is used to specify arrays of pixels or tiles. Pixels can be represented as a collection of bands in the PixelStructure entity. Thus, pixel-interleaved images are specifi

48、ed using a MetricArray of PixelStructures. The syntax of the MetricArray and BandRecord entities allow for arbitrary recursions. Thus, tiled images may be specified by constructing an array of arrays using the MetricArray entity for both hierarchical levels. Band-interleaved tiles are specified by a

49、 MetricArray containing BandRecords. Pixel-interleaved tiles are specified by a MetricArray containing MetricArrays. The recursive organization within the FundumentulImugeStructure entity is illustrated in Annex F. Entities specifying the structure of arrays in the IIF, such as MetricArrays and CompoundImageArruys, contain components specifying the number of dimensions of the array, the size of the array along each dimension, and a unique identifier for every dimension. The Serialization entity which is also part of every array description, indicates which axis varies fastest, second fas