Microsoft is to open up the source code behind its server communication protocols, in an attempt to get the European Commission off its back. The announcement covers the source code behind the communication protocols for Windows Workgroup Server and Windows Desktop. Microsoft already offers 12000 pages of technical documents and 500 hours of free technical support to anyone applying for a license. Companies making software which interacts with Microsoft servers use those licences to make their products work properly with Microsoft ones. Such license-holders will now also get to look at the source code, but will not have the right to publish the code or include it in their own products.
Post a Comment
Member since:2005-07-12
I disagree. Releasing the source was neither required nor requested, and viewing the source code would subject the viewer to the potential for additional IP burdens that would not typically be associated with a simple protocol specification document.
Unless Microsoft is willing to allow their source code to be used as a reference for the creation of competing freeware implementations of their protocols, this gesture of theirs is very close to being worthless, at least in terms of making their protocols truly available (which is the entire point of this exercise).
Member since:
2005-07-12
There's nothing like adding an additional intellectual property burden to the process, is there?
The code isn't what is being asked for -- the EU only wants the specifications on which the code is based, or to which the code must conform.
The whole idea of asking for the docs is to have a description of the processes and protocols involved which are INDEPENDENT of any one specific implementation.
Hopefully the Powers That Be on the EU side of this are technically astute enough to realize that this is not an acceptable response.
Member since:
2005-11-14
They produced 12000 pages of docs, and experts said "it is incomprehensible, please produce something that makes some sense".
So they go ahead and say "RTFSC" (read the *Fine* source code) just like the worst OSS projects. And they want money if you look at it. And you obviously become a target for Intellectual Property litigation. For LIFE.
Are they really saying that the oh-so-powerful and oh-so-full-of-money MS does not have documentation for THEIR code and protocols? It's no surprise windows it's the mess it is!
Member since:2005-06-29
Member since:2005-07-06
I don't have the link at hand, but Neil Barrett was very critical of MS in his report to the EU. If you wonder who Neil Barrett is, he is the guy appointed as Monitoring Trustee by the EU on the basis of a list submitted by MS themselves. A simple search should provide his judgement which, as you may recall, was the reason why the EU threatened to fine MS on a per day basis.
rehdon
Member since:2005-11-14
http://www.groklaw.net/article.php?story=20060125103545406
Plenty of links to read. Enjoy yourself.
Member since:
2005-10-18
The moment you've seen the Microsoft source, you've caught - if you do open source, you're likely to taint your work inadvertently and then you're open for IP litigation and bullying.
Nobody asked sources from them, just the specs.
Of course, the problem for MS is - specs (protocols) are not copyrightable as such, though any specific document containing them may be. Therefore they can't restrict dissemination if this info other than by signing an NDA, and the latter I guess does not suit EU, which wants to make the protocols truly open.
