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

Re: Parameters, Manifests, and Use Case 5.6

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Fri, 13 Oct 2006 17:27:17 +0100
Message-ID: <452FBE65.3060207@orbeon.com>
To: public-xml-processing-model-wg@w3.org

Norman Walsh wrote:
> / Alex Milowski <alex@milowski.org> was heard to say:
> | This use case is easily solved by use of xinclude:
> 
> I don't think this qualifies as "easily" in the sense that ordinary
> mortals understand that word. More specifically, I don't think
> you've got a complete solution yet.
> 
> | <p:pipeline>
> |    <p:declare-input port="manifest" />
> |    <p:declare-output port="results" sequence="yes"
> |                      step="load-documents" source="result" />
> |
> |    <p:for-each name="load-documents">
> |      <p:declare-input port="file-ref"
> |                       source="manifest"
> |                       select="/files/file" />
> |      <p:declare-output port="result"
> |                        step="load-document" source="result" />
> |
> |      <!-- make an xinclude from the href -->
> |      <p:step name="make-xinclude" type="p:xslt">
> |         <p:input name="document" step="load-documents" port="file-ref"/>
> |         <p:input name="transform">
> |            <xsl:transform version="1.0">
> |               <xsl:template match="file">
> |                  <x:include href="{@href}"/>
> 
> How have you controled when x:include (assuming you meant x: to be
> assigned to the XInclude namespace) will be expanded? I'd expect the
> Pipeline processor to expand it, causing a resource failure because
> "{@href}" isn't a valid URI.
> 
> Assuming you load your pipeline with XInclude turned off, the same
> problem arises for your XSLT processor.

Agreed, and it's more than a theoretical scenario: in the OPS platform, 
when XPL pipelines are used for producing "web pages", they first go 
through XInclude processing prior to their execution (in other cases 
this doesn't happen). When they use XInclude to actually perform 
inclusions within pipelines things works just fine. When they do it to 
try to implement what AM says above and it doesn't work, they are 
obviously confused ;-)

This said, didn't we have the task to work in XInclude processing as well?

-Erik

-- 
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/
Received on Friday, 13 October 2006 16:27:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:49 GMT