- From: James Fuller <james.fuller.2007@gmail.com>
- Date: Sun, 7 Oct 2007 08:39:30 +0200
- To: mozer <xmlizer@gmail.com>
- Cc: public-xml-processing-model-comments@w3.org
On 10/7/07, mozer <xmlizer@gmail.com> wrote: > On 10/6/07, James Fuller <james.fuller.2007@gmail.com> wrote: > > > > test-suite sparked my mind on what effects xinclude may have during > > processing of an XProc document. > > > > There maybe times when you would want to give the pipeline author a > > chance to specifically disallow xinclude processing (and have > > implementator handle this)...perhaps a flag on pipeline? > > Are you asking for a way to do that ? no, I am asking what happens when an xml parser has xinclude processing enabled and xproc processes (this question has nothing to do with xinclude step). there are some subtle interactions when one uses xinclude directly inside of xproc document. ta, Jim Fuller > <p:choose> > <p:when test="$how = 'automatic'"> > <p:xinclude/> > </p:when> > <p:otherwise> > <p:viewport match="xi:include"> > <!--... --> > </p:viewport> > </p:otherwise> > </p:choose> > > > > > > > also, thinking about the knock on effects of using xinclude within > > p:inline elements. > > That's not possible > > > > Xmlizer >
Received on Sunday, 7 October 2007 06:39:38 UTC