[#CMIS-293] Consistency - ACLControllable - put on all type definitions rather than just documents or folders

OASIS Content Management Interoperability Services (CMIS) TC

Consistency - ACLControllable - put on all type definitions rather than just documents or folders

Created: 30/Jun/09 02:43 PM Updated: 11/Jan/10 07:32 PM

Component/s:

None

Affects Version/s:

Draft 0.62

Fix Version/s:

Draft 0.62

Proposal:

put ACLControllable on all type defs not just doc & folder

Description

« Hide

put ACLControllable on all type defs not just doc & folder
- Easier to model in XSD since on base cmisTypeDefinitionType rather than on cmisTypeDocumentDefinitionType and cmisTypeFolderDefinitionType separately.
- Easy for repositories to set to 'false' for each type if not supported
- Consistent

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Florent Guillaume added a comment - 06/Jul/09 01:06 PM

[ Permalink | « Hide ]

Al Brown added a comment - 06/Jul/09 01:08 PM

accepted

[ Permalink | « Hide ]

Alison Macmillan added a comment - 07/Jul/09 03:46 AM

By allowing every type to potentially be ACLControllable we need to revisit the proposed Basic Permission Mapping table in 2.6.2.4.3. For example, if a Relationship has an ACL, what permissions are now required for getPermissions? Presumably at least read on the Relationship in addition.

If the main reason for this change is to simplify the XSD, then I think this is outweighed by complicating the Basic Permission Mappings table (which is itself runtime discoverable).