- From: <bugzilla@jessica.w3.org>
- Date: Fri, 11 Jan 2013 18:32:18 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20639 --- Comment #11 from dnovatchev@gmail.com --- (In reply to comment #7) > (In reply to comment #5) > > > Roger's use case is compelling and it comes at the right time to be > > considered for XPath 3.1. > > > > I fully support this use-case and recommend to the w3c-xsl-xquery working > > group to include XPath modularity support in XPath 3.1. > > Considering this for XPath 3.1 is more appropriate than adding it as a > requirement to XPath 3.0. > > If you want function libraries to XPath, though, why not just use XQuery? Yes, I recommend that, based on Roger's use-case, support for modularity is included in XPath 3.1. And to answer the question on the last quoted line: There are some people that don't want to be bound XQuery or XSLT and prefer to have XPath programs that can be immediately executed either standalone, or as part of an XQuery program or (trivially included) as part of an XSLT program. Creating XPath programs eliminates the "portability problem" between XQuery and XSLT. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 11 January 2013 18:32:20 UTC