- From: Norman Walsh <ndw@nwalsh.com>
- Date: Thu, 12 Aug 2010 15:44:33 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <m27hjvehum.fsf@nwalsh.com>
"Henry S. Thompson" <ht@inf.ed.ac.uk> writes:
> <p:template match="...">
> [XML goes here, with {} interpreted in both attr vals and text content,
> and something like <c:copy select="..."/> recognised]
> </p:template>
This is a totally different kind of thing. It's not an atomic or
compound step, it's more a sort of macro. That feels...tricky.
I'm a little confused about the match part and c:copy.
The match makes me think it's sort of mapped into XSLT somehow. The
c:copy makes me think that it somehow reimplements part of XSLT's
instruction set.
I wonder if p:interpolated-inline would get the job done?
<p:identity>
<p:input port="source">
<p:interpolated-inline>
<document xml:base="{$computed-base-uri}">
{ $elem }
</document>
</p:interpolated-inline>
</p:input>
</p:identity>
And doens't "{ $elem }" in there make you wish we had variables
that could contain items and not just strings :-P
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | What is familiar is what we are used
http://nwalsh.com/ | to; and what we are used to is most
| difficult to 'Know'--that is, to see as
| a problem; that is, to see as strange,
| as distant, as 'outside us'.-- Nietzsche
Received on Thursday, 12 August 2010 19:45:09 UTC