[OASIS Issue Tracker] Commented: (CMIS-635) CMIS-Core.xsdenumAllowableActionsKey does not match spec

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

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

David Caruana commented on CMIS-635:
------------------------------------

canGetFolderTree.Folder is missing completely.
canGetRenditions.Object is missing completely.

> CMIS-Core.xsd enumAllowableActionsKey does not match spec
> ---------------------------------------------------------
>
>                 Key: CMIS-635
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-635
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Schema
>    Affects Versions: Committee Draft 06
>            Reporter: David Caruana
>            Priority: Critical
>
> There are several inconsistencies between the CMIS-Core.xsd enumAllowableActionsKey and the specification.
> For example:
> canAddObjectToFolder.Folder is missing from schema (it's listed as canAddToFolder.Folder)
> canAddObjectToFolder.Object is missing from schema (it's listed as canAddToFolder.Object)
> canApplyPolicy.Object is missing from schema (it's listed as canAddPolicy.Object)
> canApplyPolicy.Policy is missing from schema (it's listed as canAddPolicy.Policy)
> canCancelCheckOut.Document is missing from schema (it's listed as canCancelCheckout.Document)
> canCheckIn.Document is missing from schema (it's listed as canCheckin.Document)
> ...

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