minutes, and more

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

All:

 

Sorry for late reminder - meeting initially cancelled is possible after all...

(assuming enough people can attend)

 

In particular, please review latest Deployment Profile Template meta-data doc uploaded today.

We need to vote on this (email voting starting Monday) as that will serve as template for future ebXML guidelines including an upgrade of ebMS 2 template.

 

 

Host: Fujitsu

Time: Monday May 2, 11am PT

Toll only :  1-512-225-3050

(new)

Participant code: 375491

 

Agenda:

 

1. Update on Test Assertions guideline and related TC
2. the new Deployment Profile Template (see latest upload May 1)
3. BPSS test assertions update
4. General (OASIS symposium)

 

Regards,

 

Jacques

 

Time: Monday April 28th, 2005, 11am PT 
Host: Fujitsu 
Toll only : 1-512-225-3050 

Attendees :

April 4:

Michael Kass (NIST)
Jacques Durand (Fujitsu)
Pete Wenzel (SeeBeyond)
Monica Martin (Sun)

April 18:

Michael Kass (NIST)
Jacques Durand (Fujitsu)
Pete Wenzel (SeeBeyond)
Monica Martin (Sun)


Agenda:
1. Revision of deployment template for ebMS 2, eAC deployt guide. (Jacques, Pete) 
2. Slides for presenting IIC work at Symposium 
3. Update on BPSS testing, what kind of test assertions.
4. Test Assertion guidelines, and revival of OASIS conformance TC: update




------- Action Items:


Jacques: write slide(s) for IIC status briefing at symposium.
Jacques, Pete: post new meta-data for "deployment profile template" that would 
accommodate eAC as well as deployment profiles for other specifications.

------- Minutes:


1- Revision of deployment template for ebMS 2, eAC deployt guide. (Jacques, Pete) 
- No objection to an update and renaming of columns of feature profiling table.
- eAC has also no issue with a renaming of the columns, but has not seen the latest
proposal for meta-data (Deployment Profile Template).
- pending question if we would have an XML version of the deployment guideline, 
that would be rendered as HTML (XSLT), so that we do not depend on a word processor format.
For now, Word doc still OK.
- The distinction "technical / Business" has been removed from the template.
To be discussed further.
- what would the template mean for BPSS? mostly a BPSS schema, or "good practices" on it?
e.g. how it should map to CPP/CPA.

2- Slides symposium:
- Jacques will do.

3- follow-up on BPSS testing 
- BSI: are we talking of testing (1) an implementation engine, (2) a set of business 
transactions and their states?
- we need to keep in mind BPSS is mostly for monitoring, at run-time. 
So the testing output is about propser error detection, conformance to bus trans.
- the patterns query-response and Request -response are different (semantically) although
could be implemented very similarly.
- signals are distinguished from other messages, in BSI engines: 
messages have either a doc envelope or a signal envelope.
- 5 different types of signal envelpe:
o Receipt Ack
o Receipt Ack Exception
o Acceptance Ack
o Acceptance Ack Exception
o General Exception
- these signals are no part of MEPs (patterns) ! are not choreographed.
- BPSS patterns: XML schemas had its challenges w/r operational semantics (outside schema)
- a subset of testing has utility beyond BPSS / Patterns.
- JJDubray is right resource to initiate cycle for generating T.Assertions.
- there is more than 1 level for testing: at least 2, maybe 3: (1) monitoring the usage, messages, 
(2) QoS at business level and guidance on CPA.

4- Update on the current cross-standard efforts for a common Test Assertion guideline doc. 
- a "conformance and interoperability technologies" TC is currently being considered,
with transient subcoms that will work on specific items such as the Test Assertion guideline.
- the draft Test Assertions guidelines initiated in the OASIS TAB (Jacques is editor),
and IIC material, would be input material.