[#CMIS-88] POST to Children resource is confusing - OASIS Technical Committees Issue Tracker

OASIS Content Management Interoperability Services (CMIS) TC

POST to Children resource is confusing

Created: 04/Mar/09 04:06 PM Updated: 11/Jan/10 06:34 PM

Component/s:

REST/AtomPub Binding

Affects Version/s:

Draft 0.50

Fix Version/s:

Draft 0.62, Draft 0.63

Proposal:

« Hide

POST to Children is for create. Ids and ObjectIds in the posted document (if any) are ignored.
Create a Move resource with a POST method. The resource identifies the destination folder, the POST should contain the Id or ObjectId of the resource to be moved (i.e. could be an Entry document with everything except id ignored, or just an xml subgroup like atom:id or something similar).

Description

« Hide

Perhaps these are several issues, but all related to posting to the children resource:

   1. How to distinguish between create and move?
   2. If create, what to do with id in the posted entry? (ignore? error?)
   3. If create, what to do if path in entry dosn't match the resource's folder? (error? ignore?)
   4. If move, all you really need is a from identity and a destination folder identity (the resource). What to do with the rest of the posted entry? (ignore? updateProperties? assert that they are correct? exception if present?)

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Ryan McVeigh added a comment - 11/Mar/09 06:23 PM

Revised proposal.

[ Permalink | « Hide ]

Al Brown added a comment - 14/Apr/09 01:07 PM

A couple of options:
1. POST moveRequest document to collection
2. use COPY/MOVE (Julian)
3. leave as-is

[ Permalink | « Hide ]

Ryan McVeigh added a comment - 21/Apr/09 05:07 PM

A few changes to the current wording would allow us to keep the basic function as-is. Here are those changes:

- Strike lines 691-694. These appear leftovers from past edits.

- Line 684, reword as follows:
- When not required by the type definitions content streams MAY be provided by any mechanism supported by Atom Publishing Protocol:

- There is a bit of inconsistency in when something is a move and when it is an addToFolder operation. If a repository supports multi-filing then addToFolder is assumed. We should simply be explicit here and make move always be a move, and addToFolder always be addToFolder instead of changing behavior based on the underlying repositories capabilities.

- We should clarify that when moving or adding to a folder, any properties specified other than the ObjectId will be ignored.

[ Permalink | « Hide ]

Al Brown added a comment - 05/Jan/10 12:34 AM

JIRA Cleanup