HTML Media Updates

From Web and TV IG

Topics

HTML

HTML Media

  • Updates
    • 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

  • Updates
    • 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)

  • Updates
    • 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

  • Updates
    • 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

  • Updates
    • 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

  • Updates
    • 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!