- From: C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>
- Date: Tue, 13 Jun 2023 06:54:02 -0600
- To: Norm Tovey-Walsh <norm@saxonica.com>
- Cc: public-ixml@w3.org
Norm Tovey-Walsh <norm@saxonica.com> writes: > I reworded your proposed text a bit: > > <p><add>An application has some latitude when serializing XML. > Particular attention should be paid to serializing whitespace and > other control characters. Consider, for example, the case where the > characters <code>#a</code> or <code>#d</code> appear in a value > serialized as an attribute. When that serialized XML is parsed, the > XML parser will replace <code>#a</code> and <code>#d</code> characters > with spaces when it performs whitespace normalization on the attribute > value. Similarly, the sequence <code>#d#a</code> will be translated to > a single <code>#a</code> by standard XML parsing. If the user of the > grammar expects to see the original characters in the XML output, it > will be necessary to encode them using numeric character references > when serializing the XML output. If on the other hand the user of does > <em>not</em> expect to see the original characters in the output, then > carefully preserving them using numeric character references is likely > to be unhelpful. See [<a href="#serialization">Serialization</a>] for > detailed discussions.</add></p> Works for me. Thanks. -- C. M. Sperberg-McQueen Black Mesa Technologies LLC http://blackmesatech.com
Received on Tuesday, 13 June 2023 12:54:42 UTC