ISO/IEC 23093-3:2026

• Abstract:

  This document specifies the syntax and semantics of description schemes for representing data exchanged by media things (e.g. media sensors, media actuators, and media storages). Moreover, it specifies the APIs to exchange these data between media things. The following interfaces are under the scope of this document: APIs for accessing media sensors, actuators, storage, managers, controllers, and aggregators; structured data formats (XML) representing media thing’s base data types, including sensors, actuators, storage, managers, aggregators, controllers, and their elements; structured data formats (XML) representing the media sensor’s output data; and, structured data formats (XML) representing media actuator’s commands. This document does not specify how sensing and actuating are carried out but defines the interfaces between the media things.

• Status: Published
• Publication Date: 23-Jul-2026
• ICS: 35.040.40 - Coding of audio, video, multimedia and hypermedia information
• Technical Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Drafting Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Current Stage: 6060 - International Standard published
• Start Date: 24-Jul-2026
• Due Date: 18-Jan-2026
• Completion Date: 24-Jul-2026

• Revises: ISO/IEC 23093-3:2022 - Information technology — Internet of media things — Part 3: Media data formats and APIs
• Effective Date: 28-Jan-2023

ISO/IEC 23093-3:2026 is an International Standard from ISO and IEC for the Internet of media things. It specifies XML-based description schemes and APIs for exchanging data between media things such as sensors, actuators, storage, managers, controllers, and aggregators. Engineers, integrators, and buyers use it when they need a common interface for media data and control rather than a description of how the devices themselves perform sensing or actuation.

What does ISO/IEC 23093-3:2026 specify?

ISO/IEC 23093-3:2026 specifies the syntax and semantics for representing data exchanged by media things and the APIs used to exchange that data. It covers both structured XML data formats and the interfaces between media things.

The scope includes:

• APIs for accessing media sensors, actuators, storage, managers, controllers, and aggregators
• XML data formats for media thing base data types and their elements
• XML data formats for media sensor output data
• XML data formats for media actuator commands

ISO/IEC 23093-3:2026 does not specify how sensing and actuating are performed. In practice, that means the standard defines the software-facing contract between devices and platforms, not the internal hardware or control mechanisms.

The document is organized into:

• Clause 1 - Scope
• Clause 2 - Normative references
• Clause 3 - Terms, definitions, and abbreviated terms
• Clause 4 - Schema documents and prefixes
• Clause 5 - APIs
• Clause 6 - Media thing description language
• Clause 7 - Media sensor output vocabulary
• Clause 8 - Media actuator command vocabulary
• Annex A - Classification scheme
• Annex B - Examples and application scenarios

Annex	What it covers
Annex A	Classification scheme for MThing types, capabilities, capability parameters, and token types
Annex B	Example uses, including NFT generation from sensor data and connecting Matter devices through a bridge to an IoMT actuator

What are the key requirements of ISO/IEC 23093-3:2026?

ISO/IEC 23093-3:2026 sets out the API patterns, schema conventions, and data models that make media things interoperable. The most important requirements are spread across Clauses 4 to 8.

• Clause 4 defines how schema documents are assembled and how prefixes are used.

  • The standard uses XML Schema components with a target namespace and a version attribute value of "ISO/IEC 23093-3".
  • It also distinguishes normative prefixes such as xml: and xmlns: from convention-based prefixes such as mtdl:, msov:, and macv:.
  • In practice, implementers need these conventions so their schemas validate and their XML fragments can be exchanged without namespace confusion.

• Clause 5 defines the main API behavior for MThings.

  • MSensor uses GET functions to provide sensed data.
  • MStorage uses SET functions to store sensed or analysed data.
  • MActuator uses SET functions to control device behavior.
  • MAnalyser provides GET functions for derived data.
  • In practice, this gives developers a common calling model for reading data from sensors, storing it, and sending commands to actuators.

