- From: Nick Stenning via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 May 2016 08:24:09 +0000
- To: public-annotation@w3.org
Discussed at F2F meeting 2016-05-17. We established, I think, that this concern is fundamentally about annotation clients *modifying* the normalisation of the underlying document, because document editors may have valid reasons for wanting to preserve a particular unicode normalisation in their document (@r12a gave the example of his International Phonetic Alphabet). Perhaps there is an editor action here to add a note to the spec suggesting or requiring the annotation clients do *not* modify the normalisation of the annotated document. If we decide they need to (for example) compute TextPositionSelector indices in terms of the fully-composed normalisation of the document, that should be done *without* modifying the document. -- GitHub Notification of comment by nickstenning Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/222#issuecomment-219958840 using your GitHub account
Received on Wednesday, 18 May 2016 08:24:11 UTC