>> What is purpose of representing the contents of Soap Envelope in Soap 1.2
using XML Infosets?

It means that if you want to do an alternative to our HTTP binding, and if
you want to optimize it differently in its representation of XML, you may.
For example, you might do something as simple (if clunky) as indicating
that the XML 1.0 representation is to be zip'd before transmission. The
bits on the wire don't have any straightforward representation of an '<',
but they are still an infoset. Same for encryption. Same for
XML-specific compression schems in which you, for example, send a symbol
table and use some proprietary structure to represent the tree structure
and tags. Of course, there may be strategic reasons why such
representations would be discouraged (proprietary, not widely deployed),
but SOAP allows them. When going to devices connected by very slow links
(think cell phone networks) or when sending encrypted XML it may be
essential.

------------------------------------------------------------------
Noah Mendelsohn Voice: 1-617-693-4036
IBM Corporation Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------







"Naresh Agarwal" <nagarwal@...>
07/23/2002 12:52 AM
Please respond to soapbuilders


To: <soapbuilders@yahoogroups.com>
cc: (bcc: Noah Mendelsohn/Cambridge/IBM)
Subject: [soapbuilders] SOAP1.2 and XML Infosets!


Hi

What is purpose of representing the contents of Soap Envelope in Soap 1.2
using XML Infosets?

Quoting from Soap 1.2 specs --
"The binding framework does NOT require that every binding use the XML 1.0
serialization as "on the wire" representation of the Infoset; compressed,
encrypted, fragmented representations and so on can be used if
appropriate. A binding, if using XML 1.0 serialization of the infoset, MAY
mandate that a particular character encoding or set of encodings be used."
This means that, *potentially*, SOAP messages can be serialized using
something other than XML. I believe that, XML is central to idea of SOAP,
which makes it a far better distributed messaging framework than the
legacy ones. If we remove the "XML Serialization" out of SOAP, would it be
able to keep all its promises??
Any help would be greatly appreciated!
regards,
Naresh Agarwal








-----------------------------------------------------------------
This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues. Please stay on-topic.

To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/