Questions about HTML5 vs EME and definitions of CDMs

I have a couple of basic questions that I am hoping this list can help
me with. (My questions throughout treat EME as though it is an
approved/published standard).

## EME is not part of HTML5, what are the implications?

Jeff Jaffe recently made the following statement:

> EME is not part of HTML5, so a browser can choose to not implement and
> be fully HTML5 compliant.

I'm wondering if this also applies to web sites that make use of EME
elements. That is, if a site uses EME specific elements (e.g.,
"onneedkey="), would that site be considered "invalid" HTML?

Put another way, if I were to set the document type to HTML5 on the W3C
validator, <http://validator.w3.org>, would a page using an EME element
return errors?

Would a website that requires EME elements to stream videos be lying if
they claimed that their site/pages are using (valid) HTML5 for video?
Or, in the very least, would that be a misleading statement?

## Why is the definition of CDM non-normative?

Right now the definition of CDM in the spec is non-normative. So far,
the only thing I can understand is that a CDM implements the Key System
interface. Why isn't a CDM just considered one and of the same as the
browser or the user agent? If "CDM" is going to be referred to in some
way that is separate from the UA or Browser, shouldn't it have a
normative definition, at least?

Received on Tuesday, 4 June 2013 07:17:37 UTC