RE: [ebxml-iic-interop] interop update

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

Title: interop update

Yes, latest draft is 0.4 you got by mail. Not posted yet on our site.

We need to review in particular Section 3:

- the detail of the test steps for each test case.

- the notion of having two "basic interop profiles", concretized by a test suite for HTTP,

and another test suite for SMTP. (no "option" inside a profile.)

- the content of these basic interop profiles (as drafted, they roughly match what remains

from the DGI tests, after removing (a) conformance tests, (b) optional tests, (c) specific tests like large payloads.)

 

Cheers,

 

Jacques

-----Original Message-----
From: Eric VanLydegraf [mailto:ericv@kinzan.com]
Sent: Monday, September 23, 2002 6:06 PM
To: 'Jacques Durand'; 'ebxml-iic-interop@lists.oasis-open.org'
Subject: RE: [ebxml-iic-interop] interop update

Just to confirm 0.40 is the latest interop document ?

-----Original Message-----
From: Jacques Durand [mailto:JDurand@fsw.fujitsu.com]
Sent: Monday, September 09, 2002 5:45 PM
To: 'ebxml-iic-interop@lists.oasis-open.org'
Subject: [ebxml-iic-interop] interop update

Steve, Hatem, Eric:

Here is an incremental update of the Interop suite document, for your review
based on improvement we discussed in past conf calls as well as F-2-F.

- Section 1.2 (concept of operations) is expanded.

- References to third-party tests (here, DGI) has been removed, as this is a general, abstract test suite,
that will be used as a reference by third parties. Comparisons with UCC/DGI test suite will be done separately,
as we expect for other existing test suites (ECOM). (We'll need to do such "comparative evaluations"
if only as a basis for discussion when negotiating with these entities, so that they understand how "compliant"
they are with our tests, and also so that they can give feedback on what may be missing in ours.

- list of Actions of  Test Service (Section 2.2) is slightly updated (configurator, also the message sending behavior
of all these actions is the same whether the Test Service is associated or not with a Test Driver.)

- still need to refine the way a Test Driver will drive the test cases by directly invoking the Test Service "Initiator" action.

- only one interop profile test suite described here for HTTP (Section 3), based on Steve's list of test cases
 as we went through in F-2-F.
It is roughly equivalent to: { DGI, minus conformance tests, minus optional tests, minus HTTP/S }
Detail of test cases (test steps, CPA...) still needs to borrow from Mike's material.
Still to discuss: idea that there is an interop profile for HTTP, another vfor SMTP. (see Section 3.3)

Regards,

Jacques

<<ebxml_ms_interoperability_testsuite_0.4.doc>>