SOAP Message Transmission Optimization Mechanism
W3C Working Draft 09 February 2004
Section 4.3.1 Sending a SOAP message
The XOP package is constructed as described in 3. An Optimized MIME Multipart Serialization of SOAP Messages with the following restriction:
· Each optimized Node MUST generate exactly one extracted binary part in the resulting package, i.e., extracted binary parts MUST NOT be referenced with more than one xop:Include in the SOAP message part.
If transmission optimization is the goal of this effort, why do you specifically disallow reuse of a binary package that has been isolated in the document? I realize this may make some processing models more complex but the potential benefit is very significant. Messaging in military systems tends to have repeated information (the exact value of which is not predictable in advance but which reoccurs daily in many messages of all types). When a value (such as GPS, time, call-sign, unit-id) is used it is often repeated. While XML design considerations might allow reuse of the information via ID and IDREF, the influence of legacy systems (an environment that would not accommodate such referential complexity very well) continues to make such an alternative infeasible.
Independent of my operational concerns for the Army, it does seem that you would want to recognize that an optimization of the message transmission should allow the potential for re-use of a defined binary representation when an opportunistic optimizer “discovers” it.
Dr. Frank J. Mabry, Jr.
Dept. of EE&CS
U.S. Military Academy
West Point, NY 10996
”The great use of life is to spend it for something that will outlast it.” – William James