OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (CMIS-463) Remove CMIS:Delete frombasic permissions



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

Al Brown commented on CMIS-463:
-------------------------------

JIRA Cleanup

> Remove CMIS:Delete from basic permissions
> -----------------------------------------
>
>                 Key: CMIS-463
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-463
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Schema
>    Affects Versions: Draft 0.63
>            Reporter: Ethan Gur-esh
>            Assignee: Ethan Gur-esh
>             Fix For: Draft 0.63
>
>
> Currently, CMIS specifies four permissions that all repositories SHOULD support -- read/write/delete/all.
> Some repositories (incl. SharePoint) don't generally have separate "write" vs. "delete" permissions (at least not in the default role/permissions configuration that most customer use). So if we have those as separate permissions in CMIS, then those repositories will have to use "repository-specific permissions" instead of the specified ones.

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