> Impact on function definitions
> ------------------------------
>
> Adding the xsl:item element allows us to get rid of the xsl:result
> element when defining functions. The xsl:function element's new syntax
> would be:
>
> <xsl:function
>   name = qname>
>   <!-- Content: (xsl:param*, sequence-constructor) -->
> </xsl:function>
>
> The xsl:function element would simply return the sequence produced by
> its content constructor.
> 
> For example:
> 
>   <xsl:function name="my:split-string">
>     <xsl:param name="string" type="xs:string" />
>     <xsl:param name="keyword" type="xs:string" />
>     <xsl:if test="$string and $keyword">
>       <xsl:variable name="before"
>                     select="substring-before($string, $keyword)" />
>       <xsl:variable name="after"
>                     select="substring-after($string, $keyword)" />
>       <xsl:item select="if (not($before) or ends-with($before, ' ')) and
>                            (not($after) or starts-with($after, ' '))
>                         then ($before, $keyword, $after)
>                         else $string" />
>     </xsl:if>
>   </xsl:result>

Syntax error: "</xsl:result>" no matching "<xsl:result>"... (should be
</xsl:function>)



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list