Re: ISSUE-71: annotatorsRef

(putting Chase and Kevin into CC, and moving this to the comments list),

Hi Yves, all,

Am 12.01.13 15:29, schrieb Yves Savourel:
> Hi all,
>
>> ii) Should annotatorsRef be updated when new provenance records are
>> created?
> Good question. Presumably, if a user agent modifies one data category on a specific node it should update the annotatorsRef for that node/data category (if one exists), even if it didn't create all the entries (in the Provenance or LQI cases). One do lose some information, but I can't see how we could preserve it.
>
> But this leads to a problem: some data categories don't require annotatorsRef so a user agent A could generate them and set annotatorsRef, then a second user agent B could modify the annotation but not the annotatorsRef because it is not required to support it.
>
> 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.

Best,

Felix

>   
>
>> iii) Can a single annotatorsRef attribute value contain multiple
>> entries for a single data category?  For example, if multiple
>> automated quality tools (with IRIs "FOO" and "BAR") process a single
>> file, could the annotatorsRef value be encoded like this?
>> <doc its:annotatorsRef="lq-issue|FOO lq-issue|BAR">
> I would expect no. And that is even in relation to the question above: Having several annotator referenced for Provenance (or LQI) where you can have several entries on the same node. There would be no way to know which entry was done by which annotator.
>
> cheers,
> -ys
>
>

Received on Monday, 14 January 2013 14:11:40 UTC