[OASIS Issue Tracker] Commented: (CMIS-317) Need to include therationale/use cases for the various names uses for types and properrtydefintions

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

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

Ryan McVeigh commented on CMIS-317:
-----------------------------------

I have a concern about the SQL-92 compliance requirement on the queryName attribute.  SQL-92 limit identifier lengths.  When we have to encode characters that are outside of the limited SQL-92 character set, we will quickly surpass any length limitation.  This is problematic for a repository which does not have this restriction internally.  

I propose that a repository vendor should be able to supply a queryName which that CMIS implementation can then use when parsing a query without any additional escaping or other work.  This implies that the contents of the queryName are opaque and therefore repository-specific.  

At this point, as this is currently specified, we don't have a reasonable or clean way to implement an encoding algorithm that will work for our products.

> Need to include the rationale/use cases for the various names uses for types and properrty defintions
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CMIS-317
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-317
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.62
>            Reporter: Ryan McVeigh
>            Assignee: Ethan Gur-esh
>
> As it currently stands there are no fewer than 4 names specified for types - name, queryName, displayName and globalUniqueName.  This is confusing to those folks who know the spec, nevermind the newcomer.  We need to document why we have these and describe what they help address.

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