Web and TV : standards for interconnected devices Multimedia content, and especially video, has started ruling the Web for several years now. It has already generated standardization activities inside W3C like the “Video in the Web” activity and also HTML5 media elements. These initiatives will provide better integration of video in the Web and manipulation from any devices through Web browsers. TV content is not handled for the moment by W3C, but some new challenges may appear due to the on-going evolution of contents towards mixture of traditional TV programs with Web content. Indeed, more than watching TV programs from the Web or browsing the Web from TV, we would expect to transparently browse and interact with both, possibly from any device. --------------------------------- Current status and applications --------------------------------- Some solutions where “TV meets the Web” start to appear. For example, HbbTV (Hybrid Broadcast Broadband TV) provides an illustration of convergence between broadcast and Web standards (HTML5, CSS, AJAX) in order to enrich TV programs with Web content: display of program related information, interactions with programs or Internet services. In this case Web content meets the TV. Another approach is Google TV that considers TV as device for the Web in addition to traditional broadcast services. The TV that will embed Google TV will provide nice features to interact with both TV programs and Web content: unified search interface for both TV and Web content, for personalization, for picture in picture mixing web and TV. It provides a “real full” Web access in addition to pre-defined Web apps as already existing on smartphones. -------------------------- Canon’s statement -------------------------- Canon devices enable consumers to create high quality multimedia files. Canon would like to improve the user experience in the display and sharing area through the adequate use of standard technologies (HTML5, SVG, Device API...). One major requirement is to enable standard high quality video communication means between devices. Multimedia devices such as smartphones or cameras may serve both as remote controllers and content producers for TV sets. The browsing of device content on TV is natural and user interaction should be made consistent between the different controllers that maybe the TV remote control, the device or both. A second use case is the display of multimedia content composed from different sources: YouTube, personal web services and personal devices. Composed multimedia content would be naturally built from hyperlinking and new advances in Media Fragment and Media Annotation accesses. While TVs are ready to use particular providers such as YouTube, users should be enabled to have direct access to as many data sources as possible. In both cases, an open solution must be designed to work for a variety of web services and devices. This requires standard APIs for devices, particularly TV devices, as well as bidirectional communication protocol, streaming capacities and standard scalable codec use. While some items are partially addressed by different efforts (IETF, DAP WG, HTML5 WG), we should ensure that all items are actually taken forward and that the combined use of all items provides a consistent solution for this use-case.