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 3124 - version_declaration-005: the Text baseline is invalid
Summary: version_declaration-005: the Text baseline is invalid
Status: CLOSED INVALID
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 0.8.6
Hardware: Other Linux
: P2 normal
Target Milestone: ---
Assignee: Frans Englich
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-20 20:13 UTC by Frans Englich
Modified: 2006-05-24 20:05 UTC (History)
0 users

See Also:


Attachments

Description Frans Englich 2006-04-20 20:13:56 UTC
version_declaration-005.xq contains:

declare default collation "xspanish";

One of the baselines is the error XQST0038(which is the correct reaction on the query, as I see it), but also the 'Text' baseline with the content "15". I don't see how that baseline is possible.

I suggest removing the collation declaration, since it seems the text was written in order to evaluate(and it is perhaps due to historical reasons or mistakes that the invalid collation declaration is there).


Regards,
Frans
Comment 1 Ravindranath (Ravi) Chennoju 2006-05-17 23:26:08 UTC
An implementation which does not recognize "xspanish" collation will go ahead
and run the query and return 15. That is the reason we have 15 as the expected output.
Comment 2 Frans Englich 2006-05-18 10:04:27 UTC
Then I need some clarification. Here's a quote from the end of 4.4 Default Collation Declaration:

<quote>
If a Prolog contains more than one default collation declaration, or the value specified by a default collation declaration (after resolution of a relative URI, if necessary) is not present in statically known collations, a static error is raised [err:XQST0038].
</quote>

So, if the collation is not present in the statically known collations, a static error is raised(XQST0038). I think this behavior is consistent in all other cases of where unknown collations are encountered.

This is why I believe implementations will fail with XQST0038 on this(except those who support collation "xspanish").
Comment 3 Ravindranath (Ravi) Chennoju 2006-05-19 16:56:25 UTC
There was a typo in my earlier comment. Sorry for the confusion caused.
Here is the correct comment.

An implementation which does recognize "xspanish" collation will go ahead
and run the query and return 15. That is the reason we have 15 as the expected
output.
Comment 4 Frans Englich 2006-05-24 20:05:37 UTC
This report is invalid as discussed internally, closing as INVALID.