[OASIS Issue Tracker] Commented: (CMIS-527) BNF Grammar Quoteissues

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

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

Ryan McVeigh commented on CMIS-527:
-----------------------------------

I don't see how we need to add complexity like this.  The repository implementation chooses the queryName and one would presume the vendor would be able to choose names that it could parse in the query.  That is, if your parser is going to choke on some reserved word, then simply don't generate queryNames that are reserved words.  The BNF grammar does not need to compensate for this, as it is completely avoidable.

> BNF Grammar Quote issues
> ------------------------
>
>                 Key: CMIS-527
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-527
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>            Reporter: Ryan McVeigh
>            Assignee: Ethan Gur-esh
>
> CMIS defers to SQL-92 for the description of <character string literal>.  SQL-92 (http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt) defines a character string literal as delimited by <quote>, which is defined as <quote> ::= ', that is, a single-quote character.
> CMIS BNF defines <quote> ::= '"' | "'", that is either a single- or double-quote character.
>           - Is CMIS attempting to "override" or "extend" the SQL definition of the <quote> production, or is CMIS's usage unique to where it is explicitly used in the CMIS text.
>           - Specifically, does CMIS's <quote> affect the <character string literal> as defined in SQL-92?
> The <text search expression> for the CONTAINS operator is specified to be delimited only by double-quote characters, not the single-quotes prescribed for SQL-92 strings, nor the "either-quotes" used within the expression itself.  The <datetime literal> is delimited with "either-quotes", unlike character string literals.  The example in section 2.10.2.4.2.3 uses double-quotes, which hints that maybe CMIS is trying to override SQL's definition of <quote>.

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