[OASIS Issue Tracker] Updated: (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:all-tabpanel ]

Ethan Gur-esh updated CMIS-635:
-------------------------------

    Proposal: 
We will create an "Approved Errata" document (see http://www.oasis-open.org/committees/process.php#errata), and we will add an errata item stating the following:
        1) For the mis-spelled keys, the XSD is correct and the spec is incorrect.
        2) The keys listed in the spec that are NOT listed in the XSD, the XSD is correct and the reference to those keys in the spec should be removed.

TODO: We should confirm with Mary that the change listed in this proposal does not meet the OASIS definition of "substantial" change (i.e. so that we can fix this in "errata" vs. a spec update w/new public review.)

  was:Adjust CMIS-Core.xsd enumAllowableActionsKey to reflect to the specification.

    Assignee: Al Brown

> 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
>            Assignee: Al Brown
>            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