• Clause 5.7 defines the return type classes used by those APIs.

  • The document includes classes such as MPEGVCapabilityType, MPEGVSensedDataType, MPEGVCommandType, IoMT SensedDataType, IoMT ActuationDataType, IoMT AnalysedDataType, IoMT MissionDataType, IoMT CapabilityListType, and IoMT MThingInfoType.
  • These are provided as object-oriented programming (OOP), C++, and C structure forms where applicable.
  • In practice, a team can map the same information into XML or binary form and still keep the same logical meaning across software stacks.

• Clause 6 defines the media thing description language (MTDL).

  • MTDL covers the basic structure of the tools in the document, including base data types, root elements, and top-level elements.
  • It also defines binary representation mnemonics such as bit-string and integer notation, using the conventions referenced from ISO/IEC 15938-3.
  • In practice, this clause is the core schema layer for describing media things in a machine-readable way.

• Clause 6 also provides description languages for each major MThing category.

  • Separate subclauses cover media sensor, media actuator, media analyser, media storage, media manager, media aggregator, and media controller description languages.
  • In practice, this lets implementers describe each device role with a compatible XML structure rather than inventing their own.

• Clause 7 defines the media sensor output vocabulary, MSOV.

  • The vocabulary includes IoMT sensed data captured time.
  • It is designed to be extensible by adding new sensor descriptions while staying aligned with MTDL.
  • In practice, sensor data can be exchanged in a standard form and extended when new sensing types are needed.

• Clause 8 defines the media actuator command vocabulary, MACV.

  • It covers IoMT speaker, IoMT display, IoMT camera actuator, IoMT consecutive vibration device, and IoMT light.
  • It is also extensible through MTDL-based actuation data types.
  • In practice, commands for different actuator types can be encoded in a consistent way, which simplifies integration and gateway translation.

• Annex A provides classification schemes that support discovery and capability descriptions.

  • It includes MThing type classification, capability classification, capability parameters, and token types.
  • In practice, this helps systems identify what a media thing is, what it can do, and how it should be handled in discovery and control flows.

What terms does ISO/IEC 23093-3:2026 define?

ISO/IEC 23093-3:2026 defines the core roles used throughout the standard so that data models, APIs, and descriptions all mean the same thing.

• media sensor (MSensor) - an MThing that can sense and produce media data.
• media actuator (MActuator) - an MThing that can actuate.
• media storage (MStorage) - an MThing that can save media or metadata.
• media manager (MManager) - an MThing that can register a list of MThings or help search for other MThings.
• media aggregator (MAggregator) - an MThing that contains multiple MThings.
• media thing controller (MController) - an MThing that can generate standard mission descriptions and monitor mission progress.
• mission - a task that MThings carry out.
• media thing description language (MTDL) - the XML-based language used to describe media thing data structures and related elements.

Who uses ISO/IEC 23093-3:2026?

ISO/IEC 23093-3:2026 is used by people who build or integrate media things and the software that talks to them.

Typical users include:

• device and firmware developers for IoMT sensors and actuators
• platform and middleware engineers who expose GET and SET APIs
• gateway and bridge developers who translate between IoMT and other ecosystems
• system architects who need common data formats for sensors, storage, managers, aggregators, and controllers
• interoperability and test teams checking whether exchanged data follows the standard
• solution designers who need capability lists, mission data, or standardized command payloads

In practice, the standard is useful when a system must discover devices, exchange structured media data, store results, or send standardized control commands across different implementations.

What changed in ISO/IEC 23093-3:2026 from the previous edition?

ISO/IEC 23093-3:2026 is the third edition and it cancels and replaces ISO/IEC 23093-3:2022. The document says it has been technically revised.

The stated main changes are:

• addition of new APIs and data formats
• addition of MController base types
• removal of MAnalyser APIs and individual data formats

For users of earlier implementations, the practical effect is that controller-related modeling has been expanded while analyser-specific API content has been reduced.

Which standards are used with ISO/IEC 23093-3:2026?

ISO/IEC 23093-3:2026 relies on several referenced standards and companion parts for its data model, binary notation, and broader IoMT framework.

