International organisation for standardisation organisation internationale de normalisation

15.3Summary of discussions

M18526 & m18476

This is an Editor input to improve the text
The contributions m18213, m18214, m18227, m18229, and a demo of the use of Scalable Application Markup Language (SAML) were presented. It was agreed that the contributors will try to re-implement the demo using

MPEG-21 DIA. They will evaluate, whether an extension needs to be specified in order to include and use MPEG-21 DIA information for the choice/selection mechanism in MPEG-21 DID. The result will be presented at the 95th MPEG meeting.

M18538

This is an input on Search License ES. Accepted to be part of Part 4 ES.

M18539

This is an input on Search Contract ES. Accepted to be part of Part 4 ES.

15.4Action Points

16MSP Service Aggregation (23006-5)

16.1Topics

16.1.1ISO/IEC 23006-5 MSP Service Aggregation

16.2Contributions

Session	Number	Title	Source		Dispositions
MSP	m18527	Comments on WorkingDraft of 23006-5	sergio matone	Accepted N11584
MSP	m18477	Input on w11414 (WD of ISO/IEC 23006-5 Service Aggregation)	Michael Grafl , Christian Timmerer	Accepted N11584

16.3Summary of discussions

M18527 & m18477

Editors input to improve the text

16.4Action Points

17Richmedia UI Widgets (23007-1)

17.1Topics

17.1.1Package, Delivery and Presentation of Widgets

17.1.2Communication

17.2Contributions

Session	Number	Title	Source		Dispositions
Scene	m17999	Table of Replies on ISO/IEC FDIS 23007-1	ITTF via SC 29 Secretariat	Noted
Scene	m18376	Proposed amendment for MPEG-U widgets	Jean-Claude Dufourd , Jean Lefeuvre , Cyril Concolato , Kyungmo Park , Jaeyeon Song	Accepted (N11585)

17.3Summary of discussions

m18376:

The contribution is presented. A comment from MPEG-V is that numberarray may also be needed. An answer is that there is then a need to provide mapping of the array types to a type acceptable to all protocols (such as mapping to/from string type). Question on whether the stringarray implementation caused any problem, and the answer was no, beyond the mapping, hence the proposed restriction in the contribution. Question on the implementation of security restrictions, which led to a discussion to be continued.

17.4Action Points

18Advanced User Interaction Interface (23007-2)

18.1Topics

18.1.1Advanced User Interaction Interface

18.2Contributions

Session	Number	Title	Source		Dispositions
Scene	m18490	Proposed mechanism to support AUI interface	Seong Yong Lim , Jihun Cha , Injae Lee , Young-kwon Lim	Noted

18.3Summary of discussions

m18490 :

Presentation of the contribution. The presented interface seems more like a higher level of MPEG-V than an MPEG-U interface.

Request to do a state of the art on mouse gestures, same as was done on the iphone SDK.

Question about what language to use to describe the gestures, and then what language to use to pass the information about a recognized gesture into a scene in a particular format: the answer for both is that the proposal is flexible.

Once the gesture is recognized, it is important to adapt the information to the target scene format, even if the actual effect in the scene is out of scope.

There seems to be a need for a database of recognized gestures, an entity which matches the output of the semantic generator to one recognized gesture (independent from the scene format), and then a module to translate the recognized gesture into some scene description specific stuff.

Suggestion that MPEG-U part 1 can be used for some of the communications between MPEG-V and the scene.

Request for a walkthrough of the system, a concrete example of a flow