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.