W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > July 2008

Re: XQuery WG comments on XProc specification

From: Alex Milowski <alex@milowski.org>
Date: Fri, 18 Jul 2008 07:09:41 -0700
Message-ID: <28d56ece0807180709x66d5fa56j7d4caf3bcf0a0043@mail.gmail.com>
To: public-xml-processing-model-comments@w3.org

On Thu, Jul 17, 2008 at 7:46 AM, Norman Walsh <ndw@nwalsh.com> wrote:
> / "Alex Milowski" <alex@milowski.org> was heard to say:
> | We had this discussion on one of our telcons quite awhile ago and
> | the WG was notably against allowing this. In fact, I originally
> | wrote the step to allow this and the consensus was it was a bad
> | idea.
> I think we're going to have to do something about the p:xquery step.
> The observation that XQuery documents don't have to be namespace well-formed
> is a show-stopper for our current solution, I think.

Right.  That is why c:query is a string element.  The Query *MUST* be escaped
even if it is well-formed XML.

> I can think of three workarounds that *I think* would work:
> Option 1: Use XInclude, we do nothing:
> <p:xinclude>
>  <p:input port="source">
>    <p:inline>
>      <c:query>
>        <xi:include href="document.xqy" parse="text"/>
>      </c:query>
>    </p:inline>
>  </p:input>
> </p:xinclude>

c:query is a string element.  The above doesn't work in the current
definition of c:query.

--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language

Bertrand Russell in a footnote of Principles of Mathematics
Received on Friday, 18 July 2008 14:10:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:25 UTC