W3C home > Mailing lists > Public > public-xsl-wg@w3.org > April 2016

Raw result, or Bug 29431 - [XSLT30] item-separator applicability

From: Abel Braaksma <abel.braaksma@xs4all.nl>
Date: Fri, 1 Apr 2016 14:18:26 +0200
To: "Public XSLWG" <public-xsl-wg@w3.org>
Message-ID: <01a901d18c10$9bbb3e00$d331ba00$@xs4all.nl>
There are a few things that have come to my mind that have not been discussed while we were going over Bug 29431 - [XSLT30] item-separator applicability.

These are assumptions based on discussion and/or my understanding, are they correct?

1) Raw Result is the "typical result" for invoking a transformation by function (I think), as serialization is an API matter in that case (which does not exclude the possibility of serialization)

2) Raw Result only ever raises a conversion error (if the result type cannot be created) for the principal result

3) Raw Result never raises in error with xsl:result-document (because there is no type)

4) xsl:result-document does *not* create a document node per se

5) xsl:result-document may create a sequence of non-serializable items, i.e. maps, if build-tree=no, in which case serialization is not applied, but getting this result is an API matter

6) the default for item-separator is "absent" which is not the same as "empty" (i.e., absent may mean a default space is introduced, empty means no space is introduced).

I think most of these, or all, are already somewhere in the spec. Though they may be unclear to a casual reader (which is not our target audience). Whether or not some of these should be made explicit through Notes or Examples I do not know.

Received on Friday, 1 April 2016 12:19:01 UTC

This archive was generated by hypermail 2.3.1 : Friday, 1 April 2016 12:19:02 UTC