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

RE: [soapbuilders] Element name escaping

From: Paul Kulchenko <paulclinger@yahoo.com>
Date: Tue, 5 Jun 2001 15:31:39 -0400 (EDT)
Message-ID: <20010605193127.89130.qmail@web13506.mail.yahoo.com>
To: soapbuilders@yahoogroups.com
Cc: xml-dist-app@w3.org
Hi, Andrew!

--- Andrew Layman <andrewl@microsoft.com> wrote:
> The most thorough and current documentation of the algorithm for
> escaping element names is in this proposal to the SQL standards
> committee:
> 
>
ftp://sqlstandards.org/SC32/WG3/Progression_Documents/WD/wd-xml-2001-05.pdf
> 
> See sections 4.2.6, 5.1 and 5.4. 
I think spec has a typo:

5.4 2) a) i) If i = 1 and X i+3 , X i+4 , X i+5 , and X i+6 are all
F, then let U 1 , U 2 , U 3 , U 4 , U 5 , U 6 , and U 7
be the zero-length string.

I believe it should be:

5.4 2) a) i) If i = 1 and X i+2 , X i+3 , X i+4 , and X i+5 are all
F, then let U 1 , U 2 , U 3 , U 4 , U 5 , U 6 , and U 7
be the zero-length string.

considering the context.

To advantage of this method, it can be implemented on top of existent
encoding, and since it basically ignores underscores ('_') if it
doesn't match pattern _xNNNN_ or _xNNNNNNNN_, there is no (big)
problem with backward compatibility.

What should be the next step? What should be the procedure in
general: 
  spec is published, 
  spec has an issue, 
  issue discussed and solutions are offered, 
  one solution is choosen,
  ?
  solution is implemented.

What should be in place of the question mark? New version of spec is
published? Some agreement is published? Comments are published? We
agree on soapbuilders list? At what point we can say: "ok, now let's
do it this way"? Thank you.

Best wishes, Paul.

> -----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.
> 
> [1]
>
http://discuss.develop.com/archives/wa.exe?A2=ind0005&L=soap&D=0&P=29921
> [2]
>
http://discuss.develop.com/archives/wa.exe?A2=ind0005&L=soap&D=0&P=30851
> [3]
>
http://discuss.develop.com/archives/wa.exe?A2=ind0005&L=soap&D=0&P=33153
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/
> 
> To unsubscribe from this group, send an email to:
> soapbuilders-unsubscribe@yahoogroups.com
> 
>  
> 
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/ 
> 
> 
> 
> To unsubscribe from this group, send an email to:
> soapbuilders-unsubscribe@yahoogroups.com
> 
>  
> 
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/ 
> 
> 


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/
Received on Thursday, 7 June 2001 10:40:46 GMT

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