W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2016

[Bug 29692] xsl:strip-space and packages

From: <bugzilla@jessica.w3.org>
Date: Sun, 12 Jun 2016 11:48:46 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29692-523-pqhUElfPik@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29692

--- Comment #4 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
On (a), (b) and (c), I think we say it all in this paragraph under 4.5:

"Formally, the stripping process modifies the mapping from URIs to document
nodes defined in the XPath dynamic context. This mapping can therefore vary
from one package to another. The mapping that applies to a particular call on
document, docFO30, or collectionFO30, or a particular evaluation of xsl:stream,
is affected by the xsl:strip-space and xsl:preserve-space declarations within
the package in which that construct appears. This means that two calls on the
docFO30 function (for example) may return different nodes if the calls appear
in different packages."

Here we mention that
1) the mapping is per package
2) it applies to doc, document, collection, xsl:stream
3) that you may get back different nodes from the same URI in different pkgs

This leaves (d) (dynamic calls to fn:doc etc). But I think that follows from
this definition: it depends on in what package the dynamic call takes place (if
we have such a notion).

And the edge case (text node only), we say in 4.5:

"The stripping process takes as input a set of element names whose child
whitespace text nodes are to be preserved."

Note an editorial typo here: last words should be "are to be stripped".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 12 June 2016 11:48:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:00 UTC