Can I continue to use the same cmis:objectId when a document is version

Hello,

I'm linzhixing, new to this mailing list, and now involved with developing a CMIS compliant server/client products.

I have a question with regard to the "version" and the "objectId" in the specification.

Each version is a document, I see, and it has a new unique id different from other versions having the same versionSeriesId. But I think there can be still two interpretation / implementation.

(A)New document with new id is created as the latest version. The former id now indicate a old version.

(B)New document is unchanged and the ex-latest object's id is now replaced with a new one.

(A) would be a natural interpretation of the specification, but (B) is I think still worthy to be considered.

In (B), whatever version it is, we can express a URI relating to a document object with a invariable objectId.

In (A), the URI could become stale indicating an old version before users know it.

As far as I can see, Alfresco continues to use the same id when a document is version upped.

The question:

The（B) can be allowed as the interpretation of CMIS spec?

In this case, I‘m worrying about conflicts against other CMIS spec like objectId immutability, creationDate and so on.

For example, (B) can be thought to be an abbreviation of the following:

every time before a document is version upped, copy the latest document to the new id object, delete the original document and create the new version document with the original id, though It would be a little tricky...

Regards,

linzhixing.

cmis-comment message