RE: Section 4.3 reference to character model

Unfortunately, we cannot take a normative dependence on the Character
Model because it's not finished yet.  That also makes it risky to copy
text from the Character Model into our spec, as it might change and get
out of sync. The compromise we were able to reach resulted in the
non-normative reference making implementers aware that the Character
Model is relevant to parse="text".  The WG doubts it can do better than
that.  Implementations must conform separately to XInclude and the
Character Model.  There should be nothing in XInclude that prevents
conformance to the Character Model for parse="text" inclusions.

Please let us know if this explanation is sufficient to close this
issue.

> -----Original Message-----
> From: www-xml-xinclude-comments-request@w3.org
[mailto:www-xml-xinclude-
> comments-request@w3.org] On Behalf Of Elliotte Harold
> Sent: Thursday, January 29, 2004 1:56 PM
> To: www-xml-xinclude-comments@w3.org
> Subject: Section 4.3 reference to character model
> 
> 
> Section 4.3 states:
> 
> The [Character Model]
> <http://www.w3.org/TR/2003/WD-xinclude-20031110/#CharMod> discusses
> normalization of included text.
> 
> 
> I'm afraid that's at most suggestive. This needs to be spelled out
> further. For example, at one extreme do you mean to say that when
> parse="text", then the text must be include normalized (which implies
> Unicode NFC) as defined in section 4.2.2 of the Character Model draft?
> Or perhaps the other extreme, of simply non-normatively referencing
this
> spec in order to make implementers aware of the issues of text
> normalization? Or something in between or completely different? The
> Character Model reference in the bibliography is in the non-normative
> section.
> 
> I think it's very important to tighten up this sentence, and make it
> clear whether this is a mandatory requirement or a non-normative
> reference.
> 
> --
> Elliotte Rusty Harold
>

Received on Wednesday, 25 February 2004 19:26:40 UTC