Next message: Bradley Sergeant: "Re: Adding a DAV:default-revision property to versioned resources"
Message-ID: <F3B2A0DB2FC1D211A511006097FFDDF501459D0A@BEAVMAIL>
From: Neil Weber <Neil.Weber@merant.com>
To: ietf-dav-versioning@w3.org
Date: Fri, 4 Feb 2000 15:10:39 -0800
Subject: RE: Adding a DAV:default-revision property to versioned resources
Geoff,
What about default workspaces do you feel is complex? I put together some
UML sequence diagrams and the handling of default workspaces fit in well.
Workspaces are not a required part of core versioning? From the extensive
discussion of workspaces in the spec I had the opposite impression. In
particular, the definition/specification of Target revolves around the
existance of a workspace. Suppose we have a versioned resource whose tip
revision is checked out. On a non-workspace server, is the target of a the
versioned resource the tip revision or the working resource?
Neil
-----Original Message-----
From: Geoffrey M. Clemm [mailto:geoffrey.clemm@rational.com]
Sent: Friday, February 04, 2000 10:54 AM
To: ietf-dav-versioning@w3.org
Subject: Adding a DAV:default-revision property to versioned resources
In the spirit of minimizing the complexity of core versioning, I
propose we replace the "default workspace" core versioning concept
with a DAV:default-revision property for versioned resources. You
simply set this property (it is a live property, restricted to
revisions of the versioned resource) when you want to specify the
default revision.
An advanced versioning server will probably allocate some label
to represent the "default revision", but that's an implementation
decision that is left to the server implementor.
The DAV:workspace property of a working resource continues to be
the way to identify a working resource (e.g. in a Workspace header),
but in core versioning, the value of this property is an opaque
identifier. When a server supports workspaces, it would always
store an href as the value of the DAV:workspace property.
Comments?
Cheers,
Geoff