[OASIS Issue Tracker] Commented: (CMIS-657) ClarifycancelCheckout's proper behavior when doc was created in a checked outstate.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19646#action_19646 ] 

Norrie Quinn commented on CMIS-657:
-----------------------------------

There was further discussion about the interpretation of checkout on create for repositories that do not have PWCUpdateable capability.  In this case the interpretation could be:

State: Immediately after creation: 
Interpretation 3: 
  Version = 1.0 (document is also visible, queryable, etc)

State: After Cancel checkout operation on this document: 
Interpretation 1: 
  Cancel checkout removes the reserved object, so the document is completely gone. No version and no reservation. Checkout is cancelled. 

State: Checking in a document after creation in a checked out state. 
Interpretation 1: 
  Version = 1.0 

Proposed further clarification is:
"Documents created in a checked out state MAY be visible and considered the LatestMajorVersion if the repository does not support the PWCUpdateable capability"

This conflicts with this statement:
> 2.1.9.4.1 Checkout
> Until it is checked in (using the checkIn service), the PWC MUST NOT be considered the LatestMajorVersion in the Version Series.


> 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