Accepted and WG11 will provide a SVN account for Klagenfurt University
m16427:
Proposes some changes to the media framework engine incorporating Graphics3D engine
Accepted and appreciated.
Other related input documents:
m16301: What are the pros and cons regarding the policy of having MPEG reference software in the form of an MXM engine if applicable?
Pros:
Easy development of applications that exercise the reference software because the new engine can be easily integrated with the other existing engines.
Easy reuse of the engine by other developers of MPEG standards (or even by the industry) thanks to the existence of the interfaces.
This would follow a common trend in the standardization environment.
Facilitate the upgrade of service provisioning.
Cons:
Additional effort to specify and implement the API.
Notes:
Need to be clear about the normative value of the API.
By developing an API the designers have to pay more attention to the requirements of the technology.
m16313:
The example mapping between NextShare functionalities and MXM engines is very useful and should be adopted by AIT.
Shall the MXM standard only contain engines for MPEG technologies or shall it also contain engines for non-MPEG technologies (P2P delivery, access to payment system, social networks, …)?