[OASIS Issue Tracker] Commented: (CMIS-660) Clarification needed onthe use of quotes in a CONTAINS() query to search on phrases

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

    [ http://tools.oasis-open.org/issues/browse/CMIS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20155#action_20155 ] 

David Choy commented on CMIS-660:
---------------------------------

As far as I can tell, the Lucene Query Parser Syntax differs from CMIS 1.0 fulltext syntax in at least the following ways:
 • Double-quotes are used for phrase.
 • Terms that are not separated by a Boolean operator are OR'ed rather than AND'ed.
 • Negation is not allowed if there is only one term.
 • Character escaping. (CMIS may have to differ in this aspect no matter what so long as the fulltext expression is embedded in a SQL statement.)

Arguments FOR adopting a subset of Lucene syntax:
 • Why invent yet another standard for fulltext query? Is our syntax better? Do we have different requirements?
 • Compatibility with Lucene would reduce confusion.
 • The semantics of the fulltext expression was not defined in v1.0 and we need to fill that hole. Adopting both Lucene's syntax and semantics could be a clean fix, and it would simplify the spec also.
 • The Lucene team probably have investigated fulltext query syntax deeper than we have.
 • For implementations that use a Lucene engine, syntax conversion for fulltext query would be unnecessary.
 • ...

Arguments AGAINST adopting Lucene syntax:
 • Backward compatibility with v1.0.
 • CMIS fulltext syntax is so simple that compatibility with Lucene is an over-concern.
 • Conversion of a CMIS fulltext expression to a Lucene query is trivial.
 • ...


> Clarification needed on the use of quotes in a CONTAINS() query to search on phrases
> ------------------------------------------------------------------------------------
>
>                 Key: CMIS-660
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-660
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Domain Model
>    Affects Versions: Draft 0.70
>            Reporter: Jane Doong
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>
> Clarification needed on the use of quotes in a CONTAINS() query to search on phrases.
> Spec:
> 2575  BNF grammar structure:: CONTAINS ( [ <qualifier> ,] ' <text search expression> ' )
> 2413  <phrase> ::= <quote> <word> [ {<space> <word>} ... ] <quote>
> 2422  <quote> ::= "'" !! Single-quote only, consistent with SQL-92 string literal
> 2597  Within a word or phrase, each (single-)quote must also be escaped by a preceding backslash "\"
> The spec specifically states that <quote> is single-quote only.
> My questions is on specifying a phrase inside the CONTAINS(). 
> Since the entire text search expression is enclosed in single quotes, 
> I question whether a phrase should again be enclosed in single quotes, or should it be in double-quotes.
> According to spec:
>  Word search:    CONTAINS('house')
>  Phrase search : CONTAINS(' 'my house' ')
> Should phrases be in double-quotes? ==> CONTAINS(' "my house" ')

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira