You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Greg Stein <gs...@lyra.org> on 2002/03/10 11:26:29 UTC
[ejw@cse.ucsc.edu: RFC 3253 - Versioning Extensions to WebDAV]
fyi...
----- Forwarded message from Jim Whitehead <ej...@cse.ucsc.edu> -----
From: "Jim Whitehead" <ej...@cse.ucsc.edu>
Subject: RFC 3253 - Versioning Extensions to WebDAV
To: "WebDAV" <w3...@w3.org>
Cc: <mo...@cinenet.net>
Date: Fri, 8 Mar 2002 10:57:16 -0800
The DeltaV protocol specification was released as an RFC today! RFC 3253 is
"Versioning Extensions to WebDAV", which extends RFC 2518 with capabilities
for versioning and configuration management. RFC 3253 is a Proposed
Standard, meaning it has resolved known technical tradeoffs, and is
considered a stable base for widespread implementations.
Major congratulations are due to Geoff Clemm, Jim Amsden, Tim Ellison, Chris
Kaler, and the members of the DeltaV Design Team, and the DeltaV Working
Group, for a job well done after 3.5 years of very hard work.
http://www.ietf.org/rfc/rfc3253.txt
Abstract
This document specifies a set of methods, headers, and resource types
that define the WebDAV (Web Distributed Authoring and Versioning)
versioning extensions to the HTTP/1.1 protocol. WebDAV versioning
will minimize the complexity of clients that are capable of
interoperating with a variety of versioning repository managers, to
facilitate widespread deployment of applications capable of utilizing
the WebDAV Versioning services. WebDAV versioning includes automatic
versioning for versioning-unaware clients, version history
management, workspace management, baseline management, activity
management, and URL namespace versioning.
- Jim
----- End forwarded message -----
--
Greg Stein, http://www.lyra.org/