[OASIS Issue Tracker] (OSLCCORE-149) Behaviour if oslc.orderBy specifies an unsupported ordering property

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

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

David Honey commented on OSLCCORE-149:
--------------------------------------

As per our discussion in the query working group 2017-12-14. I don't think the presence or absence of a resource shape should define that behaviour. Some implementations might allow properties to be stored on resources without them necsssarily being in resource shapes.

My proposal simply allows an implementation to clearly signal that the request cannot be executed because ordering is not supported on a specified property.

My motivation for doing this comes from the Jazz GCM application. The properties of a resource are not stored in a single table. Some properties like name, description, creator, created are columns in a table for that resource. Other [custom] properties are stored in a different table. While an EMF based query can order by the built-in properties, it's difficult (perhaps impossible) to also order by additional tables. EMF doesn't support arbitrary joins. Currently GCM doesn't support any use of oslc.orderBy. But if we added support on the built-in properties, and the user specifies something else, then I'd want the response to be 501 Not Implemented as per the proposal.

> Behaviour if oslc.orderBy specifies an unsupported ordering property
> --------------------------------------------------------------------
>
>                 Key: OSLCCORE-149
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-149
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> Some implementations might not support sorting by all queryable properties. If a client specifies a property that is not supported for sorting, the spec should define the behaviour.



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