Resolution: not accepted because the avatar characteristics should only contains information on avatars and not related to the user
28.3Action Points
29Reference Software (23005-5) 29.1Topics
29.2Contributions
29.3Action Points
30Conformance Testing (23005-6) 30.1Topics 30.1.1ISO/IEC 23005-5 Reference Software
30.2Contributions
30.3Action Points
31MXM Architecture (23006-1) 31.1Topics 31.1.2MXM License 31.1.3MXM Developer’s Day
31.2Contributions
Session
|
Number
|
Title
|
Source
|
MXM
|
m16542
|
Summary of Voting on Proposal for a New Work Item, Information technology -- MPEG extensible middleware (MXM)
|
SC 29 Secretariat
|
MXM
|
m16543
|
Summary of Voting on ISO/IEC CD XXXXX-1, MXM architecture and technologies
|
SC 29 Secretariat
|
MXM
|
m16694
|
Austrian NB comments on MXM
|
Michael Eberhard
Christian Timmerer
(on behalf of the Austrian NB)
|
MXM
|
m16554
|
Options for the MXM software licences
|
Leonardo Chiariglione
David Rudin
|
MXM
|
m16648
|
Revision of the License Authorisation on MXM
|
Víctor Rodríguez-Doncel
Jaime Delgado
Eva Rodríguez
|
MXM
|
m16693
|
Input for the MXM Developer's Day
|
Michael Eberhard
Christian Timmerer
Hermann Hellwagner
|
m16542
Refer DoC.
m16543
Refer DoC.
m16694
Refer DoC
m16554
Accepted. Final text will be recorded in the resolution.
m16648
The APIs should be defined so that a reasonable set of requirements is satisfied. An implementation of an engine may not be capable of executing all methods. It is necessary to check that the resulting set of engines perform properly. The MXM architecture allows to have engines of the same type to operate simultaneously. Implementers of different MXM engines are encouraged to commit their engines to the MXM repository in the mxm-engines sub-folder.
Decide whether we need requirements and a CfP or we can simply add new MXM Protocols to the existing ones
m16693
Demo presented during the MXM Developer’s Day
Dostları ilə paylaş: | 
