OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-iic message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [ebxml-iic] minutes and next call?


Title: IIC Conf Call Monday, August 12th at 10:00AM PT (1:00PM ET)
All:
 
1. Minutes of yesterday's call attached.
 
2. We need a volunteer for hosting call Monday 30th... (10am PT)
 
 
Regards,
 
Jacques
 
 
Minutes of IIC September 23, 2002
-------------------------------
 
Call info:
---------

HOST: NIST (Michael Kass) 
CALL DATE:         SEP-23-2002  (Monday) 
CALL TIME:         01:00 PM EASTERN TIME , 10 AM PACIFIC TIME 
DURATION:              1 hr 
USA Toll Free Number: 877-917-7133 
USA Toll Number: +1-212-287-1619 
Minute taker: Jacques Durand


Present:
--------

Mike Kass (NIST)
Jaques Durand (Fujitsu)
Jeff Turpin (cycloneCommerce)
Eric Van Lydegraf (Kinzan)
Monica Martin (DrakeCertivo)


Agenda:
-------

1. test Case material and MS COnformance suite: 
- finalizing : remaining issues of the test material 
(test steps and their status/type/errors, test outcomes...) 
- status on: conformance profiles (Jeff) 

2. Interoperability Test suite: 
- status on: detail of current test cases candidates for basic interop profile(s) 
-  comparison with UCC/DGI 
- ECOM completed their first ebXML interop tests (5 vendors from ASIA) 

3. Deployment templates: 
- status on: template doc from Pete. 
- input from EAN (Thomas?) 


Minutes:
--------

1. Test Case Material and MS Conformance Test Suite: (Edited by Michael Kass)

- Mike introduced the fixes to test material: 
. CPA attributes, which makes it possible to reference CPA elts inside message 
expressions of test steps, 
. a Condition operation (in addition to operations to create, send, receive mesges) 
that evaluates logical expressions (used for final test verification, as well as any 
intermediate check.)
. an errorStatus attribute associated with any operations of any step.
- Aggregation of Test Cases: would allow for re-using (both at test case definition
in the specification, as well as at execution) similar sequences of test steps.
It is not obvious we can aggregate test verification conditions, except in special 
cases (XML Schema validation).

- Jeff sent out (mail) a reduced set of 4 COnformance Levels. 
- Jeff's point in not keeping  "ordering" in level 2, is that most vendors 
did not implement it (as opposed to reliability). 
COnsequently, most implementations would not be able to certify at Level 2 
if ordering was in it, which is indeed not good. 
- An argument for consolidation of ordering in Level 2, 
is that ordering is part of a quality-of-service package, that brings value to 
ebXML messaging. (The three levels then obtained would be much similar
to the Option 3 of last year, that got substantial backing back then.)
- Also remains to see where we fit Ping and StatusRequests, even though these
are not very significant for conformance, as responses are not mandatory...
So that's where we are, and what we will we have to decide.


2. Interoperability Test suite: 

- Latest draft to review is same as 2 weeks ago: V0.4.
We need to review in particular Section 3: 
- the detail of the test steps for each test case. An important 
aspect is that unlike conformance tests, no "sniffing" on the wire
is assumed here. The interop contract is at application level, using only
material that is visible in Test Service actions. That means, testing that
Acks sent by MSH1 are well understood by MSH2, can only be deduced by
observation of the effects of these acks (e.g. if they are not well understood,
then MSH2 will resend initial business message, and we'll observe that at app level.)
Any more detailed test on Ack well-formedness, or appropriate sending, is relevant to
conformance test suite, not interop.
- 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 test suite.) 
- 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.)
- Steve currently traveling (CEN-ISSS meeting), will work on this next.

- ECOM completed their first ebXML interop tests (5 vendors from ASIA). 
They want to cooperate more closely with us. I have asked for their test suite doc.


3. MS Deployment templates / EAN guidelines.

- Pete could not attend meeting. His draft doc on template posted for broader review.
At this point, commented by Monica, Jacques, Eric.
Draft will be posted on our site.



Reminders:
---------

- Next teleconference planned for Monday, September 30th, 10am Pacific time.
(weekly until we wrap-up our specs.)
 

Jacques Durand
ebXML IIC chair









[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC