[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (CMIS-657) ClarifycancelCheckout's proper behavior when doc was created in a checked outstate.
[ http://tools.oasis-open.org/issues/browse/CMIS-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21838#action_21838 ]
David Choy edited comment on CMIS-657 at 10/18/10 3:46 PM:
-----------------------------------------------------------
As discussed in today's meeting, there are 3 possibilities for creating a document in a checked out state when PWCUpdatable is not supported:
(1) Checked-out state is not allowed when creating a document.
(2) Checked-out state is allowed on document creation, but cancelCheckOut is not allowed. The checked-out document MAY be visible to other users.
(3) Checked-out state is allowed on document creation and cancelCheckOut is also allowed. The checked-out document MAY be visible to other users. CancelCheckOut MUST delete the created document.
Possibility (1) imposes the strongest restriction, but there is no semantic deviation from the model. Possibility (2) imposes a stronger restriction than (3), and is only worth consideration if there are repositories having difficulty in deleting the created document on cancelCheckOut.
18 Oct 2010: The TC has accepted (3).
was (Author: dchoy):
As discussed in today's meeting, there are 3 possibilities for creating a document in a checked out state when PWCUpdatable is not supported:
(1) Checked-out state is not allowed when creating a document.
(2) Checked-out state is allowed on document creation, but cancelCheckOut is not allowed. The checked-out document MAY be visible to other users.
(3) Checked-out state is allowed on document creation and cancelCheckOut is also allowed. The checked-out document MAY be visible to other users. CancelCheckOut MUST delete the created document.
Possibility (1) imposes the strongest restriction, but there is no semantic deviation from the model. Possibility (2) imposes a stronger restriction than (3), and is only worth consideration if there are repositories having difficulty in deleting the created document on cancelCheckOut.
> Clarify cancelCheckout's proper behavior when doc was created in a checked out state.
> -------------------------------------------------------------------------------------
>
> Key: CMIS-657
> URL: http://tools.oasis-open.org/issues/browse/CMIS-657
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Improvement
> Components: Domain Model
> Affects Versions: Committee Draft 06
> Environment: n/a
> Reporter: Jay Brown
> Assignee: Ethan Gur-esh
> Priority: Minor
>
> Spec says
> cancelCheckOut
> Description: Reverses the effect of a check-out. Removes the private working copy of the checked-out document, allowing other documents in the version series to be checked out again.
> We should be specific that if that is this command immediately follows the creation of a document in a checked-out state, this may effectively translate into deleting the doc's entire version series. (depending on the repository)
--
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]