ISO/IEC 23093-3:2019

INTERNATIONAL ISO/IEC
STANDARD 23093-3
First edition
2019-11
Information technology — Internet of
media things —
Part 3:
Media data formats and APIs
Technologies de l'information — Internet des objets media —
Partie 3: API et formats des données
Reference number
©
ISO/IEC 2019
© ISO/IEC 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – All rights reserved

Contents Page
Foreword . vii
Introduction . viii
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
3.3 Schema documents. 2
prefixes . 3
3.4 Use of
4 APIs . 3
4.1 General . 3
4.2 APIs for IoMT sensors . 5
4.2.1 General . 5
4.2.2 MSensor class . 5
4.2.3 API for IoMT microphone . 7
4.2.4 API for IoMT camera . 9
4.2.5 API for IoMT RFID reader . 11
4.2.6 API for IoMT compass sensor . 13
4.2.7 API for IoMT orientation sensor . 15
4.2.8 API for IoMT position sensor . 16
4.2.9 API for IoMT global positioning sensor . 17
4.2.10 API for IoMT distance sensor . 20
4.3 APIs for IoMT actuators . 21
4.3.1 General . 21
4.3.2 MActuator class . 21
4.3.3 API for IoMT speaker . 23
4.3.4 API for IoMT display . 26
4.3.5 API for IoMT camera actuator . 30
4.3.6 API for IoMT hand gesture actuator . 33
4.3.7 API for IoMT vibrator . 34
4.3.8 API for IoMT sprayer . 36
4.3.9 API for IoMT light . 39
4.4 APIs for IoMT analyzers . 42
4.4.1 General . 42
4.4.2 MAnalyzer class . 43
4.4.3 API for IoMT time synchronizer . 44
4.4.4 API for IoMT social event detector . 46
4.4.5 API for IoMT hand gesture detector . 47
4.4.6 API for IoMT hand gesture recognizer . 49
4.4.7 API for IoMT healthcare information generator . 50
4.4.8 API for IoMT speech recognizer . 52
4.4.9 API for IoMT text to speech converter . 53
4.4.10 API for IoMT question analyzer . 55
4.4.11 API for IoMT odor image to scent converter . 56
4.4.12 API for IoMT direction guider . 58
© ISO/IEC 2019 – All rights reserved iii

4.4.13 API for IoMT collision coordinator . 60
4.4.14 API for IoMT people counter . 63
4.4.15 API for IoMT music frequency analyzer . 65
4.4.16 API for IoMT light color converter . 67
4.4.17 API for IoMT video content class generator . 68
4.5 APIs for IoMT storages . 70
4.5.1 General . 70
4.5.2 MStorage class . 70
4.6 APIs for IoMT managers . 73
4.6.1 General . 73
4.6.2 MManager class . 73
4.7 APIs for IoMT aggregators . 75
4.7.1 General . 75
4.7.2 MAggregator class . 76
4.8 Return type class . 78
4.8.1 General . 78
4.8.2 MPEGVCapabilityType . 78
4.8.3 MPEGVSensedDataType . 82
4.8.4 MPEGVCommandType . 85
4.8.5 IoMT SensedDataType . 88
4.8.6 IoMT ActuationDataType . 91
4.8.7 IoMT AnalyzedDataType . 94
4.8.8 IoMT CapabilityListType . 97
4.8.9 IoMT MThingInfoType . 100
5 Media thing description language . 103
5.1 General . 103
5.2 Schema wrapper . 103
5.3 Base datatypes and elements . 104
5.3.1 Syntax . 104
5.3.2 Semantics . 105
5.4 Root element . 106
5.4.1 Syntax . 106
5.4.2 Semantics . 107
5.5 Media sensor description language . 107
5.5.1 General . 107
5.5.2 Syntax . 107
5.5.3 Semantics . 108
5.5.4 Example . 109
5.6 Media actuator description language . 109
5.6.1 General . 109
5.6.2 Syntax . 109
5.6.3 Semantics . 110
5.6.4 Example . 111
5.7 Media analyzer description language . 111
5.7.1 General . 111
5.7.2 Syntax . 111
5.7.3 Semantics . 112
5.7.4 Example . 113
5.8 Media storage description language . 113
5.8.1 General . 113
5.8.2 Syntax . 113
5.8.3 Semantics . 114
5.8.4 Example . 115
5.9 Media manager description language . 115
iv © ISO/IEC 2019 – All rights reserved

