Some more comments on the LABEL section...

Hi,

I also have a couple more points/questions regarding section 8 (labels)....

The last paragraph of the introduction to the LABEL feature (section 8)
seems 
out of place.  This text is non-normative and talks about distributed
servers 
and synchronization which is not discussed elsewhere in the specification.  
It seems like the kinda text you would put in an implementers guide or a 
specification regarding synchronization between deltav servers.  I am sure 
that other aspects of deltav would cause synchronization problems in a 
distributed server environment.  At the London IETF we talked about an 
"implementers guide" for deltav, if we have such a document I propose this 
section is removed from the draft and placed in the implementers guide.


Also I am not sure I understand why UPDATE (section 8.9) can take two
labels, 
one in the header and one in the DAV:label-name element.  It seems the 
DAV:label-name is used to ensure that the VCR identified by the request URL 
has a certain label, it is only mentioned in a Precondition and so it does 
not affect the UPDATE, it simply prevents UPDATE on a VCR which has no 
versions that have that label.  The Label header on this method will cause 
the UPDATE to change the VCR to point at the version that has the specified 
label.  I guess my questions are:

What's the use case for the DAV:label-name element? Why have it at all?

Why does the DAV:must-select-version-in-history precondition only affect the

request URL, for example when you specify a depth should this precondition 
not apply to all VCRs that match that depth?

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