[Bug 2474] [SER] Can fully-normalized be implemented?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2474





------- Additional Comments From mike@saxonica.com  2006-01-27 19:30 -------
I have been asked to propose clarifying text that will resolve this issue.
(Colin, please let us know whether you are happy with this text: though it's at
the moment only a proposal). 

In Serialization 5.1.8 we currently say:

It is a serialization error [err:SERE0012] if the value of the parameter is
fully-normalized and any relevant construct of the result begins with a
combining character. The serializer MUST signal the error. See Section 2.13 of
[XML11] for the definition of the relevant constructs of XML.

I proposed that we change this to:

If the value of the parameter is <code>fully-normalized</code>, then no
<emph>relevant construct</emph> of the parsed entity created by the serializer
may start with a composing character. The term <emph>relevant construct</emph>
has the meaning defined in section 2.13 of [XML11]. If this condition is not
satisfied, a serialization error [err:SERE0012] MUST be signalled.

Note: specifying <code>fully-normalized</code> as the value of this parameter
does not guarantee that the XML document output by the serializer will in fact
be fully normalized as defined in [XML11]. This is because the serializer does
not check that the text is <code>include normalized</code>, which would involve
checking all external entities that it refers to (such as an external DTD).
Furthermore, the serializer does not check whether any character escape
generated using character maps represents a composing character.

Received on Friday, 27 January 2006 19:30:36 UTC