Including client implementation use cases for the CMIS REST services would be helpful.

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: REST/AtomPub Binding
    • None
    • Hide

      Identify specific use cases for these operations when operating against the Atom Restful binding.

      Show
      Identify specific use cases for these operations when operating against the Atom Restful binding.

      Our developers working on the atom rest CMIS prototype implementation have asked that the spec include examples of what users will do w/ CMIS Feeds and Entries? Specifically how will they consume them in a create, update or delete use case? This doesn't necessarily lend itself well to client-side development, but of course maps nicely to specific client implementations or atom pub clients.

            Assignee:
            Al Brown (Inactive)
            Reporter:
            Ryan McVeigh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: