Cart
[Home] [By Thread] [By Date] [Recent Entries]
> I have to agree with Dare here. Premature standardization with > little-to-no implementation experience has led to some really awful > standards, and a lot of the things being made into Official W3C > Recommendations don't really need to be standardized in the first > place, or at least not yet! > Freeing XSLT's evolution from the W3C process would allow more room > for experimentation and innovation. It would also provide an > opportunity to see which ideas are worth keeping and which can be > discarded, and then throwing the latter away! I agree on the principle as well. But it's been almost 4 years since XSLT 1.0, and there is a real need in the industry for a new version of XSLT. I would think that the XML community's experience with 1.0, EXSLT and other extensions would have been enough to get to a satisfying (W3C standard) XSLT 2.0 by now. Do I understand correctly that you are pointing your finger at the reliance of XSLT 2.0 on W3C Schema? Maybe W3C should require the development of a reference implementation for every spec. This is the way Sun's Java Community Process works. -Erik
|
