This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The following query examples should use //book or /books/book if we change the sample XML document fragemnt to include <books> as the top level wrapping element. (1) In 3.2 Search Tokens & Phrases: All four examples (2) In 3.3 Match Options: All two examples (3) In 3.3.1 case option, All two examples (4) In 3.3.2 diacritics option,All two examples (5) In 3.3.3 stemming option, one example (6) in 3.3.5 stop word option, first 2 examples (7) In 3.3.6 language option, first 1 example (8) in 3.3.7 wildcard option, all four examples (9) in 3.4.1 or-selection, one example (10) in 3.4.2 and-selection, all 2 examples (11) 3.4.3 mild-not selection, one example (12) 3.4.4 not-selection, 3 examples (13) 3.5 .1 ordered selection, 2 examples (14) 3.5.2 window selection all 4 examples
(15) 3.5.3 distance selection all 4 examples (16) 3.5.4 scope selection first 4 examples (17) 3.6 cardinality selection first 3 examples (18) 3.8 extension selection first 2 examples
Dang. We thought (hoped?) that it would all be as simple as wrapping the book element inside of a books document element. Seems to be wrong, though. I think we have to ask ourselves what the better fix is -- to fix all of the examples Zhen has identified that must be fixed if we add the books wrapper, or fixing the examples that are broken if we don't add that wrapper. I am happy whichever solution we choose, as long as the changes are made very, very quickly.
I have made the changes indicated in comment #1 and #2, and so am marking the issue as resolved-fixed. If you agree, please mark it closed.