W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2002

RE: Comment and author for a new version.

From: Clemm, Geoff <gclemm@rational.com>
Date: Thu, 11 Apr 2002 23:21:15 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B106819087@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
The protocol currently does not support property initialization
in the VERSION-CONTROL method, so you'd have to PROPPATCH it
after the resource was created.  Note that there are three different
resources, each with their own DAV:creator-displayname and DAV:comment,
i.e. the VCR, the version history, and the initial version.
The VCR would contain the DAV:creator-displayname and DAV:comment
of the unversioned resource (i.e. the VERSION-CONTROL request does not
change those properties).  The initial value for those properties of
the new version history and the new initial version is server defined.
The protocol only defines what happens with dead properties.


-----Original Message-----
From: Edgar Schwarz [mailto:edgar@edgarschwarz.de]
Sent: Thursday, April 11, 2002 8:15 AM
To: ietf-dav-versioning@w3.org
Subject: Comment and author for a new version.

Hi all,
my repository wants to have some information when I create a new
So I would like to put a resource under version control like this:

Host: work.edgarschwarz.de
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

<?xml version="1.0" encoding="utf-8" ?>
<version-control xmlns="DAV:">
	<creator-displayname>Edgar Schwarz</creator-displayname>
	<comment>This is a comment for a version</comment>

This also would apply to CHECKIN and BASELINE_CONTROL naturally.
Or should I do a PROPPATCH for creator-displayname and comment before

Cheers, Edgar
Received on Thursday, 11 April 2002 23:21:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:48 UTC