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 3881 - [FS] editorial: 4.1.5 Function Calls / Notation
Summary: [FS] editorial: 4.1.5 Function Calls / Notation
Status: ASSIGNED
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:33 UTC by Michael Dyck
Modified: 2007-11-04 06:00 UTC (History)
0 users

See Also:

Attachments

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

Notation

(two blurbs on fs:convert-simple-operand and PrototypicalValue)
    It seems like these two blurbs are saying mostly the same thing.
    Perhaps they could be merged.

    Maybe change "PrototypicalValue" to "PrototypicalValueForType".

"Also, note that in the case of built-in functions where the expected
type is specified as numeric, the prototypical value is a value of type
xs:double."
    This shouldn't be in a mere Note. Also, you first have
    to say that when the expected type is specified as numeric,
    Type <: xs:anyAtomicType* is deemed to be true.

    Actually, you could cover both by saying (back in 3.1.1) that for such
    functions, the signature in funcType has xs:double for each 'numeric'
    parameter.  That will ensure that Type <: xs:anyAtomicType* is true,
    and that a value of type xs:double is used for PrototypicalValue.
Comment 1 Jim Melton 2007-02-26 00:20:08 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).