Information technology — Media context and control — Part 7: Conformance and reference software

ISO/IEC 23005-7:2017 specifies the conformance and reference software implementing the normative clauses of all parts of ISO/IEC 23005. The information provided is applicable for determining the reference software modules available for the parts of ISO/IEC 23005, understanding the functionality of the available reference software modules, and utilizing the available reference software modules. The available reference software modules are specified in the form of application programming interfaces (API) according to ISO/IEC 23006‑1. Furthermore, this document provides means for conformance testing, i.e. bit-streams (XML descriptions) that conform or do not conform to the normative clauses of the other parts of ISO/IEC 23005 and informative descriptions thereof.

Technologies de l'information — Contrôle et contexte de supports — Partie 7: Conformité et logiciel de référence

General Information

Status
Withdrawn
Publication Date
05-Jan-2017
Withdrawal Date
05-Jan-2017
Current Stage
9599 - Withdrawal of International Standard
Completion Date
10-Dec-2019
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 23005-7:2017 - Information technology -- Media context and control
English language
44 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 23005-7
Third edition
    2017-01
Information technology — Media
context and control —
Part 7:
Conformance and reference software
Technologies de l’information — Contrôle et contexte de supports —
Partie 7: Conformité et logiciel de référence
Reference number
ISO/IEC 23005-7:2017(E)
©
ISO/IEC 2017

