- 1 Web and TV Interest Group
- 1.1 News
- 1.2 Task Forces
- 1.3 Resources
- 1.4 Archived Reports and Deliverables
Web and TV Interest Group
This is the Wiki for the W3C Web and TV Interest Group (Web&TV IG), used to organize work in the IG. Higher-level information about the Web&TV IG is available on the main home page of the group. The Interest Group reviews existing work and identifies requirements and potential solutions for the Web and TV. The development of Web standards, when required, takes place in other working groups.
W3C will hold a Fourth W3C Web and TV Workshop: Web and TV Convergence, 12-13 March 2014, in Munich, Germany. The Workshop is hosted by IRT.
NOTE: the tag indicated near the Task Force name MUST be used when sending email to the IG list for topics related to that TF.
Media APIs TF [apis]
- Merges the work of the Recording and Downloading Media, Terminal Capabilities and Content Metadata Exposure and Content Synchronization TFs. with the following focus:
- Identify requirements for recording and downloading media
- Investigate requirements for discover and control of device capabilities (e.g. tuner control)
- Investigate how to expose TV metadata to web applications
- Investigate mapping between Media Element API and in-band metadata
- Synchronization of broadcast content and web applications up to frame accurate
Closed or Dormant
- (Closed) Testing TF [testing]
- Identify Requirements for testing from a “Web and TV” perspective
- act as a bridge between ongoing activities in W3C and other organizations interested in testing W3C specifications
- (Closed) Stereoscopic 3D Web [3dweb]
- Investigate impact of 3D Video/Graphics on HTML and other web standards
- (note: see notes of a breakout session on this topic during TPAC here http://www.w3.org/wiki/TPAC2012/3dweb)
- (Closed) Timed Text [tt]
- Develop recommendations to facilitate the use of TTML and WebVTT content on the Web, including interoperability with other timed text formats.
- (Closed) Media Pipeline TF [mptf] — discuss requirements placed on the HTML5 video, audio and media interface by media formats that will be used for Web and TV
- Requirement document published: Adaptive Bitrate Requirements for HTML5 Media Element
- Requirement document published: Content Protection Requirements for HTML5 Media Element
- Led to the Encrypted Media Extensions proposal
- (Closed) Home Network TF — [hntf] identify gaps to enable discovery and control of devices and services in the local area IP network.
- (On hold) Web Media Profile TF [profile] — discuss a profile to be used in TV deployments.
A member only wiki is available, for member confidential information. Note that confidentiality of this wiki is at W3C membership level, and NOT IG level. Note also that use of this (public) wiki is preferred when possible.
Teleconferences / Meetings
Note that no IG-wide teleconferences or meetings are scheduled as of today, but task forces may organize regular calls and F2F meetings as needed. Please check task forces pages for more information (or contact the TF moderators)
- Archives of the firstname.lastname@example.org mailing-list are publicly available. This mailing-list should be used for all technical discussions within the group.
- Archives of the email@example.com mailing-list are available to W3C Members only. Use of this second list should be restricted to administrative purposes
Template for Use Cases
This is a generic template for proposing use cases that should be discussed by the IG TFs. Note that TFs may extend the template if/as needed, so check with your TF moderator if you are not sure.
Submitter(s): company (name), ... Tracker Issue ID: ISSUE-NN Category How would you categorize this issue?: 1. gap in existing specifications (=> IG to draft a proposal for an existing WG) 2. require new specification/WG (=> IG to draft a proposal for W3C Director) 3. can be addressed as part of a guidelines document to be produced by the IG (=> proponent to draft some text for such document) Description: * high level description/overview of the goals of the use case * Schematic Illustration (devices involved, work flows, etc) (Optional) * Implementation Examples (e.g. JS code snippets) (Optional) Motivation: * Explanation of benefit to ecosystem * Why were you not able to use only existing standards to accomplish this? Dependencies: * other use cases, proposals or other ongoing standardization activities which this use case is dependant on or related to What needs to be standardized: * What are the new requirements, i.e. functions that don't exist, generated by this use case? Comments: * any relevant comment that is good to track related to this use case
IG Specific Processes
- TF handling rule to propose the creation of a task force
- TF charter template to precise the scope of a potential new task force
- Use Case template to be used as base for drafting a use case input document. Note that TFs may have their own further refined template (check TF page)
- Tracker is used to track issues and actions within the group. For help on how to use Tracker see the related web site. For a really quick intro see here
Other Useful W3C Resources
- World Wide Web Consortium Process Document 14 October 2005
- Art of Consensus Guide W3C member confidential
- Notes on IRC at W3C
- The Zakim IRC Teleconference Agent
- Quick Start Guide to taking minutes
Emulators and Testing Tools
Archived Reports and Deliverables
Web and TV Interest Group Report
The Web and TV Interest Group Report categorizes topics of interest for the Web and TV in terms of standardization needs. The group is to publish a first snapshot of the report soon. Results of work items discussed in task forces will be integrated in the final report of the Interest Group.
- Tokyo Workshop - 2-3 September 2011
- Berlin Workshop - 8-9 February 2011
- Hollywood Workshop - 19-20 September 2011