1、 Reference number ISO/IEC 24800-3:2010(E) ISO/IEC 2010INTERNATIONAL STANDARD ISO/IEC 24800-3 First edition 2010-05-01 Information technology JPSearch Part 3: Query format Technologies de linformation JPSearch Partie 3: Format dinterrogation ISO/IEC 24800-3:2010(E) PDF disclaimer This PDF file may co
2、ntain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsi
3、bility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation p
4、arameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2010
5、 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the count
6、ry of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2010 All rights reservedISO/IEC 24800-3:2010(E) ISO/IEC 2010 All rights reserved iiiContents Page Forew
7、ord .v Introductionvi 1 Scope1 2 Normative references1 3 Terms, definitions, abbreviated terms and conventions.1 3.1 Terms and definitions .1 3.2 Abbreviated terms.3 3.3 Conventions.3 4 Structure and data model .3 4.1 Structure.3 4.2 Data model.5 5 Root Element.6 5.1 Introduction6 5.2 Syntax.6 5.3 S
8、emantics.7 5.4 Example7 6 Datatypes8 6.1 mimeType.8 6.2 MediaLocatorType.9 7 Tools of Input Query Format 9 7.1 Introduction9 7.2 Syntax.10 7.3 Semantics.10 8 Expression Types10 8.1 Introduction10 8.2 Tools for Expression.11 9 Query Types.11 9.1 Introduction11 9.2 Supported Query Types12 10 Query By
9、Media .12 10.1 Introduction12 10.2 Syntax.12 10.3 Semantics.13 11 Query By ROI .13 11.1 Introduction13 11.2 Syntax.14 11.3 Semantics.15 12 JoinType.15 12.1 Introduction15 12.2 Syntax.15 12.3 Semantics.16 13 Tools of Output Result Format 16 14 Query Management Tools.16 14.1 Introduction16 14.2 Syntax
10、.16 ISO/IEC 24800-3:2010(E) iv ISO/IEC 2010 All rights reserved14.3 Semantics.17 15 Conformance17 Annex A (normative) System Messages.18 A.1 Status messages18 A.2 Warning messages 18 A.3 Exception messages .18 Annex B (normative) Classification Scheme19 B.1 Introduction19 B.2 ServiceCapabilityCS19 B
11、.3 SpatialRelationCS22 B.4 BaseRelationCS.22 B.5 ScoringfunctionCS 23 B.6 DistancefunctionCS.23 ISO/IEC 24800-3:2010(E) ISO/IEC 2010 All rights reserved vForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized sys
12、tem for worldwide standardization. National bodies that are members of ISO 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. ISO and IEC technical committees c
13、ollaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Stand
14、ards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publicatio
15、n as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such pat
16、ent rights. ISO/IEC 24800-3 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information. ISO/IEC 24800 consists of the following parts, under the general title Information technology JPSearch: Pa
17、rt 1: System framework and components Part 2: Registration, identification and management of schema and ontology Part 3: Query format Part 4: File format for metadata embedded in image data (JPEG and JPEG 2000) The following part is under preparation: Part 5: Data interchange format between image re
18、positories Reference software will form the subject of a future Part 6. ISO/IEC 24800-3:2010(E) vi ISO/IEC 2010 All rights reservedIntroduction ISO/IEC 24800 aims to provide a standard for interoperability for still image search and retrieval systems. There are many systems which provide image searc
19、h and retrieval functionality on computer desktops, on the World Wide Web (i.e., websearch), on imaging devices, and in other consumer and professional applications. Existing systems are implemented in a way that tightly couples many components of the search process. ISO/IEC 24800 provides an abstra
20、ct framework search architecture that decouples the components of image search and provides a standard interface between these components. Aligning image search system design to this standard framework facilitates the use and reuse of metadata; the use and reuse of profiles and ontologies to provide
21、 a common context for searching; and the provision of a common query language to easily search across multiple repositories with the same search semantics. It allows image repositories to be independent of particular system implementations; and allows users to easily move or upgrade their image mana
22、gement applications or to move to a different device or upgrade to a new computer. This part of ISO/IEC 24800 contains the tools of the JPEG Query Format (JPQF) as an adaptation for the still images domain of ISO/IEC 15938-12:2008. It addresses the normative aspects of the Query Format and also illu
23、strates some non-normative examples. INTERNATIONAL STANDARD ISO/IEC 24800-3:2010(E) ISO/IEC 2010 All rights reserved 1Information technology JPSearch Part 3: Query format 1 Scope This part of ISO/IEC 24800, also known as “JPSearch Query Format (JPQF)”, provides a standardized interface for image sea
24、rch and retrieval systems in three aspects: Input Query Format, Output Result Format, and Query Management. The Input Query Format provides users/systems with a set of precise input parameters to describe their search criteria in addition to a set of preferred output parameters to depict the return
25、result sets. The Output Result Format provides users/systems with a set of output parameters to describe the aggregated return result sets for user presentation or machine consumption. The Query Management provides a means for selecting services (e.g., MPEG-7 database) or aggregated services (e.g.,
26、service provider that administers a set of different services) based on service properties (e.g., supported query format). The goal is to define a query language that provides the industry with a standardized format to accept and respond to user/system specification for image searches. 2 Normative r
27、eferences The following referenced documents are indispensable the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 15938-12, Information technology Mu
28、ltimedia content description interface Part 12: Query format XQuery 1.0 and XPath 2.0 Data Model (XDM). W3C Recommendation, 23 January 2007. http:/www.w3.org/TR/xpath-datamodel/ XML Path Language (XPath) 2.0. W3C Recommendation, 23 January 2007. http:/www.w3.org/TR/xpath20/ 3 Terms, definitions, abb
29、reviated terms and conventions 3.1 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1.1 input query format interface format going from a requester to one or more responders with two functionalities: 1) provision of a combination of syntax and sema
30、ntics of the interface, through which the requester assigns search criteria and associated data; 2) provision of syntax and semantics of the interface, through which the requester specifies the format of the result data NOTE The second functionality of the input query format provides tools by which
31、the requester can express desired output format that should be conformant to the specification of the output result format. ISO/IEC 24800-3:2010(E) 2 ISO/IEC 2010 All rights reserved3.1.2 output result format interface format going from the responder to the requester as a response to the request spe
32、cified by the input query format NOTE Output Result Format defines all possible structures of return from responder to the requester. The structure of an actual return is decided by OutputDescription element in Input Query Format. 3.1.3 query management tools tools to support the functionality requi
33、red to manage the query transaction between the requesters and the responders NOTE The query management tools do not include tools that are supported by network protocols. The query management tools are intended to be network agnostic and media agnostic. 3.1.4 multimedia content coded representation
34、 of the information contained in or related to a multimedia resource in a formalized manner suitable for interpretation by human means 3.1.5 content data and the associated metadata 3.1.6 multimedia resource URI identifiable portion of raw data of an image in JPEG format, which is associated with a
35、MIME Content- Type 3.1.7 metadata data expressed as a schema valid XML instance to carry additional information describing a multimedia resource, where the schema defines the information model of the data 3.1.8 evaluation item EI unit against which the query condition is tested NOTE By default, an E
36、I is a multimedia content of the multimedia repository, but other types of EI are also possible: a multimedia content; a segment of a multimedia resource; and an XPath-item related to the multimedia contents metadata XML tree. 3.1.9 segment spatial, temporal, or spatio-temporal unit of multimedia EX
37、AMPLE A spatial segment of an image. 3.1.10 XPath-item node from the multimedia contents metadata XML tree or an atomic value NOTE Details about the different types of nodes and atomic values can be found in the W3C Recommendation on XQuery 1.0 and XPath 2.0 Data Model. An XPath-item of a multimedia
38、 contents metadata may or may not be related to a multimedia contents segment. Also, a multimedia content or a multimedia contents segment may or may not be related to XML metadata. Within JPQF queries, XPath can be used to select a sequence of multimedia contents segments and/or metadata XPath-item
39、s. According to the W3C Recommendation on XQuery 1.0 and XPath 2.0 Data Model, a sequence is an ordered collection of zero or more XPath-items. ISO/IEC 24800-3:2010(E) ISO/IEC 2010 All rights reserved 33.2 Abbreviated terms MPEG-7 ISO/IEC 15938 JPQF JPEG Query Format (ISO/IEC 24800-3) URI Uniform Re
40、source Identifier (IETF Standard is RFC 2396) URL Uniform Resource Locator (IETF Standard is RFC 2396) XML Extensible Markup Language (W3C, http:/www.w3.org/XML/) 3.3 Conventions The Syntax defined in this part of ISO/IEC 24800 assumes the following Schema Wrapper. 4 Structure and data model 4.1 Str
41、ucture As shown in Figure 1, JPSearch architecture is conceptually divided into four layers, which are User Layer, Query Layer, Management Layer and Content Layer. The interfaces marked with rounded pink boxes are within the scope of this part of ISO/IEC 24800. Data flow between each layer is define
42、d as Input Query and Output Result. Where the nature of the data flow is requesting information, it is defined as Input Query and when the nature of the data flow is returning data upon a request, it is defined as Output Query. This part of ISO/IEC 24800 defines the format for input queries and outp
43、ut results which are used not only between the user layer and the query layer, but also between all other layers, as defined in the architecture, so that each layer of the JPSearch system can be implemented and maintained in a distributed way. This part of ISO/IEC 24800 also defines the messages for
44、 querying and providing information regarding the service description, service discovery and selection. The tools specifically serving these purposes are called Management tools. ISO/IEC 24800-3:2010(E) 4 ISO/IEC 2010 All rights reservedInput Query Output Result User Layer Query Layer Management Lay
45、er Content Layer Query E xpansion, Query (Schema/Metadata) Conversion Service Description, Service Discovery and Selection, Query Distribution with Access Control, R esult Aggregation M etadata Dat abase / Image Database Files in Metadata E mbedded File Format Metadata exchange between R epositories
46、 User Identifier Query Re su l t Input Query Output Result Personalization, history, profile, pre/post search housekeeping, and evaluation of results Management Input/ Output Input Query Output ResultFigure 1 JPSearch architecture and scope of this part of ISO/IEC 24800 The JPEG Query Fomat is defin
47、ed as the complex type of element named JPEGQuery. The JPEGQuery contains a choice of InputQuery, FetchResult, OutputResult, and Management elements. This simplified structure of the JPEGQuery element is depicted in Figure 2. Figure 2 Schema overview of the uppermost elements of the JPEG Query Forma
48、t ISO/IEC 24800-3:2010(E) ISO/IEC 2010 All rights reserved 5Table 1 explains these four elements in more detail: Table 1 Top-Level JPEGQuery elements InputQuery The InputQuery element provides a container for describing a query request. Such a request can consist of a query condition and/or the outp
49、ut description which specifies the structure and content of the output result format and/or some declaration parts. FetchResult The FetchResult element is also part of the Input Query Format. It allows the user to request the results of a previous query issued using e.g., the asynchronous mode. OutputResult The OutputResult element describes the Output Result Format. It provides a container for output result returned from servers or returned from lower layers of the JPSearch architecture. It may conta
