Web and TV Interest Group Report 201104

Status of this document An update of this document is available: Web and TV Interest Group Report 201109 This document is an initial draft of the Web and TV Interest Group published on 21 April 2011. This is the first publication of this document and it represents the views of the W3C Web and TV Interest Group at the time of publication. The document may be updated as new use cases and requirements emerge or mature. The intention of publishing this Interest Group Report is to seek feedback on the various different use cases and requirements.

Notes for editing This initial report is based on the summaries and the wrap-up sessions of the two workshops, i.e. Tokyo workshop and Berlin workshop. Member participants can edit this page from 21 April to 28 April, and any contribution would be appreciated. During the period, we will focus only on the topics from the two workshops. co-Chairs will publish the modified report on 29 April. After that, we will collect new topics from the discussion or suggestions on the public ML, and put them into this page. Basically, the result of existing TF (e.g. HNTF) will be merged into this document after the discussion in the TF finished. To create a good starting point for collaborative editing on the wiki , co-Chairs had compiled this page carefully to keep the expressions or sentences "as is" in original documents for ease of tracking of their origins. [WS-1] mark shows that the topic was discussed in the first workshop, and [WS-2] means the second workshop. The moderator of this document is Yosuke Funahashi (Tomo-Digi). If you have any questions, please feel free to ask Yosuke on the public ML.

Classification of Topics

Fundamental topics on smarter integration of Web and TV

Implementability and Realizability

General topics
- Profiling / Testing [WS-2]
Especially from the perspective of TV services
- Synchronization between broadcasting and Web Services [WS-1] [WS-2]
- Convergence of broadcasting services and CE devices [WS-1]
- Equivalence of view on various devices [WS-1]
- Disaster/Emergency information [WS-1]
- Design principles for content (limited text, Application solutions) [WS-1]
- The control over the screen in multi-app environment (was Who "owns" the display?) [WS-1]
Especially from the perspective of TV devices
- Implementability on CE environment [WS-1] [WS-2]
- Which part or subsetting of HTML5 or Web technology for CE devices [WS-1] [WS-2]
- Profile for resource limitation [WS-1] [WS-2]
- Design principles for content (e.g. big and brief text, i.e. readability on TV screen, or Application solutions) [WS-1]
- The control over the screen in multi-app environment (was Who "owns" the display?) [WS-1]

Personalization

Personalization [WS-1]
Disaster/Emergency information [WS-1]
Parental control [WS-1]
Security [WS-1]
The control over the screen in multi-app environment (was Who "owns" the display?) [WS-1]

Accessibility

Usability/accessibility [WS-1]
How to harmonize WCAG 2.0 with various accessibility regulations from the TV world [WS-2]
Smarter integration of Multimodal interactions framework and TV related use-cases [WS-2]
How Accessible Rich Internet Applications (WAI-ARIA) can enable the design of applications that work on heterogeneous devices [WS-2]

Contents right

Rights management for business use [WS-1] [WS-2]
Premium contents need DRM. (was Premium content) [WS-1]
DRM (Digital Rights Management) in HTML5 [WS-1] [WS-2]
Security on managed/unmaganed networks [WS-1]

Advanced topics on smarter integration of Web and TV

Viewpoints on use cases for Web and TV

Richer user experience [WS-1]
More attractive presentation [WS-1]
PC vs. TV - user experience [WS-1]
Smarter TV vs. more convenient & cozy TV [WS-1]

'Connect and Link'

Hyperlink in video content [WS-1]
Interaction between Web apps and home network devices [WS-1]
Nomadic TV service among multi-domains [WS-1]
Home gateway bridges the home and the Internet [WS-1]
Second screen [WS-1] [WS-2]
TV functions on Web, Web apps [WS-1]
Specifications for new type of contents on TV for "Media experience" [WS-1]
Peripheral devices for Web on TV devices [WS-1]
Device format independence [WS-1]
Content linkage between PC and TV [WS-1]
Device discovery between devices [WS-2]
Real-time communication between devices [WS-2]

Miscellaneous topics

Security on managed/unmaganed networks [WS-1]
DAP, more than smart phone [WS-1]
DAP extension for Web on TV [WS-1] [WS-2]

Specific Suggestions on APIs

From the viewpoint of traditional functions of TV devices [WS-1]
API between TV and remote [WS-1] [WS-2]
APIs, channel changing, program guide access [WS-1] [WS-2]
Video API [WS-1] [WS-2]
From the viewpoint of modern functions in TV devices (including network oriented functions)
API, DLNA and UI sharing [WS-1] [WS-2]
Framework for exchanging control code for home network devices [WS-1]

Adaptive Streaming

RF issues [WS-2]
Generic interface to Manifest/Metadata of DASH [WS-2]

Extension to HTML5

Support for multiple tracks [WS-2]
Support for secure devices [WS-2]
Support for trick play [WS-2]
Support for recoding [WS-2]

Relationship with existing approaches

Topics from Workshops

Existing DTV approaches, e.g., BML, ITU-T LIME, acTVila [WS-1] [WS-2]
CE-HTML's relationship with HTML [WS-1]
Is HTML5 really appropriate for CE (if it can't work on low-price devices)? [WS-1]
Flash vs. video tag [WS-1]
Role of SVG [WS-1]
DAP extension for Web on TV [WS-1] [WS-2]
AP, more than smart phone [WS-1]
Metadata convergence between W3C developments and industrial developments or television and radio standardisation activities [WS-2]
How to harmonize WCAG 2.0 with various accessibility regulations from the TV world [WS-2]
Smarter integration of Multimodal interactions framework and TV related use-cases [WS-2]
How Accessible Rich Internet Applications (WAI-ARIA) can enable the design of applications that work on heterogeneous device [WS-2]

Categorization of Topics

After finishing the classification of topics or use-cases — that were suggested during the workshops and on the public IG mailing list — in previous section, we will categorize them into the following four classes:

Topics that should be done by a new Working Group.
New requirements for existing Working Groups. The IG should make sure that the right requirements get passed to the right Working Groups.
Work that is satisfactorily done outside W3C and has industry-wide consensus. We should document this for the record but should not try to re-create existing standards within W3C.
Work items, where it is unclear where they should be done.

As for class 2 and class 3, we've already picked up the presumable destination groups and organizations in 'Dependencies and Liaison' section of the charter.