[Home] [By Thread] [By Date] [Recent Entries]
At 12:36 PM 7/17/2006, Mike wrote:
> It feels kind of risky to use a standard that hasn't even > been finalized by the w3c yet... And perhaps because in their case the payoff is large enough to cover the down side, when and if it ever happens. Some operations need to consider longer time horizons, perhaps do not have technical staff time to devote to learning and maintaining a leading-edge technology (in their lights, an unproven one) on narrow margins, etc. Or maybe their transformation requirements are more than adequately served already. Many factors are involved. "If you need to upgrade your tools and you haven't, you're already paying for them." The flip side is that if you don't and you do, you're also paying extra. I'm using XSLT 2.0 myself, and so are some people and operations I know. But by no means is it (yet) for everyone. Becoming a Rec and seeing more implementations will certainly help. It's a process of cultural/marketplace bootstrapping, and as such, fascinating to observe as well as take part in. Cheers, Wendell
|

Cart



