Information technology - Multimedia service platform technologies — Part 3: Conformance and reference software

ISO/IEC 23006-3:2013 describes the reference software implementing the normative clauses of ISO/IEC 23006-1, ISO/IEC 23006-2 and ISO/IEC 23006-4 and specifies conformance criteria. The information provided is applicable for determining the reference software modules available for ISO/IEC 23006-1, understanding the functionality of the available reference software modules and utilizing the available reference software modules. The conformance profiles apply to MPEG-M Services as defined in ISO/IEC 23006-4:2013 and in ISO/IEC 23006-5.

Technologies de l'information — Technologies de la plate-forme de services multimédia — Partie 3: Conformité et logiciel de référence

General Information

Status
Withdrawn
Publication Date
10-Sep-2013
Withdrawal Date
10-Sep-2013
Current Stage
9599 - Withdrawal of International Standard
Completion Date
05-Dec-2016
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 23006-3:2013 - Information technology - Multimedia service platform technologies
English language
28 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO/IEC 23006-3:2013 - Information technology - Multimedia service platform technologies
English language
28 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 23006-3
Second edition
2013-09-15

Information technology — Multimedia
service platform technologies —
Part 3:
Conformance and reference software
Technologies de l'information — Technologies de la plate-forme de
services multimédia —
Partie 3: Conformité et logiciel de référence




Reference number
ISO/IEC 23006-3:2013(E)
©
ISO/IEC 2013

---------------------- Page: 1 ----------------------
ISO/IEC 23006-3:2013(E)

COPYRIGHT PROTECTED DOCUMENT


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

---------------------- Page: 2 ----------------------
ISO/IEC 23006-3:2013(E)
Contents Page
Foreword . v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Abbreviated terms . 4
4 Namespaces and conventions . 5
4.1 Introduction . 5
5 Reference software overview . 9
5.1 Introduction . 9
5.2 The MXM software repository . 9
6 MXM Java software implementation . 10
6.1 Introduction . 10
6.2 mxm-core (normative) . 11
6.3 mxm-engines (informative) . 12
6.4 mxm-es (informative) . 13
6.5 mxm-applications (informative) . 13
6.6 mxm-dataobject (informative) . 13
6.7 Java MXM Technology Engines . 13
6.7.1 The Digital Item Engine . 13
6.7.2 The MPEG21 File Format Engine . 14
6.7.3 The REL Engine . 14
6.7.4 The IPMP Engine . 15
6.7.5 The Media Framework Engine . 15
6.7.6 The Metadata Engine . 16
6.7.7 The Event Report Engine . 16
6.7.8 The Security Engine . 16
6.7.9 The Search Engine . 17
6.7.10 The Contract Engine . 17
6.7.11 The Overlay Engine . 17
6.8 Java MXM Protocol Engines . 17
6.8.1 Java MXM Elementary Services . 17
6.8.2 Technical Guidelines . 18
6.8.3 Create Content Usage scenario . 18
7 Profiles. 19
7.1 Overview . 19
7.2 "strict" profile . 19
7.3 "lax" profile . 20
7.4 ProfileCS . 20
Annex A (informative) Check out of MXM source code from the MXM svn repository . 21
Annex B (informative) Building of MXM JAVA reference software . 22
B.1 Software requirements . 22
B.2 Building the MXM source code . 22
Annex C (informative) Development with the MXM Java implementation . 24
C.1 Overview . 24
C.2 Developing an MXM Engine . 24
© ISO/IEC 2013 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 23006-3:2013(E)
C.3 Using an MXM Engine API from MXM application .25
C.4 Extending an MXM Engine .26
C.5 How to generate on your own the mxm-dataobject module .26
Bibliography .28

