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

Normalization is for ease of comparison plus robustness across 
formats.  For example, if you don't normalize whitespace from HTML and
 then search for it in text/plain where the whitespace is meaningful 
(and hence has been normalized already because users will see it), 
then it won't match.  Similarly for entities, tags and other markup.

Of course, any search will be heuristic as to what matches and what 
doesn't. 

I don't see a solution that will get us to a CR text by the end of 
this week?

-- 
GitHub Notification of comment by azaroth42
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/227#issuecomment-223064772
 using your GitHub account

Received on Wednesday, 1 June 2016 17:25:10 UTC