This is the 03 April 2003 XInclude Conformance Test Suites Process Document.
Comments on this document are invited and are to be sent to the Xinclude public mailing list email@example.com.
This document has been produced as part of the W3C XML Activity. The authors of this document are the XML WG members.
A joined effort between W3C and NIST has been established to produce a conformance test suite (XInclude TS) for the XInclude recommendation. NIST has agreed to allocate resources to update and maintain the current test suite. Also, the test suites will be jointly developed by these two parties and will take the form of a public framework as explained below.
The XInclude TS will be produced in a public framework with contributions from developers and companies in the community. The XInclude TS will be coordinated and supervised by the XML WG and NIST.
There is a need to have a stable mechanism for submitting tests to the test suite. The points below assume that there is a technically stable mechanism for submitting tests, saving information about those tests, version handling and so forth.
It is presupposed that developers or organizations submitting tests have done a sanity check with regard to the functionality of the tests by referring to the relevant specification.
The main channel of communication for the XInclude TS will be the Xinclude public mailing list firstname.lastname@example.org.
The main channel of communication for submitting tests to the XInclude TS will be the Xinclude public mailing list email@example.com. An archive is available at http://lists.w3.org/Archives/Public/www-xml-xinclude-comments/.
In order to simplify for individuals and companies the production of the test suite and, if they so wish, contribute with tests of their own, we propose the following process for submitting tests:
The test suite's moderators investigate the test given the following criteria. At each point is also indicated possible reasons for not accepting to publish the particular test.
If the test is decided to be stable, which means that it is relevant, that it indeed tests a particular identifiable part of the specification, and that it is not wrongly written, it becomes "Reviewed and Stable" and receives this status.
Tests that at this or some other stage are judged not to be appropriate for publishing receive the "Inappropriate" status. These tests should be kept for archive purposes.
In cases where tests have received the "Reviewed and Stable" status but are found to be erroneous, the following procedure is proposed:
If it is found that a test that has been called "Reviewed and Stable" actually is not stable (if the tests are not correctly written or for any other reason), this particular test gets submitted to the XML WG for further consideration. Possible outcomes of this stage is that the test, after consideration, is judged to be
We propose that each test or whole suite comes fully documented with regard to the following (there will be an XInlcude wrapper for this kind of information available from the TS website):
It is proposed that the W3C XML WG representative act as moderator and controller for incoming tests. The XInclude TS moderator is choeon by the XML WG. All tests should be kept for archive purposes, whether they get published or not.
The XInclude TS aims, as explained above, at helping implementors to write applications that support the Xinclude recommendation. In no way are these conformance tests in the sense of providing companies or institutions with certification of XInclude support. The only claim that could be made is that a particular implementation is conformant to a particular version of the XInclude TS. There are two cases of results of running the test suite:
The XInclude TS will use the following grant of license:
The Contributor hereby grants to the W3C, a perpetual, nonexclusive, royalty-free, world-wide right and license under any Contributor copyrights in this contribution to copy, publish and distribute the contribution under the W3C Software License (19980720), as well as a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of the contribution.
The Contributor vouches that she/he has all rights necessary to contribute the Materials in a way that does not violate copyright, patent, and trademark rights; contractual obligations, or libel regulations.
Contributor further agrees that any derivative works of this contribution prepared by the W3C shalll be solely owned by the W3C. The Contributor agrees that all contributed Materials when published or otherwise distributed by the W3C will be governed by the W3C Software License (19980720).
W3C will retain attribution of authorship to the Contributor. Whenever modifications are made to the Materials, this fact, and the nature of the modifications, will be clearly signalled in the distributed version thereof. The W3C makes no a-priori commitment to support or distribute contributions.