This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1643 - [FS] proposed wording fix for dynEnv.funcDefn
Summary: [FS] proposed wording fix for dynEnv.funcDefn
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows 2000
: P2 minor
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-15 22:10 UTC by Fred Zemke
Modified: 2007-01-16 17:30 UTC (History)
0 users

See Also:


Attachments

Description Fred Zemke 2005-07-15 22:10:30 UTC
3.1.2 Dynamic context
Under dynEnv.funcDefn, the second para ends with "...
the function's body and a
list of variables, which are the function's formal parameters,
of the form "(Expr, Variable1, ,..., Variablen)"."  
As currently worded, it seems that "the function's body"
is one item, and "a list of variables, which are the function's
formal parameters, of the form (Expr, Variable1, ...., Variablen)"
is another item.  In parsing termsinology, the question is the 
precedence of "and" and "which" in the quoted sentence.  
This can be fixed
as follows: "...if the function is locally declared, the 
function definition is a tuple (Expr, Variable1, ... Variablen),
where Expr is the function body and Variable1 through Variablen
are the function's formal parameters."
Comment 1 Jerome Simeon 2005-07-19 17:20:03 UTC
I believe this is editorial.
- Jerome
Comment 2 Jerome Simeon 2006-04-15 23:08:21 UTC
Adopted the proposed rewording, with some minor editing.
- Jerome