TentativeEntertainment

From Web and TV IG

TV and Entertainment

HTML Media

  • "The basic information of the work"
    • HTML Media, core media features of Web platform, is developed in HTML (Media Extensions) WG, while new features of core Web standards are crafted in Web Platform WG. The HTML (Media Extensions) WG is currently working on two extensions: Media Source Extensions (MSE) and Encrypted Media Extensions (EME).
    • MSE is a candidate recommendation that allows JavaScript to send byte streams to media codecs within Web browsers that support HTML5 video.
    • EME is a working draft for providing a communication channel between Web browsers and digital rights management (DRM) agent software. This allows the use of HTML5 video to play back DRM-wrapped content such as streaming video services without the need for third-party media plugins like Adobe Flash or Microsoft Silverlight.
  • "Why the work is important to the Web and to the Member"
    • After the industry and the Consortium decided to enhance HTML to be capable of playing video content without the help of plug-in video players, streaming technologies over HTTP such as Dynamic Adaptive Streaming over HTTP (DASH) has rapidly emerged in the industry. W3C decided to develop two HTML5 extensions to enable UAs to play such streams.
    • These extensions are essential to achieve to meet the industry requirements for video content delivery on the Web, as well as the extensions provide Web apps with more flexible control over video content, which enable advanced services such as dynamic ad-insertion.
  • "Member gets fresh information"
    • The HTML Media Extensions, previously called the HTML WG, has continued resolving its issues around the media stream and encrypted media extensions. The AC review of December 2015 related to a further extension of this Working Group generated a substantial number of objections, most of them linked to the proposed covenant not to use section 1203 1203 of the US DMCA (and similar laws around the world) against standards implementers and security researchers as a condition of the extension. The Technical Architecture Group issued a statement back in October 2015 to support a strong and secure Web platform and avoid the unintended consequences of certain pieces of legislation which have had a chilling effect on security research on software. The W3C Team is working towards resolving the objections.
      • The charter was extended until this September.
      • The consideration on the Web and DRM will continue in Consortium in light of the discussion at the AC meeting.
    • Recently Consumer Technology Association (CTA), formerly known as Consumer Electronics Association (CEA), started a new work called Global Internet Video Ecosystem (GIVE), which aims to establish interoperability of OTT steaming devices, putting MSE and EME at the core of its architecture.
      • The GIVE work is ongoing and we might have further collaboration in the near future, esp. on testing and other interop aspects.
    • As for tech works, the version 1.0 of two extensions are planed to become W3C Recommendations sometime by the end of this year. On the other hand, there are some industry requests to include additional features such as continuous key rotation to meet original requirements of extensions. The group is on the process to decide which feature should go to version 1.0. TPAC 2016 will be an important milestone for this work.
      • The WG has decided to publish both MSE and EME by the end of September.
      • The WG booked a room at TPAC 2016 for f2f discussion on MSE/EME V.2 features although we are still not sure what new or existing group will deal with these specs after the HME-WG charter expiration on September.
      • The triage process for V.1 is almost finished.
      • We need to resolve the continuous key rotation issue, which is very important for mass broadcast live services.
    • To make them RECs in time, the group is putting more efforts on improving testing.
      • Google has decided to provide W3C with their test suites for MSE, which will improve the coverage of the test suite from 25 to 37%.
      • The WG members have been talking internaly in each organization about how they can provide their internal internal test suites for EME to W3C.
  • Additional resources:

