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 3882 - [FS] editorial: 4.1.5 Function Calls / Normalization
Summary: [FS] editorial: 4.1.5 Function Calls / Normalization
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Candidate Recommendation
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Michael Dyck
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-29 10:37 UTC by Michael Dyck
Modified: 2008-08-31 00:59 UTC (History)
0 users

See Also:


Attachments

Description Michael Dyck 2006-10-29 10:37:33 UTC
4.1.5 Function Calls

Norm

"Each argument expression in a function call is normalized to its
corresponding Core expression by applying []_FunctionArgument(Type)
for each argument with the expected SequenceType for the argument
inserted."
    Delete "for each argument"; it's redundant.
    s/SequenceType/Type/
    Change "with the expected SequenceType for the argument inserted"
    to "where Type is the corresponding parameter type".

Norm / rule 1 / conclusion
    The '==' and the following line are leftovers. Delete them.

"Note that this normalization rule depends on the function signatures,
which is used to get the types of the function parameters
(SequenceType1,...,SequenceTypen)"
    s/signatures/signature (found in statEnv.funcType)/
    s/SequenceType/Type/g

"For user-defined functions, the function signature can be obtained from
the XQuery prolog where the function is declared. For built-in functions,
the signature is given in the [Functions and Operators] document."
    No, the signatures can be obtained from the static environment
    (specifically, statEnv.funcType). They are *derived* from declarations
    that appear elsewhere, which is maybe what you meant.

"For overloaded built-in functions, several signatures may exists,
however, because they all correspond to sequences of atomic values, they
all result in the same normalization."
    This sentence is irrelevant/meaningless, because calls to overloaded
    built-in functions cannot occur in non-Core queries, and thus are not
    subject to the preceding normalization rule.
    (It's a leftover, delete it.)
Comment 1 Jim Melton 2007-02-26 00:20:22 UTC
The fix for this bug does not appear in the Recommendation of 23 January 2007. 
It will be considered for a future publication (either an Errata document or
some possible future version of the specification). 
Comment 2 Michael Dyck 2008-08-31 00:58:52 UTC
This issue has been entered as FS erratum E047, and the fix has been
committed to the source files for the next edition of the FS document.
Consequently, I'm marking this issue resolved-FIXED, and CLOSED.