This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Statically known decimal formats are defined in 2.1.1 Static Context. A row should be added to the table in C.1 Module Static Context, defining the initialization and alteration of this component.
Here's my first shot. * Default initial value output:method = "xml"; * Can be overwritten or augmented by implementation? Yes * Can be overwritten or augmented by prolog? Yes, using 2.2.4 Output Declarations * Can be overwritten or augmented by expressions? No * Consistency rules Must conform to a valid set of <termref>output declarations</termref>
>output:method = "xml"; Eh? statically known decimal formats have nothing to do with serialization.
Here's my second shot. * Default initial value Specified in http://www.w3.org/TR/xquery-30/#dt-static-decimal-formats * Can be overwritten or augmented by implementation? Yes * Can be overwritten or augmented by prolog? Yes, Decimal Format Declarations * Can be overwritten or augmented by expressions? No * Consistency rules See error conditions in http://www.w3.org/TR/xquery-30/#dt-static-decimal-formats
The Working Group has adopted the resolution in comment #3.
You added the row to the table in C.2 (dynamic context), should have added it to C.1 (static context). (Also, note that in rev 1.53 of src/back-matter.xml, I reordered the rows of the tables in appendix C so that components are grouped by overwriteability: first the ones that can be overwritten/augmented by expressions, then the ones that don't vary at the expression level but can be overwritten/augmented by (decls in) prologs, and then the ones that can't be overwritten in either. [I should have put a comment to that effect in the XML source, sorry.] Anyhow, statically known decimal formats should be in the second group.)
Fixed in current build.
Looking at the latest draft, saying "yes" to "Can be overwritten or augmented by implementation?" seems wrong. Perhaps statically known collations and default collation could act as our guide. Default decimal format * Default initial value Implementation-dependent * Can be overwritten or augmented by implementation? No * Can be overwritten or augmented by prolog? No * Can be overwritten or augmented by expressions? No * Consistency rules None. Statically known decimal formats * Default initial value only the default decimal format * Can be overwritten or augmented by implementation? no * Can be overwritten or augmented by prolog? augmentable, by Decimal Format Declarations * Can be overwritten or augmented by expressions? No * Consistency rules Each URI uniquely identifies a decimal format.
There seemed to be sentiment at the joint meeting on Tuesday to stay with one row in C.1 Static Context Components. Better understanding decimal formats, let me suggest: Statically known decimal formats * Default initial value the default (unnamed) decimal format, which has an implementation-dependent value * Can be overwritten or augmented by implementation? augmentable * Can be overwritten or augmented by prolog? augmentable, by Decimal Format Declarations * Can be overwritten or augmented by expressions? No * Consistency rules Each URI uniquely identifies a decimal format.
One reservation - decimal format names are QNames, not URIs.
In today's telcon we agreed to adopt Comment #8 modulo Comment #9.