This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
It would be practical if the schema is available on the net, just as how the schemata are for XHTML, SVG, and so on. This would promote the XQTS format and make it attractive to use in other situations. I'm thinking about that it would be downloadable via: http://www.w3.org/XML/Query/test-suite/XQTSCatalog.xsd or similar. Frans
(In reply to comment #0) > It would be practical if the schema is available on the net, just as how the > schemata are for XHTML, SVG, and so on. This would promote the XQTS format and > make it attractive to use in other situations. > > I'm thinking about that it would be downloadable via: > > http://www.w3.org/XML/Query/test-suite/XQTSCatalog.xsd > > or similar. Or you could just advertise http://dev.w3.org/cvsweb/~checkout~/2006/xquery-test-suite/TestSuiteStagingArea/XQTSCatalog.xsd which works now (and is already where google will take you if you search for XQTSCatalog.xsd. The URI's a bit longer but has the advantage that you know it's in sync with the latest version. David
Frans, does the URL that David provided meet your needs? The schemata for Recommendations such as XHTML, SVG, and so on are available from the W3C web site. I hadn't considered doing the same for the XQTS catalog schema or result schema.
It is of course not as good since it doesn't have the same URI persistence, isn't the standard way to serve W3C files and is hard to find. I see an advantage in helping people testing XQuery implementations -- it improves interoperability. One step towards that is to provide testing utilities(like schemata) in a solid way, and not with an ad-hoc approach. (End of preaching.) If we put the schemata in http://www.w3.org/XML/Query/test-suite/, how would that be done? Manually copy it? I'm currently looking into what mechanisms CVS provides for that(although I doubt it, SVN would give other opportunities, though). Another alternative is that we simply move the schemata, and adjust build scripts accordingly. Is there any particular obstacles you have in mind with putting them in XML/Query/test-suite/? I agree this is not a high priority thing(compared to the 1.0 release, for example), so this can wait. I also have acceptance for using the CVS-interface. Nevertheless, I think it would be an improvement, so I dig a bit more in this.
Nope, CVS doesn't provide a facility for linking to files. Therefore, doing this would either have to be done by moving or copying the schemata, or redirecting with the HTTP layer. A somewhat similar situation: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3414 Frans
I withdraw this request.