[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=12860#action_12860 ] 

Al Brown commented on CMIS-317:
-------------------------------

+1 I was using SQL-92 as a placeholder for a string that would not make the parser complex (e.g., introduce more escaping and special cases).  It is probably time to codify these a bit better.  I view the restrictions as:

1. no whitespace (introduces escaping and weird parsing behavior when queryname is used on properties)
2. no periods (.)  Introduces problems when used on properties

I also don't see a need for a length restriction as long as the above is satisified.

> 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