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] Commented: (CMIS-728) Clarify whether PWC is a latest version or not


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

Eric Chan commented on CMIS-728:
--------------------------------

I am submitting the ICOM model of versionable for consideration. ICOM versionable extends the CMIS versionable model with a concept of "representative copy." Below is an excerpt from ICOM Committee Specification Draft 1.0.

A versionable artifact is 
1. a representative copy, 
2. a specific versioned copy, or 
3. a private working copy 
of an artifact version series.

When a versionable artifact is not under version control, a representative copy of a versionable artifact is the only version of a version series and represents the versionable artifact itself, i.e. there is only one objectId so far.

When a versionable artifact is under version control:
• a representative copy of a versionable artifact is a versionable artifact which has its own object identifier that is different from the object identifier of any versioned copy or private working copy of the versionable artifact. It retains the object identifier it has when the artifact is created. Its version type changes from RepresentativeCopy to ViewOnlyRepresentativeCopy.
• a representative copy of a versionable artifact provides a view of a version series, depending on the check out state of the version series and the user loading the artifact. If the current user loading a representative copy is the same user who checks out from a version series, the representative copy is a copy of the content and state of a private working copy. Otherwise, the representative copy is a copy of the content and state of the latest versioned copy in a version series.

A specific versioned copy of a versionable artifact is an explicit "deep" copy of the content and state of a versionable artifact, preserving its content and state at a certain point in time. Each versioned copy of a versionable artifact is itself a versionable artifact, i.e. it has its own objectId. A versioned copy has a version number, label, and check in comment. 

A private working copy of a versionable artifact is a versionable artifact created by an explicit checkout operation on a versionable artifact under version control. The properties for a private working copy SHOULD be identical to the properties of a versioned copy of a versionable artifact on which a checkout operation was performed. Certain properties such as objectId and creationDate SHALL be different from a versioned copy. The content of a private working copy MAY be identical to the content of a versioned copy. Its object identifier must be different from that of the representative copy or any versioned copy. A private working copy can be saved to the version series for sharing and co-editing, however, it needs not be visible to users who may only have permissions to view other versioned copies in a version series. Until it is checked in using an explicit checkin operation, a private working copy MUST NOT be considered the LatestMajorVersion in a version series.

Note: A container of a versionable artifact can contain a representative copy of a version series so that it provides an artifact view of the latest state of the version series. Starting from a representative copy in a container, an actor can traverse a version series to retrieve any versioned copy or private working copy.


> Clarify whether PWC is a latest version or not
> ----------------------------------------------
>
>                 Key: CMIS-728
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-728
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: V1.0 Errata
>            Reporter: Florent Guillaume
>
> A concern has been raised in the OpenCMIS TCK about whether a PWC can have cmis:isLatestVersion=true.
> https://issues.apache.org/jira/browse/CMIS-431
> The difference of interpretation is whether or not a PWC has any characteristic of a version.
> For me, a PWC is not a version and (consequently) can never be considered the latest version.
> Florian has a different interpretation.
> This is not clear because the spec sometimes talks about "version" in a loose sense and says that the PWC is a kind of version. And also it sometimes hints at the fact that the PWC is part of the version series.

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