More interop doc suggestions

[Doug Davis <dug@us.ibm.com>]

In section 1.1
- replace "workshop" with
"f2f" - text is old from the pre-oasis workshops process
- line 14 - we're doing "online"
testing, not "f2f"
- principle 4 - should mention SSL instead
of SC/Trust - although nothing in the doc talks about SSL either  :-(
- remove the list of scenarios since
people should try all of them  :-)
- see suggested version at end of the
note.

scenario 2.1 - init step 3:  s/one
way/app/   to match the other scenarios

scenario 3.1 - success criteria - remove
the part about Rollback being received twice - its just once

scenario 5.6 - say that its the PA that
drops the Committed msg - we need to be clear on which side does it


thanks
-Doug


Suggested version of text for Scope
section:

...

Protocol Interoperability testing includes any message exchange that leverages the protocol. Following the workshop model, there are two concurrent mechanisms vendors can use to achieve interoperability: face-to-face(f2f) interop events and online interop testing. Given the time constraints for test execution during a f2f and the number of participants, it is important to prioritize tests to select only those focused on mainline scenarios and which most heavily exercise the protocol. The rest of the protocol testing can be left for online interoperability and in-house QA by each vendor.

We propose the following principles for test selection for online AT interop testing:

1. Positive tests only. The failure scenarios used in testing MUST not include invalid states/invalid messages by implementations.
2. Target Interaction. Test Scenarios should verify the interaction between two parties according to the protocol.
3. Target Protocol. Target scenarios described by WS-AT and WS-Coordination specifications.
4. Include composition with SSL

During the interop event it is recommended to start with the following scenarios:...