Re: issue-68 from an annotation representation point of view, with potential implications for annotatorsRef and standoff markup

All

@Felix: "But while doing that a question on the LQI/Provenance
implementers: is it a feature that you point to just one external standoff
unit, or an oversight, and it could it be several ones?"

My current thinking is that stand-off stores many annotations for one
segment. This is because if several segments are linked to one stand-off
block, then if one of those segments needs to have another unique issue
registered against it, you have to copy the stand-off, add the unique
annotation and change the reference id's so that the link is between the
segment with the additional annotation and the copied stand-off. Complex.

Another argument for pointing to a single stand-off is that although the
"classification" attributes of the markup might be identical (e.g.
loc-quality-issue-type="style" loc-quality-issue-severity="75") each may
have a different loc-quality-issue-comment to highlight the specific nature
of the error.

Hmm. The benefit of the id being on the segment/element and the idRefs
being on the stand-off really comes into its own if you want to have
multiple annotations across many data categories for the same
segment/element.

<span id="loaded">blah</span>

<its:prov ref="loaded"...
<its:locQualityIssues ref="loaded"...
<its:textAnalysis ref="loaded"
(on the train, I know this is not valid markup.)

Phil



On 28 Jan 2013, at 19:57, "Felix Sasaki" <fsasaki@w3.org> wrote:

> But while doing that a question on the LQI/Provenance implementers: is it
a feature that you point to just one external standoff unit, or an
oversight, and it could it be several ones?


************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail.

www.vistatec.com
************************************************************

Received on Tuesday, 29 January 2013 09:34:56 UTC