[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:all-tabpanel ]

David Honey updated OSLCCORE-105:
---------------------------------

    Proposal: If a oslc.where and/or oslc.searchTerms query parameter is specified but not supported, the server SHOULD return 501 Not Implemented,  (was: If any oslc.* query parameter is specified but not supported, the server SHOULD return 501 Not Implemented,)

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