On Fri, May 31, 2013 at 5:20 PM, François REMY <
francois.remy.dev@outlook.com> wrote:
> According to your reasoning, the <object> tag also 'formalize the platform
> fragmentation'
>
It did, see flash, silverlight, javafx, shockwave, unity-player etc.
> so does the <img>
>
<img> was fragmenting the platform because no format was mandated (largely
thanks to unisys). But after nearly 20 years this has stopped to become a
major pain and even IE is supporting PNG now.
> or the <audio> tag since the image formats to support are not restricted
> by the spec and some could be proprietary.
>
The fragmentation of the web in terms of audio is in full swing and no end
in sight. There still isn't a way to deliver audio that has at least one
commonly supported format.
> Yet, they were standardized.
>
Because something happened it was good and no flaw in the process was
identified nor needs to be corrected henceforth, so let's repeat it.
> Would they be invented today, they would still be. I think you'll have to
> accept that.
>
I don't have to accept anything.
If you want EME not to become a standards,
give the browser vendors that intend to implement it a reason *that works
> for them* why they should not implement it. That's it.
I don't take issue with "standardizing" fragmentation. I take issue with
this happening under the aegis of the standards body responsible for an
open web. If you insist on doing this, you prompt a fork.