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

[Bug 1576] New: [FS] technical: 4.1.5 Function Calls: AtomizeAtomic

From: <bugzilla@wiggum.w3.org>
Date: Thu, 14 Jul 2005 04:05:32 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Dsuya-0002RV-B8@wiggum.w3.org>


           Summary: [FS] technical: 4.1.5 Function Calls: AtomizeAtomic
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Formal Semantics
        AssignedTo: simeon@us.ibm.com
        ReportedBy: jmdyck@ibiblio.org
         QAContact: public-qt-comments@w3.org

4.1.5 Function Calls
"and Expr : Type and not(Type=empty)"
    I'm not clear on the need for these conditions. They restrict the
    catchment of the first (fn:data) alternative to expressions with a
    non-empty type; if you dropped these conditions, the only effect would
    be to move untypeable and empty-type expressions from the second to
    the first alternative. But untypeable expressions will raise an error
    in STA under either alternative, and empty-type expressions will yield
    the empty sequence under either alternative. [fn:data(()) == ()]
    So it seems to me that dropping the conditions would simplify the spec
    without changing the semantics.
Received on Thursday, 14 July 2005 04:05:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC