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

[Bug 1609] New: two notations for function evaluation (= and =>)

From: <bugzilla@wiggum.w3.org>
Date: Fri, 15 Jul 2005 00:03:26 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DtDfq-0003nx-MO@wiggum.w3.org>

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

           Summary: two notations for function evaluation (= and =>)
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Formal Semantics
        AssignedTo: simeon@us.ibm.com
        ReportedBy: fred.zemke@oracle.com
         QAContact: public-qt-comments@w3.org


2.1.4 Notations for environments
The specification uses more than one notation to indicate the
evaluation of a static environment member that is a function.
See for example 3.1.1.1 "Resolving QNames to expanded QNames"
uner "Semantics" the first inference has the following judgment 
above the line:

statEnv.namespace(NCName) = URI-or-EmptyNamespace

This means that the statEnv.namespace member is a function.
When you evaluate this function for NCName, you get 
URI-or-EmptyNamespace.  Contrast this example with section 
7.1.9 "Type Expansion" second inference, second line:

statEnv.typeDefn(expanded-QName) => define type ...

Sometimes you use = and sometimes you use => for the same 
meaning, the result of evaluating a function that is a member
of an environment.
Received on Friday, 15 July 2005 00:03:28 UTC

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