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 11950 - across-queries-results-q2b.xq test unreasonable
Summary: across-queries-results-q2b.xq test unreasonable
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 Use Cases (show other bugs)
Version: Candidate Recommendation
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Pat Case
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-01 23:49 UTC by Paul J. Lucas
Modified: 2011-02-22 19:11 UTC (History)
1 user (show)

See Also:


Attachments

Description Paul J. Lucas 2011-02-01 23:49:11 UTC
The aforementioned test (pasted here for convenience):

$input-context/books/book[content/part/introduction contains text "prototypes"]

according to the expected result in the XQFTTS, is supposed to match the text:

    <b>p</b>rototypes

Section 4.1.1 of the spec says:

Implementations may provide for the means to ignore or side-step certain structural elements when performing tokenization. In the following example, the implementation has decided to ignore the markup for <bold> and prune out the entire subtree headed by <deleted>.

The fact that the test at hand exists means that every XQuery implementation MUST ignore <b> markup (but not its content).  That's simply unreasonable.

Every XQuery implementation strives to pass 100% of the tests in the W3C test suite.  (It's a nice marketing statement.)  Such a test makes this impossible without hard-coding special knowledge about <b> markup.
Comment 1 Mary Holstege 2011-02-22 19:11:24 UTC
The WG discussed this on the meeting 2011-02-08 and agreed that there are indeed implementations that do not provide the feature tested or cannot provide it in a readily configurable fashion.  We decided to keep the test, however, as it tests an important feature that some implementations may choose to provide. We are further clarifying in the instructions that we do not expect all implementations to execute or report on all sections of the optional area of the test suite.

Please indicate your satisfaction with the resolution of this bug by marking it as CLOSED.