CAN CSA-ISO IEC 12087-3A-2001 Information Technology - Computer Graphics and Image Processing - Image Processing and Interchange (IPI) - Functional Specification - Part 3 Image Int.pdf

1、Amendment 1:2001 toNational Standard of CanadaCAN/CSA-ISO/IEC 12087-3-01Amendment 1:1996 to International Standard ISO/IEC 12087-3:1995has been adopted without modification as Amendment 1:2001 toCAN/CSA-ISO/IEC 12087-3-01. This Amendment was reviewed by theCSA Technical Committee on Information Tech

2、nology (TCIT) under thejurisdiction of the Strategic Steering Committee on InformationTechnology and deemed acceptable for use in Canada. March 2001INTERNATIONAL STANDARD ISO/IEC 12087-3 First edition 1995-02-I 5 AMENDMENT 1 1996-l 2-l 5 Information technology - Computer graphics and image processin

3、g - Image Processing and Interchange (IPI) - Functional specification - Part 3: Image Interchange Facility (IIF) AMENDMENT 1: Type definition, scoping, and logical views for image interchange facility Technologies de I in formation - lnfographie et traitemen t de Iimage - Traitemen t et kchange de /

4、image (/PI) - Spkification fon ctionnelle - Partie 3: Accessoires pour / No. 426 NonStandardizedIHS IIF syntax entity No. 427 Primaries IIF syntax entity No. 428 CIExyCoordinate IIF syntax entity No. 429 NonStandardizedCMY IIF syntax entity No. 430 NonStandardizedCM YK IIF syntax entity No. 43 1 Non

5、StandardizedNBarzd IIF syntax entity No. 432 ColourBand IIF syntax entity No. 433 TestColow IIF syntax entity No. 434 PIKSControl Entities for the description of image annotations IIF syntax entity No. 501 ImageAnnotation*) IIF syntax entity No. 502 Location Entities for the description of basic dat

6、a objects IIF syntax entity No. 601 BasicDataObject IIF syntax entity No. 602 BasicDataTlTpe*) IIF syntax entity No. 603 CompoundDataTpe*) IIF syntax entity No. 604 BasicArray IIF syntax entity No. 605 BasicRecord IIF syntax entity No. 606 BasicRecordComponerlt IIF syntax entity No. 607 BasicList II

7、F syntax entity No. 608 BasicSet IIF syntax entity No. 609 ElementaryDataTpe *) 5.3.8 Entities for the description of segmentation facility * IIF syntax entity No. 901 Segmen tProlog IIF syntax entity No. 902 SegmentEpilog IIF syntax entity No. 903 SegmentA ttributes 6 0 ISO/IEC ISO/IEC 12087-3:1995

8、/Amd.l:1996(E) 5.3.9 Entities for the description of segment types *) IIF syntax entity No. 904 IIF syntax entity No. 905 IIF syntax entity No. 906 IIF syntax entity No. 907 IIF syntax entity No. 908 IIF syntax entity No. 909 IIF syntax entity No. 910 IIF syntax entity No. 911 IIF syntax entity No.

9、912 IIF syntax entity No. 9 13 IIF syntax entity No. 914 IIF syntax entity No. 915 IIF syntax entity No. 9 16 NamedItems ImageStructureDefn ImageRelatedDataDefn ImageA ttributeDefn ImageAnnotationDefn BasicDataObjectDefn SegmentTypesDefn ExpressionElement A ttributeoccurence StructureDefn OccurenceD

10、efn RepeatElement StructureElement 5.3.10 Entities for the description of reference mechanism *) IIF syntax entity No. 917 IIF syntax entity No. 918 IIF syntax entity No. 919 IIF syntax entity No. 920 IIF syntax entity No. 921 IIF syntax entity No. 922 IIF syntax entity No. 923 IIF syntax entity No.

11、 924 IIF syntax entity No. 925 IIF syntax entity No. 926 IIF syntax entity No. 927 IIF syntax entity No. 928 IIF syntax entity No. 929 IIF syntax entity No. 930 IIF syntax entity No. 931 IIF syntax entity No. 932 IIF syntax entity No. 933 IIF syntax entity No. 934 EntityHandle ImageStructureLabeI Im

12、ageRelatedDataLabel ImageA ttributekbel ImageAnnotationLabel BasicDataTJTpeLabel SegmentLabel SegmentTypeLabel Label ImageStructureRef ImageRelatedDataRef ImageA ttributeRef ImageAnnotationRef BasicDataTJjpeRef SegmentTypeRef SegmentRef ExternalRefIndex ImageDataRef ISO/IEC 12087-3:1995/Amd.l:1996(E

13、) 0 ISO/IEC Replace the syntax entity 004 by the following: IIF syntax entity No. 004 Profile Semantics The PI-ofiZe entity stands for the description of profiles, specifying that the IIF-DF is restricted to a certain subset. One of the following predefined conformance profiles may be chosen: full p

