[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
You're mixing up your layers here - you're muddling the immediate inputs and outputs with the ultimate inputs and outputs.
The stylesheet is assembled from one or more XML documents using xsl:import and xsl:include. These documents can ultimately come from anywhere, including external entities, XInclude, or arbitrary (say Java or C#) programs.
The inputs to the stylesheet are the principal input document, the values of stylesheet parameters, documents read using the document() function, and potentially the results of extension functions and extension instructions. Again these documents can come ultimately from anywhere, including external entities, XInclude, or arbitrary (say Java or C#) programs.
In XSLT 1.0 the only outputs of the stylesheet are the principal output document and the xsl:message output, plus any data supplied to extension functions or extension instructions.
On 09/08/2010 19:58, Costello, Roger L. wrote:
Re: [xsl] [XSLT 1.0] Avenues for content to enter and exit an XSLT transform?
Subject: Re: [xsl] [XSLT 1.0] Avenues for content to enter and exit an XSLT transform? From: Michael Kay <mike@xxxxxxxxxxxx> Date: Mon, 09 Aug 2010 23:24:49 +0100 |
You're mixing up your layers here - you're muddling the immediate inputs and outputs with the ultimate inputs and outputs.
The stylesheet is assembled from one or more XML documents using xsl:import and xsl:include. These documents can ultimately come from anywhere, including external entities, XInclude, or arbitrary (say Java or C#) programs.
The inputs to the stylesheet are the principal input document, the values of stylesheet parameters, documents read using the document() function, and potentially the results of extension functions and extension instructions. Again these documents can come ultimately from anywhere, including external entities, XInclude, or arbitrary (say Java or C#) programs.
In XSLT 1.0 the only outputs of the stylesheet are the principal output document and the xsl:message output, plus any data supplied to extension functions or extension instructions.
Michael Kay Saxonica
On 09/08/2010 19:58, Costello, Roger L. wrote:
Hi Folks,
There are several avenues for XML content to enter an XSLT transform:
1. The input XML document that is specified when the XSLT processor is invoked.
2. The XML obtained using the document() function.
3. The XML content obtained using the<xsl:input> and<xsl:include> elements.
4. The XML/text content obtained using external entities.
Are there any other avenues for content to enter an XSLT transform?
There are several avenues for content to exit an XSLT transform:
1. The output document that is specified when the XSLT processor is invoked.
2. The content that is output using extension functions, such as saxon:output and xalan:write.
Are there any other avenues for content to exit an XSLT transform?
/Roger
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] [Summary] Avenues for con, Dimitre Novatchev | Thread | [xsl] Trouble transforming special , Craig Whisenhunt |
[xsl] [Summary] Avenues for content, Costello, Roger L. | Date | Re: [xsl] [Summary] Avenues for con, Dimitre Novatchev |
Month |