- From: Mark Watson <watsonm@netflix.com>
- Date: Tue, 2 Apr 2013 06:56:00 -0700
- To: Henri Sivonen <hsivonen@iki.fi>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Glenn Adams <glenn@skynav.com>, Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html-media@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Sent from my iPhone On Apr 2, 2013, at 2:30 AM, Henri Sivonen <hsivonen@iki.fi> wrote: > On Tue, Apr 2, 2013 at 12:10 PM, Silvia Pfeiffer > <silviapfeiffer1@gmail.com> wrote: >> I'd actually be curious about this as well, because I've heard people state >> that captions are just as valuable and as much "content" as the video >> itself, in their own right. So, I'm curious to hear whether people expect to >> send their captions also in encrypted form when they distribute encrypted >> content or whether they're happy to provide them in the clear through a >> <track> element. > > Well, people state all sorts of things. See font DRM claims before and > after Web fonts happened (without DRM). > > The question is: > If DRM in browsers is available for video and audio but not for > captions and regulations require captions if audio is provided, will > movie streaming services refuse to stream movies to browser because > they couldn't apply DRM to the captions? Seems highly implausible that > the answer would be "yes". > > In the Silverlight-based Netflix player, do the captions go through > PlayReady or not? If not, there's really no issue here. No, the captions are delivered in the clear using TTML. ...Mark > > -- > Henri Sivonen > hsivonen@iki.fi > http://hsivonen.iki.fi/ >
Received on Tuesday, 2 April 2013 13:56:33 UTC