Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
To: <dev@chemistry.apache.org>
Subject: Re: tck - versionSeriesId
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 13 Mar 2013 14:47:47 +0100
From: =?UTF-8?Q?Florian_M=C3=BCller?= <fmui@apache.org>
Cc: <michael.javaone+cmis@gmail.com>
In-Reply-To: 
 <CAEV0z=qN=UGgqGzEHjjna4OS7Bm3Dp51jXM9di7vovUOX3cHEw@mail.gmail.com>
References: 
 <CAEV0z=qN=UGgqGzEHjjna4OS7Bm3Dp51jXM9di7vovUOX3cHEw@mail.gmail.com>
Message-ID: 
 <ec7ffacde0ee9b9b34a21b5550ee9883-EhVcXl9JQQFXRwQFDQkEXR0wfgZLV15fQUBFBEFYXS9aBFgIVQkjAVVfDwkJFE8AXVpYSlJRWAgwXnUHVlRVXVtHQg==-webmailer2@server05.webmailer.hosteurope.de>
User-Agent: Host Europe Webmailer/2.0

 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