W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2008

[Bug 5647] [XQuery] Default collection

From: <bugzilla@farnsworth.w3.org>
Date: Sat, 19 Apr 2008 04:30:10 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Jn4iI-0006te-DX@farnsworth.w3.org>


           Summary: [XQuery] Default collection
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Platform: PC
               URL: http://www.w3.org/TR/xquery/
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery
        AssignedTo: chamberl@almaden.ibm.com
        ReportedBy: mukul_gandhi@yahoo.com
         QAContact: public-qt-comments@w3.org

In the XQuery 1.0 specification, at http://www.w3.org/TR/xquery/

It's mentioned in section: "2.1.1 Static Context", the following point:

Statically known default collection type. This is the type of the sequence of
nodes that would result from calling the fn:collection function with no
arguments. Unless initialized to some other value by an implementation, the
value of statically known default collection type is node()*.

Then in section, "2.4.4 Input Sources", it's mentioned:
The fn:collection function with zero arguments returns the default collection,
an implementation-dependent sequence of nodes.

My question is:
What practical criterias can implementation consider, when returning non-null
values from fn:collection function?

Should we not have simply said, nothing is returned (or, void) when
fn:collection function is called with no arguments?

Received on Saturday, 19 April 2008 04:30:44 UTC

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