W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2013

[Bug 20639] XPath provides insufficient "glue" (modularity)

From: <bugzilla@jessica.w3.org>
Date: Fri, 11 Jan 2013 18:18:30 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20639-523-QYuMWVtNTd@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20639

--- Comment #9 from dnovatchev@gmail.com ---
(In reply to comment #8)
> If you completed this job and made XPath a functionally complete programming
> language, how would it differ from XQuery?

I believe that this language would be lighter and much simpler. It will
eliminate the "portability problem" between XQuery and XSLT. Even only this
fact will make it popular and preferred.

XPath is not a competitor to either XQuery or XSLT -- it is a common subset of
both. A XPath program is by definition a standalone program, an XQuery program
and trivially makes an XSLT program.

Any organization that uses both XSLT and XQuery would prefer the "write once"
capability of XPath and this directly translates into significant money
savings.

To an organization that hasn't yet started using either XSLT or XQuery, XPath
can be a good "starter" to either of these languages. Even before having made a
decision which of XQuery/XSLT to use, they will know that all their XPath
programs will be immediately running as part of either of these two languages.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 11 January 2013 18:18:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 11 January 2013 18:18:32 GMT