creating new resources

XMLWordPrintable

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

      Clarify in the specification:

      • CMIS supports the 3 modes from APP (Entry + Content, Entry then Media, just media)
      • In all cases Constraints/Exceptions may be thrown
      Show
      Clarify in the specification: CMIS supports the 3 modes from APP (Entry + Content, Entry then Media, just media) In all cases Constraints/Exceptions may be thrown

      It appears that the specification recommends a model for creating new resources that is quite different from what RFC 5023 (AtomPub) suggests.

      In RFC 5023, new non-atom-entry resources are created by POSTing to a media collection, which results in both the payload being stored as media resource, and an entry document being returned (with Location pointing to the entry document, and the entry document linking to the media resource). See <http://greenbytes.de/tech/webdav/rfc5023.html#rfc.section.9.6>.

      In CMIS, createDocument suggests to create the media entry first, and to either inline the content (base64!), or to set the content in a second request on the media entry.

      What's the purpose of deviating from AtomPub here?

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

              Created:
              Updated:
              Resolved: