[OASIS Issue Tracker] (OSLCCORE-105) Query spec does not define behaviour of oslc.where or oslc.searchTerms if not implemented

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

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

David Honey commented on OSLCCORE-105:
--------------------------------------

Relying on whether a query result has any members isn't a reliable means of discovery. If no resources exist that a query capability might find, then a client cannot distinguish between any of the following:
1) The specified oslc.where is supported, the query has executed successfully, but there are no resources of the matching type.
2) The specified oslc.searchTerms is supported, the full-text search executed successfully, but there are no resources found.
3) oslc.where is specified but not supported.
4) oslc.searchTerms is specified but not supported.

 The proposal recommends that servers give an explicit error response. This disambiguates the above, and the error response explicitly provides information to the consumer about exactly what is not supported.

> Query spec does not define behaviour of oslc.where or oslc.searchTerms if not implemented
> -----------------------------------------------------------------------------------------
>
>                 Key: OSLCCORE-105
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-105
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> https://open-services.net/bin/view/Main/OSLCCoreSpecQuery describes two differenty types of query:
> 1) A text search query specified by oslc.searchTerms
> 2) A property graph based query specified by oslc.where
> In order to ease the implementation buden of the spec, we should allow servers to implement one but not necessarily both. Currently a client has no means of discovering whether either or both are supported before issuing a query request.
> The spec should define the behaviour if oslc.searchTerms or oslc.where is specified but the server does not support that capability.



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