[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-597) supportedPermissionsand its enum are missing from cmisACLCapabilityType
[ http://tools.oasis-open.org/issues/browse/CMIS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656#action_16656 ] Florent Guillaume commented on CMIS-597: ---------------------------------------- Please note the incorrect extra space in the proposal, it should actually be: <xs:element name="supportedPermissions" type="cmis:enumSupportedPermissions" /> > supportedPermissions and its enum are missing from cmisACLCapabilityType > ------------------------------------------------------------------------ > > Key: CMIS-597 > URL: http://tools.oasis-open.org/issues/browse/CMIS-597 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Bug > Components: Schema > Affects Versions: Committee Draft 04 > Reporter: Florent Guillaume > > 1.0cd04 has, line 3354: > Enum supportedPermissions: specifies which types of permissions are supported. > - basic: indicates that the CMIS Basic permissions are supported. > - repository: Indicates that repository specific permissions are supported. > - both: indicates that both CMIS basic permissions and repository specific permissions are supported. > But this output value and the corresponding enum are missing from cmisACLCapabilityType in CMIS-Core.xsd. > (I guess cmisACLCapabilityType is a better choice than cmisRepositoryInfoType.) -- 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]