Re: serializing a forrest into the output (not to a file)

Hi

> Thanks for the comment. As you probably know, Saxon includes an extension
> function saxon:serialize which does essentially what you are describing.


Didn't know that ([1]), thanks for the tip, and for the implementation :)

(more below)

> I
> have a similar requirement when including the "schema for XSLT" in the HTML
> rendition of the XSLT 2.0 working draft. 
> 
> But my instinct is not to include this feature in the spec this time round.
> It's probably something that should go into EXSLT first, to see whether
> vendors and users find it attractive, before putting it in the core
> specification.


If you need, implemented, and use it, and if I need and will use it, 
then that's already some relevant evidence of its usefulness IMHO :)

I'm sure that others will find it useful too.

Already having it in Saxon, and hopefully seeing it in EXSLT would be OK 
for now (what do the EXSLT people on this list say?). Personally I 
believe that, as a basic and general mechanism, it belongs in the spec, 
but I can understand that you want to keep the spec small.

What do you think about the syntax?:

<programlisting>
   <xsl:serialize format="xml_snippets">
     <xsl:copy-of select="$snippet"/>
   </xsl:serialize>
</programlisting>

What do you think of (instead of adding xsl:serialize) changing the 
definition of xsl:result-document, to include something like

"If the href attribute is not present, the result of the serialization
is created in place, and not written to a file. This means it 
contributes one text node to the result of the content constructor it is 
part of."

?

TIA,
Tobi

[1]
http://saxon.sourceforge.net/saxon7.4/extensions.html#serialize


-- 
http://www.pinkjuice.com/

Received on Tuesday, 29 April 2003 06:56:35 UTC