- From: BigBlueHat via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Nov 2015 15:42:48 +0000
- To: public-annotation@w3.org
@elf-pavlik I don't see ordering, collections, or even paging as an API specific feature--and dearly want Collection style stuff spec'd somewhere or other. In my current desired use case, I'm wanting to add "static" annotations to a filesystem (think Jekyll sites on GitHub Pages, for example), and would like to include paged collections of them in "blog order" (newest first) as I would with RSS and Atom Feeds. If the single collection file grows unwieldy, I would (reasonably) want to paginate them and/or break them into related collections (by month, week, etc). Expressing all of that should be possible, is not specific to API usage, and would sure be handy to have defined somewhere. :smile: Right now, it seems that ActivityStreams 2.0 [OrderedCollection](http://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection) and [OrderedCollectionPage](http://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollectionpage) do come the closest to the above use case requirements. Given @tilgovi's scalability points (and the likelihood of one or more annotations appearing in one or more pages when using `offset` or similar), we should plan to accommodate that overlap and the possibility that ordering MAY be ignored if the client is not interested--or plans to resort on some other priority (page position order vs. date order). A fun problem to be sure. :smiley: -- GitHub Notif of comment by BigBlueHat See https://github.com/w3c/web-annotation/issues/50#issuecomment-153057263
Received on Monday, 2 November 2015 15:42:50 UTC