Hi Cyril,

sorry to put you on the spot, but I don't recall this being discussed by WebApps and you're listed as one of the authors:

Can you give the WG some general ideas about what's happening around MPEG-U?

One reason I'm asking is because some of the work items in that document are interesting in a generic manner, and therefore are things that could make their way into WebApp's charter when it comes up for rechartering (which is soon). I don't think that all that's listed there would be of interest to WebApps (e.g. I'd be surprised if the WG cared about integration with BIFS or ISOFF packaging, assuming members even have heard of them), but some topics (inter-widget communication, context management, aggregation) certainly are.

Given MPEG's patent policy and inexperience with web technology one can take a fairly good bet that if MPEG-U defines solutions in this space WebApps won't adopt them, thereby leading to fragmentation: something that the document above states it wishes to avoid.

Hence my interrogation; can you enlighten us?


Robin Berjon -

Received on Wednesday, 6 January 2010 16:43:58 UTC