[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=68516#comment-68516 ] 

James Amsden commented on OSLCCORE-149:
---------------------------------------

Regarding property references in oslc.properties, or any of the query clauses, we should rely on shapes to validate the referenced properties. If there are no applicable shapes, then the specified properties are assumed to be valid and servers should execute the queries appropriately and not fail.

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