[OASIS Issue Tracker] (OSLCCORE-143) OSLC query does not specify how oslc.orderBy affects the results

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

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

James Amsden commented on OSLCCORE-143:
---------------------------------------

then we can introduce an oslc:orderBy property what has range int, and specifies the sort position of the member result.

However there are two additional points to consider. One is that introducing a sort ordering property essentially punts on ordering and pushes it back to the client. A client could just as well leave out the orderBy and sort the members on the property they wanted in the first place. Its better than nothing, but not much.

Second, it is likely that a lot of clients using OSLC query are using XML to parse the results and are likely expecting the members to be listed in sorted order. We may have to retain that capability, even though it has no meaning or use in RDF.

> OSLC query does not specify how oslc.orderBy affects the results
> ----------------------------------------------------------------
>
>                 Key: OSLCCORE-143
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-143
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> OSLC Query 2.0 describes an oslc.orderBy query parameter. However, our returned results use unordered representations such as a list of statements with rdfs:member. If the query response is non-paged, then oslc.orderBy serves no purpose - a consumer cannot determine the order from the returned RDF.
> It potentially serves a purpose for a paged response (either LDPC paging, or OSLC paging), where the first page should contain a subset of the sorted members starting at the beginning and so on. The OSLC Query 2.0 does not describe this usage pattern so it's unclear whether anything more was intended.



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