[OASIS Issue Tracker] (OSLCCORE-144) LDPC paging and max-triple-count

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/OSLCCORE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Honey updated OSLCCORE-144:
---------------------------------

    Summary: LDPC paging and max-triple-count  (was: LDPC paging)

> LDPC paging and max-triple-count
> --------------------------------
>
>                 Key: OSLCCORE-144
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-144
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Core, Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> LDPC Paging described in https://www.w3.org/2012/ldp/hg/ldp-paging.html shows an example of how a client can ask for a paged response with a Prefer header:
>     Prefer: return=representation; max-triple-count="500"
> With a GET of a container that references the members, it's not too difficult to work out which members should be included. However, with OSLC Query, a paged response could include:
> 1) The container and its subset of members in that page.
> 2) Properties of each of those members (perhaps defined by oslc.select)
> 3) Properties of other resources associated with each member defined by nested properties in oslc.select.
> It now becomes problematic to work out what needs to be included in a paged response. #3 could add many more triples to the response. At the least, I would expect the OSLC Query specification to provide some guidance.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)