Slashdot Log In
W3C Considers Royalty-Bound Patents In Web Standards
Posted by
timothy
on Sun Sep 30, 2001 11:16 AM
from the 59th-day-11th-hour-final-minute dept.
from the 59th-day-11th-hour-final-minute dept.
Svartalf writes: "There's a report on Linux Today about a proposed loosening of requirements on patented technologies being submitted for W3C consideration. Called RAND, short for 'reasonable and non-discriminatory,' it basically changes the position of W3C with respects to patents. This is a real problem as all of you know, considering that we've had all kinds of fun with other 'reasonable' licensing (MP3 and GIF come immediately to mind) -- the cutoff for comments is tomorrow (9-30) so if you want to get them in do it NOW." September 30 is now today rather than tomorrow. The same issue was raised in a post yesterday as well, but many readers have submitted news of this Linux Today piece. Reader WhyDoubt points out that comments on the change are archived on the W3C's site, including this pithy comment from Alan Cox. Do you think that fee-bound patents have a place in the standards promulgated by the W3C? Read the Patent Policy Working Group's FAQ, then add your comment.
This discussion has been archived.
No new comments can be posted.
W3C Considers Royalty-Bound Patents In Web Standards
|
Log In/Create an Account
| Top
| 224 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Good! (Score:1, Offtopic)
called Corporation. The only company...
respond (not just on this board) (Score:4, Insightful)
Please, dont just comment on this board; go ahead and send that email with your level- headed-non-profane thoughts.
This certainly looks like a sneak-it-in approach with such a short public comment periond - especially for something this large.
Hopefully some prudent arguments can be made to convince the W3C folks.
Hard to say it better than Alan Cox (Score:4, Insightful)
Said after pointing out the secretive and rule violating manner this happened and rightly snearing at how this will contribute the purpose of the organization, interoperability. His prediction:
This would mean SVG became a multi-vendor consortium pushing a private specification. But let's face it - with the patents involved - that is precisely what it is.
And so the internet becomes TV as all are shoved out to be replace by three or four big broadcasters. Can it happen? Sure it can, just look at all the empty TV and radio spectrum. There is no technical or real economic reason the airwaves are filled with nothing but comercial noise or static. It's a problem with bad laws.
Sorry. (Score:2)
Having a completely open stardard is definately better than having a standard with patents involved. Completely open means anyone can take it and work with it... without paying the piper.
But why? (Score:3, Insightful)
This is a step FORWARD (Score:4, Interesting)
What you're forgetting is that the very transistors that make up your beloved computers were once patented. Without that patent, we wouldn't even be having this discussion.
The question we should be asking is, do we want to hold back web standards by two decades to satisfy our irrational aversion to patents? I don't think we should. The consequences on the growth of the web will be disastrous if we don't take sensible steps like allowing patented technology into web standards.
Re:This is a step FORWARD (Score:5, Insightful)
Second, the FET was patented in 1927, and it is this that makes modern computers go, not the BJT of which you speak. The original patent holder didn't make a damn dime. (Yes, it was because he couldn't make one, only design one.)
The transistor is a staple of modern electronics because it is superior technology. The concern about the W3C is that inferior technology will become standard as corporations push for profits. This isn't very far fetched (Microsoft), and that is why we Slashdotters are worried.
Re:This is a step FORWARD (Score:5, Insightful)
Can we exchange text on the web, already, of any arbitrary type and format? Yes.
Can we exchange images on the web, already, of any number of supported types? Yes.
Can we run backend scripts, already, to add functionality (such as, say, to implement a discussion board?). Yes.
Sound? Yes. Video? Yes. etc etc.
In fact the only niches for patented 'standard extensions' all involve commerce.
It's not very trendy to say so, but virtually all of the basic infrastructure technologies we're now using were developed at government expense. From TCP/IP to HTTP itself (Berners-Lee was on Supercollider funds at CERN when he developed it), WE paid for these inventions. Which makes them COMMONS which makes them OURS to share however we choose. Period.
Honestly, what business does Corporate America have using cynical exploitation of patent law to co-opt what was developed with taxpayer money? Can anyone without secret (or not so secret) fantasies of being the next Bill Gates really give me a logical, non-theological reason why we should let that happen?
I have grown so weary of even having to argue this anymore.
:M
Re:This is a step FORWARD (Score:5, Insightful)
The whole point of an open standard is that anyone can implement it. If we allow the use of patents in open standards, then they cannot be implemented by just anyone, you need a license, or a whole bunch of licenses, to implement it. Furthermore, as far as I understand it companies aren't legally obligated to license a patent to any particular party, so if they decide that they don't want you, in particular, competing with them they might decide not to license it to you. All it takes is one company on the list to do this and you can *never* implement that "open standard."
We should expect this to destroy the usefulness of open standards and bring a big step back to the days when software companies had total control over your computing experience. The Internet itself only exists because of the adoption of an open, non-patented standard, TCP/IP. Imagine if Microsoft, for example, had a patent pending on TCP/IP, where would we be now? Every little Internet app author would have to fork out cash to them, probably on a yearly basis.
Re:This is a step FORWARD (Score:5, Interesting)
Patent law exists to "promote the sciences and useful arts". It does not, nor should it exist to "allow businesses to recoup their research investments". This is natural-right thinking which is explicitly rejected by the founding fathers via the constitution.
The biggest problem with patent law is that it is now the providence of big business and lawyers; when it was originally there for "inventors". Patent mechansim is not very accessable by the general developer... else we would have far less patents since the PTO would be more up-to-speed with what is "obvious". The PTO also pays it's evaluators poorly. I can get over 6 figures in the marketplace, but the PTO could only offer me 40K beacuse I don't have a masters (and then it'd be 50K or so, 60K for a pHd). How can we expect the evaluators to know what is obvious if (a) they arn't practitioners and (b) they are underpaid.
I'd rather have a "patent duty" like "jury duty" be put out for average developers... where they are paid at the prevaling wadge for ONE YEAR of service, after which they return to the market. Now, this would help prevent those big companies from patenting stupid stuff...
There are better examples. (Score:1, Insightful)
I don't think those two are a very good example of patent problems. They are not really problems at all.
You can use them and licens them in that case, thats the costs of using other peoples work (the work involved in reseaching&developing them). Otherwise you can develop your own formats. You are perfectly free to chose.
The real big problems is obvious patents, and even worse to broad patents. Those really are huge problems and will get even worse.
You don't happen to implement gif by accident but there are horribly broad patents out there locking up whole categories of software/businessmodels.
Cox would have more impact without the hyperbole (Score:1, Insightful)
First off, I actually agree with a lot of what he said in his statement. However, I think he would have had a lot better chance of getting the point across if he hadn't invoked the specter of evil corporatization, and maybe left the Microsoft bashing out.
There are many valid points he could have made without sounding so reactionary. Must have been taking lessons from RMS, yeesh.
The battle was lost a long time ago (Score:5, Interesting)
For reasons never disclosed to public, browser vendors didn't want to implement HTML 3.0. Except free browser projects, but their users were minority and the development resources were really small.
Then, one day, HTML 3.2 was revealed to the world. In terms of features it was a downgrade from HTML 3.0. In terms of sanity it had none, because it merely "standardised the current state," according to W3C. That explicitely excluded free browsers which implemented parts of HTML 3.0 and were going to implement more, but W3C never cared about them.
There never was a public discussion about HTML 3.2. After the publication the amount of flames from the free world on W3C lists was enormous. Unlike flames on Slashdot, where flamers rarely know anything about the subject of their flame, this was flaming from the people who knew everything about the subject. And it was going on for months. I don't think Slashdot flames ever managed to reach the level of revolt HTML 3.2 produced.
And now it's happening again. Surprised? You shouldn't be.
You see, W3C is a vendor consortium and vendor consortiums take care about interests of its members. That's why they exist.
Just another brick from the wall (Score:1)
The Internet was a frontier, and now it's being settled. So you know what that means? Find a new frontier!
I mean, once they start making movies like "Hackers", you have to know that it's over =)
It's not too late... (Score:5, Informative)
Obvious angles on it:
Bad for the W3C, bad for business, bad for users (Score:1, Redundant)
common protocols that promote its evolution and ensure its
interoperability"
A lofty and great goal. A pity that the W3C now proposes to throw away its
very reason for existence.
And now we have a new much abused patent politics buzzword
"Non-discriminatory"
Indeed.
I think the W3C should ask itself how allowing parties to use patents to
prevent community projects for blind access is "non-discriminatory".
Tim Berners Lee created an innovative environment about sharing and
referencing data. You plan to give large companies the power to stifle
that innovation.
It says something for the sad state of W3C that the proposal in question
has been allowed to progress, carefully arranged not to be visible to
the outside world. The dates of the short consultation period do not even
appear to have been adjusted in the light of September 11th. The proposed
shortening of the consultation period also appears to violate the W3C
rules, but then I am sure you don't care. I can smell the rot from here.
A patent-encumbered web threatens the very freedom of intellectual debate,
allowing only large companies and big media houses to present information
in certain ways. Imagine where the web would be now if only large companies
were able to use image files.
And large companies it is. I note the distinct lack of small companies on
the proposal in question. Within the ISO where the same things happen the
money simply moves in circles between big players. Accountants and lawyers
pay $100,000 sums back and forth as part of an accounting game that they
use to keep out smaller players.
I think we can also be sure that the kind of W3C members working this
little agenda have plans. I would bet on "Windows digitally-protected
uncopyable web pages" being one of them. Of course the protection they
really mean is "against reading by non IE users".
The W3C must ask itself whether it plans to continue the vision of Tim or
become another ITU, a bloated dinosaur that exists more as a corporate United
Nations of communication than a standards body.
If the W3C wishes to remain relevant to the people, to the small businesses
(the other 80%) and to the future of the web then I strongly suggest that it
Requires non-disclosed patents are freely licensed for use in that standard for all.
Without this a key infrastructure standard may suddenely be "owned" by a W3C
member who intentionally kept quiet to gain "non discriminatory" - but large -
license fees. The current wording encourages patent abuse. Licensing on a
RAND basis would only be appropriate for such a non-disclosed patent if
existing RAND licenses were on that proposal before final consultantion.
Regardless of the rest of the outcome all honest members will benefit from
such a stricter policy on non-disclosure of patents.
Does not "approve" or "recommend" or allow its logo to be used on any patent-encumbered item.
To do so will tarnish the value and reputation of the W3C name and logo. It
will also create confusion about what W3C standards indicate.
Restricts its activities on patent-encumbered projects to providing a forum where such people can work on patent encumbered projects to be released under their own names only.
Here its activities would be in a consultative role, helping to guide these
bodies in areas of overall standards compliance and interpretation of W3C
goals. It is possible to further the web standardisation goal without
becoming part of those activities that are contrary to the original goals
of the W3C.
This would mean SVG became a multi-vendor consortium pushing a private
specification. But let's face it - with the patents involved - that is
precisely what it is. It may even be appropriate for SVG work to be
transferred to the ITU.
Finally we should all remember this. When patented W3C standards ensure
there is only one web browser in the world, its owners will no longer
have time for the W3C or standards.
This is not at all surprising (Score:5, Informative)
First, in the W3C, membership is only offered to organizations. In the IETF, all individuals can participate in the Working Groups; any individual can generate a RFC.
Second, in the W3C, membership costs either $5000 or $50,000. IETF membership is free. It does cost money to attend an IETF meeting, but that cost is around $500; well within the reach of any serious developer.
Control of working groups in the IETF (and the IESG) is based on technical ability or desire. In theory, you don't really have to be a prior participant in the IETF to run a working group. (But it helps. A lot.) In the W3C, you must be a member (paying $5000 or $50,000), in order to run a WG.
In the IETF, decisions are made on rough consensus. In the W3C, decisions are also made based on consensus with elaborate procedural systems. It's interesting to compare and contrast the amount of procedural information on the W3C's web site versus the IETF's web site.
In general, all IETF working material is open and accessible to the public. You can read RFCs as they are being written; you can read, post, and comment on IETF mailing lists. W3C working material is not open to the public.
Companies may ask if the IETF is unfriendly towards business. I do not think this is the case. Look at Cisco. Cisco has certainly participated in the IETF; they are very involved in the development of several IETF standards. However, Cisco still has the ability to develop their own proprietary protocols and still has the ability to make secret agreements with other companies.
In short, membership in the W3C has always been primarily by businesses. In fact, there is no way for an individual to join the W3C. Anyone surprised by an extreme pro-business slant of the W3C is not really familiar with the W3C's nature.
[You might wonder why companies don't control the IETF as much as they control the W3C. My theory is that the W3C works on items much more relevant to the end user. A mass-market consumer is much more amazed by SVG than they are by packet switching. Companies have a strong interest in controlling what the mass-market consumer sees.]
(Refs: W3C Membership [w3.org], IETF Web site [ietf.org])
copy of my comments (Score:2, Interesting)
Hello,
I've just read the Patent Policy WG FAQ and I have grave concerns about the
world wide web consortium pursuing this avenue.
The value of the W3C is dependent on the value of the standards it
promulgates. The value of those standards depends on their widest adoption by
the global internet community. Adoption by the internet community is
dependent on the ease and value of implementing those standards.
As a member of the internet community since 1984, I've seen a few standards
come and go.
As an inventor with a few patents, I know exactly what the value of patents
are. Companies and individuals do not go through the work of obtaining
patents because it is fun, or inexpensive. They do so with the intention of
profiting from them before they expire.
Allowing patented technologies to become w3c standards will benefit no one
except the patent holder. Having the internet community given the choice of
supporting w3c standards and paying license fees or developing non-patented
pseudo-standards will result in a plethora of divergent and redundant
standards in use. The value of the w3c will go into the toilet.
I urge you to disband the working group and abandon this policy from
consideration.
regards,
Dr. Andrew E. Mossberg,
Chief Technical Officer, Asoki Corporation
Chief Information Officer, CruisExcursions.com
President, Inicom, Inc.
Director, Fuzzy Theory LLC.
My letter to comment@openphd.net (Score:1)
As a professional software developer making a living from being able to
develop platform-agnostic applications for the web, I am extremely alarmed to
see the W3C's proposed stance on patents & standards. With the proposed
changes in place the web will become more and more a showcase for large
corporations and will extinguish the independence and innovation that have
made the internet freely accessibly to anyone with a web browser (of any
flavour) and a dial-up account.
Indeed, with the proposals in place the web risks becoming a tool of a few
corporations (I think I don't need to list them specifically) and innovation
will largely be shut down. After a while, the W3C itself will cease to be
relevant, and I can hardly believe that is what is intended.
I urge you, therefore, to reject these proposals and show your organisation to
be one of integrity to the ideals of Tim Berners-Lee et al; be proud that you
are not just another tool of big business.
Totally OT, but (Score:5, Funny)
Kind of a fitting title (?)
Letter to www-patentpolicy-comment@w3.org (Score:4, Insightful)
Lets take a look at open source, shall we?
According to a Netcraft survey (http://www.netcraft.com/survey/) taken in July 2001, 60% of the internet's web servers STILL RUN APACHE. The reasons for this? It is fast, cheap, and secure. The reason it is all three of these is it is OPEN SOURCE. If the W3C began considering patented technology for standards, and incorporated those standards into core web systems (example: secure, uncopyable web page) then, if that technology uses some server-side component, Apache, the LONG TIME leader in web servers, would be LEFT OUT IN THE COLD and hence, discriminated against.
Granted, that may the whole point for this move - the authors are from some of the largest IT companies in the US - Microsoft (well, their IP law firm), Apple Computer, and HP. That's fine. It is also counter to the goals of the W3C.
(quoting from http://www.w3.org/Consortium/#goals)
"W3C's long term goals for the Web are:
1) Universal Access: To make the Web accessible to all by promoting technologies that take into account the vast differences in culture, education, ability, material resources, and physical limitations of users on all continents;
2) Semantic Web : To develop a software environment that permits each user to make the best use of the resources available on the Web;
3) Web of Trust : To guide the Web's development with careful consideration for the novel legal, commercial, and social issues raised by this technology."
So unless the W3C wants to become a hypocrisy and a joke, either this proposal has to go, or the original goals have to go. I'd hate to see the goals change. W3C has provided an amazing service to the web community, and if its goals change, I'm afraid that service would cease to exist.
Don't get me wrong - I am a small business owner and as a small business owner I understand the value of intellectual property as much as if not more than a large company. If my business model is based on my IP, then with it I make money, without it, I fall into the (if I'm not mistaken) 95% of companies that close their doors within the first five years of existence. HOWEVER, I don't think that STANDARDS should be based on patented technologies unless the patent owner freely licenses it to anyone who uses the standard.
ha ha (Score:1, Funny)
my note (Score:2)
Just fired this off, feel feel to copy:
My message to www-patentpolicy-comment (Score:5, Interesting)
Unfortunately I didn't see Alan's reply before writing up mine, he surely has some points I should have included.
Anyway:
I believe the adaption of possibly non-royalty-free standards by W3C would
be a fatal mistake. Please take the time to consider the implications:
Right now, projects like Konqueror, Mozilla, Lynx, Links and even your own Amaya are doing a pretty good job - but they can't continue if they have to pay to implement the next set of standards.
If you have been on the net long enough, you will have noticed that all attempts to create a similar infrastructure based on closed "standards" have ultimately failed (e.g. Europe Online) or turned to open standards, basically becoming an ISP and an internet portal (AOL,
Compuserve, MSN)
The problem becomes much bigger once someone starts charging royalties for something that is even a w3c standard (imagine some company finding
a reason for charging royalties on the a href= html tag).
I can understand the reasoning behind allowing RAND; yet I think it will cause far more trouble than it's worth.
Please reconsider.
Does this suprise anyone? (Score:1, Insightful)
If it ain't broke don't fix it. (Score:3, Informative)
It is not like there is a lack of innovation here.
Why fix something that's not broken? Money should not be the focus of the W3C... bringing the market to maturity and ensuring competition (and thus innovation) should be its goal.
Patents are wisely justified under the U.S. Constitution to "Promote the Sciences and Useful Arts" and are not justified under any sort of natural-rights or right to compensation logic. One must ask if the patent process is indeed satisfying its goal. If not, then institutions such as the W3C should not be rushing to support the implementation of restrictive mechanisms that are not needed.
W3C becoming irrelevant (Score:1, Flamebait)
There are a number of reasons:
* What is out there works.
* W3C specs even surpass the most obscure RFCs in their obtrusity.
* W3C specs are usually playing catch-up with existing technologies.
In the end, if I cannot view a page, I won't. This happens with flash quite frequently, I refuse to install the damn thing.
Trial by Jury of Peers? (Score:2)
Don't post here - send them an email instead! (Score:4, Interesting)
There were only 7 comments archived in August and merely 9 in the month of September... until yesterday! Way to go guys! (I have to assume that Slashdotters helped pummel them with comments.)
You can see everyone's comments here:
http://lists.w3.org/Archives/Public/www-patentp
Last time I looked there were 250+ comments! Fortunately, most of them were opposed to incorporating patented technology into W3C recommendations.
Re: sending your comments to W3C (Score:4, Informative)
For those of you not familiar with how W3C works: W3C puts documents out for public comment, announces them, and is obliged to respond to questions and critiques. This document was no different; in fact, not only was the document announced on the W3C Homepage six weeks ago, the WG produced both a FAQ and backgrounder, and the announcement was carried on a variety of syndication services which rely on RSS feeds.
As many of you may have missed the August announcement of the draft, I include the links here for your reference. I would ask that you consider reading these documents as "item 0" in Adam's "What you can do" list.
Announcement: archived with date at http://www.w3.org/News/2001
FAQ: http://www.w3.org/2001/08/16-PP-FAQ
Backgrounder: http://www.w3.org/2001/08/patentnews
W3C Patent Policy Framework: http://www.w3.org/TR/2001/WD-patent-policy-200108
For more information on how W3C works in general, I invite you to read the W3C Process Document:
http://www.w3.org/Consortium/Process/
As of now, many comments sent to W3C's Patent Policy Comment list simply say, "Don't!" By responding in this manner, writers give the Working Group nothing on which to build a constructive response or to consider. Should you decide to comment, I suggest here what you can do to help W3C make the most of your comments, and help it be in a position to act on them:
1. Read the draft itself. (You may find the FAQ and backgrounder useful.)
2. Provide your comments directed at specific sections of the draft with which you object.
3. Ask questions where you find the language of the draft itself unclear.
4. If you make philosophical objections, please base them, at least in part, on your reading of the draft.
W3C welcomes all comments - critical and otherwise - on its documents. I would say though, that the preference is for substantiated comments. This type of comment leads to action; at the very least, they demand consideration on behalf of the Working Group, as well as a thoughtful response.
Best regards,
Janet Daly
Head of Communications, W3C
RANDsom?!?! (Score:1)
My email to the W3C... (Score:1)
This is what I sent them (in case anyone cares):
The Internet was built on open standards - that is one of the main reasons why it has been successful and proprietry networks have all but disappeared.
The patent proposals being put forward are an anathema to the whole idea behind the web. We have already seen the damage done by software patents and de facto standards: GIF and MP3 are examples of this. Small developers are unable to innovate because of excessive license fees.
I have always had respect for the W3C but this move concerns me greatly. The W3C has pushed for "standards compliance" in web browsers. How will small developers be able to comply with these standards if license fees become a stumbling block? How would Tim Berners-Lee been able to develop the web if something fundamental such as TCP/IP had been patented?
The proposals are fine if you want to see web standards turned into a corporate playground, but for those of us who understood the web to be a method of exchanging rich content in a free environment, it is a sad day.
I would urge the W3C to abandon this course of action and stand up for the smaller developers in the world - people who, like Tim Berners-Lee, could be responsible for the "next big thing".
Sincerly.
Julian Regel
I've sent my comment. Have you? (Score:2)
We can sit here and talk about it all day, or we can do something...
-jerdenn
My Letter (Score:1)
As a long time internet user, I have come to realize the importance of freely implementable and open technologies as the primary factor in the scalability, reliability, and openness of the Internet. Since the beginnings of the global internet, the IETF has relied on open and freely available standards to ensure compatibility and security in the core functionality of the internet. Tools such as Sendmail, BIND, and other core technologies all rely on the existence of a free and open standard. If patented technolgies had been allowed in the critical RFCs implemented by these products, these carrier class free applications would have never been created. How much would such a situation have stifiled the growth of the internet?
Any patent incumbered technology, regardless of licensing scenario, prohibits the creation of freely available open source implementations of the techonogy. When this happens, the internet is no longer open, and a key insurance policy of free implementations of core standards in lost forever.
I urge the W3C to avoid placing control the web solely in the hands of for-profit corporations. The web is about freedom and innovation, and the policy proposal effectively cripples both.
Regards,
John Anderson
Vote for this on kuro5hin (Score:1)
Embedded designers speak out! (Score:2)
I see this crap every day of work: I cannot turn around without stumbling over a patent license that prevents me from supporting a standard. I work in the land mobile radio market. Look at the big player in this market: Motorola. They own most of the patents on the standards, and so they can pretty much prevent any competitor from gaining a foothold in the market. If you want to have a system that works correctly, you buy Motorola repeaters, Motorola consoles, Motorola mobiles, and Motorola test equipment. Try to integrate a Racal, E.F. Johnson, or Kenwood system, and all the places Big M violated the published standard break everything.
Open standards aren't just a good idea, they are the ONLY WAY to make a system that everybody can play in.
Here we go again. (Score:2, Insightful)
IETF IP policy (Score:2, Interesting)
standards are also encumbered by patents. See http://www.ietf.org/ipr [ietf.org]
Some patent holder grant the rough equivalent of
RF licenses, others RAND licenses. Only the latter
is a requirement according to RFC 2026.
One interesting difference, however, is that one
needs at least two independent, interoperable
implementations, both of which have to have exercised the licensing policy, to advance a document from Proposed to Draft Standard stage.
(For reasons unrelated to IPR issues, most recent
IETF RFCs are Proposed Standards, not Draft
Standards.)
My response .... (Score:2, Insightful)
For example, GIF should not be a recognized standard, because of the encumbrances by Unisys. The PNG standard is a much better choice because it does not base itself on one company's technology and can be adopted by all. The software used to create a patent can be trademarked, copyrighted, etc., in the author's mannter of choosing, but it does not restrict the file format itself. The PNG format will never undergo the kinds of hassles various authors of GIF-related programs due to Unisys entanglements.
A consequence of recognizing patented technology is that the W3C runs a severe risk of appearing biased in favor of one company's standard. This will open the W3C up to lawsuits by those whose technologies failed to make the standard. Even the argument of technological superiority would not hold up in court because there is no way to empirically prove that one technology is better than another for all applications.
Thank you,
signature follows, etc. etc.
Keep the comments to the W3C coming gang! (Score:2)
Remember:
1) Keep the stuff to clean, coherent comments- no flames or ranting. They won't listen to either.
2) Focus on the issue that any royalty structure is, by it's very nature discrimintory, and that they contradict themselves in the proposal several times.
3) Focus on the issue that a substantial part of the Internet is powered by open source software that will be unable to pursue implementing things because of the licensing issues.
4) Remind them that they exist for the purposes of ensuring that the WWW doesn't become balkanized- which this would do.
5) Spell-check things if at all possible- there's some embarassingly mis-spelled stuff sent in by some important figures.
Fundamental problems of the draft (Score:2, Interesting)
For example, errors in the definition of an Essential Claim leave many, many loopholes. An example: If some patented technology is included in the later stage of a Recommendation, a patent owner can, in full compliance with the W3C procedures, obtain a patent without the need to disclose it. And that's not the only error. Basically, the patent holder decides which patents to reveal and which to hold back, and W3C cannot do anything about it. This makes most of the draft meaningless.
My submission was wirtten hastily, so it's probably full of typos,strange thoughts and lack of facts, but if you are interested nevertheless, it's available at: http://www.s.netic.de/fw/w3c-patent-policy-2001-09 -30.pdf [netic.de]
Even current standards are not safe! (Score:4, Interesting)
Section 5.3 of the policy provides for the possibility of re-chartering an existing Working Group under a new Licensing Mode (i.e., given that no-one would have an incentive to change it the other way, re-chartering an RF Working Group as a RAND Working Group.)
The Patent Advisory Group (the drafters of the new policy) can initiate this process and (albeit after approval from the Director), all the members get thrown out and have to be re-nominated, and *licensing commitments made by Working Group members under the older charter are void.*
In other words, if the e.g. CSS Working Group were dissolved and reconsituted in this way, companies could start charging licensing fees for the patents they hold on current CSS standards - either under RAND, or (worse) by withdrawing from the process completely and licensing under discriminatory terms.
Who has CSS patents, and who would they like to discriminate against?
Gerv
A new and improved W3C: W4SG (Score:2)
HTML 3.0 and MathML are but two examples of how the corporate nature of the W3C has led to the delay and/or abandonment of sound technical proposals.
If you are interested in charting a new path for the web join the World Wide Web Standards Group (W4SG) [uwaterloo.ca].
Why the short notice? (Score:3, Insightful)
That said, I believe we should raise bloody hell. We can't afford to have the standards for the Web become closed and proprietary. I know of no way patents can be enforced without also closing the source of implementations. This is absolutely unacceptable. It is also unacceptable that basic software technology is owned as "property".
Not a mandatory change (Score:1)