[OASIS Issue Tracker] Created: (CMIS-745) The type ids for the secondary types defined in 2.1.6 are not valid QNames

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

The type ids for the secondary types defined in 2.1.6 are not valid QNames
--------------------------------------------------------------------------

                 Key: CMIS-745
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-745
             Project: OASIS Content Management Interoperability Services (CMIS) TC
          Issue Type: Bug
          Components: Domain Model
    Affects Versions: CD04 Substantial Changes
            Reporter: Andy Hind


While CMIS object type Ids are opaque, they are currently all valid QNames
Section 2.1.6 "Retentions and Holds" introduces the first object Ids that are not valid QNames.

These should be fixed for consistency and to avoid conflict where a repository uses QNames for type Ids. 

For example:
"cmis:rm:repMgtRetention"

Alternative suggestions:
"cmis.rm:repMgtRetention"
"cmisrm:repMgtRetention"
"cmis:repMgtRetention"
"cmis:rm.repMgtRetention"  
which all conform

the queryName should be changed to match

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