33.1.1ISO/IEC 23006-3 MXM Conformance and Reference Software
33.2Contributions
Session
Number
Title
Source
MXM
m16545
Summary of Voting on ISO/IEC CD XXXXX-3, MXM conformance and reference software
SC 29 Secretariat
MXM
m16750
Proposed text of ISO/IEC FCD 23006-3 MXM Conf. & Ref. SW
Filippo Chiariglione
Angelo Difino
Emiliano Leporati
m16545
Refer DoC
m16750
We need further harmonisation on the MXM C++ implementation to be further discussed on Tuesday between MXM C++ experts
33.3Action Points
34MXM Protocol (29116-1)
34.1Topics
34.1.12nd edition of ISO/IEC 29116-1 MXM Protocols
34.1.2Change of standard number to 23000-4
34.2Contributions
Session
Number
Title
Source
MXM
m16541
Summary of Voting on ISO/IEC CD 29116-1 [2nd Edition]
SC 29 Secretariat
MXM
m16652
Proposal for additional MXM Protocols
Filippo Chiariglione
Sergio Matone
Angelo Difino
m16541
Refer DoC
m16652
Further discuss the requirements in Systems/Requirements in a broader scope of possibly issuing a new CfP.
Include the modifications to the MXMBP protocol defining BasicResultCode and ExtendableResultCode as child of ResultCodeType
Decide whether we need requirements and a CfP or we can simply add new MXM Protocols to the existing ones
34.3Action Points
35MPEG Rich Media UI Framework (23007)
35.1Topics
35.1.1Package, Delivery and Presentation of Widgets
35.1.2Communication
35.1.3Conf. and Ref. SW
35.2General
Organization of the standard
The current standard is 37 pages, will probably be at most 50. That is small enough to manage as one part and does not necessarily need several parts. The reference software and conformance are definitely another part. The group agrees to ease the life of the editor and to keep only one part for now.