- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jun 2016 12:49:55 +0000
- To: public-annotation@w3.org
> And if there were copy paste-s done when putting together the text, then the representation of the same text may be slightly different within the text… Hence the normalization. @iherman too many 'text' words there for me to be sure what you're saying. The only way i can see to understand this is if the Text Position Selector values are manually created by users looking at the target text and typing what they think they see into the annotation body. Is that a valid use case? I don't see how normalization helps distinguish between possible matches when there are mutliple alternative ranges of text in the target document that match the text position selector values. If anything, i'd have thought it would do the opposite, by removing idiosynchratic differences, which is what normailzation is about. If you want to find all possible matches, then that's fine, but i think that here we want to find the unique match where possible, no? -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/227#issuecomment-222982149 using your GitHub account
Received on Wednesday, 1 June 2016 12:49:57 UTC