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 20:54:33 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20639-523-gnKBaCteSW@http.www.w3.org/Bugs/Public/>

--- Comment #19 from dnovatchev@gmail.com ---
(In reply to comment #17)
> (In reply to comment #15)
> > At present, if we have a set of useful functions written in pure XPath, and
> > we want to use these both in XSLT and in XQuery
> !!! SNIP !!!
> > Providing modularity in XPath completely eliminates this problem and makes
> > both XSLT and XQuery more attractive to use.
> I do not yet understand why it is important to you that this be done in pure
> XPath, rather than in an XQuery that uses only features of XPath + modules.
> If XSLT could import and use XQuery libraries, then XSLT and XQuery could
> share libraries in the same way you envision here.

Yes, and although this may be technically possible, there are non-technical
reasons why such a feature wouldn't be too-popular:

A typical XQuery programmer:

    doesn't like too much XSLT
         ==> doesn't understand it too well 
                ==> won't be able to make maximum use of imported XSLT

A typical XSLT programmer:

    doesn't like too much XQuery 
         ==> doesn't understand it too well 
                ==> won't be able to make maximum use of imported XQuery

Both, an XQuery programmer and an XSLT programmer:

    like XPath
        ==> understand XPath well
              ==> are able to make maximum use of imported XPath functions

To put it in other words, one needs to learn another language to make full use
of the benefits of importing code from that language. This requires time and
investment, and there is no guarantee that many of us are that bi-lingual.

This problem simply doesn't exist when importing XPath.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 11 January 2013 20:54:35 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:51 UTC