- From: Clemm, Geoff <gclemm@rational.com>
- Date: Mon, 29 Oct 2001 07:44:53 -0500
- To: ietf-dav-versioning@w3.org
A "configuration" is just a concept defined by the spec (i.e. the definition quoted below). It always existed in WebDAV, but didn't have a name (it was the "Depth:infinity state of a collection"). You manipulate it with standard operations like PUT/MKCOL/DELETE/COPY (a Depth:Infinity copy allows you to copy an entire configuration from one spot to another). Cheers, Geoff -----Original Message----- From: Alison Macmillan [mailto:alison.macmillan@oracle.com] Sent: Monday, October 29, 2001 5:37 AM To: Clemm, Geoff Cc: ietf-dav-versioning@w3.org Subject: Re: Definition of a configuration "Clemm, Geoff" wrote: > From: Edgar@EdgarSchwarz.de [mailto:Edgar@EdgarSchwarz.de] > > ...I would change the definitions Peter cites: > > "A configuration is a set of resources that consists of a root > collection and all version-controlled members of that root collection > except those resources that are members of another configuration" > > "A baseline is a version resource that captures the state of each > member of a configuration." > > This would not allow you to talk about non-version-controlled > configurations. I think this would be unfortunate, since it is > a useful concept even if you aren't doing versioning. > I didn't think non-version-controlled configurations were defined by the spec. How do you create and restore such a configuration?
Received on Monday, 29 October 2001 07:45:26 UTC