- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Mon, 19 Mar 2007 13:32:45 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <87r6rl16ma.fsf@nwalsh.com>
The xinclude-from-sequence[1] component offers one solution for a special case of a general problem. In the absence of that component, is the following pipeline legal? If not, what constraint in the specification[2] does it violate? If it is, what does it produce? Are all implementations required to produce the same result? If not, why not? <p:pipeline xmlns:p="http://www.w3.org/2007/03/xproc" xmlns:xi="http://www.w3.org/2001/XInclude"> <p:output port="result"/> <p:xslt2> <p:input port="source"> <p:inline> <doc/> </p:inline> </p:input> <p:input port="stylesheet"> <p:inline> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs" version="2.0"> <xsl:output method="xml"/> <xsl:template match="/"> <xsl:result-document href="http://some-imaginary-dns-name.tld/document"> <chapter> <title>Chapter Title</title> <para>Some paragraph.</para> </chapter> </xsl:result-document> </xsl:template> </xsl:stylesheet> </p:inline> </p:input> </p:xslt2> <p:xinclude> <p:input port="source"> <p:inline> <document> <title>Document Title</title> <xi:include href="http://some-imaginary-dns-name.tld/document"/> </document> </p:inline> </p:input> </p:xinclude> </p:pipeline> Be seeing you, norm [1] http://www.w3.org/XML/XProc/docs/langspec.html#c.xinclude-from-sequence [2] http://www.w3.org/XML/XProc/docs/langspec.html -- Norman Walsh XML Standards Architect Sun Microsystems, Inc.
Received on Monday, 19 March 2007 17:34:33 UTC