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 6366 - Incosistent Error Codes for fn:doc in XQUTS and XQTS-CVS
Summary: Incosistent Error Codes for fn:doc in XQUTS and XQTS-CVS
Status: CLOSED FIXED
Alias: None
Product: XQuery Update Facility Test Suite
Classification: Unclassified
Component: XQuery Update Facility Test Suite (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Andrew Eisenberg
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-06 10:39 UTC by Peter M. Fischer
Modified: 2009-01-08 09:10 UTC (History)
1 user (show)

See Also:

Attachments

Description Peter M. Fischer 2009-01-06 10:39:51 UTC 
In put-011, FODC0005 is expected from fn:doc() if a
resource cannot be found

In the XQuery 1.0 Test Suite, CVS version a very similar case (fn-doc-3) gives FODC0002.

This could as well be that I'm missing some of subtle differences in
fn:doc or an issue in the XQuery test suite.
Comment 1 Andrew Eisenberg 2009-01-07 16:57:26 UTC 
I believe that F&O allows an implementation to raise either FODC0002 or FODC0005 when a resource cannot be retrieved during an invocation of fn:doc.

I've modified the expected results for put-011 to include both of these errors.

I believe that the same is true of fn-doc-3 and I suggest that you open a bug report to that effect.

Please close this bug report if you agree with this resolution.
Comment 2 Peter M. Fischer 2009-01-08 09:10:37 UTC 
(In reply to comment #1)
> I believe that F&O allows an implementation to raise either FODC0002 or
> FODC0005 when a resource cannot be retrieved during an invocation of fn:doc.
> 
> I've modified the expected results for put-011 to include both of these errors.
> 
> I believe that the same is true of fn-doc-3 and I suggest that you open a bug
> report to that effect.

Can you point me to the Product/Component for the "regular" test suite - I could not find it when searching

> Please close this bug report if you agree with this resolution.
>