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

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





------- Additional Comments From davidc@nag.co.uk  2005-12-13 14:03 -------
I agree that XSLT can't know the semantics of the elements it writes out so
xs:include is probably out of scope, but I'm not sure about entity references.
If I use a character map to write out &foo; and use xsl:output to specify a
doctype that defines foo to be a combining acute can it really be said that the
result is fully-normalised if the result contains e&foo; ? Perhaps it can, as
basically the output of a character map is absolved from requirements of unicode
normalisation, well formedness etc.

> with "fully-normalized" the output cannot start with a composing

yes, so long as by start here you mean start of each text node (or attribute
value) not just the start of the whole result tree?

If that isn't the case I see it raises
err:SERE0012

perhaps it would be helpful if the spec defined rather more explictly than
"any relevant construct"
exactly which constructs are affected.
Presumably this is text nodes and attribute values.
Does it include each individual token in a attribute or text node that is schema
typed with a list type? (If the system knows the result schema)
I'm assuming (but haven't checked) that no NameStartChar are combining
characters (in which case "relevant constructs" would need to include element
and attribute names as well)

David

Received on Tuesday, 13 December 2005 14:04:30 UTC