- From: Paul Cotton <Paul.Cotton@microsoft.com>
- Date: Tue, 16 Apr 2013 13:28:48 +0000
- To: Florian Bösch <pyalot@gmail.com>
- CC: "Mays, David" <David_Mays@Comcast.com>, David Dorwin <ddorwin@google.com>, "<public-html-media@w3.org>" <public-html-media@w3.org>, "Philippe Le Hegaret (plh@w3.org)" <plh@w3.org>, "Michael(tm) Smith (mike@w3.org)" <mike@w3.org>
- Message-ID: <AB5704B0EEC35B4691114DC04366B37F2031B86E@TK5EX14MBXC297.redmond.corp.microsoft.>
As HTML WG co-chair I want to reinforce the point that asking for product specification documentation on a W3C email list is not appropriate. You have told this before, so please desist in making this kind of request. /paulc Paul Cotton, Microsoft Canada 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 Tel: (425) 705-9596 Fax: (425) 936-7329 From: Mays, David [mailto:David_Mays@Comcast.com] Sent: Tuesday, April 16, 2013 9:03 AM To: Florian Bösch; David Dorwin; <public-html-media@w3.org> Cc: Paul Cotton Subject: Re: Chromebook DRM specification This is not an appropriate venue for this request. If you want Widevine documentation, I suggest you reach out to Widevine directly, as David Dorwin already told you, the day after you asked your question. The W3C does not have Widevine documentation. David Mays | sr. software architect | 15.217 | one comcast center | philadelphia, pa. 19103 | 215.286.3395 w | 267.307.4195 m _____________________________________________________________________________________________________________________________ From: Florian Bösch <pyalot@gmail.com<mailto:pyalot@gmail.com>> Date: Tuesday, April 16, 2013 1:01 AM To: David Dorwin <ddorwin@google.com<mailto:ddorwin@google.com>>, "<public-html-media@w3.org<mailto:public-html-media@w3.org>>" <public-html-media@w3.org<mailto:public-html-media@w3.org>> Cc: Paul Cotton <Paul.Cotton@microsoft.com<mailto:Paul.Cotton@microsoft.com>> Subject: Re: Chromebook DRM specification Resent-From: <public-html-media@w3.org<mailto:public-html-media@w3.org>> Resent-Date: Tuesday, April 16, 2013 1:01 AM It has now been a month since my request for documentation/software on how to encode video for chromebooks compatible with chromebooks DRM. None has been produced. On Tue, Mar 19, 2013 at 7:11 PM, Florian Bösch <pyalot@gmail.com<mailto:pyalot@gmail.com>> wrote: Widevines proprietary DRM solution is suggested to achieve DRMed video hosting. Widevine is not offering libraries/documentation to the public to use. This will not keep most people from using flash/silverlight to implement their own solution. I do not see any improvement by this over the status quo. EME proponents are still without an answer and a resolution to this simple question: How do I encode and host DRMed content. This issue is not addressed. On Tue, Mar 19, 2013 at 6:42 PM, David Dorwin <ddorwin@google.com<mailto:ddorwin@google.com>> wrote: I addressed this issue in https://www.w3.org/Bugs/Public/show_bug.cgi?id=20967#c11, which you replied to. Container and encryption details can be found at https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#containers, and there are no special hosting requirements. You can try it out with the Clear Key ("webkit-org.w3.clearkey"), which is available on Chrome and Chrome OS. If you are interested in providing licenses to the Widevine CDM, I suggest contacting Widevine: http://www.widevine.com/contact.html. On Mon, Mar 18, 2013 at 11:52 AM, Florian Bösch <pyalot@gmail.com<mailto:pyalot@gmail.com>> wrote: As a reminder, no answer has been provided how I could encode and host DRMed video for the Netflix/Google Chromebook DRM since a week now. On Tue, Mar 12, 2013 at 7:15 PM, Paul Cotton <Paul.Cotton@microsoft.com<mailto:Paul.Cotton@microsoft.com>> wrote: I expect that David can answer your questions about Google's implementation. Paul Cotton, Microsoft Canada 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 Tel: (425) 705-9596<tel:%28425%29%20705-9596> Fax: (425) 936-7329<tel:%28425%29%20936-7329> From: Florian Bösch [mailto:pyalot@gmail.com<mailto:pyalot@gmail.com>] Sent: Monday, March 11, 2013 7:44 PM To: <public-html-media@w3.org<mailto:public-html-media@w3.org>> Subject: Chromebook DRM specification Apparently Google Chromebook now supports "HTML DRM" and Netflix has started serving content that way (source: http://news.slashdot.org/story/13/03/11/2155219/netflix-using-html5-video-for-arm-chromebook) Could anybody point out the specification and required libraries that'd allow me (or anybody) to encode/host their videos compatible with chromebooks html DRM implementation?
Received on Tuesday, 16 April 2013 13:29:38 UTC