W3C home > Mailing lists > Public > xml-dist-app@w3.org > June 2001

RE: [soapbuilders] Element name escaping

From: Andrew Layman <andrewl@microsoft.com>
Date: Tue, 5 Jun 2001 11:24:26 -0700
Message-ID: <C3729BBB6099B344834634EC67DE4AE102623A41@red-msg-01.redmond.corp.microsoft.com>
To: <soapbuilders@yahoogroups.com>
Cc: <xml-dist-app@w3.org>
The most thorough and current documentation of the algorithm for
escaping element names is in this proposal to the SQL standards


See sections 4.2.6, 5.1 and 5.4. 

-----Original Message-----
From: Paul Kulchenko [mailto:paulclinger@yahoo.com] 
Sent: Thursday, May 03, 2001 3:24 PM
To: soapbuilders@yahoogroups.com
Subject: [soapbuilders] Element name escaping

Hi, All!

This question is already covered in XML Protocol issues, but there is no
solution offered, so I would like to get opinions here.

Problem: encoding of element with illegal characters in the name ('a c',
space between a and c)

Possible solutions:
1. specific type, like recently discussed Map. 
  - specific for hash/map/struct encoding
  - didn't get much support
  + already implemented by ApacheSOAP and SOAP::Lite

2. element escaping as in [1]. <a c> becomes <a_x0020_c>
  + works for all elements
  - list of issues [2]
  - doesn't supported by any SOAP toolkit

3. name substitution. <a c> becomes <n1 realname="a c"> [3]
  + works for all elements
  + less number of issues than 2.
  - doesn't supported by any SOAP toolkit

I personally like 2, but I couldn't find document Andrew mentioned in
[1], and current webDAV specification doesn't have anything about
character escaping (or I missed it there). So, what's everybody's
opinion on encoding elements with illegal names?
Best wishes, Paul.


Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices

To unsubscribe from this group, send an email to:


Your use of Yahoo! Groups is subject to
Received on Tuesday, 5 June 2001 15:42:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:13 UTC