[annotator-dev] how to deal with content change.

[Randall Leeds]

If you want to have some robustness to change and attempt to show
annotations where they match, there are approaches to this, but they're not
easily integrated into Annotator. There is an example of this in the
Hypothesis code, but it deeply overrides Annotator's methods.

If you are interested in exploring this I can offer you pointers, but if
failing fast is okay for you that's the easiest thing.

On Wed, Jul 12, 2017 at 10:21 AM Shi Yan <billconan at gmail.com> wrote:

> I guess I can self answer my question now after looking at the source code.
>
> annotator has some fault tolerance, if it can't find a matching pattern in
> the current document, the annotation won't be shown.
>
> this is implemented via xpath-range.
>
>
> this fault tolerance is good enough for me I think.
>
> On Thu, Jul 6, 2017 at 12:01 AM, Shi Yan <billconan at gmail.com> wrote:
>
>> hello,
>>
>> I want to integrate annotator to a blog site, similar to Medium.
>>
>> the content on the site, however, is very dynamic, it changes all the
>> time.
>>
>> I'm wondering how to handle this content change properly?
>>
>> For example, a sentence is currently annotated but then gets removed or
>> modified.
>>
>> How do I notify the storage backend to deprecate the old annotation?
>>
>> Or I don't explicitly deprecate the old annotation, I load it anyway and
>> annotator can figure out that the annotation is invalid and won't show it
>> anymore?
>>
>> Thanks,
>>
>> Shi
>>
>
> _______________________________________________
> annotator-dev mailing list
> annotator-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/annotator-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/annotator-dev/attachments/20170712/16f4cf20/attachment-0003.html>