RE: ISSUE-71: annotatorsRef from Yves Savourel on 2013-01-14 (public-multilingualweb-lt-comments@w3.org from January 2013)

From: Yves Savourel <ysavourel@enlaso.com>
Date: Mon, 14 Jan 2013 08:34:50 -0700
To: <public-multilingualweb-lt-comments@w3.org>
CC: "'Chase Tingley'" <chase@spartansoftwareinc.com>, "'Kevin Lew'" <kevin@spartansoftwareinc.com>
Message-ID: <assp.07266e517d.assp.07269918ab.000901cdf26c$b148a410$13d9ec30$@com>

Hi Felix, all,

>> Updating the annotatorsRef also puts a big burden on the implementer:
>> the easiest way to do it is to set it for the modified node, and then
>> you can end-up with a document full of meaningless annotatorsRef 
>> (set on parents and immediately overridden).
>
> I understand the issue, but do you have a solution in mind?
> Just trying to move the discussion forward.

Sorry, no solution in mind for now.

I'm currently trying to implement modify/delete/add functionalities in our HTML5 filter (in addition to just reading the information) and annotatorsRefs is not looking very cooperative so far.

cheers,
-ys

Received on Monday, 14 January 2013 15:35:25 UTC