- From: Robert Sanderson <azaroth42@gmail.com>
- Date: Mon, 16 Sep 2019 12:11:10 -0700
- To: Benjamin Young <byoung@bigbluehat.com>
- Cc: "public-openannotation@w3.org" <public-openannotation@w3.org>
- Message-ID: <CABevsUEp1De+Hb9w5zBnGpa=hUAce=fDfs8V6Vq1f5zMGRAeJA@mail.gmail.com>
Hi Benjamin, I don't follow the concern. The spec doesn't just imply you have to use an AnnotationPage, that is the model we came to. If you're not doing pagination either embedded (as per example 40) or referenced (as per example 38), then you're not consistent with the AnnotationCollection model. Rob On Mon, Sep 16, 2019 at 12:32 AM Benjamin Young <byoung@bigbluehat.com> wrote: > Hi all! > > Recently I was building some small AnnotationCollection objects--where > pagination will (deliberately) not be used. I found example 40 confusing as > it seems to express a requirement that an AnnotationPage inside `first` > must be used. The `items` property is only mentioned (in the Web Annotation > Data Model spec) as being related to AnnotationPage. However, the > ActivityStreams vocabulary we "cribbed" these terms from have different > ranges defined--i.e. CollectionPage extends Collection and `items` is > defined on Collection. > > Consequently, I think Example 40 sends the wrong message and I'd like to > improve it (at least) via errata--and eventually via a spec version bump or > a CG-based revision. > > Example 40: https://www.w3.org/TR/annotation-model/#example-34 > vs. > ActivityStreams 2.0 Collection definition and examples: > https://www.w3.org/TR/activitystreams-core/#collections > > That sound OK and like the right "revisioning" approach? > > Cheers, > Benjamin > > -- > > http://bigbluehat.com/ > > http://linkedin.com/in/benjaminyoung > -- Rob Sanderson Semantic Architect The Getty Trust Los Angeles, CA 90049
Received on Monday, 16 September 2019 19:11:44 UTC