[Bug 4030] [F+O] "may not" ambiguity

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





------- Comment #2 from davidc@nag.co.uk  2006-12-04 15:52 -------
(In reply to comment #1)

> I believe the "may not be normalized" means may or may not be normalized -- in
> the sense that there is no need to normalize the result.  This reads OK to me
> but if you feel strongly we can change to "may or may not be normalized". 

I'm not the original poster, but I think that change would make things more
confusing.

I think the main confusion arises because it is not clear (either in the spec,
or in the comment #1 quoted above whether "normalized" in "may not be
normalized" refers to the action of applying the normalization algorithm, or
a description of the resulting string being in normal form.

The sentence in 7.1 and the later example in section 7.4.1 make clear, Unicode
Normalization will _not_ be applied automatically, this has the effect that the
result of concat (like any string) may or may not be "normalized"
in the sense that it may or may not be in one of the Normal forms.

So I'd suggest changing the first sentence of the note in 7.4.1 to say

As mentioned in [Section 7.1 String Types] Unicode normalization is not
automatically applied to the result of fn:concat.

Received on Monday, 4 December 2006 15:52:54 UTC