[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=68473#comment-68473 ] 

David Honey commented on OSLCCORE-103:
--------------------------------------

Although there are hostorical documents that describe an algorithm, I think in most cases, query and full-text search use different technoloigies. For most applications, where persistence is a RDB, query will be based on SQL or an abstraction of SQL such as EMF (Eclipse Modelling Framework). Full-text search is commonly implemented using components such as Lucene. Almost all applications will support query. A subset of those might implement full-text search. A significantly smaller subset would support use of both together.

We shouldn't burden implementations by implying that oslc.searchTerms is a MUST, and that combined use of oslc.where + oslc.searchTerms is a MUST.

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