S.
Hi Miguel. So you really believe that the only people entitled to an
opinion about a topic are those who, by your sole judgement, have a
totally internally consistent and blameless approach in all related
areas?
You're too perfect for me in that case. I know I am not, so
it's not even worth discussing how you are, as ever, completely
ignoring my real point by taking offence at all possible other points
Hello Simon,Hi Miguel. So you really believe that the only people entitled to an
opinion about a topic are those who, by your sole judgement, have a
totally internally consistent and blameless approach in all related
areas?
No Simon, I do not believe that. That would be a position based on
fallacious premises. Am able to decouple the messenger from the
message.
I merely find it "funny to be lectured" as I said on my blog post.
The core of the problem is that your message is either lost on the noise
that you made about Microsoft's EULA (and the analysis is in addition
botched) or was based on a fairly exaggerated position of loosing
fundamental freedoms.
You're too perfect for me in that case. I know I am not, so
it's not even worth discussing how you are, as ever, completely
ignoring my real point by taking offence at all possible other points
And what would that real point be?
Considering that your intro paragraph is still confusing (You got me
and Matt confused!) and your analysis is wrong.
Maybe the issue is that you think that am assisting people that distribute
an implementation under a license that you deem unacceptable (and here
is where your EULA analysis comes into play).
So explain to me what is this real point, it was lost to me.
I thought the LGPL was among the more clearly-written docs I read, but
there's enough complexity in any of these licenses that a casual read
could lead to misunderstandings.
I really think the spirit of Simon's post comes more from a religious
anti-Microsoft base than anything else. If Microsoft is Satan, then
anything close to them must be tainted, right?
I'll be the first to crack on Microsoft when they do something truly
stupid or even evil, but I sure hope I retain the ability to judge
products and companies on the merits of what's real. I've always
loved Microsoft's development environments, for instance, but I hate
the fact that they've been so reluctant to embrace other platforms.
Personally, I've never seen an argument turn constructive once the
"religion" button is pushed. The conversation far too frequently
takes leave of the facts, and it's hard to find the rails again.
For the record, I'm really glad you're getting a little cooperation
from Microsoft. I don't see a way this can be anything other than a
win for both organizations.
-D. Lambert
Actually no. But I am taking factors other than technology into
account in forming my judgements. Some people call that "religion",
but I regard an approach that takes only the technology into
consideration and ignores social, commercial and political issues as
amoral.
I can understand, however, how those who have spent a lot of time
close to people at the opposite (and equally erroneous) extreme (all
politics, no technology) might err in a technology-only direction.
S.
Cool. We need more humour in the world.As it happens, I believe the best way to spread software freedom is to get people to use as much Free software as they can in the order that works for them. I don't believe it's essential to start from the operating system and work outwards, any more than I agree with religions that describe a perfect God and then claim he hates some sins more than others....
The core of the problem is that your message is either lost on the noise
that you made about Microsoft's EULA (and the analysis is in addition
botched) or was based on a fairly exaggerated position of loosing
fundamental freedoms.Actually, I'm fascinated to understand why you think my analysis of the MPEG-LA license is wrong. The terms say:THIS PRODUCT IS LICENSED UNDER THE VC-1 PATENT PORTFOLIO LICENSES FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER TO (A) ENCODE VIDEO IN COMPLIANCE WITH THE VC-1 STANDARD ("VC-1 VIDEO") OR (B) DECODE VC-1 VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE VC-1 VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.So if my activity is either commercial or on behalf of another person (e.g. paid employment) or both, my use of VC-1 is unlicensed. Or do I have this wrong?
Plenty of other people we'ren't confused, but I've now added a clarification just in case people still can't see that I am referring to Silverlight, not Moonlight, and to the platforms Silverlight is implemented on, not Linux.
So explain to me what is this real point, it was lost to me.It's the same point I know we disagree about over Mono. I know you have plenty of cool technology in Mono and likely will in Moonlight, so please don't take umbrage again over that - I'm not criticising the programming. But in both cases you're chasing Microsoft's tail-lights as they intentionally create a non-free ecosystem, and encouraging others to join you. With Moonlight, you will probably be the vehicle that brings DRM to Linux. But I know from experience we're unlikely to agree here.
Actually, I'm fascinated to understand why you think my analysis of the MPEG-LA license is wrong. The terms say:THIS PRODUCT IS LICENSED UNDER THE VC-1 PATENT PORTFOLIO LICENSES FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER TO (A) ENCODE VIDEO IN COMPLIANCE WITH THE VC-1 STANDARD ("VC-1 VIDEO") OR (B) DECODE VC-1 VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE VC-1 VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.So if my activity is either commercial or on behalf of another person (e.g. paid employment) or both, my use of VC-1 is unlicensed. Or do I have this wrong?
Sure. The section (b) above is the key, it is an (a) or (b) conditions, not an (a) and (b).
And (b) gives you the option to watch VC1 content that was "obtained from a video provider licensed to provide vc-1 video", ie anyone that has encoded and has taken a license to do so from MPEG-LA.
So the consumer is effectively empowered to watch the video. In fact section (A) does not even apply to Silverlight as Silverlight does not do any encoding itself.
If you're a business, you're also not covered by the MPEG patent licenses
twisting the MPEGLA terms
Actually, I'm fascinated to understand why you think my analysis of the MPEG-LA license is wrong. The terms say:THIS PRODUCT IS LICENSED UNDER THE VC-1 PATENT PORTFOLIO LICENSES FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER TO (A) ENCODE VIDEO IN COMPLIANCE WITH THE VC-1 STANDARD ("VC-1 VIDEO") OR (B) DECODE VC-1 VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE VC-1 VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.So if my activity is either commercial or on behalf of another person (e.g. paid employment) or both, my use of VC-1 is unlicensed. Or do I have this wrong?
Sure. The section (b) above is the key, it is an (a) or (b) conditions, not an (a) and (b).
And (b) gives you the option to watch VC1 content that was "obtained from a video provider licensed to provide vc-1 video", ie anyone that has encoded and has taken a license to do so from MPEG-LA.
So the consumer is effectively empowered to watch the video. In fact section (A) does not even apply to Silverlight as Silverlight does not do any encoding itself.OK, we agree about that. But you disagreed with me about the implications for commercial users and for those in employment. The terms say that such people have no license at all to MPEG-LA's patents: "NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE." Note that this and the words "THIS PRODUCT IS LICENSED UNDER THE VC-1 PATENT PORTFOLIO LICENSES FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER" apply to both a and b.
twisting the MPEGLA termsSo I was asking why you think I am twisting those terms. As far as I can see, anyone using Silverlight at or for work is violating MPEG-LA's patents if they view VC-1 video.
It's a pity to see you resort to personal attacks and engage in
pissing contests.
THIS PRODUCT IS LICENSED UNDER THE VC-1 PATENT PORTFOLIO LICENSES FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER TO (A) ENCODE VIDEO IN COMPLIANCE WITH THE VC-1 STANDARD (“VC-1 VIDEO”) OR (B) DECODE VC-1 VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE VC-1 VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
The first sentence specifies the rights (that includes the "a or b" clause). The second sentence states that other than the rights specified in the first sentence you have no further rights.
THIS PRODUCT IS LICENSED UNDER THE VC-1 PATENT PORTFOLIO LICENSES FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER TO (A) ENCODE VIDEO IN COMPLIANCE WITH THE VC-1 STANDARD ("VC-1 VIDEO") OR (B) DECODE VC-1 VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE VC-1 VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
I think you're misreading it and neglecting the very first phrase. Let's break it down. There are two different statements conflated in the capitalised text:THIS PRODUCT IS LICENSED UNDER THE VC-1 PATENT PORTFOLIO LICENSES FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER TO ENCODE VIDEO IN COMPLIANCE WITH THE VC-1 STANDARD ("VC-1 VIDEO"). NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.andTHIS PRODUCT IS LICENSED UNDER THE VC-1 PATENT PORTFOLIO LICENSES FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER TO DECODE VC-1 VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE VC-1 VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
Both statements apply only "FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER" and "NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE"
Commercial and non-personal users of Silverlight have no license of any kind to "VC-1 VIDEO". What part of that am I getting wrong?
S.
So what about the bit before (A)?
You got me thinking about what commercial means in this case.
What this probably means is that you can not use your PC with Silverlight/QuickTime/Flash to project movies in a movie theater without paying a licensing fee to MPEGLA.
Oops, typo - UNlicensed :-)
The first is the question of Moonlight's use of Microsoft-licensed,
proprietary codecs. It goes without saying that that's not going to
fly on many distros, Debian, Fedora and Ubuntu among them (and
*hopefully* OpenSUSE too. but I'm not as familar with their rules).
Will Moonlight be architected in such a way that the codecs are
pluggable, so that free software implementations can be used instead
by people in jurisdictions not subject to patent infringement, or
people willing to take the patent risk onto themselves? Ideal, from my
admittedly not fully informed PoV, would be if Moonlight used
GStreamer for its audio and video pipeline, and the Microsoft codecs
were just plugged into the GStreamer stack in the usual way.
The second is your comment that people can port Moonlight to Windows
or Mac. The rest of Mono already runs on those platforms today, as I
understand it. I'm sure Novell doesn't consider those platforms its
primary target, but the code for them is still in the main Mono
repository hosted on Novell's servers. Can you confirm that the deal
with Microsoft won't prevent the main Mono/Moonlight repository from
including code for Moonlight on these platforms, and that the
Moonlight team will accept those patches to the main development trunk
if someone writes them?
Are there answers to these questions out there somewhere?
What gives the scope of usage here is [. Any use that falls outside the scope of [ is prohibited by ]. Your cinema example is certainly one example, but in fact any use that is not both personal and non-commercial is licensed as far as a direct English reading of the text is concerned.IANAL and there may be a deeper magic from before the dawn of time that I don't know about but prima facie any business using Silverlight to view VC-1 Video under these terms is acting without a license from MPEG-LA.
On Sep 8, 5:59 am, "Miguel de Icaza" <miguel.de.ic...@gmail.com>
wrote:
> I agree that the legalese makes things blurry.
So, are you saying maybe I didn't twist the MPEG terms after all?
> In any case, since the wording comes from MPEG-LA and this is the same
> wording that is used for Quicktime (H.264) and other codecs that are
> commonly distributed (Flash, iTunes and QuickTime) either every Apple
> customer using a Mac in a commercial enterprise is in violation of the
> license or we are missing a subtlety.
I'm looking for that subtlety, yes. Of course, it's possible that the
intent is indeed to drive diligent commercial users to buy patent
licenses - that's the way software patent extortion works.
S.
- c
An excellent, excellent post and rebuttal to what I also believe are
misconstrued and in some cases, indefensible claims. It is impressive
to see such a detailed and thought provoking response with a deep
rooted message of "practice what you preach".
Keep up the excellent work.
Jono Bacon
PS. The patents are an issue, but that guy does not even mention them.
I wasn't trying to get into the Moonlight discussion at all, Miguel,
because I recognized (after reading your comment on Simon's blog) that
the licensing terms applied to Silverlight, not Moonlight. I think I
was just a little sloppy in introducing the topic.
You know (I think) that my real concern is with Novell's patent
partnership with Microsoft, and anything that relates to it. I think
that deal was wrong for open source - against the ethics of open
source and harmful to its future. I suppose we disagree on this, but
that is my position. I apologize for painting my argument too broadly
in this case.
Matt
It will be clear once you know what does MPEGLA mean by "commercial
use". I guess the answer can be found somewhere in the MPEGLA web site
(the license notice points there for more info). In any case, I think
it is obvious that "commercial use" here means using the decoder in a
commercial product, but not using the decoder in commercial facilities
or for doing your job.
applications. Without a common, open video platform, I don't see this
as much of a step forward from flash (as a user). So - congrats, but
I think the video piece is pretty important and hope it can be worked
out.
> I agree that the legalese makes things blurry.
So, are you saying maybe I didn't twist the MPEG terms after all?
I'm looking for that subtlety, yes. Of course, it's possible that the
intent is indeed to drive diligent commercial users to buy patent
licenses - that's the way software patent extortion works.
The only reason I read Simon's blog is because you found it worthy to
post a comment on.
After reading that original post I am shocked that you did not just
ignored it -- the impartiality and the lack of logic in that text is
more then obvious.
Why bother?
Would you care to elaborate? I have agreed with some of the issues
Miguel has raised and added comments, and Miguel has just said he
agrees after all with my concerns over MPEG-LA.
Right now I stand by the assertion that Moonlight incites people to
join an ecosystem that raises serious concerns (notably that the
control point is in the CODECs and not the code). Which other aspects
of my posting do you believe lack logic? I'm happy to debate them.
S.
You know (I think) that my real concern is with Novell's patent
partnership with Microsoft, and anything that relates to it. I think
that deal was wrong for open source - against the ethics of open
source and harmful to its future. I suppose we disagree on this, but
that is my position. I apologize for painting my argument too broadly
in this case.
Would you care to elaborate? I have agreed with some of the issues
Miguel has raised and added comments, and Miguel has just said he
agrees after all with my concerns over MPEG-LA.
Right now I stand by the assertion that Moonlight incites people to
join an ecosystem that raises serious concerns (notably that the
control point is in the CODECs and not the code). Which other aspects
of my posting do you believe lack logic? I'm happy to debate them.
Why exactly do you think that's obvious? The terms specifically
isolate the grant of rights to "personal use" as well as "non-
commercial use".
S.
Uggh.
So much time wasted over what is simply boilerplate MPEG-LA language.
Anyone that thinks that this boilerplate language prevents a user from
watching commercial content is either being disingenuous or is simply
stupid. And nobody is that stupid, so I can only conclude that the
former is the case here.
And another thing. Ideological purity has its place but so does
pragmatism. Are you saying, that as a matter of principle, you refuse
to watch any video that was encoded with a "proprietary codec"? You
watch no DVDs? You watch no digital cable? You watch no OTA SDT or
HDTV? You watch no .mov, .wmv, .mpg videos? You watch no DivX or
XVid videos? You just make do with OGG? I don't believe that for a
second. But if that's the case, you can simply use Moonlight with OGG
and nothing else if you want. Sure, you'll miss out on the large
amount of content that was made with proprietary codecs, but you've
been doing that all along by not watching DVDs, HDTV, etc, right?
Lastly, in this thread you focused soley on the MPEG-LA boilerplate
license issue, I suppose because that's the only issue that concerns
Moonlight, while the rest of your issues concerned Silverlight. But
what about the other issues that Miguel called you on? Like the $5
Silverlight liability, which you implied was so horrible, but is in
fact right in line with others (better than Java and Flash, and the
same as Helix) and the fact that Silverlight's EULA is just as good if
not better than Flash, Java, Helix, Alfresco, etc. Are you conceding
you were wrong on the non-MPEG-LA Silverlight issues?
Actually no. I wasn't being comparative in my blog and I would not
recommend any of those other proprietary licenses within the context
of Free software either (including the Java one, which will not apply
to Java implementations derived from OpenJDK). We could niggle over
which is the most evil EULA but that wasn't & isn't the point.
S.
It's obvious (to me) because any other interpretation doesn't make any
sense, taking into account what's the goal of Silverlight.
>>Will I have to suffer
>>the shadow of Microsoft patents over Silverlight when using or
>>developing Moonlight?
>>Not as long as you get/download Moonlight from Novell which will include
>>patent
>>coverage.
And you have the gall to accuse others of poor language skills, i.e.
not understanding whatever the hell the real situation with
silverlight/moonlight is?
Because, in other words, you're saying that Moonlight is 100% freshly
squeezed open source, (and then, in the tiny light grey text at the
bottom of the screen), BUT, Microsoft may sue you or threaten to sue
you unless you use OUR implementation of Moonlight.
What was that about open source again?