Tobias Reif wrote:
If they were paying, either for the specs or for the products, then they
might have more ability to influence the outcome...
If it's true that $s rules the development of the specs (XSLT etc) more
than anything else, then that's a very sad state of affairs IMHO.
Payment can be in items other that $s. A developer pays in effort to
develop or update an XSLT processor. If the spec is going to make upgrading
the processor too much effort, he has two choices: Not do it or send
feedback to the WG. There are more than enough ways to get feedback to the
WG; and I am fairly sure most, particularly those on this list, will not
ignore the comments simply because they are not from the $ paying members.
I've lost count of the number of times Michael Kay on this list has asked
people to provide him with use cases, etc. I have no idea how many did, but
I sure he wasn't asking just to be difficult.
The key is to not just say "It's too difficult;" but to say "I think this
section/point/feature is asking too much of developers and is likely to
prevent adoption of the new standard in new versions of XSLT processors."
Back it up with constructive critiques and the standard can actually be
affected; just screaming "I can't do that; I give up!" and the specs
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list