Search
×
FR

Placeholder headline

This is just a placeholder headline

API STD 521: Guide for Pressure-relieving and Depressuring Systems – Edition 6

$

682

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 653: Tank Inspection, Repair, Alteration, and Reconstruction – Edition 4

$

507

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z662:19 – Oil and gas pipeline systems

$

1197

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z341 Series-18: Storage of hydrocarbons in underground formations

$

878

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z246.2-14 – Emergency preparedness and response for petroleum and natural gas industry systems

$

596

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z341 Series:22 – Storage of hydrocarbons in underground formations

$

878

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z731-09 (R2014) – Emergency Preparedness and Response

$

177

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z662:23 – Oil and gas pipeline systems

$

1197

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z341 Series:26 – Storage of Hydrocarbons in underground formations

$

878

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA B51:24 Boiler, Pressure Vessel, and Pressure Piping Code

$

389

BUY NOW

ISO 23006:2016

ISO 23006:2016 Information technology – Multimedia service platform technologies – Part 2: MPEG extensible middleware (MXM) API

CDN $336.00

Description

ISO/IEC 23006-2:2016 specifies a set of Application Programming Interfaces (called for short MXM APIs) so that MPEG-M Applications running on an MPEG-M Device can access the standard multimedia technologies contained in its Middleware as MPEG-M Engines, as specified by ISO/IEC 23006‚Äë1.

The MXM APIs belong to two classes:

– the MPEG-M Engine APIs, i.e. the collection of the individual MPEG-M Engine APIs providing access to a single MPEG technology (e.g. video coding) or to a group of MPEG technologies where this is convenient;

– the MPEG-M Orchestrator API, i.e. the API of the special MPEG-M Engine (called Orchestrator Engine) that is capable of creating chains of MPEG-M Engines to execute high-level application calls such as “Play a video”, as opposed to the typically low-level MPEG-M Engine API calls.

Edition

3

Published Date

2016-12-05

Status

PUBLISHED

Pages

40

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

ISO/IEC 23006-2:2016 specifies a set of Application Programming Interfaces (called for short MXM APIs) so that MPEG-M Applications running on an MPEG-M Device can access the standard multimedia technologies contained in its Middleware as MPEG-M Engines, as specified by ISO/IEC 23006‚Äë1.

The MXM APIs belong to two classes:

- the MPEG-M Engine APIs, i.e. the collection of the individual MPEG-M Engine APIs providing access to a single MPEG technology (e.g. video coding) or to a group of MPEG technologies where this is convenient;

- the MPEG-M Orchestrator API, i.e. the API of the special MPEG-M Engine (called Orchestrator Engine) that is capable of creating chains of MPEG-M Engines to execute high-level application calls such as "Play a video", as opposed to the typically low-level MPEG-M Engine API calls.

Previous Editions

Can’t find what you are looking for?

Please contact us at: