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

David Honey updated OSLCCORE-103:
---------------------------------

    Proposal: 
The specification should define that support for:
1) oslc.where is a MAY
2) oslc.searchTerms is a MAY
3) oslc.where + oslc.search is a MAY
4) at least one of #1 or #2 is a MUST.

and that if a server does not implement #1, #2, or #2, that the server SHOULD respond with 501 Not Implemented with an oslc:Error response that describes what capability or capabilities are not supported.
Describe that a server may choose to treat them as mutually exclusive and return 400 Bad Request if both are specified but not supported.

Recommend that OSLC clients only use both where it knows a specific implementation supports both.

  was:
Describe that a server may choose to treat them as mutually exclusive and return 400 Bad Request if both are specified but not supported.

Recommend that OSLC clients only use both where it knows a specific implementation supports both.


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