iv © ISO/IEC 2013 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 23006-3:2013(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 23006-3 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
This second edition cancels and replaces the first edition (ISO/IEC 23006-3:2011), which has been technically
revised.
ISO/IEC 23006 consists of the following parts, under the general title Information technology — Multimedia
service platform technologies:
 Part 1: Architecture
 Part 2: MPEG extensible middleware (MXM) API
 Part 3: Conformance and reference software
 Part 4: Elementary services
 Part 5: Service aggregation
© ISO/IEC 2013 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 23006-3:2013(E)
Introduction
ISO/IEC 23006 is a suite of standards that has been developed for the purpose of enabling the easy design
and implementation of media-handling value chains whose devices interoperate because they are all based
on the same set of technologies, especially MPEG technologies, accessible from the middleware APIs,
elementary services and aggregated services.
ISO/IEC 23006 is referred to as MPEG Extensible Middleware (MXM) in its first edition, and it specifies an
architecture (Part 1), an API (Part 2), a conformance and reference software (Part 3) and a set of protocols to
which MXM Devices had to adhere (Part 4).
ISO/IEC 23006 is referred as Multimedia Service Platform Technologies (also abbreviated as MPEG-M) in its
second edition, and it conserves the architecture and design philosophy of the first edition, while stressing the
Service Oriented Architecture character. It specifies also how to combine elementary services into aggregated
services (Part 5).
ISO/IEC 23006 is subdivided in five parts:
Part 1 – Architecture: specifies the architecture that can be used as a guide to an MPEG-M implementation;
Part 2 – MPEG Extensible Middleware (MXM) Application Programming Interface (APIs): specifies the
middleware APIs;
Part 3 – Conformance and Reference Software (the present document): specifies conformance criteria and a
reference software implementation with a normative value;
Part 4 – Elementary Services: specifies elementary service protocols between MPEG-M applications; and
Part 5 – Service Aggregation: specifies mechanisms enabling the combination of Elementary Services and
other services to build Aggregated Services.
vi © ISO/IEC 2013 – All rights reserved

---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO/IEC 23006-3:2013(E)

Information technology — Multimedia service platform
technologies — Part 3: Conformance and reference software
1 Scope
This part of ISO/IEC 23006 describes the reference software implementing the normative clauses of
ISO/IEC 23006-1, ISO/IEC 23006-2 and ISO/IEC 23006-4 and specifies conformance criteria. The information
provided is applicable for determining the reference software modules available for ISO/IEC 23006-1,
understanding the functionality of the available reference software modules and utilizing the available
reference software modules.
The conformance profiles apply to MPEG-M Services as defined in ISO/IEC 23006-4:2013 and in
ISO/IEC 23006-5.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 23006-1, Information technology — Multimedia service platform technologies — Part 1: Architecture
ISO/IEC 23006-2, Information technology — Multimedia service platform technologies — Part 2: MPEG
extensible middleware (MXM) API
ISO/IEC 23006-4, Information technology — Multimedia service platform technologies — Part 4: Elementary
services
ISO/IEC 23006-5, Information technology — Multimedia service platform technologies — Part 5: Service
aggregation
ISO/IEC 15938 (all parts), Information technology — Multimedia content description interface
ISO/IEC 21000 (all parts), Information technology — Multimedia framework (MPEG-21)
ISO/IEC 23000 (all parts), Information technology — Multimedia application format (MPEG-A)
ISO/IEC 23001 (all parts), Information technology — MPEG systems technologies
ISO/IEC 23002 (all parts), Information technology — MPEG video technologies
ISO/IEC 23003 (all parts), Information technology — MPEG audio technologies
1
ISO 15836:2003 , Information and documentation — The Dublin Core metadata element set

1
ISO 15836:2003 has been cancelled and replaced by ISO 15836:2009.
© ISO/IEC 2013 – All rights reserved 1

---------------------- Page: 7 ----------------------
ISO/IEC 23006-3:2013(E)
IETF RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, IETF Request For Comments, January
2005
W3C XML, Extensible Markup Language (XML) 1.0 (Fourth Edition), W3C Recommendation, 29 September
2006
W3C XMLNAMES, Namespaces in XML 1.0 (Second Edition), W3C Recommendation, 16 August 2006
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply:
3.1.1
Aggregated Service
service resulting from the combination of Elementary Services
3.1.2
Elementary Service
basic unit of service
3.1.3
content
Digital Item and its component elements, namely resources (e.g., media, scripts, executable), identifiers,
descriptions (e.g., metadata), event reports
3.1.4
contract
set of metadata, licenses, promises and signers agreed by Users of a multimedia value chain, where a
promise is a signed collection of statements about, e.g., obligations, prohibitions and assertions, and a signer
is a user whose signature makes the contract valid
3.1.5
device
hardware/software or simply software apparatus that enables a user to play a role in multimedia value chains
3.1.6
event
performance of a specified set of functions or Operations
3.1.7
entity
one of the following elements in the multimedia value chain: content, contract, device, event, license,
service, and user
3.1.8
license
collection of authorizations, conditions and payment terms granted by a user to other users
3.1.9
protocol
set of rules and data format used by two Devices to communicate
2 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 8 ----------------------
ISO/IEC 23006-3:2013(E)
3.1.10
resource
individually identifiable asset or a sequence of assets such as a video or audio clip, a 3D synthetic scene, an
image, a textual asset, a 2D LASeR scene, a web page, a single program or a full 24 hour programming of a
TV broadcast, a script or executable, etc.
3.1.11
right
ability of a user to perform an Operation in the multimedia value chain
3.1.12
role
ability of a user to perform a set of Operations in the multimedia value chain
3.1.13
service
operation performed on an entity by a user on behalf of other users
3.1.14
service provider
user offering services to other users
3.1.15
user
any participant in multimedia value chains
3.1.16
value chain
collection of users, including Creators, End Users and Service Providers, that conform to this standard
3.1.17
MPEG-M Application
application that runs on an MPEG-M device and makes calls to the MPEG-M Application API and MPEG-M
Engine APIs
3.1.18
MPEG-M Device
device equipped with a selected set of MPEG-M engines
3.1.19
MPEG-M Engine
collection of specific technologies that are bundled together to provide a specific functionality that is needed
by MPEG-M Applications
3.1.20
MPEG-M Engine API
API of a single MPEG-M Engine
3.1.21
MPEG-M Orchestrator API
API of the MPEG-M Orchestrator Engine.
3.1.22
MPEG-M Orchestrator Engine
special MPEG-M Engine capable of creating chains of MPEG-M engines, i.e. to set-up a sequence of
connected MPEG-M engines for the purpose of executing a high-level application call such as Play
© ISO/IEC 2013 – All rights reserved 3

---------------------- Page: 9 ----------------------
ISO/IEC 23006-3:2013(E)
3.1.23
MPEG-M Technology
technology that is required to implement (a profile of) MPEG-M
3.2 Abbreviated terms
For the purposes of this document, the abbreviated terms given in the following apply:
AIT Advanced IPTV Terminal
AS Aggregated Service
BBL Bitstream Binding Language
BPMN Business Process Model and Notation
CEL Contract Expression Language
DI Digital Item
DIA Digital Item Adaptation
DID Digital Item Declaration
DIDL Digital Item Declaration Language
DII Digital Item Identification
DIS Digital Item Streaming
ER Event Report
ERR Event Report Request
ES Elementary Service
IPMP Intellectual Property Management and Protection
IPTV Internet Protocol Television
MDS Multimedia Description Schemes
MPEG Moving Picture Experts Group
MPEG-21 Multimedia Framework (see ISO/IEC 21000)
MPEG-A Multimedia application format (see ISO/IEC 23000)
MPEG-M Multimedia Service Platform Technologies (see ISO/IEC 23006)
MPQF MPEG Query Format
REL Rights Expression Language
RTP Real Time Protocol
RTSP Real Time Streaming Protocol
URI Uniform Resource Identifier
URL Uniform Resource Locator
WSDL Web Services Description Language
XML   Extensible Markup Language
XSD   XML Schema Definition
XSLT   Extensible Stylesheet Language Transformations
4 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 23006-3:2013(E)
4 Namespaces and conventions
4.1 Introduction
For clarity, throughout this Part of ISO/IEC 23006, consistent namespace prefixes are used.
"xml:" and "xmlns:" are normative prefixes defined in W3C XMLNAMES. The prefix "xml:" is by definition
bound to "http://www.w3.org/XML/1998/namespace". The prefix "xmlns:" is used only for namespace
bindings and is not itself bound to any namespace name.
"xsi:" prefix is not normative. It is a naming convention in this document to refer to an element of the
http://www.w3.org/2001/XMLSchema-instance namespace. All other prefixes used in either the text
or examples of this specification are not normative, e.g., "mpegm:", "dia:".
In particular, most of the informative examples in this specification are provided as XML fragments without the
normally required XML document declaration and, thus, miss a correct namespace binding context declaration.
Unless specified otherwise, all unqualified descriptions fragments assume the default namespace
"urn:mpeg:mpegM:schema:02-service-NS:2012".
In these descriptions fragments the different prefixes are bound to the namespaces as given in Table 1. The
schema locations of the namespaces in Table 1 are only an informative indication as schema locations may
change over time.
Tabelle 1 — Mapping of prefixes to namespaces used in examples and text
Prefix Corresponding namespace Schema location
mpegm urn:mpeg:mpegM:schema:02-service-NS:2011
mpegmb urn:mpeg:mpegM:schema:01-base-NS:2011
dia urn:mpeg:mpeg21:2003:01-DIA-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
/MPEG-
21_schema_file
s/dia-2nd/UED-
2nd.xsd
erl urn:mpeg:mpeg21:2005:01-ERL-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
/MPEG-
21_schema_file
s/er/er.xsd
fru urn:mpeg:mpegB:schema:FragmentRequestUnits:2007 Defined in
ISO/IEC 23001-
2:2008
mpeg7 urn:mpeg:mpeg7:schema:2004
mpeg7s urn:mpeg:mpeg7:systems:2001
cel urn:mpeg:mpeg21:cel:contract:2011
bbl urn:mpeg:mpeg21:2007:01-BBL-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
© ISO/IEC 2013 – All rights reserved 5

---------------------- Page: 11 ----------------------
ISO/IEC 23006-3:2013(E)
/MPEG-
21_schema_file
s/dis/bbl.xsd
dii urn:mpeg:mpeg21:2002:01-DII-NS
mpqf urn:mpeg:mpqf:schema:2008 Defined in
ISO/IEC 15938-
12
mpeg4ipmp urn:mpeg:mpeg4:IPMPSchema:2002 Defined in
ISO/IEC 14496-
13:2004
ipmpdidl urn:mpeg:mpeg21:2004:01-IPMPDIDL-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
/MPEG-
21_schema_file
s/ipmp/ipmpdid
l.xsd
ipmpmsg urn:mpeg:mpegB:schema:IPMP-XML-MESSAGES:2007 Defined in
ISO/IEC 23001-
3:2008
ipmpinfo urn:mpeg:mpeg21:2004:01-IPMPINFO-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
/MPEG-
21_schema_file
s/ipmp/ipmpgen
eral.xsd
didl urn:mpeg:mpeg21:2002:02-DIDL-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
/MPEG-
21_schema_file
s/did/didl.xsd
mpegm-urn:mpeg:mpegM:schema:06-didl-NS:2012
didl
didmodel urn:mpeg:mpeg21:2002:02-DIDMODEL-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
/MPEG-
21_schema_file
s/did/didmodel
.xsd
didl-msx urn:mpeg:maf:schema:mediastreaming:DIDLextensions Defined in
ISO/IEC 23000-
5:2011
dii urn:mpeg:mpeg21:2002:01-DII-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
/MPEG-
6 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 12 ----------------------
ISO/IEC 23006-3:2013(E)
21_schema_file
s/dii/dii.xsd
rel-r urn:mpeg:mpeg21:2003:01-REL-R-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
/MPEG-
21_schema_file
s/rel-r/rel-
r.xsd
rel-sx urn:mpeg:mpeg21:2003:01-REL-SX-NS http://standar
ds.iso.org/itt
f/PubliclyAvai
lableStandards
/MPEG-
21_schema_file
s/rel-r/rel-
sx.xsd
xsd http://www.w3.org/2001/XMLSchema http://www.w3.
org/2001/XMLSc
hema.xsd
xsi http://www.w3.org/2001/XMLSchema-instance
dsig http://www.w3.org/2000/09/xmldsig# http://www.w3.
org/TR/2002/RE
C-xmldsig-
core-
20020212/xmlds
ig-core-
schema.xsd
xenc http://www.w3.org/2001/04/xmlenc#
bpmn http://www.omg.org/spec/BPMN/20100524/MODEL http://www.omg
.org/spec/BPMN
/20100501/BPMN
20.xsd
bpmnext1 urn:mpeg:mpegM:schema:04-bpmn-ext-mfr-NS:2012
ca urn:mpeg:mpegM:service-type:04-content-adaptation-
NS:2012
cel urn:mpeg:mpeg21:2010:01-CEL-NS
cidl urn:mpeg:mpeg-v:2010:01-CIDL-NS
dc http://purl.org/dc/elements/1.1/ http://dublinc
ore.org/schema
s/xmls/qdc/200
8/02/11/dc.xsd
dcdv urn:mpeg:mpeg-v:2010:01-DCDV-NS
ebucore urn:ebu:metadata-schema:ebuCore_2010 http://www.ebu
.ch/metadata/s
chemas/EBUCore
/20100820/EBU_
CORE_20100820.
xsd
esi urn:mpeg:mpegM:service-type:03-extract-sensory-
© ISO/IEC 2013 – All rights reserved 7

---------------------- Page: 13 ----------------------
ISO/IEC 23006-3:2013(E)
information-NS:2012
etsi urn:dvb:metadata:iptv:sdns:2008-1 Defined in
ETSI TS 102
034 [6]
ipmpinfo- urn:mpeg:maf:Schema:mediastreaming:IPMPINFOextensioDefined in
msx ns:2007 ISO/IEC 23000-
5:2011
rs urn:mpeg:mpegM:service-type:01-recognize-speech-
NS:2012
saml urn:oasis:names:tc:SAML:2.0:assertion http://docs.oa
sis-
open.org/secur
ity/saml/v2.0/
saml-schema-
assertion-
2.0.xsd
samlp urn:oasis:names:tc:SAML:2.0:protocol http://docs.oa
sis-
open.org/secur
ity/saml/v2.0/
saml-schema-
protocol-
2.0.xsd
sedl urn:mpeg:mpeg-v:2010:01-SEDL-NS
sepv urn:mpeg:mpeg-v:2010:01-SEPV-NS
sev urn:mpeg:mpeg-v:2010:01-SEV-NS
sid urn:mpeg:mpegM:schema:05-sid-NS:2012
ss urn:mpeg:mpegM:service-type:02-synthesize-speech-
NS:2012
tva urn:tva:metadata:2010 Defined in
ETSI TS 102
822-3-1 [7]
wsdl http://www.w3.org/ns/wsdl http://www.w3.
org/2002/ws/de
sc/ns/wsdl20.x
sd
xsl http://www.w3.org/1999/XSL/Transform http://www.w3.
org/2007/schem
a-for-
xslt20.xsd
xhtml http://www.w3.org/1999/xhtml http://www.w3.
org/MarkUp/SCH
EMA/xhtml11.xs
d
8 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 14 ----------------------
ISO/IEC 23006-3:2013(E)

5 Reference software overview
5.1 Introduction
The reference software described in this Part of ISO/IEC 23006 covers all the main functionalities highlighted
in the MPEG-M standard Part 1, Part 2 and Part 4.
5.2 The MXM software repository
The Figure 1 — The MXM software structure shows a graphical representation of the MXM software structure.
The MXM software is provided in attach or on the official MPEG-M svn repository [1].
The JAVA trunk folder contains all the JAVA MXM reference software modules. At the moment no C/C++
reference software for MXM is provided for the second edition of ISO/IEC 23006.
© ISO/IEC 2013 – All rights reserved 9

---------------------- Page: 15 ----------------------
ISO/IEC 23006-3:2013(E)

Figure 1 — The MXM software structure
6 MXM Java software implementation
6.1 Introduction
The Java MXM software is available in source code under the terms of the BSD License [2]. The software is
organised in a number of projects, whose build is managed by Maven [5]. All projects have a common
structure:
10 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 16 ----------------------
ISO/IEC 23006-3:2013(E)
— src/main/java, containing the main classes and/or interfaces organised in packages;
— src/main/resources, containing the resources (e.g. xml files, properties files, etc.) used by the engine or
the application at runtime;
— src/test/java, containing the unit test classes used to test the main classes;
— src/test/resources, containing those resources which are used by the tests when being executed.
The Java MXM software is divided in the mxm-core, mxm-engines, mxm-es, mxm-applications and mxm-
dataobject modules.
6.2 mxm-core (normative)
It defines the MXM APIs and it provides a thin layer of code implementing MXM as a factory of MXM Engines
based on the contents of the MXM Configuration File passed to MXM when instantiated. Summarising, mxm-
core contains the following categories of classes:
— all the interfaces defining the MXM API conforming but not limited to the MPEG-M Part 2 API
specifications of Protocol and Technology Engines [ISO/IEC 23006-2];
— a number of classes for:
o parsing the MXM Configuration File (conforming to the MXM Configuration Schema depicted in
Annex A from MPEG-M Part 2) defining which MXM Engines specific implementations shall be
loaded;
o loading the specified MXM Engines. mxm-core acts as a factory providing to the MXM
Applications one or more instances of the MXM Engines listed in the MXM Configuration File.
The mxm-core is the part of MXM that essentially enables the interoperability between the various
implementations of MXM Engines and guarantees the conformance of the software to the standard. The
former is achieved by:
— using a general container to carry the data units;
— defining all the interfaces provided by the MXM APIs, so that, even if their implementation is different, the
same calls will be made to the Technology Engines transparently, using the methods defined in the core
interfaces.
The latter is achieved because the MXM Engines implement a standard interfaces; hence, an MXM
Application that only relies on the standard APIs to make the calls to the MXM Technology Engines will only
work if the underlying middleware implementation conforms to the standard APIs.
MXM defines a fundamental interface called MXMObject and the class implementing is the MXMAdpater.
These two are the basic containers for the data exchanged between the MXM Engines ensuring the
interoperability between different MXM Engine implementations. Every information unit has to be wrapped
inside an MXMObject to be passed to another MXM Engine, which in turn converts it back to a data structure
that can be handled.
Other important parts of mxm-core are the MXM Engine related classes and interfaces that define t
...

INTERNATIONAL ISO/IEC
STANDARD 23006-3
Second edition
2013-09-15

Information technology — Multimedia
service platform technologies —
Part 3:
Conformance and reference software
Technologies de l'information — Technologies de la plate-forme de
services multimédia —
Partie 3: Conformité et logiciel de référence




Reference number
ISO/IEC 23006-3:2013(E)
©
ISO/IEC 2013

---------------------- Page: 1 ----------------------
ISO/IEC 23006-3:2013(E)


This CD-ROM contains:
1) the publication ISO/IEC ISO/IEC 23006-3:2013 in portable document format (PDF), which can be
viewed using Adobe® Acrobat® Reader;
2) reference software.
Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

This second edition cancels and replaces the first edition (ISO/IEC 23006-3:2011), which has been technically
revised.
COPYRIGHT PROTECTED DOCUMENT


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

---------------------- Page: 2 ----------------------
ISO/IEC 23006-3:2013(E)
Installation
If this publication has been packaged as a zipped file,
...

Questions, Comments and Discussion

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