Re: EME

> > You're right, if not doing this way, you would be forcing to use the
web browser to see the content... If you've definitelly downloaded the
media file, why you must be forced to use a specific viewer? It doesn't
make sense and goes against portability and users rights, it's the same
situation about using closed specifications, your data is tied to a
specific software. That's not fair.
>
> Again, I'm most interested in scenarios where you have not
"definitely downloaded the media file". You are accessing a service which
has particular terms and conditions to which you must agree in order to use
the service. The user doesn't have a right to use the service in a way that
is inconsistent with the terms to which they have agreed, unless those
terms are so egregious as to fall foul of some law.
>
I understand your point of view regarding to streaming, but think about
this: also doing streaming, aren't you being downloading a file? What's the
diference between being it downloaded to a cache or to an user selected
folder? Doesn't I'm able to go to the cache folder on my computer and copy
the streamed file? Is it supposed to go against the agreed usage terms to
navigate on my own computer file hierarchy? I don't think so, and
definitely W3C shouldn't respald this kind of arbitrary restrictions.

I agree that Netflix or others has some commertial requeriments by the
entertainment industry and I respect that, but the fact is that this kind
of restrictions are not from a technical point of view but from a bussiness
model, and just for this reason, not only sooner or later it will be broken
or evited (just thinking about some combination of getUserMedia() and
RecordAPI if there're no direct and easier solution, for example canvas or
reading directly from the video tag) and this is another reason why it
should not be discussed on the W3C: just with current HTML5 technologies is
fairly simple to break it down, so it doesn't make sense to think nor
discuss about this topic: it will not work.