Microsoft: Open Standards Are Good... If They're The Open Standards We Get Paid For
from the but-of-course dept
Our own Glyn Moody has been doing some digging and has come up with some interesting info about how Microsoft has been trying to derail an effort in the UK by the government to use open, royalty free standards wherever possible. Microsoft, apparently went on the offensive, arguing strongly that the government should reconsider and also include FRAND (fair, reasonable and non-discriminatory) licenses. FRAND is better than nothing, but it's not royalty free, and can certainly limit access to information for those who cannot afford to pay. But what's impressive is how much Microsoft tries to demonize royalty free offerings -- even as it admits in its initial letter than it contributes to "dozens" of royalty free standards.Moody also notes that Microsoft is misleading in trying to show just how popular FRAND is in open standards when it comes to software:
In a further attempt to downplay RF standards, the letter claims:In other words, when it comes to software, the royalty free stuff is the core software that's used to power much of the internet itself. But Microsoft goes on to suggest that royalty free software is somehow limiting, mainly by highlighting some confusion people have had with the open document format. It's the typical Microsoft play: spread FUD to try to push people to its (more costly) solutions. Apparently competing on the merits is just too difficult.one recent study found that a typical laptop contains over 250 technical interoperability standards - with 75% of these being developed under FRAND terms, and only 23% under Royalty Free terms.But when we look at the study itself, this is what we find:we created a set of broad categories - display, graphics, sound, storage, BIOS, input device, processor, power, file system, networking, wireless, I/O ports, memory, software, codecs, content protection, security and “other” - and sought relevant standards.As this makes clear, those "250 technical interoperability standards" were mostly about hardware interoperability. Of the purely software standards a far greater proportion were in fact made available under RF terms. Even more interesting, those RF-licensed standards included many of the absolutely core ones like HTML5, HTTP and HTTPS.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: frand, fud, glyn moody, open standards, royalties
Companies: microsoft
Reader Comments
Subscribe: RSS
View by: Time | Thread
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
Paying to be allowed to follow someone's standard or other rules is a stupid idea and should only ever be considered if circumstance have you trapped.
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
(Let me pause to note that the entire Internet is built on open standards, open protocols, open formats, and open source. Those are key factors at to why it's the most successful computing project ever by an enormous margin.)
[ link to this | view in chronology ]
IPX/SPX
It's unsupported. God help the tech who has to deal with the outage when the lease line operator changes out a switch or router that's incompatible
[ link to this | view in chronology ]
Re: Re: Re:
[citation needed]
[ link to this | view in chronology ]
Re:
https://en.wikipedia.org/wiki/Category:Open_microprocessors
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re:
According to Wikipedia Itanium and SPARC are open and royalty free.
[ link to this | view in chronology ]
FRAND-lexic?
I know I sure did...
[ link to this | view in chronology ]
Re: FRAND-lexic?
I'm getting a tshirt whipped up that says "I'm a freetard and PROUD with the Linux penguin on the lower left of the quote and the BSD devil on the upper right". Might as well go public!
[ link to this | view in chronology ]
Re: Re: FRAND-lexic?
[ link to this | view in chronology ]
Re: Re: Re: FRAND-lexic?
[ link to this | view in chronology ]
Re: FRAND-lexic?
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
Doubt?
Read what is required to achieve ISO certification for anything and what you see is that they talk about processes but nowhere they tell you how you should implement those and as long as the processes are there you are ISO worthy even if the processes don't work. Which makes sense why choose one or two ways of doing things but there is no requirement in ISO to test or verify the methods ISO only requires that you have the processes in place and it doesn't bother to see if they work or not.
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
If your data isn't in an open format...
(By "open" I mean "free", in case that's not clear.)
[ link to this | view in chronology ]
[ link to this | view in chronology ]
How?
[ link to this | view in chronology ]
Re: How?
[ link to this | view in chronology ]
Re: How?
[ link to this | view in chronology ]
Re: How?
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Microsoft is dying a slow painful death
[ link to this | view in chronology ]
Which of course was their plan when they named their crappy format "Office Open XML".
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
SERIOUS case
[ link to this | view in chronology ]