On Apr 15, 2012, at 9:54 PM, Robert O'Callahan wrote: On Mon, Apr 16, 2012 at 11:47 AM, Charles Pritchard <chuck@jumis.com<mailto:chuck@jumis.com>> wrote: In your statement: What's the distinction between a "weak" CDM and a "strong" CDM? Would a "strong" CDM satisfy your concerns about the allowing "a situation" to develop? A "strong CDM" is one that is allowed to play HD Hollywood content. Let's say, to be precise, all of Netflix's HD content. Hmm, such a thing does not exist for desktop browsers today. Our objective for desktops was to enable the same service we have today using <object> through the <video> element instead. Can we say, instead, all content currently available through the use of plugins such as Silverlight and Flash ? …Mark On your second suggestion: "Alternatively, for a platform that offers built-in DRM API, you could define a CDM that maps onto that API, and explain the mapping in enough detail that any UA running on that platform could implement it." Are you requesting that a "User Agent Implementation Guide" be produced by the TF in addition to spec? What platforms would you expect that document to cover? Whatever platform CDMs (e.g. PlayReady) we want to expose to the Web. "Alternatively, for a proprietary DRM product, you could define a CDM that maps onto that product and explain that mapping in enough detail that any UA running where that product is present could implement it." Are you requesting that DRM vendors in the TF be required to publish some baseline of documentation? If they want their CDMs to be exposed to the Web, yes. Rob -- “You have heard that it was said, ‘Love your neighbor and hate your enemy.’ But I tell you, love your enemies and pray for those who persecute you, that you may be children of your Father in heaven. ... If you love those who love you, what reward will you get? Are not even the tax collectors doing that? And if you greet only your own people, what are you doing more than others?" [Matthew 5:43-47]
Received on Monday, 16 April 2012 16:36:25 UTC