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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

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

Subject: Re: [ebxml-dev] ebXML specifications interdendancies

   Date: Tue, 04 Dec 2001 14:16:32 -0500
   From: "Anarkat, Dipan" <DAnarkat@uc-council.org>

       This means that the ebMS TR&P cannot be used independantly for TR&P and
   forces you to use ebCPPA and ebBPSS. As such, even though an agreement may
   not be required between trading partners , we still need a bare bones 'void
   agreement' . 
   Is my understanding right, or am I missing a point here !? 

You don't necessarily need a CPA document, but the two ends have to
have some understanding of the parameters of the communication.  For
example, if one side feels that it doesn't trust the provenance of a
document unless the document is digitally signed, then this fact needs
to be conveyed somehow to the sender, so that the sender will know to
digitally sign what he sends.  The message protocol requires the
endpoints to agree on this and other parameters.  But you don't have
to do it with an actual XML CPA document.

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC