Document Envelope

["Jean-Jacques Dubray" <jeanjadu@Attachmate.com>]

I must admit that I did not follow too well the arguments about document
envelope in the call today.

For me Document Envelope has a series of attributes 

isPositiveResponse 	: maps easily to web service operations
isAuthenticated  		: maps easily to WS-Security
isConfidential  		: requires encryption
isTamperDetectable  	: requires digital signature

All these attributes can be mapped easily to existing WS technologies. 

So I can easily define a binding for these attributes if this document
envelope were to be exchanged in the context of an operation activity,
but I don't have to change their meaning like I would need to do to map
an operation to a business transaction. This actually illustrates my
point is that we can make the ebXML and WS stacks co-exist, but I don't
think we are ready to merge them until ebXML layers itself on top
of/with the WS stack.

Am I missing something?

JJ-