14、rofile, fidU PKS profile, and foundation profile. For a definition of these profiles refer to clause 6. Additional application profiles are subject to registration as defined in 6.2. While application-profile constraints the conformance-profile by “linguistic” means, assuming that specific name is k

15、nown to the IIF Gateway, or to the application, the same is achieved by profile-definition, pointing to the formal definition how data types shall be used in the current IIF data stream, or simply, giving a “generic example” of what is allowed inside the conformance-profile. The profile-definition c

16、an be therefor considered as generic logical structure of a given IIF data stream. Both application-profile and profile-definition may constrain the range implied by conformance-profile, but never extend it. Syntax Profile := CHOICE application-profile IA5String, profile-definition SegmentTypeRef 1

17、- No. 722 - No. 931 Constraints For the Profile entity, only the values Ifull profile”, lfull PIKS profile”, and youndation projile” and values which have been internationally registered are permitted. Refer to 6.2. A generic logical structure can be either defined with help of the profile-definitio

18、n component referencing directly to an external data repository containing definition of segment type that models the structure of an IIF data stream, or this definition shall be taken from type-guide component in ContentsHeader entity 0 ISOIIEC ISO/IEC 12087-3: 199YAmd.l: 1996(E) IIF syntax entity

19、No. 005 ContentsHeader Semantics The ContentsHeuder entity provides some common information about the contents of the IIF data stream. No further semantics are defined for the convention of the title, owner, date-and-time, and message components. Also, no semantics are defined for the application-da

20、ta component which can be represented using any ASN.1 tY Pe. The externaLreferences component describes the sources of data which are outside of the current IIF data stream. The access-information component provides additional information which will facilitate random access to the content of the cur

21、rent IIF data stream. It points to the specification of an external file in the list of external references. The type-guide component is a pointer to an external data repository from which the default attributes are inherited and from which type definitions can be referenced. NOTE - Information fiel

22、ds, such as “processing platform” or “acquisition process” are regarded as too application- specific to be included in this header as a separate entity. This kind of information can either be put into the message field as readable text or handled as an image annotation or image attribute (using eith

23、er one of the built-in fields or a freeform field). EXAMPLE - The application-data component (as well as any other component that is typed with the ASN. 1 type ANY) could be structured by an application in the following way: ApplicationData . -= SET OF . . SEQUENCE tag 0 IMPLICIT INTEGER, value l IM

24、PLICIT OCTET STRING Syntax ContentsHeader := SEQUENCE C title 0 CharacterString OPTIONAL, owner 1 CharacterString OPTIONAL, date-and-time 2 GeneralizedTime OPTIONAL, message 3 CharacterString OPTIONAL, - No. 006 - No. 006 - No. 724 - No. 006 application-data WI ANY OPTIONAL, external-references 5 IM

25、PLICIT SEQUENCE OF ExternalReference OPTIONAL, - No. 211 access-information 6 IMPLICIT ExternalRefIndex OPTIONAL, - No. 927 type-guide 7 IMPLICIT ExternalReference OPTIONAL - No. 211 Constraints The type-guide component shall be present if profile-definition component in Profile entity does not spec

26、ify an external data repository. In specification of EntityHandle in the type-guide component the segment-handle option should be applied. 9 ISO/IEC 12087.3:1995/Amd.l:1996(E) 0 ISO/TEC IIF syntax entity No. 008 IIF syntax entity No. 009 Contents and ContentsElement Semantics The Contents entity con

27、sists of a sequence of ContentsElement entities. The ContentsEZetnent entity provides a sequence of prolog, ho - the image-related data component contains data that conform to one of the image-related data types as defined in ISO/IEC 12087- 1. - the image-attributes component contains data that conf

28、orm to one of the attribute types as defined in ISOIIEC 12087- 1. - the image-annotations component contains data that conform to one of the attribute types as defined in ISO/IEC 12087- 1. - the basic-data-component contains data that are structured according to a basic data type as defined in ISOII

29、EC 12087- 1. - the contents-element provides a recursion because its subentities refer back to the ContentsBody entity. According to the constraint given below, this recursion is prohibited. The only reason for incorporating the contents-element component into the syntax is to prepare the introducti

30、on of a hierarchical type definition and validity space concept that may be given in a separate Ammendment to this International Standard. Image annotations and image-related data are provided in two ways: bound to images, using the corresponding subentities within the Image entity, or separate from

31、 images using the ContentsBody entity as stated above. The latter way allows for the exchange of non-iconic parameters from and to the IPI-PIKS without any image data. Syntax ContentsBody := CHOICE 1 image VI Image, image-related-data l ImageRelatedData, image-attribute 2 ImageAttribute, image-annot

