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 3275 - Some tests of version_declaration-* are positive cases, should not have <expected-error>*</expected-error> specified in XQTSCatalog.xml
Summary: Some tests of version_declaration-* are positive cases, should not have <expe...
Status: RESOLVED WONTFIX
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Jinghao Liu
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-11 18:25 UTC by Jinghao Liu
Modified: 2006-05-18 01:17 UTC (History)
0 users

See Also:

Attachments

Description Jinghao Liu 2006-05-11 18:25:29 UTC 
For example, this case:

(:*******************************************************:)
(: Test: version_declaration-001.xq          :)
(: Written By: Pulkita Tyagi                             :)
(: Date: Tue Aug  9 04:11:16 2005                        :)
(: Purpose: Demonstrates version declaration,the version :)
(:          declaration occurs at the beginning of the   :)
(:          module and identifies the applicable XQuery  :)
(:          syntax and semantics for the module          :)
(:*******************************************************:)

xquery version "1.0";
1,2

The case looks valid, and the result looks correct.  However in XQTSCatalog.xml, it has element <expected-error>*</expected-error> with it.
Comment 1 Andrew Eisenberg 2006-05-15 20:17:15 UTC 
I believe that the expected error was added to cover the following statement in section 4.1, Version Declaration, of XQuery:

"If a version declaration is present, no Comment may occur before the end of the version declaration. If such a Comment is present, the result is implementation-dependent."

Ravi, do you agree with this?
Comment 2 Ravindranath (Ravi) Chennoju 2006-05-18 01:02:42 UTC 
Yes Andrew that is correct. Reassigning the bug to JingHao for closure or comments.
Comment 3 Jinghao Liu 2006-05-18 01:17:55 UTC 
According to the response, resolved it as Won't Fix.