---------------------- Page: 1 ----------------------
ISO/IEC 23005-7:2017(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2017, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2017 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 23005-7:2017(E)

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 2
4 Reference software for the ISO/IEC 23005 series . 2
4.1 Overview . 2
4.2 ISO/IEC 23005-2 APIs . 3
4.2.1 Overview . 3
4.2.2 CIM engine . 3
4.2.3 CIM creation . 3
4.2.4 CIM access. 3
4.3 ISO/IEC 23005-3 APIs . 3
4.3.1 Overview . 3
4.3.2 SEM engine . . 3
4.3.3 SEM creation . 4
4.3.4 SEM access . 4
4.4 ISO/IEC 23005-4 APIs . 4
4.4.1 Overview . 4
4.4.2 VWOC engine . . 4
4.4.3 VWOC creation . 4
4.4.4 VWOC access . 4
4.5 ISO/IEC 23005-5 APIs . 4
4.5.1 Overview . 4
4.5.2 IID engine . 5
4.5.3 IID creation . 5
4.5.4 IID access . 5
4.6 Binary representation APIs for the ISO/IEC 23005 series . 5
4.6.1 Overview . 5
4.6.2 BinaryIO . 5
4.6.3 DefaultBinaryIO . 5
5 Conformance for the ISO/IEC 23005 series . 6
5.1 General . 6
5.2 Rule-based conformance for the ISO/IEC 23005 series . 6
5.2.1 Overview . 6
5.2.2 Validation schema . 6
5.2.3 Description . . .17
5.2.4 Conformance bit-streams .22
5.3 Schema-based conformance for the ISO/IEC 23005 series .41
5.3.1 Overview .41
5.3.2 Example Valid CIM .41
5.3.3 Example Not Valid CIM .42
5.3.4 Example Valid SEM .42
5.3.5 Example Not Valid SEM .42
5.3.6 Example Valid VWOC .43
5.3.7 Example Not Valid VWOC .43
5.3.8 Example Valid IIM .43
5.3.9 Example Not Valid IIM . .43
Bibliography .44
© ISO/IEC 2017 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 23005-7:2017(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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
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. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO’s adherence to the World Trade Organization (WTO) principles in the
Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html.
This document was prepared by ISO/IEC Joint Technical Committee ISO/IEC JTC 1, Information
technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
This third edition cancels and replaces the second edition (ISO/IEC 23005-7:2014), which has been
technically revised.
A list of all parts in the ISO/IEC 23005 series can be found on the ISO website.
iv © ISO/IEC 2017 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 23005-7:2017(E)

Introduction
This document specifies the conformance and reference software for the ISO/IEC 23005 series. The
conformance and reference software serves three main purposes:
— validation of the written specification of the several parts of ISO/IEC 23005;
— clarification of the written specification of the several parts of ISO/IEC 23005;
— conformance testing for checking interoperability for the various applications against the reference
software which aims to be compliant with ISO/IEC 23005.
© ISO/IEC 2017 – All rights reserved v

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 23005-7:2017(E)
Information technology — Media context and control —
Part 7:
Conformance and reference software
1 Scope
This document specifies the conformance and reference software implementing the normative clauses
of all parts of ISO/IEC 23005. The information provided is applicable for determining the reference
software modules available for the parts of ISO/IEC 23005, understanding the functionality of the
available reference software modules, and utilizing the available reference software modules. The
available reference software modules are specified in the form of application programming interfaces
(API) according to ISO/IEC 23006-1.
Furthermore, this document provides means for conformance testing, i.e. bit-streams (XML descriptions)
that conform or do not conform to the normative clauses of the other parts of ISO/IEC 23005 and
informative descriptions thereof.
2 Normative references
The following documents are referred to in text in such a way that some or all of their content
constitutes requirements 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 23005-2, Information technology — Media context and control — Part 2: Control information
ISO/IEC 23005-3, Information technology — Media context and control — Part 3: Sensory information
ISO/IEC 23005-4, Information technology — Media context and control — Part 4: Virtual world object
characteristics
ISO/IEC 23006-1, Information technology — Multimedia service platform technologies — Part 1:
Architecture
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 23006-1 apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http://www.electropedia.org/
— ISO Online browsing platform: available at http://www.iso.org/obp
© ISO/IEC 2017 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO/IEC 23005-7:2017(E)

3.2 Abbreviated terms
API application programming interface
CIM control information metadata
MXM MPEG extensible middleware
SEM sensory effect metadata
VWOC virtual world object characteristics
IIM interaction information metadata
4 Reference software for the ISO/IEC 23005 series
4.1 Overview
[5]
This subclause specifies the reference software for the ISO/IEC 23005 series, which is written in Java
and adopts the following package structure:
Name Definition
org
Java package name for reference software provided by organizations
such as ISO/IEC, W3C, or similar.
org.iso
Java package name for reference software provided by ISO/IEC.
org.iso.mpeg Java package name for reference software provided by ISO/
IEC JTC 1/SC 29.
org.iso.mpeg.mpegv
Java package name for reference software provided in the course of
the development of the ISO/IEC 23005 series.
NOTE 1  Subsequent packages for the individual ISO/IEC 23005 parts
use the uncapitalized abbreviations as defined in 3.2, e.g.
—  org.iso.mpeg.mpegv.cidl,
org.iso.mpeg.mpegv.dcdv,
org.iso.mpeg.mpegv.sapv,
org.iso.mpeg.mpegv.scdv and
org.iso.mpeg.mpegv.sepv for ISO/IEC 23005-2,
—  org.iso.mpeg.mpegv.sedl and
org.iso.mpeg.mpegv.sev for ISO/IEC 23005-3,
—  org.iso.mpeg.mpegv.vwoc for ISO/IEC 23005-4, or
—  org.iso.mpeg.mpegv.iidl,
org.iso.mpeg.mpegv.dcv and
org.iso.mpeg.mpegv.siv for ISO/IEC 23005-5.
—  org.iso.mpeg.mpegv.ct for ISO/IEC 23005-6.
NOTE 2  Code included within these packages can be generated auto-
matically by using tools such as JAXB.
org.iso.mpeg.mpegv.{part}.
Java package name for binary representation of reference software
binary
provided in the course of the development of the ISO/IEC 23005 series.
the {part} placeholder is replaced by the component of each part,
i.e. cidl, dvdv, sapv, scdv, sepv, sedl, sev, vwoc, iidl, dcv,
siv and ct.
org.iso.mpeg.mxm
Java package name for reference software provided in the course of
the development of ISO/IEC 23006-1. The actual API is defined within
this package.
2 © ISO/IEC 2017 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 23005-7:2017(E)

4.2 ISO/IEC 23005-2 APIs
4.2.1 Overview
This subclause specifies the API to the ISO/IEC 23005-2 reference software. The API is defined in Java
and adopts the following package structure:
Name Definition
org.iso.mpeg.mxm.engine.cimengine
Java package name for API to the ISO/IEC 23005-2 refer-
ence software.
4.2.2 CIM engine
The CIMEngine interface defines the methods for operating over data structures as defined within
ISO/IEC 23005-2. Classes implementing the CIM engine interface act as factories creating instances of
classes performing the following functionalities:
— classes to create data structures, by means of the CIM creation engine;
— classes to access data contained in data structures, by means of CIM parser engine.
4.2.3 CIM creation
Creating CIM structures involves the following interfaces:
— CIMCreator: an interface defining the methods to create CIM structures.
4.2.4 CIM access
Accessing CIM structures involves the following interfaces:
— CIMParser: an interface defining the methods to parse CIM structures.
4.3 ISO/IEC 23005-3 APIs
4.3.1 Overview
This subclause specifies the API to the ISO/IEC 23005-3 reference software. The API is defined in Java
and adopts the following package structure:
Name Definition
org.iso.mpeg.mxm.engine.semengine
Java package name for API to the ISO/IEC 23005-3 refer-
ence software.
4.3.2 SEM engine
The SEMEngine interface defines the methods for operating over data structures as defined within
ISO/IEC 23005-3. Classes implementing the SEM engine interface act as factories creating instances of
classes performing the following functionalities:
— classes to create data structures, by means of the SEM creation engine;
— classes to access data contained in data structures, by means of SEM parser engine.
© ISO/IEC 2017 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO/IEC 23005-7:2017(E)

4.3.3 SEM creation
Creating SEM structures involves the following interfaces:
— SEMCreator: an interface defining the methods to create SEM structures.
4.3.4 SEM access
Accessing SEM structures involves the following interfaces:
— SEMParser: an interface defining the methods to parse SEM structures.
4.4 ISO/IEC 23005-4 APIs
4.4.1 Overview
This subclause specifies the API to the ISO/IEC 23005-4 reference software. The API is defined in Java
and adopts the following package structure:
Name Definition
org.iso.mpeg.mxm.engine.vwocengine
Java package name for API to the ISO/IEC 23005-4
reference software.
4.4.2 VWOC engine
The VWOCEngine interface defines the methods for operating over data structures as defined within
ISO/IEC 23005-4. Classes implementing the VWOC engine interface act as factories creating instances
of classes performing the following functionalities:
— classes to create data structures, by means of the VWOC creation engine;
— classes to access data contained in data structures, by means of VWOC parser engine.
4.4.3 VWOC creation
Creating VWOC structures involves the following interfaces:
— VWOCCreator: an interface defining the methods to create VWOC structures.
4.4.4 VWOC access
Accessing VWOC structures involves the following interfaces:
— VWOCParser: an interface defining the methods to parse VWOC structures.
4.5 ISO/IEC 23005-5 APIs
4.5.1 Overview
This subclause specifies the API to the ISO/IEC 23005-5 reference software. The API is defined in Java
and adopts the following package structure:
Name Definition
org.iso.mpeg.mxm.engine.iidengine
Java package name for API to the ISO/IEC 23005-5 refer-
ence software.
4 © ISO/IEC 2017 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 23005-7:2017(E)

4.5.2 IID engine
The IIDEngine interface defines the methods for operating over data structures as defined within
ISO/IEC 23005-2. Classes implementing the IID engine interface act as factories creating instances of
classes performing the following functionalities:
— classes to create data structures, by means of the IID creation engine;
— classes to access data contained in data structures, by means of IID parser engine.
4.5.3 IID creation
Creating IID structures involves the following interfaces:
— IIDCreator: an interface defining the methods to create IID structures.
4.5.4 IID access
Accessing IID structures involves the following interfaces:
— IIDParser: an interface defining the methods to parse IID structures.
4.6 Binary representation APIs for the ISO/IEC 23005 series
4.6.1 Overview
This subclause specifies the API to the ISO/IEC 23005 series reference software for binary
representation. The API is defined in Java and adopts the following package structure:
Name Definition
org.iso.mpeg.mpegv.binary.core
Java package name for API to the ISO/IEC 23005 series
reference software for binary representation.
4.6.2 BinaryIO
The BinaryIO interface defines the methods for operating over data structures as defined within the
ISO/IEC 23005 series. Classes implementing the BinaryIO interface act as factories creating instances
of classes performing the following functionalities:
— classes to generate a binary structure from a MXM object tree, by means of the construct binary
structure function;
— classes to generate a binary file from a binary structure, by means of the write binary function;
— classes to generate a binary structure from a binary structure, by means of the read binary function;
— classes to restore a MXM object tree from a binary structure, by means of the create MXM object
function.
4.6.3 DefaultBinaryIO
DefaultBinaryIO class defines function “Encode” and “Decode”. Root elements of other parts
(e.g. ISO/IEC 23005-2, ISO/IEC 23005-3, ISO/IEC 23005-4) can be extended from this DefaultBinaryIO
class. DefaultBinaryIO involves the following functions:
— encode: a function defining the methods to create binary file from a MXM object tree;
— decode: a function defining the methods to restore a MXM object tree from a binary file.
© ISO/IEC 2017 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO/IEC 23005-7:2017(E)

5 Conformance for the ISO/IEC 23005 series
5.1 General
This subclause defines conformance for the ISO/IEC 23005 series. A bit-stream is compliant to the
ISO/IEC 23005 series if it conforms to the conformance definitions specified in 5.2 and 5.3.
5.2 Rule-based conformance for the ISO/IEC 23005 series
5.2.1 Overview
This subclause defines a validation schema based on ISO/IEC 19757-3 to check the conformance bit-
streams (XML descriptions) that conform or do not conform to the normative clauses of the other parts
of ISO/IEC 23005 and descriptions thereof. In particular, the additional validation rules as specified in
the other parts of ISO/IEC 23005 are checked with this validation schema. The actual schema can be
found in 5.2.2 and a more readable version of the rules and assertion messages is provided in 5.2.3. The
actual conformance bit-streams (XML descriptions) are defined in 5.2.4. The actual conformance bit-
streams and corresponding code can be found attached to this document.
For transforming the validation schema according to ISO/IEC 19757-3 and for validating the examples,
[6]
Saxon is used. Saxon is not mandatory and other tools can be used for validating the examples.
5.2.2 Validation schema
 xmlns = “http://purl.oclc.org/dsdl/schematron”
 xmlns:sedl = “urn:mpeg:mpeg-v:2010:01-SEDL-NS”
 xmlns:sev = “urn:mpeg:mpeg-v:2010:01-SEV-NS”
 xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
 xmlns:si = “urn:mpeg:mpeg21:2003:01-DIA-XSI-NS”
 xmlns:cidl = “urn:mpeg:mpeg-v:2010:01-CIDL-NS”
 xmlns:dcdv = “urn:mpeg:mpeg-v:2010:01-DCDV-NS”
 xmlns:scdv = “urn:mpeg:mpeg-v:2010:01-SCDV-NS”
 xmlns:sepv = “urn:mpeg:mpeg-v:2010:01-SEPV-NS”
 xmlns:mpegvct = “urn:mpeg:mpeg-v:2010:01-CT-NS”
 xmlns:mpeg7 = “urn:mpeg:mpeg7:schema:2004”
 xmlns:dia = “urn:mpeg:mpeg21:2003:01-DIA-NS”
 xmlns:iidl = “urn:mpeg:mpeg-v:2010:01-IIDL-NS”
 xmlns:dcv = “urn:mpeg:mpeg-v:2010:01-DCV-NS”
 xmlns:siv = “urn:mpeg:mpeg-v:2010:01-SIV-NS”
 queryBinding = ‘xslt’ schemaVersion = ‘ISO 19757-3’>





6 © ISO/IEC 2017 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC 23005-7:2017(E)











Schema for validating SEDL/CIDL/IIDL descriptions




 
 
   @max-
Value) then false() else true() else true()”>
    A minValue shall be less than or equal to a maxValue.
  
 


 
 
   @max-
Value) then false() else true() else true()”>
    A minValue shall be less than or equal to a maxValue.
  
 


 
 
   @max-
Value) then false() else true() else true()”>
© ISO/IEC 2017 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO/IEC 23005-7:2017(E)


    A minValue shall be less than or equal to a maxValue.
  
 


 
 
   @maxValue) then
false() else true() else true()”>
    A minValue shall be less than or equal to a maxValue.
  
 


 
 
   @maxValue) then
false() else true() else true()”>
    A minValue shall be less than or equal to a maxValue.
  
 


 
 
   ...

Questions, Comments and Discussion

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