5.9.1 General . 115
5.9.2 Syntax . 115
5.9.3 Semantics . 116
5.9.4 Example . 117
5.10 Media aggregator description language . 117
5.10.1 General . 117
5.10.2 Syntax . 118
5.10.3 Semantics . 119
5.10.4 Example . 119
6 Media sensor output vocabulary . 122
6.1 General . 122
6.2 Schema wrapper . 122
6.3 IoMT sensed data captured time . 122
6.3.1 General . 122
6.3.2 Syntax . 123
6.3.3 Semantics . 123
6.3.4 Example . 123
7 Media actuator command vocabulary . 123
7.1 General . 123
7.2 Schema wrapper . 124
7.3 IoMT speaker . 124
7.3.1 General . 124
7.3.2 Syntax . 124
7.3.3 Semantics . 125
7.3.4 Example . 125
7.4 IoMT display . 126
7.4.1 General . 126
7.4.2 Syntax . 126
7.4.3 Semantics . 127
7.4.4 Example . 127
7.5 IoMT camera actuator . 127
7.5.1 General . 127
7.5.2 Syntax . 128
7.5.3 Semantics . 129
7.5.4 Example . 129
7.6 IoMT light . 130
7.6.1 General . 130
7.6.2 Syntax . 130
7.6.3 Semantics . 130
7.6.4 Example . 131
8 Media analyzer output vocabulary . 131
8.1 General . 131
8.2 Schema wrapper . 132
8.3 IoMT time synchronizer . 132
8.3.1 General . 132
8.3.2 Syntax . 133
8.3.3 Semantics . 133
8.3.4 Example . 133
8.4 IoMT social event detector . 134
8.4.1 General . 134
8.4.2 Syntax . 134
8.4.3 Semantics . 134
8.4.4 Example . 134
© ISO/IEC 2019 – All rights reserved v

