Slashdot Mirror
Revised W3C Patent Policy Out, Comments Invited
Janet Daly, W3C writes "Today, the World Wide Web Consortium (W3C) began what it expects to be the final review of the proposed Royalty-Free Patent Policy. A new draft has been published; the review period has been extended to allow for
public and W3C Member comments alike. Review closes 30 April 2003. The press release and summary give a short version of goals and changes of the policy."
whos web ?
the American web or the UK web or the Chinese web or the Austrailian web or the japanese web or the other 260 nations that are online's web ?
Americans forget while living in their bubbles there is a thing called the "World" and their patents and laws dont extend to most of it, so go ahead make all the laws and patents you like, no one is going to follow them especially the chinese/russians etc etc
people cant even follow w3c recomendations as it is
Okay, I'll bite. The idea is that you can do whatever you want with your owns stuff patented - however, if you want your patented material to be incorporated into the W3C standard, then its up to you to comply with their requirements. All standards boards have various requirements before something can be considered as "standard". It is for the good of the economy.
I guess I'm just stuck in the last century, because I don't really understand the whole thing. I didn't have the patience to read the draft, but I read the press release, and I'm scratching my head over the whole idea of software patents. It's been a long time since I did any coding (anyone working with the 6502 any more?) but I seem to remember that there were always an infinite number of ways to accomplish any programming task. How do you patent one way, and then claim that no one's allowed to use another way to do the same thing? Or am I completely confused here? (I admit that this is almost a certainty.)
As a writer, I can't help but make comparisons with copyright law, another form of abstract intellectual property protection. If you're a writer, you can't copyright ideas. If I want to write a book about a great white whale, I can. I can even call it Moby Dick, and not just because Melville's copyright has expired. Titles cannot be copyrighted. So how come, for example, the .gif standard can be patented?
Of course, I may have completely misunderstood all of this. In which case, never mind.
Possibly because Slashdot is full of pedants? I'm sure you can work out the rest yourself.
I'm scared of numbers that can't be written as a fraction. It's an irrational fear.
BUT, IMHO, as soon as you try to make it a "standard" - thus forcing the world to use it, you should be required to make it royalty free and fully documented. There is a certain responsibility to the larger community for any organization or company that finds itself in this possition.
Information is too important to risk limiting its exchange. Case-in-point: M$ word documents. The "defacto standard" for document exchange is Microsoft's Office formats. However, the formats aren't fully documented and are at risk of changing with every new version of office. We would love to be able to ditch Office for an open-source (open format) solution, but we deal with other companies and government agencies who expect documents in Office format and send documents in Office format to us. It's a catch 22. We can't move to an open standard format without having a (redundant) system to be able to communicate with "the other 95%".
M$ has every right to sell their products. They have worked hard on them. However, because the formats have become the "standard", (and Microsoft has been doing everything it can to make it that way), M$ should be forced to open the format and fully document it, so that others don't have to reverse engineer it every time, to inter-operate. An open standard does not preclude MS from selling office. If it is the best product, it will sell. But an open standard for document exchange will allow true competition, and hence greater product improvement, by allowing software companies to compete on the technical merits of their products instead of on a closed format.
The same concept goes for audio and video. If you're going to call it a "standard" you shouldn't be able to charge for it. Charge for your product, not for the method of data exchange.
My $.02
"terrorism" and "pedophilia" are the root passwords to the Constitution
Internet Explorer is NOTORIOUS for not following standards. Ever wonder why so many DHTML-heavy sites won't work in Mozilla? They follow Internet Explorer's "standards" and use workarounds for all the bugs in Internet Explorer's page renderer, rather than making normal code that is more compatible with alternative browsers.
Karma: Excellent (fuck, even in the future moderation doesn't work!)
Since other folks clarified that the suit needs to be about patents that are claimed to be essential for implementing W3C specifications, it just remains to fill out point 1 and swap A and B in your point 4:
1. Entities A, B ..Z implement a W3C standard, in the process receiving a royalty-free license for some implicated technology from Entities A, B ...Z.
4. B sues A on a related matter, for example they claim a patent on some essential W3C technology
As a result:
5. A sends B their new license terms for the assorted patents they hold, plus a request for prompt payment of fees or removal of product from distribution
6. B considers whether they can pass this cost on to their customers and still remain competitive with C..Z who still get A's patent claims royalty free.
Chris Lilley W3C spec creation droid
Yes, the patent license imposes conditions on "you"; and yes, those receiving the software may not have all the rights (ie, unfettered modification) that the GPL requires. But the second is not caused by the first, and therefore section 7 does not apply.
Specifically, as I understand, the hypothetical patent licenses would say something like, "this license permits you to practice patent P only for the purposes of implementing standard S". It would not say anything about the terms under which you may distribute your implementation. The fact that others will be restricted in how they may modify your software is due to their license from the patent holder (even if it happens to be the same license you have), not due to a "condition imposed on you".
The "detailed step-by-step example" makes the fallacy more plain:
I similarly know full well that C's patent licence prohibits folks from taking GNU Emacs and adding URL parsing code. By this logic, I am prohibited from redistributing Emacs.
The only difference between the two cases is that a large class of modifications (any that would remove the program from the scope of the patent license) is prohibited in the first, while a smaller class (any that would bring Emacs under the scope of the patent) is prohibited in the second. But this is immaterial to the GPL.
The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.