Search
×
FR

Placeholder headline

This is just a placeholder headline

MSS SP-44-2026: Steel Pipeline Flanges

$

450

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 576: Inspection of Pressure-relieving Devices

$

460

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 591: Process Valve Qualification Procedure

$

226

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 576: Inspection of Pressure-relieving Devices: Addendum 1

$

0

BUY NOW

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-6 Chapter 6 – Density

$

204

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 560: Fired Heaters for General Refinery Services

$

721

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 64: Diverter Equipment Systems

$

324

BUY NOW

Placeholder headline

This is just a placeholder headline

API MPMS CH 17.10.1: Refrigerated Light Hydrocarbon Fluids – Measurement of Cargoes on Board LNG Carries

$

417

BUY NOW

ISO 23000:2018

ISO 23000:2018 Information technology – Multimedia application format (MPEG-A) – Part 16: Publish/Subscribe Application Format

CDN $273.00

Description

ISO/IEC 23000-16:2018 specifies four formats that are used by parties communicating using the Publish/Subscribe (PubSub) communication model for their multimedia communication purposes.

The PubSub parties are: Publisher, Subscriber, Match Service Provider (MSP) and Consumer and the formats employed are Resource Information (RI), Publication Information (PI), Subscription Information (SI) and Notification Information (NI).

ISO/IEC 23000-16:2018 specifies RI, PI, SI and NI in such a way that typical multimedia communication requirements can be supported. The following is a non-exhaustive list of such requirements.

– The Publisher can

  • – describe the Resource for consumption purposes,
  • – define the contract that will bind the Publisher and a Consumer,
  • – request a device to report use of the Resource,
  • – describe the Resource for distribution purposes,
  • – define the contract that will bind the Publisher and a Match Service Provider (MSP) of a match involving the Publication, and
  • – request the MSP to notify/not to notify a list of users.

– The Subscriber can

  • – query the Resource,
  • – define the contract that will bind the Subscriber and a Match Service Provider (MSP), and
  • – request the MSP to notify/not to notify a list of users of a match involving the Subscription.

ISO/IEC 23000-16:2018 does not specify the protocols used to carry these payloads.

Edition

1

Published Date

2018-01-17

Status

PUBLISHED

Pages

27

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

ISO/IEC 23000-16:2018 specifies four formats that are used by parties communicating using the Publish/Subscribe (PubSub) communication model for their multimedia communication purposes.

The PubSub parties are: Publisher, Subscriber, Match Service Provider (MSP) and Consumer and the formats employed are Resource Information (RI), Publication Information (PI), Subscription Information (SI) and Notification Information (NI).

ISO/IEC 23000-16:2018 specifies RI, PI, SI and NI in such a way that typical multimedia communication requirements can be supported. The following is a non-exhaustive list of such requirements.

- The Publisher can

  • - describe the Resource for consumption purposes,
  • - define the contract that will bind the Publisher and a Consumer,
  • - request a device to report use of the Resource,
  • - describe the Resource for distribution purposes,
  • - define the contract that will bind the Publisher and a Match Service Provider (MSP) of a match involving the Publication, and
  • - request the MSP to notify/not to notify a list of users.

- The Subscriber can

  • - query the Resource,
  • - define the contract that will bind the Subscriber and a Match Service Provider (MSP), and
  • - request the MSP to notify/not to notify a list of users of a match involving the Subscription.

ISO/IEC 23000-16:2018 does not specify the protocols used to carry these payloads.

Previous Editions

Can’t find what you are looking for?

Please contact us at: