This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
fn:format-number has the following signature for its 3-argument variant. fn:format-number($value as numeric?, $picture as xs:string, $decimal-format-name as xs:string) as xs:string Might I suggest changing it to: fn:format-number($value as numeric?, $picture as xs:string, $decimal-format-name as xs:string?) as xs:string with behaviour such that if the $decimal-format-name is the empty sequence, the default decimal format is used. Thus fn:format-number($value, $picutre) would be equivalent to fn:format-number($valud, $picture, ())
I have no objection to this change. It's probably a good design principle that if there's a 3-argument form of a function and a 2-argument form, then there should always be a value for the 3rd argument that makes the call equivalent to the 2-argument form.
I think the two-argument format should also be marked context-dependent.
In their Joint teleconference on 2011-12-06, the WGs decided to accept the proposal for the 3rd argument to fn:format-number to become xs:string? I am not marking this bug RESOLVED pending the completion of the changes to F&O 3.0.
The accepted changes have been applied to the spec baseline, so I am marking this resolved/fixed.
Thanks.