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] Created: (CMIS-31) creating new resources

creating new resources

                 Key: CMIS-31
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-31
             Project: OASIS Content Management Interoperability Services TC
          Issue Type: Task
          Components: REST/AtomPub Binding
            Reporter: Julian Reschke
            Assignee: Al Brown

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?

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]