W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > April 2007

Re: standard components edits

From: Alex Milowski <alex@milowski.org>
Date: Mon, 16 Apr 2007 07:21:57 -0700
Message-ID: <28d56ece0704160721g4f998ea6vae4867bec6b1876a@mail.gmail.com>
To: public-xml-processing-model-wg@w3.org
On 4/16/07, Henry S. Thompson <ht@inf.ed.ac.uk> wrote:
> I strongly agree -- no special-casing for N3 or Relax-NG or XQuery or . .
> .
> I note that we can get an arbitrary text document into a pipe with a
> trivial wrapper element as follows
> <p:xinclude>
>   <p:input port="source">
>    <p:inline>
>     <wrapper>
>      <xi:include href="[your doc URI here]" parse="text"/>
>     </wrapper>
>    </p:inline>
>   </p:input>
> </p:xinclude>

Nice.  That trick gets written down! :)

Should we provide a micro-component for this case, e.g.
> <p:wrapped-text href="[anyURI]" wrapper="[QName]"/>
> ?

Since you can do this with xinclude, I think this is  OK to leave alone.

We could then say that compact syntax for RelaxNG or XQuery query docs
> must be wrapped in specified elements, and then their secondary inputs
> are to a limited extent polymorphic, distinguished by their document
> elements, as between full/compact for Relax-NG and XQueryX/text for
> XQuery.

Right now we're defining a step-vocabulary element for XQuery.  I think we
could define an extra step vocabulary element for text wrappers and
then steps like relax can use that.

Unfortunately, XQuery isn't all text but may not have a document element
(e.g. the "declare namepace f="...";" in the prolog).  As such, that element
needs to be different.

--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 Monday, 16 April 2007 14:22:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:42 UTC