8.5 IoMT hand gesture detector . 135
8.5.1 General . 135
8.5.2 Syntax . 135
8.5.3 Semantics . 136
8.5.4 Example . 138
8.6 IoMT hand gesture recognizer . 142
8.6.1 General . 142
8.6.2 Syntax . 142
8.6.3 Semantics . 143
8.6.4 Example . 144
8.7 IoMT hand gesture command generator . 144
8.7.1 General . 144
8.7.2 Syntax . 145
8.7.3 Semantics . 145
8.7.4 Example . 145
8.8 IoMT healthcare information generator . 145
8.8.1 General . 145
8.8.2 Syntax . 145
8.8.3 Semantics . 147
8.8.4 Examples . 148
8.9 IoMT odor image to scent converter . 150
8.9.1 General . 150
8.9.2 Syntax . 150
8.9.3 Semantics . 150
8.9.4 Example . 151
8.10 IoMT question analyzer . 151
8.10.1 General . 151
8.10.2 Syntax . 152
8.10.3 Semantics . 152
8.10.4 Examples . 153
8.11 IoMT music frequency analyzer . 154
8.11.1 General . 154
8.11.2 Syntax . 154
8.11.3 Semantics . 155
8.11.4 Examples . 155
8.12 IoMT video content class generator . 156
8.12.1 General . 156
8.12.2 Syntax . 156
8.12.3 Semantics . 156
8.12.4 Examples . 156
Annex A (normative) Classification scheme . 157
Annex B (informative) Schema documents . 277
Bibliography . 278
vi © ISO/IEC 2019 – All rights reserved

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.
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) or the
IEC list of patent declarations received (see http://patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, 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 www.iso.org/iso/foreword.html.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
A list of all parts in the ISO/IEC 23093 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
© ISO/IEC 2019 – All rights reserved vii

Introduction
The ISO/IEC 23093 series provides an architecture and specifies APIs and compressed representation
of data flowing between media things.
The APIs for the media things facilitate discovering other media things in the network, connecting and
efficiently exchanging data between media things. The APIs also provide means for supporting
transaction tokens in order to access valuable functionalities, resources, and data from media things.
Media things related information consists of characteristics and discovery data, setup information from
a system designer, raw and processed sensed data, and actuation information. The ISO/IEC 23093
series specifies data formats of input and output for media sensors, media actuators, media storages,
media analyzers, etc. Sensed data from media sensors can be processed by media analyzers to produce
analysed data, and the media analyzers can be cascaded in order to extract semantic information.
This document contains the tools to describe data exchanged between media things (e.g. media sensors,
media actuators, media analyzers, media storages) and their APIs. It addresses the normative aspects of
the data and APIs for media things and also illustrates non‐normative examples.
The International Organization for Standardization (ISO) and the International Electrotechnical
Commission (IEC) draw attention to the fact that it is claimed that compliance with this document may
involve the use of patents.
ISO and the IEC take no position concerning the evidence, validity and scope of these patent rights.
The holders of these patent rights have assured the ISO and IEC that they are willing to negotiate
licences under reasonable and non‐discriminatory terms and conditions with applicants throughout the
world. In this respect, the statements of the holders of these patents right are registered with ISO and
IEC. Information may be obtained from the patent database available at www.iso.org/patents.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights other than those identified in the patent database. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
viii © ISO/IEC 2019 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 23005-3:2019(E)

Information technology — Internet of media things —
Part 3:
Media data formats and APIs
1 Scope
This document specifies syntax and semantics of description schemes to represent data exchanged by
media things (e.g. media sensors, media actuators, media analyzers, media storages). Moreover, it
specifies the APIs to exchange these data between media things.
This document does not specify how the process of sensing and analyzing is carried out but specifies the
interfaces between the media things.
2 Normative references
The following documents are referred to in the 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 15938‐5:2003, Information technology — Multimedia content description interface — Part 5:
Multimedia description schemes
ISO/IEC 23005‐2, Information technology — Media context and control — Part 2: Control information
ISO/IEC 23005‐5, Information technology — Media context and control — Part 5: Data formats for
interaction devices
ISO/IEC 23093‐1, Information technology — Internet of media things — Part 1: Architecture
ISO/IEC 23093‐2, Information technology — Internet of media things — Part 2: Discovery and
communication API
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 23093‐1 and 23093‐2
and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/
© ISO/IEC 2019 – All rights reserved 1

3.1.1
media actuator
MActuator
MThing that can actuate
3.1.2
media aggregator
MAggregator
MThing that contains multiple MThings
3.1.3
media analyzer
MAnalyzer
MThing that can analyze media or metadata, and produce interpreted media, metadata, or commands
3.1.4
media manager
MManager
MThing that can register a list of MThings or be facilitated to search other MThings
3.1.5
media sensor
MSensor
MThing that can sense and produce media data
3.1.6
media storage
MStorage
MThing that can save media or metadata
3.2 Abbreviated terms
API application programming interface
MACV media actuator command vocabulary
MAOV media analyzer output vocabulary
MSOV media sensor output vocabulary
MTDL media thing description language
SCDV sensor capability description vocabulary
XML extensible mark‐up language
XSI XML streaming instructions
3.3 Schema documents
In the main text of this document, the syntax of description schemes and descriptors is provided
whenever possible as a single schema document.
In some cases though, and in particular for Clauses 6, 7 and 8, the syntax of description schemes and
descriptors is provided as a collection of schema snippets imbricated with other text. In order to form a
valid schema document, these schema components are intended to be gathered in the same document
2 © ISO/IEC 2019 – All rights reserved

with the schema wrapper provided at the head of the clause. For better readability, the relevant schema
documents are provided in Annex B.
In all cases, each schema document has a version attribute, the value of which is "ISO/IEC 23093‐3".
Furthermore, an informative identifier is given as the value of the id attribute of the schema
component. This identifier is non‐normative and used as a convention in this document to reference
another schema document. In particular, it is used for the schemaLocation attribute of the include
and import schema components.
3.4 Use of prefixes
For clarity, throughout this document, consistent namespace prefixes are used.
"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.
"xml:" and "xmlns:" are normative prefixes defined in Reference [1]. 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.
All other prefixes used in either the text or examples of this document are not normative, e.g. “mtdl:”,
“msov:”, “macv:”, “maov:”, “mpeg7:”, “scdv:”.
In particular, most of the informative examples in this document are provided as XML fragments
without the normally required XML document declaration and, thus, miss a correct namespace binding
context declaration. In these descriptions fragments, the different prefixes are bound to the
namespaces as given in Table 1.
Table 1 — Mapping of prefixes to namespaces in examples and text
Prefix Corresponding namespace
scdv urn:mpeg:mpeg-v:2018:01-SCDV-NS
mpeg7 urn:mpeg:mpeg7:schema:2004
mtdl urn:mpeg:mpeg-IoMT:2018:01-MTDL-NS
msov urn:mpeg:mpeg-IoMT:2018:01-MSOV-NS
macv urn:mpeg:mpeg-IoMT:2018:01-MACV-NS
maov urn:mpeg:mpeg-IoMT:2018:01-MAOV-NS
xsi http://www.w3.org/2001/XMLSchema-instance
xsd http://www.w3.org/2001/XMLSchema
Unlike the informative descriptions examples, the normative specification of the syntax of tools in XML
schema follows the namespace binding context defined in the relevant schema declaration such as the
one defined in 6.2.
4 APIs
4.1 General
This subclause specifies APIs and their descriptions to operate MThings and/or exchange structured
data between MThings. Figure 1 shows an example of “GET” and “SET” functions invoked between
© ISO/IEC 2019 – All rights reserved 3

MThings. For example, an MSensor should have “GET” functions to evoke and provide its sensed data.
An MStorage should have “SET” functions to save sensed data obtained by an MSensor or to save
analyzed
...