[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-731) Explicit representation of version-independent copy of a versionable document
[ http://tools.oasis-open.org/issues/browse/CMIS-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28976#action_28976 ]
Florent Guillaume commented on CMIS-731:
----------------------------------------
I can envision a system where there are several representative copies instantiated with different characteristics, for instance one pointing to the latest version, and another pointing to the latest major version.
Is that compatible with what you had in mind?
> Explicit representation of version-independent copy of a versionable document
> -----------------------------------------------------------------------------
>
> Key: CMIS-731
> URL: http://tools.oasis-open.org/issues/browse/CMIS-731
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: New Feature
> Components: Domain Model
> Affects Versions: V1.1
> Reporter: Eric Chan
>
> Section 2.1.11.8 and 2.1.11.9 in the CMIS draft http://www.oasis-open.org/apps/org/workgroup/cmis/download.php/43639/cmis11-draft.pdf define the version-independent membership in Folders and Relationships in terms of Navigation service requests getChildren, getDescendants, and getObjectRelationships. The concept of a version-independent copy can be defined more explicitly by designating an object identifier to represent a version-independent copy in a version series. It facilitates an externalized URI for a version-independent representative copy to enable bookmarking or tagging. It also generalizes the concept of version-independent copy for un-filed versionable documents.
> ICOM CSD 2.0 http://www.oasis-open.org/committees/download.php/44405/icom-ics-v1.0-csprd02.zip, which adopts some of the CMIS domain model, introduces the concept of "representative copy" as an optional feature. ICOM CSD stipulates that a representative copy must have its own object identifier that is different from the object identifier of any versioned copy or private working copy of a versionable document.
> Assignment of an object identifier to a representative copy of a versionable document is implementation-dependent. A representative copy may retain the object identifier of a non-version-controlled copy (a private working copy at the start of the version series). Alternatively, a representative copy may be assigned a new object identifier that is different from the object identifier of a non-version-controlled copy of a versionable artifact. The object identifier of a representative copy should not change once it is assigned (a representative copy cannot be deleted).
> Content and state of a representative copy of a versionable artifact in a version series is also implementation-dependent. A representative copy may be a copy of the content and state of the latest versioned copy or the latest major versioned copy in a 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]