W3C home > Mailing lists > Public > xml-dist-app@w3.org > October 2000

RE: Issues with Packaging Application Payloads

From: David Ezell <David_E3@Verifone.Com>
Date: Thu, 19 Oct 2000 08:51:58 -0400
Message-ID: <472E220BA79DD11186340060B06B38D9033ACFC2@tpantmail1.ssr.hp.com>
To: "'HUGHES,MARK (Non-HP-FtCollins,ex1)'" <mark_hughes@non.hp.com>
Cc: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
On Thu 10/19/2000 8:43 AM David Ezell (myself) wrote:
>On Wed 10/18/2000 6:27 PM +5:00 Mark Hughes wrote:
>>  Then there's #4, the *RIGHT WAY* to do this, which is:
>>A) Before inserting your arbitrary text into your XML wrapper, run it
>>through a filter that replaces & with &amp;, < with &lt;, and > with &gt;.
>>B) Before handing arbitrary text back to the user, run it through a filter
>>that replaces &lt; with <, &gt; with >, and &amp; with &.
>>  Voila, the problem is solved.  You don't have the byte bloat of base64,
>>you don't have the limitation of not including ]]> in CDATA, and you don't
>>have to mess up validation.
>Not a bad idea for simple uses, but it won't nest (at least I don't think it
>the export filter would convert all the PCDATA at once.  It seems to me a safe
>that if you need to nest one level, you'll have use cases for nesting to N
>It may be that the other suggestions suffer the same drawback.

I was wrong -- it will nest (at least I think it will :-) ).  

Received on Thursday, 19 October 2000 08:52:06 UTC

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