• ISO/IEC 15938-3 - provides the binary notation mnemonics used to describe bit-level representations.
• ISO/IEC 23005-2 - supplies control information referenced by the standard.
• ISO/IEC 23005-5 - supplies data formats for interaction devices.
• ISO/IEC 23093-1 - provides the IoMT architecture and foundational definitions.
• ISO/IEC 23093-2:2025 - provides the discovery and communication API and shared terminology.
• ISO/IEC 23093-5:2025 - covers IoMT autonomous collaboration.
• ISO/IEC 23093-6:2026 - covers IoMT media data formats and API for distributed AI processing.

These references matter because ISO/IEC 23093-3:2026 builds its API and schema model on the shared architecture and data conventions of the wider series.

What does the ISO/IEC 23093-3:2026 document contain?

ISO/IEC 23093-3:2026 contains schema conventions, API definitions, XML vocabularies, binary-representation rules, and worked examples. It also includes figures showing how functions are invoked between MThings and how data flows in a call sequence.

A practical reading of the contents is:

• Clause 4 gives schema document wrappers, namespace usage, and prefix mapping.
• Clause 5 gives API families for sensors, actuators, storage, managers, aggregators, and return type classes.
• Clause 6 gives the MTDL structure, binary mnemonics, base data types, root elements, and description languages for each MThing role.
• Clause 7 gives the sensor output vocabulary and its XML representation.
• Clause 8 gives the actuator command vocabulary and examples such as camera position, zoom, and resolution controls.
• Annex A gives classification scheme material for types, capabilities, capability parameters, and token types.
• Annex B gives application examples, including NFT generation from sensor data and a bridge-based connection to Matter devices.

For implementers, the useful part of the document is the combination of schema fragments, data types, and examples that can be assembled into valid XML schema documents and exchanged between media things.

International
Standard
ISO/IEC 23093-3
Third edition
Information technology — Internet
2026-07
of media things —
Part 3:
Media data formats and application
programming interface (API)
Technologies de l'information — Internet des objets media —
Partie 3: API et formats des données
Reference number
© ISO/IEC 2026
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: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2026 – All rights reserved
ii
Contents Page
Foreword .vii
Introduction .viii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, and abbreviated terms . 2
3.1 Terms and definitions .2
3.2 Abbreviated terms .3
4 Schema documents and prefixes . 3
4.1 Schema documents .3
4.2 Use of prefixes .3
5 APIs . 4
5.1 General .4
5.2 APIs for IoMT sensors.5
5.2.1 General .5
5.2.2 MSensor class .6
5.2.3 API for IoMT microphone.7
5.2.4 API for IoMT camera .9
5.2.5 API for IoMT RFID reader .11
5.2.6 API for IoMT compass sensor . 12
5.2.7 API for IoMT orientation sensor .14
5.2.8 API for IoMT position sensor . 15
5.2.9 API for IoMT global positioning sensor .16
5.2.10 API for IoMT distance sensor .17
5.2.11 API for IoMT light sensor .18
5.2.12 API for IoMT ambient noise sensor .19
5.2.13 API for IoMT temperature sensor . 20
5.2.14 API for IoMT humidity sensor .21
5.2.15 API for IoMT atmospheric pressure sensor . 22
5.2.16 API for IoMT velocity sensor . 23
5.2.17 API for IoMT acceleration sensor .24
5.2.18 API for IoMT angular acceleration sensor . 25
5.2.19 API for IoMT angular velocity sensor . 26
5.2.20 API for IoMT force sensor .27
5.2.21 API for IoMT torque sensor . 28
5.2.22 API for IoMT pressure sensor . 29
5.2.23 API for IoMT motion sensor . 30
5.2.24 API for IoMT intelligent camera sensor .31
5.2.25 API for IoMT multi-interaction point sensor .32
5.2.26 API for IoMT gaze tracking sensor . 33
5.2.27 API for IoMT wind sensor . 34
5.2.28 API for IoMT altitude sensor . 35
5.2.29 API for IoMT gas sensor . 36
5.2.30 API for IoMT dust sensor .37
5.2.31 API for IoMT bend sensor . 38
5.2.32 API for IoMT body height sensor . 39
5.2.33 API for IoMT body weight sensor . 40
5.2.34 API for IoMT body temperature sensor .41
5.2.35 API for IoMT body fat sensor .42
5.2.36 API for IoMT blood-type sensor .43
5.2.37 API for IoMT blood pressure sensor . 44
5.2.38 API for IoMT blood sugar sensor .45
5.2.39 API for IoMT blood oxygen sensor . 46
5.2.40 API for IoMT heart rate sensor .47

