[OASIS Issue Tracker] (ODATA-1100) Add mechanism for specifying match type for $search

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

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

Ralf Handl commented on ODATA-1100:
-----------------------------------

Feedback from SAP search team: don't try to define a syntax for $search, just allow passing through whatever the user types into the search field. This allows each search engine to create and evolve its own search language. 

Which means: even the current syntax with words, phrases, AND/space, OR, NOT, and parentheses is just a proposal that can be ignored by service implementations, allow everything that can be the value of a query option according to the URL spec:

searchExpr = ( OPEN BWS searchExpr BWS CLOSE
             / searchTerm 
             ) [ searchOrExpr
               / searchAndExpr
               ]
           / 1*qchar-no-AMP

The last line is the "escape hatch" for anything.

> Add mechanism for specifying match type for $search
> ---------------------------------------------------
>
>                 Key: ODATA-1100
>                 URL: https://issues.oasis-open.org/browse/ODATA-1100
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: Protocol
>    Affects Versions: V4.01_CSD02
>            Reporter: Mark Biamonte
>            Assignee: Mark Biamonte
>             Fix For: V4.01_CS01
>
>
> When doing text searches, many of the common algorithms we use have a number of different ways to define a match (Exact match, begins with, synonym, base word or inflection, etc).  The spec currently says it is up to the implementation as to what constitutes a match, this is fine, but in the case where the search algorithm provides different matching types it would be nice if the query writer could specify the type of match they want in the $search expression.



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