- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Nov 2015 11:32:03 +0000
- To: public-annotation@w3.org
> Even if the whole annotation collection were loaded into memory, you may still want them paginated for display--even if you're merely paginating on the total length of the collection divided by # of items per page. I try to keep distinction between **data model**, API or UI As I understand each Annotation has logical relation with a List of annotations (in this case ordered) and pages have no other purpose than split this list into small chunks when accessed over network http://w3c.github.io/web-annotation/protocol/wd/paging.html#multiple-ordered-responses-with-annotations I see this question possibly helps with clarifying it: If we add more annotations to the list, can they possibly move between pages? Or annotation has permanent relationship with a page which can only change by intentional operation: "Move this annotation from this page to this page" and once again not as side effect of adding annotations to the whole list. Actually in such case, one should never insert annotations directly to the list but always interact only with pages and use the List as collection of pages, not collection of annotations! Pages become here collections of annotations. -- GitHub Notif of comment by elf-pavlik See https://github.com/w3c/web-annotation/issues/50#issuecomment-153325789
Received on Tuesday, 3 November 2015 11:32:04 UTC