minutes previous meeting

Time: Monday January 9th, 2006, 11am PT

Host: Fujitsu

Toll only : 1-512-225-3050

Attendees :

Monica Martin (Sun)

Jacques Durand (Fujitsu)

Pete Wenzel (Sun)

Sacha Schlegel (CycloneCommerce )

Agenda:

1. ebBP Deployment Template WD.

2. Test script language update.

------- Minutes:

1- ebBP Deployment Template WD:

- Bus doc profiling may refer to 3rd party tech: CC, CAM...

- Profile Req Item tables may be repeated: make it clearer in template.

Monica> how much should we cover in the profiling of BPSS?

- Two aspects in the profiling:

(a) modular process definitions, (b) run-time monitoring, e.g. timing, etc.

- In case some of these monitoring parameters are defined at run-time, how are

they communicated? Need be agreed by the parties.

- external semantic info & context can be known at run-time only.

- (b) should be part of "operational profile": e.g. specify how dynamic info is obtained,

e.g. point to external docs. Also includes test and validation procedures. Verify the BT type.

- what else remains to be added in current draft?

2- Test script language update.

- Jacques introduced the proposed updates, differences with previous TestFramework 1.1. Notion of "test event" and test event log (TEL) is central. Workflow is

Simplified (more primitive operators). Not ebXML centric.

- how close is that from WS-Choreography? Test script: executable, not declarative.

Monica> ebBP editor doc published on ebBP site.

Sacha> Flow of Bus Transactions neeeds be tested as well: the sequence at run-time

may depend on outcome of previous BT. Pre-conditions and post-conditions in BTs:

may use file access, previous message.

- How general the standardization of the notion of event? Digital sig certs, transport level.

Would a CPA fit-in?

ebxml-iic message