No to DRM in HTML
Post from November 22, 2013 (↻ December 12, 2016), filed under Web Development.
This and many other posts are also available as a pretty, well-behaved e-book: On Web Development.
It’s been quiet around DRM lately so I like to share my opinion, in brief: DRM doesn’t belong into nor anywhere near HTML.
For one, HTML is a language to describe documents and, since HTML 5, applications. I don’t deem DRM in scope for HTML. Even in the form of EME, as there won’t actually be a DRM-related HTML element nor even a section in the actual HTML spec. Setting the scope’s not my call given that I’m neither one of the spec editors nor in W3C’s chain of command, but that doesn’t all of a sudden make DRM relevant to describe a document or application.
Figure: -1. (Copyright Gif Central?)
For another and more importantly, there are far too many problems around intellectual property. The whole copyright system is broken. DRM itself doesn’t work and is argued to not work on the Web either. With a broken patent system on top you can say that everything around intellectual property is dysfunctional—and go further and regard all of this a socio-political problem in the first place.
From my point of view there needs to be a fair, lenient, simple, robust, and actually working solution to intellectual property first before we should even think about bringing anything to the Web and its standards.
I’ve been contemplating to leave the HTML Working Group because of the whole DRM drama, symbolically, but I’m still staying in a holding pattern until I’m clear about a more effective course of action. No matter the confidence, this is a bit out of my comfort zone.
About the Author
Jens Oliver Meiert is a technical lead and author (sum.cumo, W3C, O’Reilly). He loves trying things, including in the realms of philosophy, art, and adventure. Here on meiert.com he shares and generalizes and exaggerates some of his thoughts and experiences.
If you have any thoughts or questions (or recommendations) about what he writes, leave a comment or a message.
Internet routing - Border Gateway Protocol (BGP) - renders the transportation path for an instant document unforeseeable. However to “extend” this uncertainty to mean that every document “must” at some point pass through a virtual jurisdiction where digital rights are modifiable or do not even exist is far far beyond the scope of a document format including HTML.
On November 25, 2013, 5:37 CET, Arthur Clifford said:
My personal opinion is that part of marking up a document or document could include marking up digital rights expression. That is I intend this document to be seen but not copied. Or, I’ve provided this document with the hope people will copy it as they see fit. Digital rights enforcement on the other hand is a bit different and better addressed by the hypertext protocol or some other layer. I don’t have a problem with the notion of allowing expression of preferred or intended use of a document. I agree that there is a socio political element to it all that I’m sure will be chipped away at slowly over time. But I don’t think that happens by symbolic gestures such as leaving the working group, but rather by continuing to represent your perspective. The right answer is not the majority or minority opinion, the loudest presented, or unspoken, but found somewhere in the overlap of differing ideas in a community of ideas. The truth is, the copyright system has not figured out, like most industries, what to do with the internet. It seems a wierd statement, but in the grander scheme of thigns the internet a and what it allows is still new, still evolving, and quite confounding and it takes time to properly and fairly encapsulate freedoms in legal terms. I think it is flawed to say copyright system is broken, it just hasn’t evolved to where it needs to be yet. All the “DRM drama” is part of the process of figuring out what the new paradigm is. It is a necessary evolutionary process; its just growing pains.
On November 26, 2013, 10:08 CET, Chris said:
It seems funny to me that around year 2000, W3C departed from HTML and promoted the unpopular and restrictive XHTML. Now they are trying to restrict HTML5 also…it seems that giant companies like Netflix, Google, Microsoft and BBC are supporting W3C in their mission to “lead the World Wide Web to its full potential.”
Have a look at the most popular posts, possibly including:
- New Book! 100 Things I Learned as an Everyday Adventurer
- CSS, HTML, and the Problem of Spec Fragmentation
Looking for a way to comment? Comments have been disabled, unfortunately.