← Prev in month ← Prev in thread

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

From
OASIS Issues Tracker <>
Date
2017-09-29T14:58:00+00:00
ID
Thread
[OASIS Issue Tracker] (OSLCCORE-105) Query spec does not define behaviour of oslc.where or oslc.searchTerms if not implemented
David Honey created OSLCCORE-105:
------------------------------------

             Summary: 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)
← Prev in month ← Prev in thread