[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=68480#comment-68480 ] David Honey commented on OSLCCORE-143: -------------------------------------- One of the suggestions in a previous meeting was to use oslc:score. However, that's not suitable since the current spec defines it as being an integer in the range 0..100. If you have more than 101 returned members, you cannot uniquely identify ordering. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]