On Wed, Aug 20, 2014 at 1:25 PM, Michael Kay mike(_at_)saxonica(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
We're keeping our options open. It's very hard to predict how long a spec
will take to get through the final hurdles. At present neither spec is
dependent on the other, and we're planning to keep it that way if we can.
We've also put clauses into XSLT 3.0 that say you can use it with a version
of XPath that comes out after XSLT 3.0 is published.
Doesn't this allow for misalignment between the two Specs that could
lead to having two different versions and implementations of Maps?
Will we need to be aware of "XSLT maps" vs. "XPath maps" and study
these separately?
Will anything make it obligatory for an implementor of XSLT 3.0 to
replace the XSLT maps with XPath maps at a future date, when XPath 3.1
becomes a recommendation?
Here is what I believe would be a good solution:
I. In case XPath 3.1 becomes Recommendation before XSLT 3.0, then XSLT
3.0 will remove the chapter on Maps and refer to XPath 3.1
2. In case XPath 3.1 becomes Recommendation after XSLT 3.0, then a
3.1 version of XSLT will be published (or just a note maybe), that
will invalidate/remove the Maps chapter from the specification.
Is this realistic at all, or is it just wishful thinking?
Cheers,
Dimitre Novatchev
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--