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 28081 - [XP3] Named function references and the xs:numeric type
Summary: [XP3] Named function references and the xs:numeric type
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: SGI All
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-23 10:46 UTC by Michael Kay
Modified: 2015-07-06 08:55 UTC (History)
1 user (show)

See Also:


Attachments

Description Michael Kay 2015-02-23 10:46:22 UTC
Section 3.1.6 (Named Function References) contains the following text:

<quote>
Certain functions in the [XQuery and XPath Functions and Operators 3.1] specification are defined to be polymorphic. These are denoted as accepting parameters of "numeric" type, or returning "numeric" type. Here "numeric" is a pseudonym for the four primitive numeric types xs:decimal, xs:integer, xs:float, and xs:double. For the purposes of named function references, these functions are regarded as taking arguments and producing results of type xs:anyAtomicType, with a type error raised at runtime if the argument value provided is not of the correct numeric type.

Note:

The above way of modeling polymorphic functions is semantically backwards compatible with XPath 2.0. An implementation that supports static typing can choose to model the types of these functions more accurately if desired.
</quote>

This is obsolete and can be deleted. Since xs:numeric has been defined as a standard union type, there is nothing special about these functions that needs to be said here.
Comment 1 Andrew Coleman 2015-04-24 10:27:35 UTC
At the teleconference on 2015-04-21, the WG agreed to adopt this change
Comment 2 Michael Kay 2015-07-06 08:55:33 UTC
Confirmed that this change has been applied in the current draft spec.