32、ation 3 ImageAnnotation, basic-data-object 4 BasicDataObject, contents-element 5 ContentsElement 1 - No. 101 - No. 301 - No. 401 - No. 501 - No. 601 - No. 009 Constraints None. ISO/IEC 12087-3:1995/Amd.l:1996(E) 0 ISO/IEC IIF syntax entity No. 102 ImageStructure Semantics The ImageStructure entity s

33、tands for the description of IPI-IIF data types as defined in ISO/IEC 12087- 1. The image data type can be either a compound-structure or a ftindamentaZ-structure. NOTES 1 The following fields of the “representation attribute”, defined in ISO/IEC 120874, are represented in the IIF-DF by the ImageStr

34、ucture entity and its subentities: image size, barId data type, image structure code. 2 This entity and its subentities do not contain pixel values. They are used to specify the structure of image data according to the data types defined in ISOAEC 12087-l. (The pixel values are contained in theRefer

35、ence a data field that is partitioned into a number of equal-sized portions, given by the subdivided-data- wit component; a reference to a ReferencedUnit entity which is stored remotely, given by the external-data-unit component, or a remote data set, which is specified as entity-index component by

36、an index into the list of externaz-references in the header of the current IIF data stream For the description of the partitioning concept refer to the SubdividedData referral scheme to external data sets refer to the ExternalReference entity. Syntax DataUnit . l = CHOICE e * Unit entity. For the de

37、scri ption of the single-data-unit 0 SingleDataUnit, - No. 204 subdivided-data-unit l SubdividedDataUnit, - No. 203 external-data-unit 2 ExternalReference, - No. 211 external-ref-index 3 ExternalRefIndex - No. 927 Constraints See subenti ties. 15 ISO/IEC 120873:1995/Amd.l: 1996(E) 0 ISO/IEC IIF synt

38、ax entity No. 211 ExternalReference and IIF syntax entity No. 212 ExternalAddress Semantics The ExternalReference entity supports a referral mechanism to an externally stored data set within a heterogeneous and distributed computing environment. NOTE - Within ISO/IEC 12087, this mechanism is exclusi

39、vely used to refer to a field of pixel values that is not present within the current data stream. The object-address entity is used to describe the address of the external object. Both local environments (e.g., file names in a UNIX file system) and heterogeneous, distributed environments (e.g., addr

40、esses of objects that may be obtained via ftp) are supported. The object-format component allows for a description of the format of the externally stored data set. This is done by a unique identifier of the grammar. If this component is absent, the external data portion shall be interpreted as a Ref

41、erencedUnit entity, according to the IIF-DF syntax. The object-internal-id component is an optional component which may be used to identify a specific object part within the object specified by the object-address component (e.g., by giving a byte offset that points from the top of the file to the be

42、ginning of the valid data). A concrete interpretation of this component may be specified within an application profile. Application profiles are subject to registration, as defined in 6.2. The entity-address component is an optional component which allows to constrain the refernced data to either a

43、specific segment and its nested segments if the referenced data is an IIF data stream, or to an application specific information quanta if referenced data set is structured otherwise. The ExternaZAddress entity provides two alternatives for the representation of an external object address. The struc

44、tured-address component provides a unique location and name of the external object, according to ISO/IEC 1003 1, Distributed Office Application Model (DOAM), Part 2: Distinguished Object Reference (DOR). The cLeartext-address component may be used for an informal representation. A concrete interpret

45、ation of this component may be specified within an application profile. Application profiles are subject to registration, as defined in 6.2. Syntax ExternalReference := SEQUENCE object-address 0 ExternalAddress, - No. 212 object-format l IMPLICIT OBJECT IDENTIFIER OPTIONAL,- No. 706 object-internal-

46、id 2 IMPLICIT CharacterString OPTIONAL,- No. 006 entity-address 3 IMPLICIT EntityHandle OPTIONAL - No. 917 ExternalAddress := CHOICE structured-address LoI DO% cleartext-address l IMPLICIT CharacterString - No. 802 - No. 006 Constraints None. 16 0 ISOIIEC ISO/IEC 1208703:1995/Amd.l: 1996(E) IIF synt

47、ax entity No. 301 ImageRelatedData Semantics The ImageRelatedData entity stands for the description of image-related data, as defined in ISO/IEC 12087- 1. The following types of image-related data are provided: match point, look-up table, histogram, region of interest, neighbourhood, and feature lis

48、t. The identifier component is used to associate the image-related data with those parts of an image structure which have the same identifier. The usage component allows for a verbal description of the way the image-related data type is used. The types of image-related data named above are given by

49、the histogram, look-up-table, region-of-interest, neighbourhood-array, static array, feature-list, value-bounds-collection, matrix, pixel-record, tuple, and referenced-data components. Instead of explicitly specifying one of these types, the ImageRelatedData entity may also reference the desired type (via an image-related data reference) from the name space of the current segment or from the name space provided by an external address. The data-required component is usable in the specification of