At the F2F, we identified an issue regarding the Infoset and its serialization in XML. Briefly, SOAP 1.2 is defined as transporting Infosets. However, some bindings may/will not be capable of accepting some Infosets, because different serializations are capable of representing different subsets of the possible range of characters in the Infoset. As a result, there may be interoperability problems when different bindings are in use, and some synthetic Infosets will not be able to be transported by SOAP, even though it currently intimates that they can be. This issue is potentially related to that regarding XML 1.1. -- Mark Nottingham Principal Technologist Office of the CTO BEA SystemsReceived on Wednesday, 3 March 2004 05:19:00 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:14:17 UTC