ISO/IEC 24800-3:2010
(Main)Information technology — JPSearch — Part 3: Query format
Information technology — JPSearch — Part 3: Query format
ISO/IEC 24800-3:2010, also known as “JPSearch Query Format (JPQF)”, provides a standardized interface for image search and retrieval systems in three aspects - input query format, output result format and query management - as a specialization of ISO/IEC 15938-12:2008 for images and accompanying metadata. The top-level tools defined in ISO/IEC 24800-3:2010 are InputQuery, FetchResult, OutputResult and Management. Both InputQuery and FetchResult tools belong to input query format. 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 result sets through InputQuery. Through InputQuery, users can use queries of various types, such as query by media, query by description, query by free text, and combine them using algebraic or logical expressions. Through FetchResult, users can retrieve search results of a query from the past. When a query request is issued using the asynchronous mode, the FetchResult element is used to indicate the preparedness of the user to receive results. When a query request is issued using the synchronous mode, the FetchResult element is used to receive individual pages of the result set (if paging is activated). The OutputResult, which is 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 Management tool, which is the query management tool set, provides a means for selecting services (e.g. MPEG-7 database or Core Metadata services) or aggregated services (e.g. service provider that administers a set of different services) based on service properties (e.g. supported query format, supported metadata standard). 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. In the framework of JPSearch, the JPSearch Query Format is designed to be used as an interface between querying client and answering servers, as well as between aggregation service agent and individual service providers.
Technologies de l'information — JPSearch — Partie 3: Format d'interrogation
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 24800-3
First edition
2010-05-01
Information technology — JPSearch —
Part 3:
Query format
Technologies de l'information — JPSearch —
Partie 3: Format d'interrogation
Reference number
ISO/IEC 24800-3:2010(E)
©
ISO/IEC 2010
---------------------- Page: 1 ----------------------
ISO/IEC 24800-3:2010(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's 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 responsibility of not infringing Adobe's 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
parameters 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
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
ISO's member body in the country 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2010 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 24800-3:2010(E)
Contents Page
Foreword .v
Introduction.vi
1 Scope.1
2 Normative references.1
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 Introduction.6
5.2 Syntax.6
5.3 Semantics.7
5.4 Example.7
6 Datatypes.8
6.1 mimeType.8
6.2 MediaLocatorType.9
7 Tools of Input Query Format .9
7.1 Introduction.9
7.2 Syntax.10
7.3 Semantics.10
8 Expression Types.10
8.1 Introduction.10
8.2 Tools for Expression.11
9 Query Types.11
9.1 Introduction.11
9.2 Supported Query Types.12
10 Query By Media .12
10.1 Introduction.12
10.2 Syntax.12
10.3 Semantics.13
11 Query By ROI .13
11.1 Introduction.13
11.2 Syntax.14
11.3 Semantics.15
12 JoinType.15
12.1 Introduction.15
12.2 Syntax.15
12.3 Semantics.16
13 Tools of Output Result Format .16
14 Query Management Tools.16
14.1 Introduction.16
14.2 Syntax.16
© ISO/IEC 2010 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 24800-3:2010(E)
14.3 Semantics.17
15 Conformance.17
Annex A (normative) System Messages.18
A.1 Status messages.18
A.2 Warning messages .18
A.3 Exception messages .18
Annex B (normative) Classification Scheme.19
B.1 Introduction.19
B.2 ServiceCapabilityCS.19
B.3 SpatialRelationCS.22
B.4 BaseRelationCS.22
B.5 ScoringfunctionCS .23
B.6 DistancefunctionCS.23
iv © ISO/IEC 2010 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 24800-3:2010(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system 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 collaborate 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 Standards 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. Publication 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 patent 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:
⎯ Part 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 repositories
Reference software will form the subject of a future Part 6.
© ISO/IEC 2010 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 24800-3:2010(E)
Introduction
ISO/IEC 24800 aims to provide a standard for interoperability for still image search and retrieval systems.
There are many systems which provide image search 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 abstract 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 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 management 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
illustrates some non-normative examples.
vi © ISO/IEC 2010 – All rights reserved
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO/IEC 24800-3:2010(E)
Information 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 search 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 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.,
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 references
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 — Multimedia 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, abbreviated 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 semantics 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 the requester can express desired
output format that should be conformant to the specification of the output result format.
© ISO/IEC 2010 – All rights reserved 1
---------------------- Page: 7 ----------------------
ISO/IEC 24800-3:2010(E)
3.1.2
output result format
interface format going from the responder to the requester as a response to the request specified 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 required 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 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 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 EI 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 content’s metadata
XML tree.
3.1.9
segment
spatial, temporal, or spatio-temporal unit of multimedia
EXAMPLE A spatial segment of an image.
3.1.10
XPath-item
node from the multimedia content’s 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 content’s metadata may or may not be related to a
multimedia content’s segment. Also, a multimedia content or a multimedia content’s segment may or may not be related to
XML metadata. Within JPQF queries, XPath can be used to select a sequence of multimedia content’s segments and/or
metadata XPath-items. 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.
2 © ISO/IEC 2010 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 24800-3:2010(E)
3.2 Abbreviated terms
MPEG-7 ISO/IEC 15938
JPQF JPEG Query Format (ISO/IEC 24800-3)
URI Uniform Resource 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.
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:mpqf="urn:mpeg:mpqf:schema:2008"
targetNamespace="urn:jpeg:jpqf:schema:2008" elementFormDefault="qualified"
attributeFormDefault="unqualified">
4 Structure and data model
4.1 Structure
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 defined 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 output 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 querying and providing information regarding the service
description, service discovery and selection. The tools specifically serving these purposes are called
Management tools.
© ISO/IEC 2010 – All rights reserved 3
---------------------- Page: 9 ----------------------
ISO/IEC 24800-3:2010(E)
User Identifier Query Result
Personalization, history, profile, pre/post search
User Layer
housekeeping, and evaluation of results
Input Query Output Result
Query Layer
Query Expansion,
Query (Schema/Metadata) Conversion
Management
Input/Output
Input Query Output Result
Service Description, Service Discovery and Selection,
Management
Query Distribution with Access Control, Result
Layer
Aggregation
Input Query Output Result
Content Layer
Metadata Database / Image Database
Files in Metadata Embedded File Format
Metadata exchange between Repositories
Figure 1 — JPSearch architecture and scope of this part of ISO/IEC 24800
The JPEG Query Fomat is defined 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 Format
4 © ISO/IEC 2010 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 24800-3:2010(E)
Table 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 output 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 contain not only query results but also any
messages such as errors, exceptions or comments.
Management A set of tools for the query management defined for the JPEG Query Format
including service discovery, querying service capability, and service capability
description. The structure defined for the Management element provides a
container for Management Input Tools or the Management Output Tools.
Note that the Input and the FetchResult elements belong to the Input Query Format, which provides a
container for describing a query request (e.g., the query condition and/or the output description which
specifies the structure and content of the output result format).
The Management element of the JPEG Query Format represents the Query Management Tools of the Query
Format as defined in ISO/IEC 15938-12:2008. It describes a set of tools for the query management including
service discovery, querying service capability, and service capability description. Similar to the query tools
(Input Query Format and Output Result Format), the management part distinguishes the tools for the request
(Input Management Type) and the response (Output Management Type). Table 2 depicts the containing
elements in more detail.
Table 2 — Elements in Query Management Tools
Input
The Input element, which is defined for the management tools, is intended to be
sent from a requester to one or more responders.
Output
The Output element, which is defined for the management tools, is intended to
be sent from a responder to one requester.
4.2 Data model
Processing and evaluation of a JPFQ query is executed against one or more multimedia repositories. Note, all
introduced terms used within this Subclause are explained in 3.1.
JPQF assumes the same data model defined in 1.3 of ISO/IEC 15938-12:2008. For details of the data model,
refer to 1.3 of ISO/IEC 15938-12:2008.
© ISO/IEC 2010 – All rights reserved 5
---------------------- Page: 11 ----------------------
ISO/IEC 24800-3:2010(E)
5 Root Element
5.1 Introduction
The JPEGQuery element serves as the root element of the JPEG Query Format. The root element shall be
used as the topmost element in all messages transmitted. This applies on the one side to the input query
format and the output result format of a query request/response as well as on the other side to the query
management of the input/output.
5.2 Syntax
6 © ISO/IEC 2010 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC 24800-3:2010(E)
5.3 Semantics
Semantics of the JpegQueryType type:
Name Definition
JPEGQuery
Serves as the root element of the JPEG Query Format. The JPEGQuery element
shall be used as the topmost element in any instance of JPEG Query Format.
JPEGQueryType
Specifies the syntax of the root element. Within this element, either one of the
InputQuery, FetchResult or OutputResult element to specify the query and
search result, or one of the Input or Output element of the Management element
shall be instantiated, respectively.
InputQuery Wraps the user query specified using the Input Query Format, which is to be sent
from the requester to the responder.
FetchResult Allows the user to request the result of a previous query. In case of a query request
issued using the asynchronous mode (with the immediateResponse attribute of
the InputQueryType type set to false), the FetchResult element shall be used
to indicate the preparedness of the user to receive results. In case of a query
request issued using the synchronous mode, the FetchResult element shall be
used to receive individual pages of the result set (if paging is activated).
queryID The requester is looking for a the result of a certain identifier in asynchronous
mode. The attribute queryID specifies this identifier.
retrivePageNum Specifies the number of page the requester wants the responder to return
(optional). The default value is ‘1.’
OutputResult Wraps the responder response to a user query as described using the Output
Query Result Format. The OutputResult is sent from the responder to the requester.
Management Describes the Query Management tools which may be exchanged between
responders and requesters. Within this element only one of Input or Output
element shall be instantiated.
Input Wraps a user request for service capabilities.
Output Wraps the response to a user request for service capabilities.
jpqfID
Specifies a unique identifier which is assigned to every message sent between a
requester and a responder.
5.4 Example
The following examples show the use of the root element for the JPEG Query Format. The first three
examples demonstrate the use of the Query element. First, a user query request is simulated by using the
Input element. Note, that no details have been specified. Second, the result of a previous asynchronous
request is going to be fetched by the user. Finally, the result set of a query request is demonstrated by using
the Output element.
The last example shows the use of a service discovery request by using the Management element followed
by an Input element. In this case the response would contain a list of all available services which are
registered.
© ISO/IEC 2010 – All rights reserved 7
---------------------- Page: 13 ----------------------
ISO/IEC 24800-3:2010(E)
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.