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: [DRAFT REVIEW] cmis-v1.1-wd03


First, there is one small typo in Section 2.2.4.18 setContentStream.  There is a transposed pair of letters (a carry-over from v1.0):

In v1.1-wd03 it reads:

Notes: A repository MAY automatically create new document versions as part of this service method.  Therefore, the obejctId [emphasis mine] output NEED NOT be identical to the objectId input.

 

obejctId should be replaced with objectId

 

 

Second, some comments/questions on the PWC in the Versioning CheckOut Service:

 

I like the way that the language of checkout has been clarified from v1.0, but perhaps more clarification is necessary around the PWC?  2.1.13.5.1 Checkout contains:

The effects of invoking the checkOut service MUST be as follows:

...

- the PWC is NOT be considered a version in the version series but inherits the version series id from the document it was created from.

 

(aside: note that there is a grammatical error in the quote as well.. it probably was intended to say "the PWC is NOT to be considered")

 

It appears that this is in contradiction with the statement in 2.1.13.1 Version Series that

"A version series for a document object is a transitively closed collection of all document objects that have been created from an original document in the repository."

 

To be consistent, 2.1.13.1 Version Series should say something like

" A version series for a document object is a transitively closed collection of all document objects, other than any Private Working Copy, that have been created from an original document in the repository."

 

Also, by explicitly stating that the PWC is not in the version series, the draft leaves undefined the action of checkOut on the PWC.  Again from 2.1.13.5.1 Checkout:

the effects on other documents in the version series MUST be as follows:

·         The repository MUST throw an exception if the checkOut service is invoked on any document in the version series...

·         The value of the cmis:isVersionSeriesCheckedOut property MUST be TRUE....

 

Since the PWC is not to be considered a version in the version series, these statements do not apply to the PWC.  Consistent wording might be:

the effects on the PWC or any documents in the version series MUST be as follows:

·         The repository MUST throw an exception if the checkOut service is invoked on any document in the version series...

·         The value of the cmis:isVersionSeriesCheckedOut property MUST be TRUE....

 

Finally, one question on the PWC in the Versioning CheckIn Service:

Section 2.1.13.5.4 CheckIn states:

If the check-in returns a new cmis:objectId, then the PWC object MUST disappear if the checkIn call was successful and the new checked in version will use the new specified id.

...

Note: The repository MAY change the id of the PWC upon completion of the checkIn  service invocation.

 

It is not clear to me how these are intended to interact.  It appears to say that "if the check-in does not return a new cmis:objectId, (in other words, the cmis:objectId of the PWC is returned), then the id of the PWC may be changed".

This seems contradictory... what have I missed?

 

 

 

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]