- From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
- Date: Sat, 13 Jan 2001 09:23:31 -0500 (EST)
- To: ietf-dav-versioning@w3.org
From: "Mark A. Hale" <mark.hale@interwoven.com> I would like to suggest the following changes that were discussed in this morning's teleconference and this week's threads: - Rename Chapter 6 to Working Resource Option Done. - Rename Chapter 7 to Workspace Option Done. - Highlight in Chapter 6 that the server may set a DAV:workspace property when a new working resource is created. The property is asserted by servers that utilize server-managed workspaces for resource management. I agree that a server that supports both workspaces and working resources might reasonably make such an association, and a server is certainly allowed to set a DAV:workspace property on a working resource (since any resource can have a DAV:workspace property) but what would a client do with this property value (i.e. what interoperability would we get by highlighting this fact)? We've already got a complex spec, so I try to leave out anything that doesn't directly contribute to interoperability. Cheers, Geoff
Received on Saturday, 13 January 2001 09:24:22 UTC