Re: [web-annotation] Reference to text encoding in spec perhaps not appropriate

We discussed this in our [WG 
call]( today 
and I drew the action item to update this thread :-)

I18N recommends that the "normalization" paragraph be removed 
unless/until specific requirements are developed. In addition, we 
don't believe that Unicode Normalization, either directly or 
indirectly through DOM String Comparison, should be applied. Whether 
whitespace or markup normalizations are applied depend on your WG's 
requirements, not on any specific I18N concern.

We also suggest that a health warning about the need to Unicode 
Normalize on comparison (matching of the TextQuoteSelector to the 
source text) should be included, provided that you intend 
differently-encoded-but-Unicode-equivalent sequences to match (the 
Ivan/Ivan discussion above). If that is not your intention, then you 
might consider the counter health warning (that distinct sequences 
that represent the same "logical" character will not match each other)
 with a pointer to Charmod-Norm.

GitHub Notification of comment by aphillips
Please view or discuss this issue at
 using your GitHub account

Received on Thursday, 2 June 2016 16:49:05 UTC