There is no "standard way" because correctness in the face of changes is often subjective.
There is a bit of history around the Annotator and Annotator-derived Hypothesis project of efforts to use different identifiers for ranges as a way to find text that is more likely to be correct than the text that happens to be at the same xpath and offset. The support libraries for this are all standalone modules: https://github.com/tilgovi/dom-anchor-fragment https://github.com/tilgovi/dom-anchor-text-position https://github.com/tilgovi/dom-anchor-text-quote Integration into Annotator v1.2 is not provided anywhere. Hypothesis achieves it be aggressive subclassing and overriding of many of the methods of the Annotator class. I am working now to split apart more of the lifecycle hooks in Annotator v2 so that there are extensibility points for extensions to participate in text range identification using these modules. I don't have a timeline for that. On Thu, Nov 19, 2015 at 1:22 AM Денис Обыденных <denis.obydenn...@gmail.com> wrote: > Hello. > > I've found that in case of changing annotated text - annotations move over > the text. Is there any standard way to fix this? > > Using v 1.2. > > > -- > Всего наилучшего, Обыденных Денис > ICQ: 40-10-808 Skype: denis.obydennykh > http://avtomurmansk.ru/ > _______________________________________________ > annotator-dev mailing list > annotator-dev@lists.okfn.org > https://lists.okfn.org/mailman/listinfo/annotator-dev > Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev >
_______________________________________________ annotator-dev mailing list annotator-dev@lists.okfn.org https://lists.okfn.org/mailman/listinfo/annotator-dev Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev
