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

[Bug 29791] New: [XP31] Non-deterministic with respect to ordering

From: <bugzilla@jessica.w3.org>
Date: Wed, 24 Aug 2016 09:58:10 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29791-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29791

            Bug ID: 29791
           Summary: [XP31] Non-deterministic with respect to ordering
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

(This bug is probably only editorial)

Under 1.7.4 Properties of functions, we state:

<quote>
All functions defined in this specification are ·deterministic· unless
otherwise stated. Exceptions include the following:

* Some functions (such as fn:distinct-values and fn:unordered) produce results
in an ·implementation-defined· or ·implementation-dependent· order. In such
cases there is no guarantee that the order of results from different calls will
be the same. These functions are said to be non-deterministic with respect to
ordering.
<quote>

I find a few issues with this:

1) neither fn:distinct-values nor fn:unordered have a mention in the body of
their resp. entries that they are non-deterministic with respect to ordering

2) the functions map:keys and map:for-each have a mention in the body of their
entries, but the line explaining the effect is slightly different with the
definition above: "two calls with the same argument are not guaranteed to
produce the results in the same order." versus "no guarantee that the order of
results from different calls will be the same.".

I propose the to bring the sentence in 1.7.4 in line with this, i.e., make it
"no guarantee that the order of results from different calls with the same
arguments will be the same."

3) none of fn:distinct-values, fn:unordered, map:for-each and map:keys are
marked "non-deterministic" under their resp. properties. I think they should
be.

----
I'm not 100% sure that these four functions is an exhaustive list of the
non-deterministic wrt ordering functions. For instance, should
fn:in-scope-prefixes be in here?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 24 August 2016 09:58:18 UTC

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