W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2005

[Bug 1897] [XSLT2.0] cardinalities of unparsed-text-available function

From: <bugzilla@wiggum.w3.org>
Date: Wed, 28 Sep 2005 14:17:40 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1EKcke-0005ht-0K@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1897


mike@saxonica.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From mike@saxonica.com  2005-09-28 14:17 -------
The XSL WG agreed with my amended proposal, which now is in three parts:

(a) to align with doc-available(), the first argument of
unparsed-text-available() will accept an empty sequence, and will return false
in this case.

(b) we normally adopt a principle that where a value is optional, then it ought
to be possible to specify an explicit value whose effect is equivalent to
defaulting it. Applying this principle, I propose that if the second argumnent
of unparsed-text-available() is an empty sequence, the effect should be the same
as calling the one-argument version of the function. [There are
counter-examples. We don't allow an empty sequence as the third argument of
substring(), for example. However, it's not a big issue either way, and this
seems a reasonable approach.]

(c) change the summary of the function to read:

The unparsed-text-available function determines whether a call on the
unparsed-text function with identical arguments would return a string.

We are therefore marking the issue as FIXED/CLOSED. If you have any problems
with this resolution, please reopen the bug.

Michael Kay
for the XSL Working Group
Received on Wednesday, 28 September 2005 14:18:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:08 UTC