[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-258) Need to explainAllowableActions as they relate to AtomPub links
[ http://tools.oasis-open.org/issues/browse/CMIS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119#action_17119 ]
Al Brown commented on CMIS-258:
-------------------------------
JIRA Cleanup
> Need to explain AllowableActions as they relate to AtomPub links
> ----------------------------------------------------------------
>
> Key: CMIS-258
> URL: http://tools.oasis-open.org/issues/browse/CMIS-258
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Bug
> Components: REST/AtomPub Binding
> Affects Versions: Draft 0.62
> Reporter: Ryan McVeigh
> Assignee: Al Brown
> Priority: Minor
> Fix For: Draft 0.62
>
>
> AtomPub's use of links (and their presence vs absense) makes many of the AllowableAction definitions redundant. It is important to note (as is noted about atom elements vs cmis properties). I think the spec should say something like if an action is allowed, the corresponding link must be present so you can navigate to the resource to perform that action. And if an action is not allowed, the link should not be present. For example, if canDelete, canUpdateProperties, and canGetProperties are all false, then you should not have a link to the document/folder resource. But if any of these are true, then that link must be available.
--
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]