[OASIS Issue Tracker] (OSLCCORE-127) OSLC Query doesn't describe paging

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

    [ https://issues.oasis-open.org/browse/OSLCCORE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68477#comment-68477 ] 

James Amsden commented on OSLCCORE-127:
---------------------------------------

OSLC Core 3.0 describes resource paging:
1) OSLC paging is a SHOULD.
2) LDPC paging is a MAY

I think we got the preference between OSLC 2.0 and LDP wrong in 3.0. OSLC 2.0 should take precedence over LDP because integration and interoperability is its primary goal, not to be compatible with a technology that may not be widely implemented by current OSLC enabled tools. See https://www.w3.org/wiki/LDP_Implementations.

> OSLC Query doesn't describe paging
> ----------------------------------
>
>                 Key: OSLCCORE-127
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-127
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> The OSLC Query spec does not define paging. The earlier and now obsolete OSLC simple query defined paging support using oslc.limit and oslc.offset.
> OSLC Core 3.0 describes resource paging:
> 1) LDPC paging is a SHOULD
> 2) OSLC paging is a MAY.
> However LDPC paging was defined after the OSLC Core 2.0 specs were published. If a server implements paging, it is most likely for query results. Query results are more likely to use OSLC paging in existing implementations. Does Core 3.0 need to be changed to reflect a changed order, or perhaps both #1 and #2 should be a MAY?
> I think the query spec should discuss paging, but reference OSLC Core for the details. OSLC Core should reference the current LDPC paging information at https://www.w3.org/2012/ldp/hg/ldp-paging.html. Since query results may contain additional triples from associated resources of member resources through the use of nested oslc.select properties, the spec should give some guidance as to how the page boundaries might be implemented.



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