minutes last meeting

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

Title: minutes last meeting

A little late...
But just in time for this Monday call (Monica facilitating).

Jacques
<<IIC_June_16_03_Minutes.txt>>

IIC Conference Call Minutes: Monday, June 16, 2003
 
Attendance:

Mike Kass (NIST)
Jacques Durand (Fujitsu)
Monica Martin (Sun)
Mike Dillon (DGI)
Serm Kulvatunyou (NIST)
Tim Sakach (Drake Certivo)

Excused:
Pete Wenzel (SeeBeyond)

Minutes taker: Jacques Durand


Time: Monday June 16th, 11am PT
Host: Fujitsu
Toll Free - :  1-800-251-6413
Toll - :  1-913-905-1400
Participant code: 598136

Agenda: 

1. Status on external related activities 
- global MS interop testing (Rik Drummond): 
requirements/purpose, logistics, test suites (role of MS BIP?), IP issues, market. 
- others? (eBES, ITG)

2. MS conformance test suite spec. (Mike / Jacques) 
- review current status and test suite material. 
- comments on our test requirements (Mike Dillon?)
- main spec format: test case narrative... 

3. Test suites for other specs: 
- BPSS testing (Serm) 
- review / comments on the "test requirements guidelines" (Monica). 

4. TestFramework implementation and product status 
- Implementations under way (Tim Sakach, Mike ) 
 
-----

1. Status on external related activities 
- Global interop testing: Mike stated that matrix testing is the only way.
Jacques: that could be done, e.g. use of MS BIP asymetric test suite, 
repeated from each region, e.g. driven once from Asia community to US community , 
then once from US to Asia, each driver party also taking in charge the logistics.
Facilitators such as DGI, ECOM, would be the drivers. Financially, things could be
simplified: financial transactions if any, can be reduced to those between a regional 
user community and its local facilitator (ECOM, DGI). 
The remote community could be involved "for free" if they accept in return to drive 
the reverse test round at no charge for the foreign community.
Three communities tobe considered: US, Asia, Europe.
- Mike stated that one of the main issues he sees, is in the time zone problem.
Tests have to be automated so at least one side does not have to "wake up".
- eBES: Monica is following. eBES is going to publish their Interop test suite
on the IDEAlliance site. Will forward two press releases of interest.


2. MS conformance specs. (Mike / Jacques)

- Revision of latest proposed changes in the format for the normative "abstract suite":
clearer semantics of $parameters, rename PutMessage / GetMessage, XPath refinements, 
use of same logical expressions in sending/receiving. Jacques to send examples.
- Serm asked if we could express business rules using this notation. Should be fine,
but concerns the payload and has no place in this conformance tet suite.
- Mike Dillon will review the annotated spec, and its coverage. Says the link between
target spec and the test requirements should be very clear both ways.
- We still need to post conformance test suite material (working drafts) on our site.
Mike to provide a set of drafts (annotated spec, test reqs, abstract suite) and Jacques
will package and post.

 
3. Test suites for other specs.

- Serm work on BPSS: it appears he has focused so far on an interop suite for BPSS.
issues: real bus process need be used, with bus documents, as interop otherwise
reduced to MSH interop. Difficult to require symmetric setting on each side.
So the suite is likely to be process-dependent, specific to users apps?
- need to clearly distinguish again BSI conformance, from interop: a "test process"
can be design for BSI conformance, and reused for each BSI impl. However, a test service
must be defined, that implements "test business activities" needed by the BSI
to execute the test process,e.g. will process/generate "test bus documents".

4. TestFramework implementation status, (Mike Kass, Tim Sakach, Serm K.): 

- Tim: DCertivo is going to implement MS conformance tests. 
- doing RN conf testing for 4 solutions providers. TestFramework
impl is adapted to accommodate other messaging standards (RNIF 2).