Article:		XML, SOAP and Binary Data
Subject:		. . . and?
Date:		2003-02-26 22:42:44
From:		W. E. Perry
parturiunt montes, nascetur ridiculus mus: "These are only two examples of how one could preserve the Infoset and avoid the performance issues associated with base64/hex text encoding. They are not fully specified here, but serve to illustrate that viable alternatives to current approaches exist and should be considered before radically changing SOAP and Web services." followed by "Finally (and perhaps most importantly), ALL SOAP messages can be represented in pure text. Even in the face of exotic in-memory or on-disk data structures for representing XML, one can always produce a purely text-based form of the message. The utility of the installed base of text processing tools should not be overlooked. Text is our heritage and abandoning it loses a key feature of the web service architecture." and then by "The authors also believe that the XMLP WG charter allows sufficient freedom in associating opaque data with SOAP Messages to define a SOAP specific processing model, including the XInclude approach, as well as participating in or leading other approaches." Great. No surprises. Defining A/The Processing Model For XML is a familiar xml-dev permathread. Are we to understand that the message of this whitepapaer is that you will in time propose a processing model for merging 'XML Infosets' (your usage of the term), based on and effectively subsuming XInclude? Walter Perry

Previous Message

Next Message