ISSUE-33: Pagination for non-container resources

pagination

Pagination for non-container resources

State:
CLOSED
Product:
Linked Data Platform Spec
Raised by:
Richard Cyganiak
Opened on:
2012-11-05
Description:
Pagination is handy for containers, but actually equally necessary for any kind of resource.

Many resources in a graph have lots of in- or outlinks with the same property: a person's friends, an author's publications, a company's employees, a class's members, a geographical area's contained entities, and so on.

If a node has many arcs, the representation can become way too large, so that GET and PUT become impractical.

The solution would be to split these properties out into a separate document, and enable paging over that document. The paging mechanism currently defined for containers seems to be perfectly adequate for this, except that the problem described is independent from the question whether the resource and its arcs have some sort of container/composition semantics.

Like in containers, it is useful for a client to know the ordering in which the paging happens, or even to be able to affect the ordering.

Related stuff:

* TimBL's seminal “Linked Data” post already has hints of this problem in the section on “Limitations on browseable data”: http://www.w3.org/DesignIssues/LinkedData.html

* A D2RQ issue for implementing this: https://github.com/d2rq/d2rq/issues/126

* ISSUE-18 (robust pagination)
Related Actions Items:
Related emails:
  1. LDP Rec (from eric@w3.org on 2015-02-20)
  2. Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior - take #2 (from henry.story@bblfish.net on 2013-04-29)
  3. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from ashok.malhotra@oracle.com on 2013-04-05)
  4. Re: ISSUE-33 (from andy.seaborne@epimorphics.com on 2013-02-11)
  5. Re: ISSUE-33 (from Erik.Wilde@emc.com on 2013-02-11)
  6. Re: ISSUE-33 (from sergio.fernandez@salzburgresearch.at on 2013-02-11)
  7. Re: ISSUE-33 (from Erik.Wilde@emc.com on 2013-02-11)
  8. Re: ISSUE-33 (from sergio.fernandez@salzburgresearch.at on 2013-02-11)
  9. Re: ISSUE-33 (from Erik.Wilde@emc.com on 2013-02-11)
  10. Re: ISSUE-33 (from henry.story@bblfish.net on 2013-02-11)
  11. ISSUE-33 (from Erik.Wilde@emc.com on 2013-02-11)
  12. Re: LDP Agenda for December 17, 2012, with a list of issues to be closed (from kevin.page@oerc.ox.ac.uk on 2012-12-17)
  13. Re: forms, direction, query, etc Š (from henry.story@bblfish.net on 2012-11-24)
  14. Re: forms, direction, query, etc Š (from Erik.Wilde@emc.com on 2012-11-23)
  15. Re: forms, direction, query, etc … (from kidehen@openlinksw.com on 2012-11-21)
  16. Re: forms, direction, query, etc … (from henry.story@bblfish.net on 2012-11-21)
  17. Re: forms, direction, query, etc … (from Roger.Menday@uk.fujitsu.com on 2012-11-21)
  18. Re: forms, direction, query, etc … (from lehors@us.ibm.com on 2012-11-20)
  19. Re: forms, direction, query, etc … (from kidehen@openlinksw.com on 2012-11-20)
  20. Re: forms, direction, query, etc … (from lehors@us.ibm.com on 2012-11-20)
  21. Re: forms, direction, query, etc … (from Roger.Menday@uk.fujitsu.com on 2012-11-20)
  22. Re: forms, direction, query, etc … (from henry.story@bblfish.net on 2012-11-20)
  23. Re: forms, direction, query, etc … (from olivier.berger@it-sudparis.eu on 2012-11-19)
  24. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from roger.menday@uk.fujitsu.com on 2012-11-15)
  25. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from a.loizou@vu.nl on 2012-11-15)
  26. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from kidehen@openlinksw.com on 2012-11-14)
  27. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from kidehen@openlinksw.com on 2012-11-14)
  28. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from henry.story@bblfish.net on 2012-11-14)
  29. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from Erik.Wilde@emc.com on 2012-11-13)
  30. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from henry.story@bblfish.net on 2012-11-13)
  31. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from Erik.Wilde@emc.com on 2012-11-13)
  32. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from Erik.Wilde@emc.com on 2012-11-13)
  33. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from roger.menday@uk.fujitsu.com on 2012-11-13)
  34. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from henry.story@bblfish.net on 2012-11-13)
  35. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from henry.story@bblfish.net on 2012-11-13)
  36. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from roger.menday@uk.fujitsu.com on 2012-11-13)
  37. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from henry.story@bblfish.net on 2012-11-13)
  38. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from Erik.Wilde@emc.com on 2012-11-13)
  39. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from henry.story@bblfish.net on 2012-11-13)
  40. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from Erik.Wilde@emc.com on 2012-11-12)
  41. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from henry.story@bblfish.net on 2012-11-12)
  42. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from Erik.Wilde@emc.com on 2012-11-12)
  43. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from Erik.Wilde@emc.com on 2012-11-12)
  44. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from henry.story@bblfish.net on 2012-11-12)
  45. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from Erik.Wilde@emc.com on 2012-11-12)
  46. Re: ldp-ISSUE-33 (pagination): how to structure functionality (from ashok.malhotra@oracle.com on 2012-11-12)
  47. ldp-ISSUE-33 (pagination): how to structure functionality (from Erik.Wilde@emc.com on 2012-11-12)
  48. Re: Can ISSUE-7 be closed? (from andy.seaborne@epimorphics.com on 2012-11-07)
  49. Re: (un)blessed container use cases and implementation expectations (from andy.seaborne@epimorphics.com on 2012-11-07)
  50. Re: Can ISSUE-7 be closed? (from lehors@us.ibm.com on 2012-11-06)
  51. Can ISSUE-7 be closed? (from richard@cyganiak.de on 2012-11-06)
  52. Re: (un)blessed container use cases and implementation expectations (from richard@cyganiak.de on 2012-11-06)
  53. ldp-ISSUE-34 (aggregation): Adding and removing arcs in weak aggregation [Linked Data Platform core] (from sysbot+tracker@w3.org on 2012-11-05)
  54. ldp-ISSUE-33 (pagination): Pagination for non-container resources [Linked Data Platform core] (from sysbot+tracker@w3.org on 2012-11-05)

Related notes:

[davidwood]: Pagination for non-container resources

14 Mar 2013, 19:00:11

RESOLVED: Close ISSUE-33 by saying that the same pagination mechanism defined for LDPCs be adopted for LDPRs.
(FTF2 on second day)

David Wood, 14 Mar 2013, 19:03:12

Resolution: Close ISSUE-33 by saying that the same pagination mechanism defined for LDPCs be adopted for LDPRs.
See http://www.w3.org/2012/ldp/meeting/2013-03-14#resolution_1

Arnaud Le Hors, 16 Mar 2013, 03:49:32

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 33.html,v 1.1 2015/08/17 04:43:08 denis Exp $