[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-144) Full text search syntaxand semantics
[ http://tools.oasis-open.org/issues/browse/CMIS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10648#action_10648 ] David Caruana commented on CMIS-144: ------------------------------------ As requested, proposal for FTS including BNF. http://www.oasis-open.org/apps/org/workgroup/cmis/download.php/32524/cmis_fts_proposal_v0_1.txt > Full text search syntax and semantics > ------------------------------------- > > Key: CMIS-144 > URL: http://tools.oasis-open.org/issues/browse/CMIS-144 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Bug > Components: Domain Model > Affects Versions: Draft 0.60 > Reporter: David Caruana > Assignee: Ethan Gur-esh > > The text search expression is defined as a <character string literal> (as defined by SQL-92). However, the syntax and semantics of the full text search expression are repo specific. > I remember there was some resistance to defining a 'lowest common denominator' full text search language, but I don't remember why. > Given that we define SQL, and that query is a key use case, I think there's value in a deeper FTS definition. > As a starting point, JCR provides minimal definition. I'm not sure we would need to much further than that to start with. -- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]