- From: <bugzilla@jessica.w3.org>
- Date: Mon, 16 Jun 2014 19:10:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24873 --- Comment #14 from Jerry Smith <jdsmith@microsoft.com> --- We would prefer to replace the DOMString capability with a dictionary that exposed specific capabilities with defined responses. The capabilities would need to confirm DRM specific needs (Hardware or Software DRM, Hardware or Software Media Pipeline, and Link Protection). There are also a set of capabilities that have more general media capabilities. These may fit here as a convenience, though they might better belong on the MediaElement directly. This could include capabilities like display resolution or a multi-channel audio configuration. The upside of using a dictionary is it would standardize the capabilities. A downside is that it might confine future capabilities we don’t anticipate now, and also might include specific technologies in the allowed responses (e.g. HDCP 2.0). An alternative we may want to discuss is the concept of validating DRM license constraints in some way that doesn’t download content, but submits the license for pre-approval. This might be done with a small amount of protected content included with the app, and has the advantage of being open ended, and definitive in that the license is processed by the CDM and passed or failed. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 16 June 2014 19:10:24 UTC