W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2010

[Bug 10902] <video> element needs to support some form of DRM solution

From: <bugzilla@jessica.w3.org>
Date: Wed, 13 Oct 2010 19:30:29 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P671x-0001rp-Nb@jessica.w3.org>

--- Comment #45 from Maciej Stachowiak <mjs@apple.com> 2010-10-13 19:30:27 UTC ---
Although I personally dislike DRM, it's clearly not something Apple is entirely
opposed to as a vendor.

However, I don't really see what could be added at the HTML level to support

If in the future browsers choose to support DRM-capable formats in the <video>
element, I suspect the best way to express that would be a custom MIME type or
a custom codecs paramater value. A custom MIME type would have the intended
effect that non-supporting browsers wouldn't try to load the DRM'd resource. It
would also allow selection from multiple possibly vendor-specific DRM schemes.
It would not require any changes at the HTML level.

Adding a drm= MIME parameter would also not require any changes at the HTML
level - it should be defined for the specific MIME types that it applies to,
not by HTML.

If anyone believes that HTML5 should change to add some form of DRM support, I
think there needs to be an example of what kind of change at the HTML level (as
opposed to inside individual media formats) would actually be helpful.

That being said, it's likely to be hard to evaluate whether any given feature
is helpful until at least one implementor is ready to add DRM support. DRM
schemes tend to be extraordinarily complicated, and making a guess in a vacuum
about what HTML may need is unlikely to be successful.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 13 October 2010 19:30:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:59 UTC