-
Type: Bug
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Component/s: Core
-
Labels:None
-
Proposal:
Currently the core spec says "OSLC Services may ignore oslc.pageSize."
What this probably means is it could respond with the requested number of values, or it could respond with no paging at all, or it could respond with a different number of values than what was requested. Which means, there really aren't any constraints on the server when the client makes this request, in which case we may as well drop this request option entirely since it duplicates the functionality of oslc.paging=true. Assuming we want to get value from oslc.pageSize, we should probably differentiate between servers that can do paging and simply choose to not do so, or servers that can't support paging at all. Not sure what to do about that but some guidance on discoverability may be in order.