© ISO/IEC 2026 – All rights reserved
iii
5.2.41 API for IoMT electrograph sensor . 48
5.2.42 API for IoMT EEG sensor. 49
5.2.43 API for IoMT ECG sensor . . 50
5.2.44 API for IoMT EMG sensor .51
5.2.45 API for IoMT EOG sensor .52
5.2.46 API for IoMT GSR sensor . 53
5.2.47 API for IoMT bio sensor . 54
5.2.48 API for IoMT weather sensor . 55
5.2.49 API for IoMT facial expression sensor . 56
5.2.50 API for IoMT facial morphology sensor . .57
5.2.51 API for IoMT facial expression characteristics sensor . 58
5.2.52 API for IoMT geomagnetic sensor .59
5.2.53 API for IoMT proximity sensor . 60
5.2.54 API for IoMT switch sensor .61
5.2.55 API for IoMT spectrum camera sensor .62
5.2.56 API for IoMT colour camera sensor . 63
5.2.57 API for IoMT depth camera sensor . 64
5.2.58 API for IoMT stereo camera sensor . 65
5.2.59 API for IoMT thermographic camera sensor . 66
5.2.60 API for IoMT engine oil temperature sensor .67
5.2.61 API for IoMT intake air temperature sensor . 68
5.2.62 API for IoMT tyre pressure monitor system sensor . 69
5.2.63 API for IoMT distance travelled sensor .70
5.2.64 API for IoMT speed sensor .71
5.2.65 API for IoMT vehicle speed sensor . . 72
5.2.66 API for IoMT mass airflow sensor . 73
5.2.67 API for IoMT percentage sensor .74
5.2.68 API for IoMT fuel level sensor . 75
5.2.69 API for IoMT manifold absolute pressure sensor .76
5.2.70 API for IoMT engine RPM sensor . 77
5.2.71 API for IoMT centre of mess sensor . 78
5.2.72 API for IoMT RADAR sensor . 79
5.2.73 API for IoMT array camera sensor . 80
5.2.74 API for IoMT e-nose sensor . 81
5.3 APIs for IoMT actuators . 82
5.3.1 General . 82
5.3.2 MActuator class . 82
5.3.3 API for IoMT speaker . 83
5.3.4 API for IoMT display . 85
5.3.5 API for IoMT camera actuator . 88
5.3.6 API for IoMT vibrator . 90
5.3.7 API for IoMT sprayer .91
5.3.8 API for IoMT light . 93
5.3.9 API for IoMT heater . 95
5.3.10 API for IoMT cooler . 96
5.3.11 API for IoMT fan . 97
5.3.12 API for IoMT motion chair. 98
5.3.13 API for IoMT tactile generator . . 99
5.3.14 API for consecutive vibration device . 100
5.3.15 API for IoMT 3D printer . . . 101
5.4 APIs for IoMT storage . 102
5.4.1 General . 102
5.4.2 MStorage class . 103
5.5 APIs for IoMT managers . 104
5.5.1 General . 104
5.5.2 MManager class . 104
5.6 APIs for IoMT aggregators . 105
5.6.1 General . 105
5.6.2 MAggregator class . 107

