Hi Michael,
For versionable documents this check is correct. For non-versionable
documents the spec allows using the same Version Series Id for multiple
documents. I have changed the check from reporting a failure message to
an info message in this case.
However, we have seen clients that used the Version Series Id to
correlate documents without checking if they are versionable or not.
Those applications get confused when they find that all non-versionable
documents belong to the same version series. Therefore, repositories
should always provide a unique Version Series Id, even if the spec
doesn't require it.
- Florian
Hi,
On trunk the tck now checks that versionSeriesId's are different for
multiple new documents.
However, my understanding is that the versionSeriesId is repository
specific if the document is not versionable.
For example it could use "none" for all documents.
Should the check not be conditional on versionable attribute of the
type?
Michael
