Information technology — Multimedia content description interface — Part 12: Query format — Amendment 2: Semantic enhancement

Technologies de l'information — Interface de description du contenu multimédia — Partie 12: Format de requête — Amendement 2: Amélioration sémantique

General Information

Status
Withdrawn
Publication Date
20-Jul-2011
Withdrawal Date
20-Jul-2011
Current Stage
9599 - Withdrawal of International Standard
Completion Date
23-Oct-2012
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 15938-12:2008/Amd 2:2011 - Semantic enhancement
English language
13 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 15938-12
First edition
2008-12-15
AMENDMENT 2
2011-08-01

Information technology — Multimedia
content description interface —
Part 12:
Query format
AMENDMENT 2: Semantic enhancement
Technologies de l'information — Interface de description du contenu
multimédia —
Partie 12: Format de requête
AMENDEMENT 2: Amélioration sémantique




Reference number
ISO/IEC 15938-12:2008/Amd.2:2011(E)
©
ISO/IEC 2011

---------------------- Page: 1 ----------------------
ISO/IEC 15938-12:2008/Amd.2:2011(E)

COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2011
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 2011 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 15938-12:2008/Amd.2:2011(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.
Amendment 2 to ISO/IEC 15938-12:2008 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 2011 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 15938-12:2008/Amd.2:2011(E)

Information technology — Multimedia content description
interface —
Part 12:
Query format
AMENDMENT 2: Semantic enhancement
In 3.2, add the following:
RDF: Resource Description Framework (W3C, http://www.w3.org/RDF/)
SPARQL: SPARQL Query Language for RDF. W3C Recommendation 15 January 2008.
http://www.w3.org/TR/rdf-sparql-query/

After 6.7, add the following subclause:
6.8 SemanticFieldType
The SemanticFieldType supports the addressing of individual Subject/Object parts of an RDF triple which are
involved in a comparison expression or the sorting operation.
6.8.1 Syntax

 
  
 


6.8.2 Semantics
Semantics of the SemanticFieldType:
Name Definition
SemanticFieldType
Specifies the representation of a semantic field within the
query format. A semantic field addresses a node
(subject/object) according to the RDF data model (triple). The
syntax is similar to the SPARQL query language and starts
with a question mark and a descriptive identifier or a specific
URI for the variable.
Var Defines a place holder for the subject of a RDF triple. The
place holder must start with a question mark and a descriptive
identifier or a specific URI.
© ISO/IEC 2011 – All rights reserved 1

---------------------- Page: 4 ----------------------
ISO/IEC 15938-12:2008/Amd.2:2011(E)
6.8.3 Example
The main purpose of the SemanticFieldType (the variable element) is the addressing of RDF nodes to be
used in sorting and comparison expressions. For instance, one want to have the result set sorted after a
specific node information or want to filter the result set according to specific literal values. An example might
be the price of a hotel which is modeled like hotel->hasPrice->value (e.g., Bloom->hasPrice->80 which results
to a requesting triple: ?hotel -> hasPrice -> ?price), then one want to filter all hotels whose price is above a
certain threshold. In this case, the GreaterThan condition (comparison expression already defined in MPQF) is
used to filter the identified literal to a specific bound.


 
 
  
  
   ?hotel
   hasPrice
   ?price
  
  
   
    ?price
   
   100.0
  
  
 
 



In 8.1 Introduction, add the following paragraph:
[…]
Its structure is defined by the QFDeclarationType type, which consists of a sequence of DeclaredField
and Resource elements and Prefix information declaring used namespaces. A DeclaredField
element allows declaring a reusable data path within an item’s metadata. A Resource element allows
declaring a reusable resource description using one of the subtypes of the ResourceType (the
MediaResourceType type or the DescriptionResourceType type). A Prefix element allows
declaring a shortcut for a namespace which is used in semantic expressions.

In 8.2 Syntax, add the following (highlighted):

 
      minOccurs="0" maxOccurs="unbounded"/>
      maxOccurs="unbounded"/>
  
   
     
     
   
  
2 © ISO/IEC 2011 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 15938-12:2008/Amd.2:2011(E)
 
 


8.3 Semantics
Semantics of the Prefix element:
Name Definition
Prefix
Defines the name and the unique URI of a namespace, e.g.
http://www.w3.org/1999/02/22-rdf-syntax-ns# for RDF.
name
Defines the name or shortcut of the namespace. For instance:
xsd.
uri
Defines the assigned URI for this prefix and shortcut. For
instance: http://www.w3.org/2001/XMLSchema#

In 9.2 Syntax, add the following (highlighted):

 
        maxOccurs="unbounded"/>
        maxOccurs="unbounded"/>

        maxOccurs="unbounded"/>

 
 
               maxOccurs="unbounded"/>
               type="mpqf:AggregateExpressionType"
            minOccurs="0" maxOccurs="unbounded"/>
 
 

        minOccurs="0" maxOccurs="unbounded"/>
 
         use="optional"/>
         use="optional"/>
 
 
 
 
         default="false"/>

© ISO/IEC 2011 – All rights reserved 3

---------------------- Page: 6 ----------------------
ISO/IEC 15938-12:2008/Amd.2:2011(E)
In 9.3 Semantics, add the following at the end of the table:
Enhanced Semantics of the OutputDescriptionType:
Name Definition
ReqSemanticField
Describes the place holder of the desired semantic variable
which is filtered in the Semantic Expression part of the
QueryCondition. The place holder follows the SPARQL syntax
beginning with a question mark and a descriptive identifier:
e.g. ?person

In 9.5.2, add the following:
9.5.2 Syntax

 

 
  
  
 

 


In 9.5.3, add the following:
9.5.3 Semantics
Name Definition
SemanticField
Describes the place holder of the desired semantic variable
which should be used for sorting. The semantic field is filtered
in the Semantic Expression part of the QueryCondition or
stems from the SPARQL query type. The place holder follows
the SPARQL syntax beginning with a question mark and a
descriptive identifier: e.g. ?person

4 © ISO/IEC 2011 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 15938-12:2008/Amd.2:2011(E)
After 11.9, add the following subclause:
11.10 Semantic Expression Types
11.10.1 Introduction
11.10.2 Syntax

 

            type="nonNegativeInteger" use="required" />
 

 



 

 
 

 


 

 
 
  
 


 

 
 

 


 

 
 

 


 

 
 

 

© ISO/IEC 2011 – All rights reserved 5

---------------------- Page: 8 ----------------------
ISO/IEC 15938-12:2008/Amd.2:2011(E)

 

 
 

 


 

  
 

 


 

 
 

 



 

 
 
 

 


11.10.3 Semantics
Semantics of the SemanticExpressionType:
Name Definition
SemanticExpressionType
An abstract type based on the BooleanExpressionType type
that is the base type for defining semantic expressions.
anchorDistance Defines the number of hops the identified triple is reachable
through the RDF graph from the given starting RDF triple. The
starting RDF triple is indicated by enabling the anchor flag. An
anchorDistance of 0 indicates that the addressed node can be
within any distance to the anchor node.
anchor Defines a marker for a RDF triple within a query graph which
serves as source for other triples. The main idea is to simplify
the generation of semantic queries and to allow optimizers to
improve resulting SPARQL queries.
6 © ISO/IEC 2011 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 15938-12:2008/Amd.2:2011(E)
Semantics of the class specific types:
Name Definition
SubClassOf A complex type based on the SemanticExpressionType
type for defining a sub class relationship. This operation has
two attributes that are required to represent the following
pattern: var SubClassOf class. The var and class parameter
can be URIs or place holder based on the SPARQL notation
(starting with a question mark and a descriptive identifier).
TypeOf
A complex type based on the SemanticExpressionType
type for defining a type of relationship. The attributes are
defined as for the SubClassOf operation.
EquivalentClass
A complex type based on the SemanticExpressionType
type for defining an equivalent class relationship. The
attributes are defined as for the SubClassOf operation.
ComplementOf
A complex type based on the SemanticExpressionType
type for defining a complement of relationship. The
attributes are defined as for the SubClassOf operation.
IntersectionOf
A complex type based on the SemanticExpressionType
type for defining an intersection of relationship. The
attributes are defined as for the SubClassOf operation.
UnionOf
A complex type based on the SemanticExpressionType
type for defining a union of relationship. The attributes are
defined as for the SubClassOf operation.
InverseOf
A complex type based on the SemanticExpressionType
type for defining an inverse of relationship. The attributes
are defined as for the SubClassOf operation.
DisjointWith
A complex type based on the SemanticExpressionType
type for defining a disjoint with relationship. The attributes
are defined as for the SubClassOf operation.

Semantic
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.