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 30263 - [FO31] Context-dependency of format-number#2 and format-integer#3
Summary: [FO31] Context-dependency of format-number#2 and format-integer#3
Status: NEW
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (show other bugs)
Version: Recommendation
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2018-06-09 12:08 UTC by Abel Braaksma
Modified: 2018-06-09 12:08 UTC (History)
0 users

See Also:


Description Abel Braaksma 2018-06-09 12:08:34 UTC
Currently, format-number#2 is defined to be context-independent. However, the text says it uses the unnamed decimal format. Since this format is defined in the static context, it can be different in a different (static) context, hence I believe it should be marked context-dependent instead.

In XSLT for instance, you can have different unnamed decimal formats in different packages, which means that dependent on which package you use the static context can be different and hence the unnamed decimal format can be different.

Conversely, format-integer#3 is said to be context-independent, but the third parameter can be the empty sequence and the text says "then the number is formatted using the default language from the dynamic context.", which implies it is dependent on the dynamic context *if* it is empty.

I don't think the text is unclear or that implementers would have a difficulty here, it is merely in the defined properties of the function that come as a bit of a surprise (hence marked "Minor").