Cloud Browser

  • "The basic information of the work"
    • The Cloud Browser Task Force is a subset of the Web and TV Interest Group, whose goal is to discuss support for web browser technology within devices such as HDMI dongles and lightweight STBs (set-top boxes).
    • New cloud browser Runtime Environments (RTEs) require the definition of APIs that would enable communication between the cloud browser and the client. The Task Force will look into use cases, requirements and gaps in cloud UI architectures.
  • "Why the work is important to the Web and to the Member"
    • To enable arbitrary Web apps to run on cloud browser RTEs, we need to modify some existing W3C APIs such as MSE and EME for video delivery services. This Task Force will figure out such gaps between cloud browser RTEs and existing Web standards.
    • The Task Force deals with not only TV-like-service-centric use cases but also use cases from other industries such as gaming, signage, etc, if the TF gets interest or contribution from the stakeholders.
    • This technology can achieve architectural flexibility about User Agents or Web browsers, which can provide users with better privacy and security and cloud service providers with a different level of control over Web browsing features, as well as it can provide new privacy and security issues if we will have done it in a wrong way.
  • "Member gets fresh information"
    • At the f2f meeting during TPAC 2015, the Web and TV IG decided to launch Cloud Browser TF, which just started on Jan 20, 2016, and will end at TPAC 2016.
    • The TF is currently gathering use cases, holding its regular call on every Wednesday for the time being.
      • The TF has finished the use case gathering phase, and currently start extracting features from it.
      • The Technical Architecture Group, TAG, has started discussing the impact of Cloud/Split Browser to the Web architecture at their f2f they held in Paris at the end of March. The TF might work collaboratively with TAG.
      • Deuche Telecom, the leading member company of the TF, is also developing extensions for MSE and EME to use them on cloud browsers.
      • The TF will have a session during the Web and TV IG f2f meeting at TPAC 2016.
  • Additional resources

GGIE (Glass-to-Glass Internet Ecosystem)

  • "The basic information of the work"
    • The GGIE TF is a subset of the Web and TV Interest Group, whose goal is to discuss the end to end Internet digital video ecosystem focusing on all phases of the video life cycle: Capture-Edit-Package-Distribute-Find-Watch for both professional and non-professional digital video.
    • Digital video is dependent on a large number of global internationally developed and interdependent standards from a variety of global organizations including W3C, IETF, IEEE, CEA, SMPTE, MPEG just to name a few. GGIE will examine the end to end ecosystem for digital video and identify recommended standards and features that could be developed.
  • "Why the work is important to the Web and to the Member"
    • Thanks to the efforts of the above-mentioned SDOs, the Internet-based or Web-based video content delivery services are expanding in the entertainment content market. However, the efforts were done in a distributed, sometime ad-hoc way, and now is the good time to go back to use cases: capture existing use cases, analyze them, and enhance them to further develop new standards for better services.
    • From an ambitious point of view, this work would result in new standards to enable stakeholders to build more flexible content delivery systems where content providers, platforms, and viewers can be connected in a way different from the current primary model: a platform is the key component to connect content and viewers.
  • "Member gets fresh information"
    • The TF finished its first round at TPAC, Sapporo, on Oct, 2015, where the TF wrapped-up its work thus far.
    • In the wrap-up report, the TF emphasized that flexible content identification more than traditional in- and out-band content-id and metadata would be the key component for GGIE. It would use ID-less content identification such as fingerprint and watermark technologies in addition to conventional content-id systems.
    • The IG agreed that the TF proceed to the second round to further elaborate key components and write down requirement docs which we can use to begin new technical works. The second round will start Feb. 2016 and finish at TPAC 2016.
      • The TF currently focuses on Content ID, which they are aiming standardizing at W3C. The TF has finished basic consideration on identity and privacy for content id and ecosystem.
      • The TF will have a session during the Web and TV IG f2f meeting at TPAC 2016.
  • Additional resources

