RE: Legal operations on members of a Baseline Collection...

Hi,

OK...I guess that section does make it clear.

But, how much of the normative text should be captured in pre and post
conditions? Without any pre or post condition to enforce the paragraph
that you quoted do vendors have to obey that paragraph?

Would I am getting at is that other areas where we are enforcing something
we explicitly enforce it using pre or post conditions.  But not this one.

Regards,
--
Peter Raymond - MERANT
Principal Architect (PVCS)
Tel: +44 (0)1727 813362
Fax: +44 (0)1727 869804
mailto:Peter.Raymond@merant.com
WWW: http://www.merant.com



-----Original Message-----
From: Clemm, Geoff [mailto:gclemm@rational.com]
Sent: 27 September 2001 16:00
To: ietf-dav-versioning@w3.org
Subject: RE: Legal operations on members of a Baseline Collection...


The definition of the DAV:baseline-collection property states:

"each member of this collection has the same 
DAV:checked-in version and relative name as a 
member of the baseline-controlled collection at
the time the baseline was created"

I believe this makes it sufficiently clear that no operations
that would add/remove/change members of the DAV:baseline-collection
are allowed.

Cheers,
Geoff

-----Original Message-----
From: Peter Raymond [mailto:Peter.Raymond@merant.com]
Sent: Thursday, September 27, 2001 9:46 AM
To: Clemm, Geoff; ietf-dav-versioning@w3.org
Subject: RE: Legal operations on members of a Baseline Collection...


Hi, 
The Baseline Collection is a collection so there is nothing to stop you 
doing a PUT on that collection.  Unless we explicitly have a precondition 
for PUT that says you cannot put to a baseline collection. 
Same for destination for a MOVE or COPY.