W3C home > Mailing lists > Public > xmlp-comments@w3.org > January 2003

XMLP Issue 402: change to Unicode escape sequence algorithm

From: David Fallside <fallside@us.ibm.com>
Date: Wed, 29 Jan 2003 16:14:07 -0800
To: Jim Melton <jim.melton@acm.org>
Cc: xmlp-comments@w3.org
Message-ID: <OF83C33321.92CCDA75-ON88256CBD.0083BDC9@us.ibm.com>

Jim, the XMLP WG today decided to change the description of the "escape
sequence algorithm" in the SOAP 1.2 specification to match the change you
describe. With this action, we will close our issue #402
(http://www.w3.org/2000/xp/Group/xmlp-cr-issues.html#x402) which
corresponds to the change. We trust you will consider this resolution
satisfactory. If not, please contact me asap.

In addition, the WG would like to know about the status of implementations
of the algorithm. In particular, can you tell us whether (a) there exist
implementations of the original algorithm, (b) implementations exist or are
planned for the modified algorithm, and (c) whether you have any developer
feedback on the new algorithm (perhaps the change was in part motivated by
developer feedback?)? Any information you could provide that would help
establish that there exist, or will exist, implementations of the new
algorithm would be useful for us. Thanks.

On behalf of the XMLP WG,
David Fallside

David C. Fallside, IBM
Ext Ph: 530.477.7169
Int  Ph: 544.9665

|         |           Jim Melton       |
|         |           <jim.melton@acm.o|
|         |           rg>              |
|         |                            |
|         |           01/16/2003 07:56 |
|         |           PM               |
|         |                            |
  |                                                                                                               |
  |       To:       David Fallside/Santa Teresa/IBM@IBMUS                                                         |
  |       cc:       sqlx_lst@sql-99.org                                                                           |
  |       Subject:  FYI: SQL/XML changing Unicode escape sequence algorithm                                       |
  |                                                                                                               |


I was given an action item by the group developing the SQL/XML
specification to inform the XML Protocol Working Group of a change being
made to the SQL/XML document.

We are aware that the XML Protocol WG, of which you are the chair, is using

SQL/XML's "escape sequence" algorithm in your specifications.  We also
believe that your use of that algorithm is by copy and not by reference, so

we think that it is incumbent on us to notify you if we change our
algorithm so that you can consider whether or not to change yours
correspondingly.  Please circulate this to your Working Group as you feel

The change that we have made is fairly simple, in fact.  As you will
recall, we represent Unicode characters from the Basic Multilingual Plane
(BMP) either as their native character or as an escape sequence of the form

"_xXXXX_", where "XXXX" represents exactly four hexadecimal digits
(hexits).  Unicode characters not on the BMP were formerly represented by
an escape sequence of the form "_xXXXXXXXX_", using exactly eight hexits.

In order to better align with the Unicode Consortium's requirements and
recommendations, we have agreed to change the non-BMP escape sequence to
use exactly *six* hexits instead of eight: _xXXXXXX_

If you would like more information about this change, you might be
interested to read the paper that proposes this change.  You can find it


Feel free to contact me with questions you might have about this change.

Best regards,
Jim Melton --- Editor of ISO/IEC 9075-* (SQL)     Phone: +1.801.942.0144
Oracle Corporation            Oracle Email: mailto:jim.melton@oracle.com
1930 Viscounti Drive          Standards email: mailto:jim.melton@acm.org
Sandy, UT 84093-1063              Personal email: mailto:jim@melton.name
USA                                                Fax : +1.801.942.3345
=  Facts are facts.  However, any opinions expressed are the opinions  =
=  only of myself and may or may not reflect the opinions of anybody   =
=  else with whom I may or may not have discussed the issues at hand.  =
Received on Wednesday, 29 January 2003 19:17:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:16:59 UTC