One member expressed concern that we express our concerns to ensure real solutions. Entering data on a Web form which stores that data at the server doesn't solve the local user's need. Another example are all the shadow systems of 3270 transactions because the office's can't get at the data once it's entered. And office fills out a Purchase Order request and keeps a copy, then gets a copy of the purchase order and files that. When the invoice comes in, the office compares these filed items in a post-processing step.
Electronic messaging needs to support users capturing data locally to support similar processing.
We don't want this aspect of messaging to devolve to policy statements on how business processes are to operate, because that fight tends to be lost in long run. We don't want to come up with standards that prolong need for shadow systems. We might end up writing guidelines, not standards. All who touch data have interests in it, call them workflow interests. Need to be aware of data residency in stream and out of stream.