[OASIS Issue Tracker] (OSLCCORE-103) Query spec does not define behaviour if both oslc.where and oslc.searchTerms is specified

David Honey created OSLCCORE-103:
------------------------------------

             Summary: Query spec does not define behaviour if both oslc.where and oslc.searchTerms is specified
                 Key: OSLCCORE-103
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-103
             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 does not define the behaviour if bothg oslc.where and oslc.searchTerms is specified. In practice, oslc.searchTerms is likely to be a free-text search performed by something like Lucene, whereas oslc.where will either be a SPARQL query or some form of SQL query. Does it make sense to have one request to perform both of these quite separate operations?



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