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 9497 - [XQuery11] 4.16 Context Item Declaration: VarValue/VarDefaultVal inside a library module
Summary: [XQuery11] 4.16 Context Item Declaration: VarValue/VarDefaultVal inside a lib...
Status: RESOLVED FIXED
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
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-12 08:56 UTC by Tobias
Modified: 2010-06-15 16:46 UTC (History)
1 user (show)

See Also:

Attachments

Description Tobias 2010-04-12 08:56:57 UTC 
please clarify what happened if there is a context item declaration with a VarValue or VarDefaultVal inside a library module. should an error be raised? If so, which one?

4.16 Context Item Declaration:
When a context item declaration appears in a library module, neither VarValue nor VarDefaultValue may be specified. Such a context item declaration serves only to declare the expected type of the context item.
Comment 1 Jonathan Robie 2010-04-20 14:59:20 UTC 
Nice catch - I need to define an error for this.
Comment 2 Jonathan Robie 2010-06-15 14:24:31 UTC 
I propose to change the text as follows:

<new>
A context item declaration allows a query to specify the static type,
value, or default value for the initial context item.

In a library module, a context item declaration specifies only the
static type.  Specifying a VarValue or VarDefaultValue for a context item
declaration in a library module is a static error [err:XQST0113].
</new>

And to add this error description:

<new>
err:XQST0113

Specifying a VarValue or VarDefaultValue for a context item declaration
in a library module is a static error.
</new>