saxon6:output
The saxon6:output
element (in namespace xmlns:saxon="http://icl.com/saxon"
) is a synonym
for xsl:result-document, provided to enable
the popular DocBook 1.0 stylesheets to run using Saxon-PE/EE 9.9 and later.
Category: instruction
Content:
sequence-constructor
Permitted parent elements:
any XSLT element whose content model is
sequence-constructor; any literal result element
Attributes
|
|
If present, it gives the name of an xsl:output element that describes
the serialization format for this output document; if absent, the unnamed
|
|
|
The URI for the result document. If this is a relative URI, it is interpreted
relative to the base output URI. The base output URI is the systemID of the
result object supplied as the destination for the transformation, or if you
are using the command line, the value of the If the base output URI is not known, and the supplied This base output URI must be a writable location. Usually it will therefore be a URI that uses the "file:" scheme. However, Saxon attempts to open a connection whatever URI scheme is used, and it should therefore work with any URI where the Java VM has the capability to open a writable connection. Users have reported success in using "ftp:" and "mailto:" URIs. If the configuration option Feature.ALLOW_EXTERNAL_FUNCTIONS
is set, then for security reasons use of the
|
|
|
Requires Saxon-PE or Saxon-EE. |
|
|
Determines what happens to any type annotations on element or attribute nodes. Requires Saxon-PE or Saxon-EE. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Not available in XSLT. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
New in XSLT 3.0. Not implemented in Saxon 9.7. Allows serialization to be configured in an external document. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Serialization attribute, see Details for more information. |
|
|
Overrides the |
|
|
The default
for Saxon-EE is |
Details
The instruction is a synonym for xsl:result-document. Historically, support for multiple
output documents was first introduced as a Saxon extension to XSLT 1.0 in the form of the saxon:output
instruction. Other vendors followed suit, and the idea was eventually standardized in XSLT 2.0 under the
name xsl:result-document
. The DocBook 1.0 stylesheets, however, remain in widespread use, and include
calls on saxon:output
. It is
often difficult for users to move forwards because they have written their own DocBook customization layers; as a result,
many users have been locked into Saxon 6.5.5 which is now obsolete and no longer maintained.
Saxon 9.9 reintroduces saxon6:output
(in the original Saxon 6.5.5 namespace, which differs from
the usual Saxon namespace, so here we use a different prefix) so that the
DocBook 1.0 stylesheets can now be executed with a modern Saxon release. Note that the specification is
not identical with the Saxon 6.5.5 original, but it serves the purpose in supporting DocBook. The main difference
is that in Saxon 6.5.5, the attribute saxon:output/@href
was interpreted as a filename (not a URI)
relative to the current working directory.