ISO/IEC 24800-6:2012
(Main)Information technology — JPSearch — Part 6: Reference software
Information technology — JPSearch — Part 6: Reference software
ISO/IEC 24800-6:2012 describes reference software for the normative clauses as well as utility software demonstrating the usage scenarios of ISO/IEC 24800-2 to ISO/IEC 24800-5. The information provided is applicable for the reference software modules available for ISO/IEC 24800-2 to ISO/IEC 24800-5 and helps users of ISO/IEC 24800 to understand functionality and usage of ISO/IEC 24800 and software. Each software module provided in ISO/IEC 24800-6:2012 can be used either as standalone software or as a part of larger integrated software depending on the module. This suite of software contains four independent running software modules: Metadata Translation Module for ISO/IEC 24800-2; JPQF Query Processor Module for ISO/IEC 24800-3; Embedded Metadata Codec Module for ISO/IEC 24800-4; Repository Import/Export Module for ISO/IEC 24800-5. The Metadata Translation Module allows users to translate metadata instances from/to one of MPEG-7, Dublin Core and JPSearch Core metadata. The JPQF Query Processor Module checks the syntactic and semantic validity of JPQF queries and allows users to search and retrieve from the provided small-size example metadata file. The Embedded Metadata Codec Module allows users to actually embed and retrieve JPSearch Core or MPEG-7 metadata in JPEG or JPEG2000 image files. The Repository Import/Export Module provides an example case of importing and exporting content repository using the XML schema defined in ISO/IEC 24800-5 and the provided small test database.
Technologies de l'information — JPSearch — Partie 6: Logiciel de référence
General Information
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 24800-6
First edition
2012-05-01
Information technology — JPSearch —
Part 6:
Reference software
Technologies de l'information — JPSearch —
Partie 6: Logiciel de référence
Reference number
ISO/IEC 24800-6:2012(E)
©
ISO/IEC 2012
---------------------- Page: 1 ----------------------
ISO/IEC 24800-6:2012(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2012
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 2012 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 24800-6:2012(E)
Contents Page
Foreword . iv
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Overview and conventions . 2
4.1 Organization of the document . 2
4.2 Overview of the architecture of the ISO/IEC 24800 reference software . 2
5 Reference software for the ISO/IEC 24800 . 3
5.1 Metadata Translation Module . 3
5.2 JPQF Query Processor Module . 11
5.3 Embedded Metadata Codec Module . 20
5.4 Repository Import/Export Module . 26
Bibliography . 34
© ISO/IEC 2012 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 24800-6:2012(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-6 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)
Part 5: Data interchange format between image repositories
Part 6: Reference software
iv © ISO/IEC 2012 – All rights reserved
---------------------- Page: 4 ----------------------
INTERNATIONAL STANDARD ISO/IEC 24800-6:2012(E)
Information technology — JPSearch —
Part 6:
Reference software
1 Scope
This part of ISO/IEC 24800 describes reference software for the normative clauses as well as utility software
demonstrating the usage scenarios of ISO/IEC 24800-2 to ISO/IEC 24800-5. The information provided is
applicable for determining the reference software modules available for ISO/IEC 24800-2 to ISO/IEC 24800-5
and understanding their functionality and usage. A software module provided in this part of ISO/IEC 24800
can be used either as standalone software or as a part of larger integrated software depending on the module.
2 Normative references
The following referenced documents, in whole or in part, indispensable for 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/corrigenda) applies.
ISO/IEC 24800-2, Information technology — JPSearch — Part 2 Registration, identification and management
of schema and ontology
ISO/IEC 24800-3, Information technology — JPSearch — Part 3: Query format
ISO/IEC 24800-4, Information technology — JPSearch — Part 4: File format for metadata embedded in image
data (JPEG and JPEG 2000)
ISO/IEC 24800-5, Information technology — JPSearch — Part 5: Data interchange format between image
repositories
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
module
software component implementing reference software or utility software
3.2
reference software
one or more modules utilizing normative parts of ISO/IEC 24800-2, -3, -4, -5
3.3
utility software
one or more modules utilizing informative parts of ISO/IEC 24800-1, -2, -3, -4, -5 and/or the usage of
reference software within real-world applications
© ISO/IEC 2012 – All rights reserved 1
---------------------- Page: 5 ----------------------
ISO/IEC 24800-6:2012(E)
4 Overview and conventions
4.1 Organization of the document
In the remainder of this document, each reference and utility software module is described following the
convention as below:
Name of the ZIP file with the following structure: //-
-.zip
: directory name in which the module can be found
Module name
: name of the module, e.g., Parser, Validator, etc.
: letter A, B, C, etc. for different implementations.
: version number, i.e., n_n_n | n_n | n
Functional
Describes the functionality the module provides.
Description
Installation
Describes how the module can be installed/prepared to be used.
Guideline
Describes necessary interface (e.g. command line instructions with parameters) to
Interface Description
use the module.
INPUT Describes the input of the module.
OUTPUT Describes the output of the module.
Programming
Lists the programming language(s) in which the module is written.
Language(s)
Platform(s) Lists the platforms the module has been tested on and is supposed to run on.
Dependencies Lists the required libraries and code with version information.
Details Lists any implementation details, such as architecture diagrams and data flows.
4.2 Overview of the architecture of the ISO/IEC 24800 reference software
The Part 2 module will allow 1) registering external metadata schemas and 2) validating if certain metadata
instance is valid according to the Core Schema in combination with the registered external schemas. It can be
used in combination with Part 4 and Part 5 modules to validate the metadata ingested into a JPSearch
compliant system.
The Part 3 module will process JPQF queries against the repository. It can be used alone, acting over an
independent image repository, or it can be used in combination with the other modules, acting over the
repository generated by the usage of the other modules.
The Part 4 and Part 5 modules are responsible for the interchange of content and metadata between the
JPSearch system and the external applications. The Part 4 module will allow extracting/annotating metadata
2 © ISO/IEC 2012 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 24800-6:2012(E)
embedded within an image file. The Part 5 module will allow interchanging metadata from the whole repository
or parts of it in XML or in binary format.
For each software module mentioned in the table below, next clauses describe a brief architecture of the
module with description, functionality, instructions for installation and utilization, description of using provided
interface which may be command line and/or graphical user interface, and examples of inputs and outputs
with any additional information required to properly use the software module.
module name type description
Metadata
normative Schema registry and metadata validation (Part 2)
Translation
Module
JPQF Query
normative JPQF query validation and processing (Part 3)
Processor Module
Embedded
Metadata embedded in image files. Annotation and
Metadata Codec normative
extraction (Part 4)
Module
Repository
Import/Export normative Repository interchange in binary and XML formats (Part 5)
Module
5 Reference software for the ISO/IEC 24800
5.1 Metadata Translation Module
5.1.1 Summary
The JPSearch translation rules framework supports understanding XML instance documents of metadata
formats by providing translation rules from an XML instance documents of metadata formats into the
JPSearch core metadata format and vice versa. For this purpose, the framework bases on the following
external technologies: a XML database called BaseX for managing the individual translation rules and JDOM
which is an open-source library for java optimized XML data manipulation routines.
Module name Metadata Translation Module
The Java based translation module provides means for translating metadata
descriptions of XML based metadata formats to and from JPSearch Core
descriptions. Currently supported metadata formats are MPEG-7, Dublin Core and
JPSearch Core. The current framework can be further extended by adding
respective translation rules (XML instance documents) from and to JPSearch
Functional
Core. Furthermore, the implementation has to be extended by a new
Description
TranslationToXXX module.
Besides, the current version of the translation module supports the management
(upload, download, delete) of translation rules. This is implemented by a JavaFX
based GUI application which can be used as web application or standalone
application.
Installation Runs as Java (web) application or can be used as Java library in projects.
Guideline Detailed information is provided below.
Interface Description
JPQF query containing XML based metadata. The metadata has to be stored in a
INPUT
QueryByDescription query type. Currently MPEG-7, Dublin Core and JPSearch
© ISO/IEC 2012 – All rights reserved 3
---------------------- Page: 7 ----------------------
ISO/IEC 24800-6:2012(E)
Core is supported.
JPQF query containing the translated metadata format in the respective
QueryByDescription query type. Translation means MPEG-7 or Dublin Core
OUTPUT
metadata are translated into JPSearch Core and JPSearch Core is either
translated into MPEG-7 or Dublin Core.
Programming
Java 1.6 and higher
Language(s)
Platform(s) Any platform is supported that is aware of Java
JavaFX library for the visualization and Tomcat 6 or higher web server in case of
Dependencies using the translation framework as web application. A BaseX database for storing
registered translation rules.
Details
5.1.2 Functionality
5.1.2.1 Introduction
This Subclause describes the complete architecture of the metadata translation module. Figure 1 presents
the individual components of the framework and its interplay. In the following, the components are described
in more detail.
Figure 1 — Translation Rule Framework Class Hierarchy
4 © ISO/IEC 2012 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 24800-6:2012(E)
5.1.2.2 Translation manager
The translation manager is a Java FX application which deals as frontend for user input and supports the
registration of translation rules and the translation of XML input instances. Figure 2 presents a screenshot of
the main frontend with the provided functionality: upload a new translation rule, view the existing rules and
translate an input document.
Figure 2 — Translation Manager
5.1.2.3 Module Translator
In our demo application the Translator class is instantiated directly by the translation manager. However, it
can be used and instantiated in any other Java based application as well. As input parameters, the class
requires a JPQF query and one or more namespaces denoting the target metadata format. Several
constructors are available for different settings. If only a query is transmitted, the translator assumes to
translate the content of the input query into the JPSearch core metadata format. In this case, the responsible
class (TranslateIntoJPSearch) is used. The needed translation rules are (if not submitted by parameters)
loaded from the BaseX database.
5.1.2.4 Module TranslateIntoXXX
For every supported metadata format a specific Java class has to be provided. This class follows a name
convention like TranslateTo. For instance for a translation into the Dublin Core
schema a respective TranslateIntoDublinCore need to be implemented. The main task of those classes
is to construct a valid XML instance document regarding to the target scheme (here for instance Dublin Core)
and the given translation rule.
5.1.2.5 Module Translate
The module Translate contains the whole application logic for applying the translation rules. The class
Translate receives the input query and the translation rules. After preparation of the query, the
executeTranslationRules method is executed. This method traverses over all translation rules and calls
the fitting rule paradigm (one-to-one, one-to-many, or many-to-one). In general, the available XPath
expression is evaluated by using the JDOM-API in order to separate the desired value. The processing of the
fromField expression is done automatic but for the evaluation of the toField the respective helper classes
(TranslateInto) are required. In addition, it has to be noted that the order of the
translation rules is important for the final validity of the received instance document.
5.1.2.6 Integration of new metadata formats
For the integration of new metadata formats, a respective TranslateIntoXXX implementation has to be
provided. In addition, the necessary translation rules for the new metadata formats need to be established
© ISO/IEC 2012 – All rights reserved 5
---------------------- Page: 9 ----------------------
ISO/IEC 24800-6:2012(E)
containing all XPath rules for mapping a JPSearch core schema instance document into the target schema
and vice versa. Finally, the TranslateIntoXXX implementation has to be integrated into the project and the
rules file can be uploaded by the user interface.
5.1.3 Installation / Utilization
The JPSearch Metadata Translation Module comes as a set of zip file and its implementation relies on a Java
1.6 installation on the target computer. Furthermore, for using the Java FX client application as a web
application a running Apache Tomcat is necessary. Furthermore, a BaseX database has to be installed in
case the web application is used.
The package contains the following zip files
1. Rules.zip: Contains the four necessary translation rule XML files.
2. Schema.zip: contains the according XML scheme files for MPEG-7, Dublin Core and JPSearch.
3. Querys.zip: contains 3 example queries for testing
4. Applet.zip: contains the complete Java project
5. Translation Manager.zip: contains the Java project for the JavaFx user interface
6. WebApp.zip: contains the .war file which can be directly exported to a Tomcat server
The following steps have to be applied in order to start the web project:
1. copy the transformer.war into the webapps folder of the Tomcat installation (assuming the Tomcat is
already running and automatic deployment of web application is activated)
2. start the application by using your favorite browser with the following
URL: http://localhost:8080/transformer
3. The Upload, Download and Delete Button are self-explanatory
4. For translating a query, one can select a given one from the example set and the name space field
has to be selected as follows:
a. urn:mpeg:mpeg7:schema:2004 in case a JPSearch Query to MPEG-7 should be translated.
b. http://purl.org/dc/elements/1.1/ in case a JPSearch Query to Dublin Core should be
translated.
c. Keep the field empty in case any Query should be translated into JPSearch core schema.
For using this module as API, one of the constructors of the Translator.class file should be used as starter.
5.1.4 Metadata Comparison
This Subclause provides information about the implemented translation guideline of the supported metadata
formats, namely MPEG-7 and Dublin Core. Here, the identified corresponding elements of the JPSearch core
schema and the respective target schema are modeled. In detail, the MPEG-7 schema and Dublin Core has
been used. For each metadata format, the semantic relations along with the mappings are specified.
Table 1 — Semantic relations of JPSearch elements and MPEG-7 elements
JPSearch core Semantic MPEG-7 XPath
element relation
Identifier more //DescriptionMetadata/PublicIdentifier
generic
OR
//MediaInformation/MediaIdentification /EntityIdentifier
Modifiers more //CreationInformation/Creation/Creator/Role
specific [@href="'modifier"']/following-sibling::Agent
[@type="'PersonType"'] /Name
6 © ISO/IEC 2012 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 24800-6:2012(E)
Creators exact //CreationInformation/Creation/Creator/Role
[@href="'creator"']/following-sibling::Agent
[@type="'PersonType"']/Name
Publisher more //CreationInformation/Creation/Creator/Role
specific
[@href="'publisher"']/following-sibling::Agent OR
//UsageInformation/Availability/Dissemination
/Disseminator/Role[@href="'publisher"']/Agent
CreationDate exact //CreationInformation/Creation/
CreationCoordinates/Date/TimePoint
ModifiedDate more //DescriptionMetadata/LastUpdate
generic
Description more //CreationInformation/Creation/Abstract
generic
/FreeTextAnnotation
RightsDescription more //CreationInformation/Creation/CopyrightString OR
specific
//UsageInformation/Rights
Source more //Variation/Source
specific
OR
//MediaInformation/MediaIdentification
/EntityIdentifier
Keyword exact //CreationInformation/Classification/Subject/
KeywordAnnotation/Keyword
Title exact //CreationInformation/Creation/Title
CollectionLabel exact //DescriptionUnit[@type="'DescriptorCollectionType"']
/@name
PreferenceValue more //UserPreferences/FilteringAndSearchPreferences
generic /CreationPreferences/attribute::preferenceValue
Rating exact //CreationInformation/Classification/MediaReview /Rating
OriginalImage more //Variation/Source/*/MediaLocator/MediaUri
specific
GPSPositioning more //Semantics/SemanticBase[@type="'SemanticPlaceType"']
specific /Place/GeographicPosition/Point/
RegionOfInterest more //SpatialDecomposition/StillRegion
specific
AND
//Semantics/SemanticBase
© ISO/IEC 2012 – All rights reserved 7
---------------------- Page: 11 ----------------------
ISO/IEC 24800-6:2012(E)
Table 2 — Corresponding elements of JPSearch elements and MPEG-7 elements
JPSearch core JPSearch element MPEG-7 element
element
Identifier Identifier (anyURI) PublicIdentifier (anyURI)
OR
EntityIdentifier (anyURI)
Modifiers GivenName (string) GivenName (string) FamilyName
FamilyName (string) (string)
Creators GivenName (string) GivenName (string) FamilyName
FamilyName (string) (string)
Publisher PersonName/GivenName Name/GivenName (string)
(string)
PersonName/FamilyName Name/FamilyName (string)
(string)
OrganizationInformation/Name Name (string)
(string)
OrganizationInformation/Addres Address/Name (string)
s /Name (string)
OrganizationInformation/Addres Address/PlaceDescription (string)
s /Description (string) &
CreationDate CreationDate (dateTime) TimePoint (dateTime)
ModifiedDate ModfiedDate (dateTime) LastUpdate (dateTime)
Description Description (string) FreeTextAnnotation (string)
RightsDescription Description (string) RightsID (string)
Source SourceElementType (string)
SourceElement/SourceElement
Title (string)
SourceElement/SourceElement
-Description (string)
SourceElement/SourceElement */MediaLocator/MediaUri (anyURI)
Identifier (anyURI)
Keyword Keyword (string) Keyword (string)
Title Title (string) Title (string)
CollectionLabel CollectionLabel (string) attribute::name (string)
PreferenceValue PreferenceValue (integer) attribute::preferenceValue (integer)
Rating LabelDefinition (anyURI)
LabelValue (string) RatingValue (float)
OriginalImage OriginationOfID (anyURI) MediaUri (anyURI)
Identifier
GPSPositioning attribute::longitude (double) attribute::longitude (double)
attribute::latitude (double) attribute::latitude (double)
attribute::altitude (double) attribute::altitude (double)
RegionOfInterest RegionLocator/Region StillRegion/SpatialLocator/Box (integer
(IntegerMatrixType) list)
8 © ISO/IEC 2012 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC 24800-6:2012(E)
Description (string) StillRegion/CreationInformation
/Creation/Abstract/FreeTextAnnotation
(string)
Keyword (string) StillRegion/CreationInformation
/Classification/Subject/KeywordAnnotat
ion/Keyword (string)
Title (string) StillRegion/CreationInformation
/Creation/Title (string)
ContentDescription/Person/Na SemanticBase[@xsi:type=”mpeg7:Age
me/GivenName (string) ntObjectType”]/Agent
/Name/GivenName (string)
ContentDescription/Person/Na SemanticBase[@xsi:type=”mpeg7:Age
me/FamilyName (string) ntObjectType”]/Agent
/Name/FamilyName (string)
ContentDescription/Person/Affili SemanticBase[@xsi:type=”mpeg7:Age
ation/Name (string) ntObjectType”]/Agent[@xsi:type=”mpe
g7:OrganizationType”]/Name (string)
ContentDescription/Person/Affili SemanticBase[@xsi:type=”mpeg7:Age
ation/Address/Name (string) ntObjectType”]/Agent[@xsi:type=”mpe
g7:OrganizationType”]/Address/Name
(string)
ContentDescription/Person/Affili SemanticBase[@xsi:type=”mpeg7:Age
ation/Address/Description ntObjectType”]/Agent[@xsi:type=”mpe
(string) g7:OrganizationType”]/Address/PlaceD
escription (string
ContentDescription/Person/Add SemanticBase[@xsi:type=”mpeg7:Age
ress/Name (string) ntObjectType”]/Agent[@xsi:type=”mpe
g7:PersonType”]/Address/Name
(string)
ContentDescription/Person/Add SemanticBase[@xsi:type=”mpeg7:Age
ress/Description (string) & ntObjectType”]/Agent[@xsi:type=”mpe
g7:PersonType”]/Address/PlaceDescri
ption (string)
ContentDescription/Person/Des SemanticBase[@xsi:type=”mpeg7:Age
cription (string) ntObjectType”]/Agent[@xsi:type=”mpe
g7:PersonType”]/PersonDescription
(string)
ContentDescription/Person/Nati SemanticBase[@xsi:type=”mpeg7:Age
onality (string) ntObjectType”]/Agent[@xsi:type=”mpe
g7:PersonType”] /Nationality ([a-zA-Z])
ContentDescription/Object/Nam SemanticBase[@xsi:type=”mpeg7:Obj
e (string) & ectType”]/Object/Label/Name (string)
ContentDescription/Place/Nam SemanticBase[@xsi:type=”mpeg7:Sem
e (string) anticPlaceType”]/Place/Name (string)
ContentDescription/Place/Descr SemanticBase[@xsi:type=”mpeg7:Sem
iption (string) anticPlaceType”]/Place/PlaceDescriptio
n (string)
ContentDescription/Event/Label SemanticBase[@xsi:type=”mpeg7:Eve
(anyURI) ntType”]/Event/Label/Name (string)
© ISO/IEC 2012 – All rights reserved 9
---------------------- Page: 13 ----------------------
ISO/IEC 24800-6:2012(E)
Table 3 — Semantic relations of JPSearch core schema and Dublin Core
JPSearch core element Semantic relation Dublin Core element
Identifier exact Identifier (string)
Modifiers more generic Contributor (string)
Creators more generic creator (string)
Publisher more generic publisher (string)
CreationDate more generic date (string)
ModifiedDate more generic date (string)
Description exact description (string)
RightsDescription exact rights (string)
Source exact source (string)
Keyword exact subject (string)
Title exact title (string)
CollectionLabel not available not available
PreferenceValue not available not available
Rating not available not available
OriginalImage exact relation (string)
GPSPositioning more generic coverage (string)
RegionOfInterest not available not available
Table 4 — Corresponding elements in JPSearch core schema and Dublin Core
JPSearch core element JPSearch element Dublin Core element
Identifier Identifier (anyURI) Identifier (string)
Modifiers GivenName (string) FamilyName Contributor (string)
(string)
Creators GivenName (string) FamilyName creator (string)
(string)
Publisher GivenName (string) FamilyName publisher (string)
(string)
CreationDate CreationDate (dateTime) date (string)
10 © ISO/IEC 2012 – All rights reserved
---------------------- Page: 14 ----------------------
ISO/IEC 24800-6:2012(E)
ModifiedDate ModfiedDate (dateTime) date (string)
Description Description (string) description (string)
RightsDescription Description (string) rights (string)
Source SourceElementType (string) source (string)
Keyword Keyword (string) subject (string)
Title Title (string) title (string)
CollectionLabel not available not available
PreferenceValue not available not available
Rating not available not available
OriginalImage OriginationOfID (anyURI) relation (string)
GPSPositioning attribute::longitude (double) coverage (string)
attribute::latitude (double)
RegionOfInterest not available not available
5.2 JPQF Query Processor Module
5.2.1 Summary
Module name JPQF Query Processor
Checks the syntactic and semantic validity of a JPQF input/output query according
to the rules of XML 1.1 and the JPQF XML schema. Interprets the basic conditions
Functional
of an JPQF input query (without QueryTypes) over an example metadata file (e.g.
Description
an MPEG-7 collection of image descriptors) and returns a coherent JPQF
response
Copy the Java jar file to the local filesystem. Requires a previous Java 1.6
Installation
installation and the operating system execution path environment variable properly
Guideline
pointing to the Java application launcher (java command).
java -Dlog4j.configuration=file:./WEB-INF/classes/log4j.properties -
classpath ./WEB-INF/lib/mpqf-1.0.jar;./WEB-INF/lib/xmldb.jar;./WEB-
INF/lib/exist.jar;./WEB-INF/lib/log4j-1.2.15.jar;./WEB-INF/lib/xmlrpc-1.2-
patched.jar;./WEB-INF/lib/jaxen-1.1.1.jar;./WEB-INF/lib/commons-pool-
1.4.jar;./WEB-INF/lib/antlr-2.7.6.jar;./WEB-INF/lib/xercesImpl-2.9.1.jar;./WEB-
INF/lib/resolver-1.2.jar;./WEB-INF/lib/quartz-1.6.0.jar;./WEB-INF/lib/commons-
Interface Description
logging-1.0.4.jar;./WEB-INF/lib/jta.jar;./WEB-INF/lib/commons-collections-
3.1.jar;./WEB-INF/lib/stax-api-1.0.1.jar;./WEB-INF/lib/caliph-emir-cbir.jar;./WEB-
INF/lib/lucene-core-2.1.0.jar;./WEB-INF/lib/lire.jar
org.barcelonatech.kaikoMPQFTester [test_jpsearch_p3_query.xml]
[test_jpsearch_p5_interchangefile.xml] [outputfile.xml]
© ISO/IEC 2012 – All rights reserved 11
---------------------- Page: 15 ----------------------
ISO/IEC 24800-6:2012(E)
INPUT A JPQF query; An example metadata file
OUTPUT A JPQF response
Programming
Java 1.6
Language(s)
Platform(s) Windows, Linux and any other platform supporting Java 1.6.
Dependencies NO
Module based in the reference software module described in
ISO/IEC 15938-12:2008/Amd.1, which provides an MPEG Query Format Basic
Interpreter. The provided JPQF Query Processor module extends the software in
Details ISO/IEC 15938-12:2008/Amd.1 by adjusting the parameters of the query
processor to allow the compilation and execution of queries with features which
are specific of ISO/IEC 24800-3, and also by allowing the execution of the queries
over metadata compliant with ISO/IEC 24800-2.
Figure 3 — JPQF query validation and processing module architecture overview
5.2.2 Functionality
The provided JPQF Query Processor module is based in the reference software module described in
ISO/IEC 15938-12:2008/Amd.1, which provides an MPEG Query Format Basic Interpreter. The provided
JPQF Query Processor module extends the software in ISO/IEC 15938-12:2008/Amd.1 by adjusting the
...
INTERNATIONAL ISO/IEC
STANDARD 24800-6
First edition
2012-05-01
Information technology — JPSearch —
Part 6:
Reference software
Technologies de l'information — JPSearch —
Partie 6: Logiciel de référence
Reference number
ISO/IEC 24800-6:2012(E)
©
ISO/IEC 2012
---------------------- Page: 1 ----------------------
ISO/IEC 24800-6:2012(E)
This CD-ROM contains:
1) the publication ISO/IEC 24800-6:2012 in portable document format (PDF), which can be viewed
using Adobe® Acrobat® Reader;
2) reference software containing four independent running software modules:
Metadata Translation Module for ISO/IEC 24800-2;
JPQF Query Processor Module for ISO/IEC 24800-3;
Embedded Metadata Codec Module for ISO/IEC 24800-4;
Repository Import/Export Module for ISO/IEC 24800-5.
Adobe and Acrobat are trademarks of Adobe Systems Incorporated.
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2012
All rights reserved. Unless required for installation or otherwise specified, no part of this CD-ROM may be reproduced, stored in a retrieval
system or transmitted in any form or by any means without prior permission from ISO. Requests for permission to reproduce this product
should be addressed to
ISO copyright office Case postale 56 CH-1211 Geneva 20 Switzerland
Internet copyright@iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
Published in Switzerland
ii © ISO/IEC 2012 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 24800-6:2012(E)
Installation
If this publication has been packaged as a zipped file, do NOT
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.