OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

James Amsden commented on OSLCCORE-143:

orderBy could be extended to include the oslc:order property for the members. And this could be applicable even if there is no oslc:select that includes the orderBy property - the members can be sorted whether the sortBy, or any other  property is included or not.

Another approach, and probably what is currently done, is to simply require the response body to order the members in the RDF resource representation (syntatically). In this case, clients would be expected to use something other than an RDF parser to consume the resource - perhaps XPath, or some JSON query mechanism. Not sure we need to specify any more than that.

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]