This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
[Affects XQuery11 too.] 2.1.1 Static Context Statically known decimal formats. [1] The spec is inconsistent on "decimal format" vs "decimal-format". (Also true for F+O spec.) [2] "This is the set of known decimal formats." It would be more consistent to say that it's a set of (EQName, decimal format) pairs or a mapping from EQNames to decimal formats [3] "Each format is used for serializing decimal numbers using fn:format-number()." [3a] Change "is" to "can be" (because the declaration of a format is not a guarantee that it will be used). [3b] Change "decimal numbers" to just "numbers" (because fn:format-number "can be used to format any numeric quantity", not just xs:decimals). [4] "Each format is identified by a QName, except for the default format, which has no visible name." It would be more consistent to have a separate 'default decimal format' component. [5] "Each format contains the properties described in the following paragraphs." I think it would make more sense for the description of the properties to be in section 4.10 Decimal-Format Declaration. [6] "The following attributes control the interpretation of characters in the picture string supplied to the format-number function." [6a] Change "attributes" to "properties". [6b] Change "format-number" to "<code>fn:format-number</code>". [7] "The following attributes specify characters or strings that may appear in the result of formatting the number:" Change "attributes" to "properties" again.
Re [5]: Oops, XPath doesn't have a section 4.10. (I originally wrote the comment for XQuery.) So on second thought, drop the description of properties, and just refer the reader to F+O section 4.6.1.
This requires some discussion. See http://lists.w3.org/Archives/Member/w3c-xsl-query/2011Apr/0167.html
I have now checked in changes proposed in http://lists.w3.org/Archives/Member/w3c-xsl-query/2011Apr/0176.html. The other changes had already been made. I am marking this bug Resolved/Fixed.