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

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

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

James Amsden commented on OSLCCORE-103:
---------------------------------------

I think the client would make the desired query, and if it didn't return anything, make the other.


> 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 defines the behaviour if both oslc.where and oslc.searchTerms is specified. That description could be referenced earlier in the document to answer a reader's obvious question when the terms are first mentioned.
> 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. Many implementations might choose to support query but not free text search, or query and free text search separately, but mutually exclusive. How does a client discover this?



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