Bug 19215 - [XQuery30] unprefixed name of decimal format
Summary: [XQuery30] unprefixed name of decimal format
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3.0 (show other bugs)
Version: Working drafts
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2012-10-02 16:31 UTC by Michael Dyck
Modified: 2012-10-09 15:36 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Dyck 2012-10-02 16:31:32 UTC
Section 4.10 "Decimal Format Declaration" is missing a sentence that would tell me how to resolve the name of a decimal format when it's a lexical QName.

For the case of a QName with a prefix, it's true that section 2 already says that it's resolved using the statically known namespaces, but most places repeat this anyway.

For the case of a QName without a prefix, the section definitely needs to say.
  -- It's in the default element/type namespace.
  -- It's in the default function namespace.
  -- It's in no namespace (like variables and attributes).
  -- It's in a spec-defined namespace (like Option names).
  -- It's disallowed (like Pragma names).


By the way, there's also a similar sentence missing from:
  -- 3.10.4 "Window Clause"
     re the CurrentItem, PreviousItem, NextItem in WindowVars
  -- 4.18 "Function Declaration"
     re the name of a Param
Presumbly they're resolved the same as the VarName in a VarDecl, but it wouldn't hurt to say so.

[first raised here: https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Jul/0041.html ]
Comment 1 Jonathan Robie 2012-10-09 15:36:39 UTC
In today's call we decided that an unprefixed name is in no namespace, like format-number.

All variable names in variable references should follow the same rules as a  VarName in a VarDecl.