[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-407) capabilityChangesOnTypeis required even if capabilityChanges is none
[ http://tools.oasis-open.org/issues/browse/CMIS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144#action_17144 ]
Al Brown commented on CMIS-407:
-------------------------------
JIRA Cleanup
> capabilityChangesOnType is required even if capabilityChanges is none
> ---------------------------------------------------------------------
>
> Key: CMIS-407
> URL: http://tools.oasis-open.org/issues/browse/CMIS-407
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Bug
> Components: Schema
> Affects Versions: Draft 0.62
> Reporter: David Caruana
> Fix For: Draft 0.63
>
>
> schema <xs:element name="capabilityChangesOnType" type="cmis:enumBaseObjectTypeIds" minOccurs="1" maxOccurs="unbounded" />
> Repositories supporting capabilityChanges of none, are forced to list one capabilityChangesOnType.
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]