Uploaded image for project: 'OASIS Content Management Interoperability Services (CMIS) TC'
  1. OASIS Content Management Interoperability Services (CMIS) TC
  2. CMIS-258

Need to explain AllowableActions as they relate to AtomPub links

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: REST/AtomPub Binding
    • Labels:
      None
    • Proposal:
      Hide

      Clarify - if 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.

      Show
      Clarify - if 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.

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              albertcbrown Al Brown (Inactive)
              Reporter:
              ryan.mcveigh Ryan McVeigh (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: