[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ebxml-cppa-negot] vanilla SOAP binding
I reviewed the contents of the MessagingCharacteristics attributes and DocExchange elements in the CPPA and MSG spec with regard to the bootstrap problem in the NCPA. My conclusion is that we can be specify them to be set to define a minimum-subset of MSH function that is probably not much more than "vanilla SOAP" and in any case, leaves nothing to negotiate about use of ebXML messaging. I propose that we define these elements and attributes accordingly and not try to introduce a pure SOAP binding at this time.
Analysis:
ebXMLSenderBinding and ebXMLReceiverBinding: Following are the elements and their functions:
ReliableMessaging: If present, reliable messaging is to be used.
PersistDuration: Used only for reliable messaging.
xxxNonRepudiation: Used only for message security.
xxxDigitalEnvelope: Used only for message security
NamespaceSupported: Used with MSG options, extensions, and body parts
MessagingCharacteristics: All of its attributes relate to Reliable Messaging.
syncReplyMode: reliable messaging
ackRequested: reliable messaging
ackSignatureRequested: reliable messaging
duplicateElimination: Used mostly for reliable messaging. If there is any other use, it is optional.
actor: reliable messaging (supports ackRequested)
Conclusions:
It appears that all of the child elements of ebXMLSenderBinding and ebXMLReceiverBinding can be properly omitted. The effect of omission is that neither reliable messaging nor message security will be used. It is probably not necessary to say anything more in the CPPA spec about the effect of omitting all of them.
All of the attributes of MessagingCharacteristics relate to reliable messaging. If all the child elements are omitted under ebXMLxxxBinding, the MessagingCharacteristics attributes are probably ignored. However to be sure, we can specify in the NCPA that syncReplyMode="none",
ackRequested, ackSignatureRequested, and duplicateElimination = "never". The CPPA spec states that the value of the actor attribute is ignored if ackRequested="never", so either of the enumerated values will work.
At least for version 1, the NCPA can omit reliable messaging and message security. NameSpaceSupported is only needed if we need to specify body parts for negotiation messages. Therefore, it should be sufficient for elimination of the messaging bootstrap problem to omit all of the child elements of ebXMLxxxBinding and set all the MessagingCharacteristics attribute values to those listed above. NOTE: The default values of the attributes of MessagingCharacteristics are not appropriate.
Regards,
Marty
*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
----- Forwarded by Martin W Sachs/Watson/IBM on 07/30/2002 04:07 PM -----
07/24/2002 09:59 AM | To: ebxml-cppa@lists.oasis-open.org, ebxml-cppa-negot@lists.oasis-open.org cc: From: Martin W Sachs/Watson/IBM@IBMUS Subject: vanilla SOAP binding |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC