Codes & Standards - Purchase
CSA ISO/IEC 23000-16:19
Information technology — Multimedia application format (MPEG-A) — Part 16: Publish/Subscribe Application Format (Adopted ISO/IEC 23000-16:2018, first edition, 2018-01)
Standards development within the Information Technology sector is harmonized with international standards development. Through the CSA Technical Committee on Information Technology (TCIT), Canadians serve as the SCC Mirror Committee (SMC) on ISO/IEC Joint Technical Committee 1 on Information Technology (ISO/IEC JTC1) for the Standards Council of Canada (SCC), the ISO member body for Canada and sponsor of the Canadian National Committee of the IEC. Also, as a member of the International Telecommunication Union (ITU), Canada participates in the International Telegraph and Telephone Consultative Committee (ITU-T).
The International Standard was reviewed by the CSA TCIT under the jurisdiction of the CSA Strategic Steering Committee on Information and Communications Technology and deemed acceptable for use in Canada. From time to time, ISO/IEC may publish addenda, corrigenda, etc. The TCIT will review these documents for approval and publication. For a listing, refer to the Current Standards Activities page at standardsactivities.csa.ca. This Standard has been formally approved, without modification, by the Technical Committee and has been developed in compliance with Standards Council of Canada requirements for National Standards of Canada. It has been published as a National Standard of Canada by CSA Group.
This document 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).
This document 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.
This document does not specify the protocols used to carry these payloads.