Re: XSLT version

/ Jeni Tennison <jeni@jenitennison.com> was heard to say:
| Norman Walsh wrote:
|> Suppose instead we say that there's a single, required p:xslt step and
|> an implementation may implement XSLT 1.0 or XSLT 2.0 (or both) at its
|> option.
|>
|> Here's the proposed signature:
|>
|> <p:declare-step type="p:xslt">
|>      <p:input port="source" sequence="true" primary="true"/>
|>      <p:input port="stylesheet"/>
|>      <p:input port="parameters" kind="parameter" sequence="true"/>
|>      <p:output port="result" primary="true"/>
|>      <p:output port="secondary" sequence="true"/>
|>      <p:option name="initial-mode"/>
|>      <p:option name="template-name"/>
|>      <p:option name="output-base-uri"/>
|>      <p:option name="version"/>
|> </p:declare-step>
|
| What's the 'version' option do?

If the pipeline author specifies a version and the pipeline engine
doesn't support that version, it throws a dynamic error.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | The function of the imagination is not
http://nwalsh.com/            | to make strange things settled, so much
                              | as it is to make settled things
                              | strange.--G. K. Chesterton