- From: Norman Walsh <ndw@nwalsh.com>
- Date: Mon, 30 Apr 2007 19:48:36 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <87ps5lfmp7.fsf@nwalsh.com>
/ Innovimax SARL <innovimax@gmail.com> was heard to say:
| You're absolutely right for p:delete, but what about p:replace ?
I'm just as confused about p:replace. Consider:
<p:pipeline name="pipeline" xmlns:p="http://www.w3.org/2007/03/xproc">
<p:output port="result"/>
<p:replace>
<p:input port="source">
<p:inline>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:output method="xml" encoding="utf-8" indent="no"
omit-xml-declaration="yes"/>
<xsl:preserve-space elements="*"/>
<xsl:template match="*">
<xsl:copy>
<xsl:copy-of select="@*"/>
<xsl:apply-templates/>
</xsl:copy>
</xsl:template>
<xsl:template match="comment()|processing-instruction()|text()">
<xsl:copy/>
</xsl:template>
</xsl:stylesheet>
</p:inline>
</p:input>
<p:input port="replacement">
<p:inline>
<this-was-an-xsl-template/>
</p:inline>
</p:input>
<p:option name="target" value="xsl:template"/>
</p:replace>
</p:pipeline>
What would the "other" output result of this replace step be?
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | A man can believe a considerable deal
http://nwalsh.com/ | of rubbish, and yet go about his daily
| work in a rational and cheerful
| manner.--Norman Douglas
Received on Monday, 30 April 2007 23:48:52 UTC