W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2001

Re: Introduction

From: <Tim_Ellison@uk.ibm.com>
Date: Fri, 2 Feb 2001 12:19:17 +0000
To: ietf-dav-versioning@w3.org
Message-ID: <802569E7.0043AFBC.00@d06mta07.portsmouth.uk.ibm.com>


Hmm, this feels like you are leading the reader down a certain path -- I
suggest this is better covered in a scenarios doc.

Regards,

Tim


"James J. Hunt" <jjh@allerton.de> on 2001-02-02 06:11:50 AM

Please respond to jjh@ira.uka.de

To:   ietf-dav-versioning@w3.org
cc:
Subject:  Introduction






Dear Colleagues,

The introduction is a bit short.  In particular, no mention is made of
the different operating modes that
this protocol is designed to support.  That makes it a bit difficult for
someone who has not sat in on
several committee meetings to understand why the protocol is "so
complicated".  Can a new paragraph
after the second paragraph in the introduction as follows be added?

The extensions to WebDAV described here are designed to support three
different client/server
interaction scenarios: versioning unaware clients, server managed
workspaces, and client managed
workspace.  In core versioning a compliant server provides a single
access point for each resource.
In essence, this is a default server side workspace.  A server may allow
versioning unaware clients
to modify resources in this workspace though normal WebDAV requests.
This allows sequential
modification of resources.  In order to support parallel modification of
resources, there needs to be
a method to create new workspaces.  To possibilities are supported:
server side workspaces via the
workspace option and client side workspace through the <client-workspace
resource> option.

Sincerely,
James J. Hunt
Jürgen Reuter
Received on Friday, 2 February 2001 07:20:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:40 GMT