I believe you, but that's not what is in the spec now. Right now the spec just says that OnceAndOnlyOnce means the message must be sent using a reliableMessagingMethod that will result in the application or other process at the To Party receiving the message once and only once (10.2.1). This does not sound like it must be done using ebXML RM. This says ANY RM method will do. What would it take to make the spec fit your drawing (which would also eliminate the issue about unreliable nodes)? At the very least we would have to eliminate the reliableMessagingMethod attribute. We would also have to specify somewhere that if ebXML RM is not supported then send back an error (DFN). Is this what we want to do? David Fischer Drummond Group.
