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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-iic-interop message

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

Subject: RE: FW: [ebxml-iic-interop] comments on Interop suite


   More comments.  Key questions:

1) Need to assign <Manifest><Reference xlink:href =""abc">" at the application level in order to do any
meaningful payload testing for interop, otherwise we have no way of fetching or evaluating a particular
payload ( no CID to refer to ).

2) Fold <SetPayload> operation into <Manifest> declaration, and eliminate <SetPayload> as an operation..
not needed, and it is cleaner.

3) Define a standard message payload format for including the digest(s) of payloads used in the PayloadVerify
operation, consisting of a list of CIDs and their corresponding Digest values.


At 11:40 PM 1/14/2003 -0800, Jacques Durand wrote:
You are right for the CPA: we assume the same on each side, for a given test case,
as usually the CPA covers a conversation. That is anyway simpler for running the tests,
which is needed especially for interop.
That measn our messages will refer to same CPAId, within a test case.
Here is attached my comments for interop test case scripts - I think we are there.
I guess we need to go through the rest of the test cases (beyond #2 or #3) to see if
they are consistent with latest changes. Also proper CPA names need be used.
(should we use the ones I proposed in previous mail?)

Attachment: BIP_testcases_scripting_MK2_JD3_MK3.doc
Description: MS-Word document

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

Powered by eList eXpress LLC