[Bug 29146] [FO31] fn:transform options update

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29146

--- Comment #3 from Debbie Lockett <debbie@saxonica.com> ---
I propose separating the rules for combinations of options from the table of
meanings. This can also be done for the XSLT 1.0/2.0 case. Then most of the
meanings can stay the same for 2.0 and 3.0 (exceptions are delivery-format, and
source-node), while the rules are updated.

Rather than a list of rules (describing which options are mutually exclusive,
etc.), Mike suggested using some more visual presentation. The hope is that
this is also more useful for people actually using the function, when deciding
which options to use.

See the attached html for a suggested presentation using tables.

The list of XSLT 1.0/2.0 option meanings should be edited to remove any
combination rules (i.e. for stylesheet-location, source-node, initial-mode,
initial-template).

We are proposing that for XSLT 3.0, the option initial-match-selection is added
to replace the source-node option (i.e. source-node is no longer a valid option
for XSLT 3.0, initial-match-selection and/or global-context-item should be used
instead).

So updates for the list of XSLT 3.0 options are:

package-version - required type is xs:string not xs:decimal: Defaults to "*".

initial-match-selection - required type item()*: The initial match selection,
as defined in XSLT 3.0.


Note that in XSLT 3.0, for the Call Template invocation, the option
initial-template is no longer required, instead it has the default
xsl:initial-template.

(I’m not sure if it’s necessary to add a note (also relating to Abel’s point
9), that for the apply templates invocation, initial-mode defaults to #unnamed,
or the [xsl:]default-mode if specified in the stylesheet.)

Returning to Abel’s “final after thought” (about an alternative
“invocation-type” option), Mike suggested that rather than being required, a
new optional option could be added, which can be used to help make the
invocation method explicit. See the html.


Mike also noted that the following assumption should be added to the text: 
If the top level stylesheet or package invoked makes reference to other
stylesheet modules or packages via xsl:include/import/use-package then the way
these references are resolved is not under the control of this API (vendors may
add additional parameters to control this).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 28 October 2015 15:41:32 UTC