© ISO/IEC 2026 – All rights reserved
iv
5.7 Return type class. 108
5.7.1 General . 108
5.7.2 MPEGVCapabilityType . 108
5.7.3 MPEGVSensedDataType .110
5.7.4 MPEGVCommandType . 112
5.7.5 IoMT SensedDataType .114
5.7.6 IoMT ActuationDataType .116
5.7.7 IoMT AnalysedDataType . 118
5.7.8 IoMT MissionDataType . 120
5.7.9 IoMT CapabilityListType . 122
5.7.10 IoMT MThingInfoType . 124
6 Media thing description language .126
6.1 General . 126
6.2 Schema wrapper . 126
6.3 Mnemonics for binary representations . 127
6.4 Base data types and elements . 127
6.4.1 General . 127
6.4.2 Syntax . . 127
6.4.3 Binary Representation . 131
6.4.4 Semantics .134
6.4.5 Examples .142
6.5 Root element .142
6.5.1 General .142
6.5.2 Syntax . .142
6.5.3 Binary Representation .143
6.5.4 Semantics . 144
6.6 Media sensor description language .145
6.6.1 General .145
6.6.2 Syntax . .145
6.6.3 Binary Representation . 146
6.6.4 Semantics .147
6.6.5 Examples . 148
6.7 Media actuator description language . 148
6.7.1 General . 148
6.7.2 Syntax . . 148
6.7.3 Binary Representation . 149
6.7.4 Semantics . 150
6.7.5 Examples . 151
6.8 Media analyser description language . 152
6.8.1 General . 152
6.8.2 Syntax . . 152
6.8.3 Binary Representation . 153
6.8.4 Semantics .154
6.8.5 Examples . 155
6.9 Media storage description language . 156
6.9.1 General . 156
6.9.2 Syntax . . 156
6.9.3 Binary Representation . 157
6.9.4 Semantics . 158
6.9.5 Examples . 159
6.10 Media manager description language . 159
6.10.1 General . 159
6.10.2 Syntax . . 159
6.10.3 Binary Representation . 160
6.10.4 Semantics .161
6.10.5 Examples . 162
6.11 Media aggregator description language . 162
6.11.1 General . 162

© ISO/IEC 2026 – All rights reserved
v
6.11.2 Syntax . . 162
6.11.3 Binary Representation . 164
6.11.4 Semantics . 166
6.11.5 Examples .167
6.12 Media controller description language .170
6.12.1 General .170
6.12.2 Syntax . .170
6.12.3 Binary representation .171
6.12.4 Semantics . 172
6.12.5 Examples . 173
7 Media sensor output vocabulary .173
7.1 General . 173
7.2 Schema wrapper . 173
7.3 IoMT sensed data captured time .174
7.3.1 General .174
7.3.2 Syntax . .174
7.3.3 Binary Representation .174
7.3.4 Semantics .174
7.3.5 Examples .174
8 Media actuator command vocabulary .175
8.1 General . 175
8.2 Schema wrapper . 175
8.3 IoMT speaker .176
8.3.1 General .176
8.3.2 Syntax . .176
8.3.3 Binary Representation . 177
8.3.4 Semantics . 177
8.3.5 Examples . 177
8.4 IoMT display . 178
8.4.1 General . 178
8.4.2 Syntax . . 178
8.4.3 Binary Representation . 179
8.4.4 Semantics . 179
8.4.5 Examples . 180
8.5 IoMT camera actuator . 180
8.5.1 General . 180
8.5.2 Syntax . . 180
8.5.3 Binary Representation . 182
8.5.4 Semantics . 183
8.5.5 Examples .184
8.6 IoMT consecutive vibration device . 185
8.6.1 General . 185
8.6.2 Syntax . 185
8.6.3 Binary Representation . 186
8.6.4 Semantics . 187
8.6.5 Examples . 188
8.7 IoMT light . 188
8.7.1 General . 188
8.7.2 Syntax . . 188
8.7.3 Binary Representation . 189
8.7.4 Semantics . 190
8.7.5 Examples . 190
Annex A (informative) Classification scheme .191
Annex B (informative)  .262
Bibliography .265

© ISO/IEC 2026 – A
...