[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:all-tabpanel ]

David Honey updated OSLCCORE-127:
---------------------------------

    Description: 
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.

  was: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. Clearly, in OSLC 3.0, the intent is to leverage OSLC LDPC paging semantics. However, the OSLC Query spec does not define the query result as an LDPC. Should we leave query paging support effectively undefined, or should we make the query result an LDPC that can support paging?


> 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.



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