W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2002

Re: Draft resolution for issue 59

From: <noah_mendelsohn@us.ibm.com>
Date: Sun, 24 Feb 2002 10:40:19 -0500
To: Jacek Kopecky <jacek@systinet.com>
Cc: xml-dist-app@w3.org
Message-ID: <OFC6432CBB.099BF3BA-ON85256B6A.00567150@lotus.com>
Since we don't require use of XML 1.0 at all, I think it's confusing and 
redundant to try and restate what XML 1.0 is.  If some particular binding 
wants to adopt a UTF-8 only, ASCII only, or UTF-16 only subset of XML 1.0, 
that's no more prohibited by us than not using XML 1.0 at all.  I would 
say:

>>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.

<optionalIWouldSkipThis>
NOTE: for bindings using XML 1.0 
serializations, interoperability may be increased if support
for UTF-8 and/or UTF-16 is included.  Support for these
encodings is mandated in all XML 1.0 processors, so 
implementations are widely available.
<optionalIWouldSkipThis>
<<

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







Jacek Kopecky <jacek@systinet.com>
Sent by: xml-dist-app-request@w3.org
02/22/2002 08:25 AM

 
        To:     <xml-dist-app@w3.org>
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        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)
                   http://www.systinet.com/
Received on Sunday, 24 February 2002 10:54:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:06 GMT