- From: Jeni Tennison <jeni@jenitennison.com>
- Date: Wed, 17 May 2006 21:54:17 +0100
- To: public-xml-processing-model-wg@w3.org
Hi, > In short: > > 1. I think allowing a choice is unacceptably risky. > 2. I think requiring XPath 2 is unnecessary. > 3. Anyone anxious to use XPath 2 can do so even if we don't provide > it in V1.0 of the language: authors can use the XSLT 2.0 component > and implementors can provide custom components. > > Let's choose XPath 1.0 for expressions in the core language. I'm mostly persuaded, mostly because XPath 2.0 will be accessible through the XSLT 2.0 component anyway. My only reservation is that if we choose XPath 1.0 now, but want 2.0 later, we will have to handle all the interoperability issues then. If we went for 2.0 (and no choice) now then we wouldn't have to worry about XPath version interoperability for a long long time. Cheers, Jeni -- Jeni Tennison http://www.jenitennison.com
Received on Wednesday, 17 May 2006 20:54:28 UTC