regarding how to handle test tools legacy

[Jacques Durand <JDurand@us.fujitsu.com>]

All:

Here is an option discussed privately with some of you, that seems attractive on several accounts, regarding how to handle test tools legacy. To be discussed on the mailing list and at next meeting, to be scheduled March 7 very likely:

1.      The BRSP TC  - as an OASIS TC - will primarily focus its work on the profile specifications, not the test tools – at least not on these as a TC asset / deliverable. In fact, will avoid completely processing the test tools & test suites in OASIS, as OASIS is not intended for software distribution nor provides a framework for code licensing.

2.      Any former contributors of the WS-I test tools are invited to re-contribute their test code to a 3^rd party open-source project  (TBD) and hosting site,  both for distribution and maintenance. This external project can be open to outsiders (non members of BRSP TC).

3.      When submitting test tools and test suites to an external OSS host it is preferable that contributors agree on a common, open-source code license for all tools. That is not a mandatory requirement though.

4.      The TC has the testing of Profiles as part of its charter. The TC can make use and refer to the test tools and test suites of their choice, to do this testing. These test tools and suites can either be externally developed and hosted, or developed by members, or both, as long as their licensing allows for this.

5.   The TC can make (approve) statements that a particular version of the referred tools and suites is appropriate for verifying conformance to a particular version of a particular profile. Such statements would include precise references to these tools and suite. The best format for such statements is still TBD (they could be made as part of the Statements of Use required for a Profile standard, or in form of an “interoperability and conformance test report” periodically updated and released by the TC). With such statements, the TC exercises its authority to indicate to 3^rd party users what tools/suites are appropriate for a particular profile.

For review and comments,

Jacques