cmis message

Subject: [OASIS Issue Tracker] Created: (CMIS-16) Create / Move ambiguity in REST/AtomPub

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: cmis@lists.oasis-open.org
Date: Mon, 1 Dec 2008 18:21:30 -0500 (EST)

Create / Move ambiguity  in REST/AtomPub
----------------------------------------

                 Key: CMIS-16
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-16
             Project: OASIS Content Management Interoperability Services TC
          Issue Type: Bug
          Components: REST/AtomPub Binding
    Affects Versions: Draft 0.50
            Reporter: Ethan Gur-esh
            Assignee: Al Brown
            Priority: Minor


It's not clear how to distinguish between a "create" and "move" when posting an entry to a collection. There's mention of the CMIS-removeFrom header/arg which could be used to distinguish (an approach I personally dislike), but this arg is optional anyway.

An intended move on an object that does not exist results in a create. Another option is to use PUT to change the parent folder id. Although this would require other changes to the spec to support parent id on docs as well as the fact the parent id is read only. 


-- 
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