Second Screen

  • "The basic information of the work"
    • Web content is available on an ever expanding array of devices including ebook readers, phones, tablets, laptops, auto displays, and electronic billboards. These devices have a variety of display screens. There are also a variety of mechanisms that allow these devices to use secondary display screens available in the local environment, attached by wired connections or remotely with wireless, peer-to-peer media.
    • However, in most cases, lower layers such as OS provide those connection mechanisms, which Web apps, consequently, have no access and control over. Second screen scenarios such as using a big screen device to watch a movie selected on and streamed from a smartphone are getting more common as OTT services like Netflix emerge. Web apps should be capable of implementing services which cover such scenarios.
  • "Why the work is important to the Web and to the Member"
    • The Second Screen Presentation Working Group aims at defining simple APIs that allow web applications to show and control web content on one or more secondary displays. Focus in 2015 was on the Presentation API. The interfaces defined in this specification have stabilized and the specification should move forward to Candidate Recommendation by mid-2016. In parallel to the Presentation API, the group is now also developing the Remote Playback API that allows controlling remote playback of media from a web page.
  • "Member gets fresh information"
    • Participants of the Working Group plan to re-charter the Second Screen Community Group in the next few months to discuss protocols that are out of scope of the Working Group.
    • The group also expects to start WG re-chartering discussions in May 2016. Preliminary discussions suggest extending the scope to address more multi-device bootstrapping scenarios. We encourage interested parties to share their thoughts with their favorite point of contact in the team.
      • The group has successfully published its updated WD on February 11.
      • The group is having an f2f meeting on 24-25 May in Mountain View, CA, USA, planning to talk about re-chartering and other topics.

TV Control API

  • "The basic information of the work"
    • In 2014, The Web and TV IG launched the TV Control API CG to create a draft specification about APIs that make Web apps to be capable of use cases such as accessing TV tuners and other broadcasting resources. TV sets are another major type of devices which use HTML5 as its runtime engine. Some regional SDOs have created HTML5-based runtime engines for their TV specs by expanding HTML5 in their space. This caused a fragmentation of Web apps on TV. The TV Control API is being developed as a way to address this fragmentation issue.
  • "Why the work is important to the Web and to the Member"
    • TV-like user interfaces are still common on big screen devices, so easy to understand for a broad range of users around the world that it's useful to provide generic APIs to easily create such UIs in an underlying-layer-agnostic way.
  • "Member gets fresh information"
    • The TV Control API published the first version of the TV Control API specification as a final report in November 2015. The group has then been working on a draft charter for a possible transition to a TV Control Working Group. The draft charter will hopefully soon reach the Advisory Committee for review. We encourage interested parties to contribute to the review once possible.
      • The TV Control API WG has successfully launched, and just started to working on its V.1 spec based the spec written by the CG.
      • The CG is gathering ideas on V.2 features.
      • The WG is planning to have its f2f meeting at TPAC 2016.
      • Advanced Television Systems Committee (ATSC) is considering adopting the TV Control API WG's work in their V.3 spec. Moreover, they've decided to adopt vanilla Web standards for their runtime engine for TV sets. They were originally planning to adopt HbbTV2.0 as their start point but gave up the plan this February.
  • Additional resources

Multi-device Timing

  • "The basic information of the work"
    • In 2015, The Web and TV IG launched the Multi-device Timing CG to a create draft specification that defines a common, multi-device, timing mechanism and a practical programming model e.g. to allow Web apps to synchronize the playback of multiple streams on multiple devices.
  • "Why the work is important to the Web and to the Member"
    • Timing mechanisms allow operations to be executed at the correct time. The Web already has several mechanisms supporting timed operations, including setTimeout, controllers for media playback, audio output, and animations. However, the clocks followed by some of these mechanisms may be custom, and the Web lacks support for multi-device timing. A multi-device timing mechanism would allow timed operations across Web pages hosted by different devices. Multi-device timing is particularly important for the broadcasting industry, as it is the key enabler for web-based secondary device offerings.
    • This mechanism would also make Web media more accessible. For example, third party can easily provide additional audio track, such as Clean Audio, to improve accessibility of the media content.
    • More generally, multi-device timing has wide utility in communication, collaboration and multi-screen presentation.
  • "Member gets fresh information"
    • The Multi-device Timing CG has developed an initial draft of the Timing Object specification, along with a reference polyfill implementation in JavaScript. Since TPAC 2015, the group has reached out to various members to gather feedback on the topic in general and on the proposed approach in particular, with a view to assessing practical next steps from a standardization perspective. Contributions to the discussions would be particularly welcome!
Retrieved from "https://www.w3.org/2011/webtv/wiki/index.php?title=TentativeEntertainment&oldid=4190"