Well, we decided already to change reviewing to assessing, which is in the
most recent editor's draft on github :)
I expect this version is what will be taken to CR, so it should hopefully
go up on W3C by the end of the June.
And then dqv:qualityAssessing skos:broader oa:assessing seems like an easy
addition.
http://w3c.github.io/web-annotation/model/wd2/#motivation-and-purpose
Rob
On Wed, Jun 1, 2016 at 6:38 AM, Antoine Isaac <aisaac@few.vu.nl> wrote:
> Dear all,
>
> Thanks for the feedback on this.
>
> I will forward the suggestions for motivation vs subclassing.
>
> About the introduction of new motivation(s) in WA to support our case: I
> think Rob's solution is workable on our side.
> Is it possible to know when the WA group would make a decision about it?
> I reckon that if DQV keeps dqv:qualityAssessment and the only change we
> have to make is to add a skos:broader statement between it and a new
> 'assessment' motivation in the WA namespace, this can be done very easily.
> But it would make our life easier if we can have an idea of when the
> motivation would be available for us to link to.
>
> Cheers,
>
>