- From: Greg Stein <gstein@lyra.org>
- Date: Fri, 15 Dec 2000 14:46:39 -0800
- To: ietf-dav-versioning@w3.org
On Fri, Dec 15, 2000 at 04:03:50PM +0000, Tim_Ellison@uk.ibm.com wrote: >... > Discussion of defining a DAV:is-branch property on an activity to advise a > client whether the activity represents a branch or change set. The > property would have no impact on the server behaviour. Alternative > suggestion was to define a DAV:is-change-set property that would require > the server to enfore there was only one version per history per activity. > Howevr, it was noted that this would require a means for setting the > property when the activity is created (defining a body to initialize > properties during MKACTIVITY?) As one of the guys using activities :-), I'm fine with adding the DAV:is-change-set property, and extending the request body. > James H. agreed to write up his semantics differences between a chane set > and a branch (both being sets of resources) and why it would be useful for > servers to distinguish them. James to post this to the list. Sounds great. Cheers, -g -- Greg Stein, http://www.lyra.org/
Received on Friday, 15 December 2000 17:42:54 UTC