Re: Single implementation, multiple annotations (model testing)

It makes sense, and I think that is fine as long as we add entries to the
README.md index to explain what each subcode means.

Alternately, I would be interested in seeing what happens if multiple
annotations, each with a variation as you mentioned, are included in a
single message.  I think that the data model accomodates this.  If it were
done that way, would the test just "pass" for all of the various features ?

On Thu, Sep 8, 2016 at 8:21 AM, Cole, Timothy W <t-cole3@illinois.edu>
wrote:

> Shane-
>
> It is commonplace for a single annotation client to generate multiple
> kinds of annotations. Each kind of annotation from a given implementation
> may implement different features of the model. So to capture this
> information, an implementer will need to run multiple annotations through
> our test suite. As best I can tell this means multiple test results
> reports, each of which will need to be submitted to
> http://w3c.github.io/test-results/annotation-model/ each resulting in a
> separate column in the all.html report.
>
> First, is my understanding corrrect, or is there some way to combine test
> result reports?
>
> If my understanding is correct, is it therefore appropriate to use the
> same 2 letter prefix (representing implementation), and then label each
> report with its own 2-digit number? So for Janina's emblem annotation
> client which implements 3 kinds of annotations, she would have EB01, EB02,
> EB03.  EB01 might implement a embedded textual body, while EB02 might
> implement an external Web resource as body, and so on.
>
> Does this make sense?
>
> Thanks,
>
> Tim Cole
>



-- 
Shane McCarron
Projects Manager, Spec-Ops