new issue against 1.2: serializable range of characters in Infosets

At the Cannes F2F, we identified an issue against SOAP 1.2. SOAP 
specifies that XML Infosets are the fundamental unit of messaging in 
SOAP, and that it's the binding's job to faithfully transport the 
Infoset.

However, there are some Infosets that bindings will not be capable of 
transporting, because different versions of XML are capable of 
serializing different ranges of Unicode characters. For example, an XML 
contains several control characters that are not legal in XML 1.0; 
furthermore, there are characters that are legal in an Infoset that 
cannot be serialized in any existing version of XML.

As a result, it may be necessary to clarify what SOAP1.2 is capable of 
transporting, and/or clarifying the responsibilities of a binding.

--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems