On Fri, 30 Jan 2009, Robert Burrell Donkin wrote:
...
Proposal
--------
To "4.2. Structured Comments" Add:
If "*/" is found in the XML content, when mapped into a comment it
would prematurely terminate that comment. Escaping of this sequence
would often be inconvenient for processors. Editors SHALL NOT include
"*/" within displayblock, displaydata or foreign markup. Processors MAY
regard documents containing "*/" in foreign markup, displayblock
or displaydata as invalid.
Ick. Wouldn't it be better to tell processors to generate '#' style
comments instead of /*...*/ style comments, at least in that case?
To "5. Security Considerations" Add:
Little effective protection can be offered by a processor to the user
of a malicious editor.
How is this specific to sieve-in-xml and not just a general consideration
for anyone using any editor for any purpose?
Philip Guenther