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 tests do not have an XQueryX version: revalidation-declaration-02 revalidation-declaration-04 revalidation-declaration-06 id-insert-expr-093 I don't think this was intentional. I noticed this because of the generated HTML XQueryX report. It shows less than 100% passing because of these 4 missing tests but really no tests are failing.
(In reply to comment #0) > The following tests do not have an XQueryX version: > revalidation-declaration-02 > revalidation-declaration-04 > revalidation-declaration-06 Our generation of XQueryX is imperfect. We cannot generate XQueryX for these test cases, because our parser recognizes that each query has two revalidation declarations and raises an error. Without parse trees, we cannot generate XQueryX documents. > id-insert-expr-093 This test case was added to XQUTS after XQUTS 1.0.0 was published. I've just generated XQueryX for this new test case. > I noticed this because of the generated HTML XQueryX report. It shows less > than 100% passing because of these 4 missing tests but really no tests are > failing. > I use the XQUTS 1.0.0 catalog when I generate reports, so missing (or failing) new test cases is not a problem. For the test cases without XQueryX, this is a failing of the stylesheet that I wrote to generate our reports. I'm not going to attempt to fix this, as I know that it would be very difficult to do so. Please close this bug report if you are satisfied with this resolution.
Created attachment 842 [details] revalidation-declaration-02
Created attachment 843 [details] revalidation-declaration-04
Created attachment 844 [details] revalidation-declaration-06
Our XQuery->XQueryX converter does not have the same limitation so I went ahead and converted the missing files and attached them to this bug. If for whatever reason you don't want to use the attached files, it is fine with us if you close this bug. Thanks.
The parser limitation I mentioned was actually a limitation in our XQueryX generation and I've fixed it. The following XQueryX documents were just added to CVS: revalidation-declaration-02.xqx revalidation-declaration-04.xqx revalidation-declaration-06.xqx Please close this bug report if you are satisfied with this resolution.
Excellent. Thanks!