Liam R E Quin wrote:
Hi,
Since then, the XML Processing Model Working Group (XProc)'s
pipelining language has some support for HTTP, and I think may
offer a better answer.
Actually, I rewrote the design of the HTTP Client in the early
days to match the design of p:http-request (the structure of the
elements, the names of the elements and attributes, etc.) So at
the end of the day, it provides the functionality of the standard
XProc step back to all XPath-based languages.
But yes, let's talk in Prague about it - it's actually one of
the topics for my session too: should we (W3C) do more work
*around* the current scope of XSLT and XQuery, e.g. fitting
XProc and XSLT and Query together more tightly
I think the main problem here is that XProc is not based on
XDM. If it was not that far in the standardization process, I
guess there would be enough voices to change that, but that's not
an option anymore, sadly. I am sure that is going to cause some
pain in the next few years...
or maybe enough of a Web framework that people can use these
languages as back ends for Web apps directly. There seems to
be quite a bit of interest in such things.
That's one of the two main topics of my presentation. My new
website http://h2oconsulting.be/ is based on an experimental
implementation of the EXPath Webapp module (still in draft stage,
that's a kind of servlet container) for instance. But shush,
more in XML Prague ;-)
Regards,
--
Florent Georges
http://www.fgeorges.org/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--