W3C home > Mailing lists > Public > public-html-media@w3.org > April 2016

[encrypted-media] EME specification needs to include a CDM specification

From: Gravis via GitHub <sysbot+gh@w3.org>
Date: Thu, 14 Apr 2016 20:46:13 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-148477492-1460666772-sysbot+gh@w3.org>
GravisZro has just created a new issue for 
https://github.com/w3c/encrypted-media:

== EME specification needs to include a CDM specification ==
I've been looking over some existing and [plans for future CDMs with 
DRM](http://www.extremetech.com/extreme/204319-windows-10s-playready-3-0-mandates-hardware-drm-for-4k-playback)
 and they are **in total conflict with the [W3C's 
mission](https://www.w3.org/Consortium/mission)**.

> One of W3C's primary goals is to make these benefits available to 
all people, whatever their **hardware, software**, network 
infrastructure, native language, culture, geographical location, or 
physical or mental ability.

So with Microsoft plotting to have both software and hardware 
dependencies integrated into their CDM, **the omission of a CDM 
specification from the EME only serves to give aid to what can only be
 described as global scale abuse.**

The only way to ensure full interoperability between platforms and 
architectures is to use a virtual machine.  The good news is that full
 and open specification exists for just such a thing, it's called 
[SPIR-V](https://www.khronos.org/spir) which is better known for being
 part of the recently released [Vulkan 
API](https://www.khronos.org/vulkan/).  All the documentation and 
tools are both free and open and it is hardware accelerated as well as
 software implemented, so it is the ideal platform for CDMs.

Please view or discuss this issue at 
https://github.com/w3c/encrypted-media/issues/166 using your GitHub 
account
Received on Thursday, 14 April 2016 20:46:15 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 14 April 2016 20:46:15 UTC