Draft resolution for issue 59

 Hi all, 
 I was tasked to draft a resolution for the issue #59 [1]. The
issue is about requirement 609 which says "The XMLP specification
may mandate the use of a specific character encoding".
 During the telcon discussion, the sentiment was that since the
spec is now infoset based, this issue should only matter to
transport bindings which serialize the infoset. XML 1.0 requires
that processors support at least the encodings UTF-8 and UTF-16, 
other encodings may be supported.
 The proposed resolution text:

 >>It is the responsibility of transport bindings to specify how 
the infoset is being transfered to and reconstituted by the 
binding at the receiving node. Such a binding, if using XML 1.0 
serialization of the infoset, may mandate that a particular 
character encoding or set of encodings be used.
 The SOAP HTTP binding does not mandate any character encoding. 
When using other encodings than UTF-8 and UTF-16 (mandated by the 
XML 1.0 specification), the application designer must be aware of 
possible interoperability issues. It is therefore advisable that 
messages sent to unknown endpoints use UTF-8 or UTF-16.<<

 Best regards,

                   Jacek Kopecky

                   Senior Architect, Systinet (formerly Idoox)

Received on Friday, 22 February 2002 08:25:17 UTC