Next message: Geoffrey M. Clemm: "draft-ietf-deltav-verisioning-08.2 now available"
Date: Wed, 20 Sep 2000 15:25:44 -0400 (EDT)
Message-Id: <200009201925.PAA17456@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Comments on 08.1
From: "Boris Bokowski/OTT/OTI" <Boris_Bokowski@oti.com>
Date: Wed, 20 Sep 2000 14:32:42 -0400
Here are a few comments on the 08.1 spec:
5.3.4 DAV:auto-version
This property only makes sense for a checked in version selector.
If a user can modify this property, you probably don't want it
disappearing (and needing to be re-set) when you checkout the version
selector, so having it on the checked-out version selector is probably
best.
8 Versioning and existing methods, last paragraph
If a server puts a newly created resource under version control
automatically, will the new version selector be in the checked in state or
in the checked out state? The spec should be explicit about this.
Done. In particular: "The new version selector MUST be in the
state that would result from applying the VERSION-CONTROL method to
the new resource."
10.2 CHECKOUT (Marshalling)
The Target-Selector header is in the header, not in the body :-)
Oops (:-). Fixed.
The effect of the Target-Selector header is not specified. Should be
something like: If a Target-Selector header is included and the
request-URL identifies a version selector, a new working resource will be
created as if the request was applied to the version selected by the
Target-Selector header.
Added.
Note: this is always the case whenever a Target-Selector is specified
(as specified in the Target-Selector header), but I'm happy to
repeat it here (I added it to the post-conditions).
The effect of the request body is not specified. Should be something
like: If a request body is present and it includes the DAV:target element
and the request-URL identifies a version selector, a new working resource
will be created as if the request was applied to the version selected by
the DAV:target property of the version selector.
Added.
10.3 CHECKIN (Postconditions)
Refers to the DAV:version property of versions, which was removed.
Removed this reference.
10.4 UNCHECKOUT (Postconditions)
Typo: "The version selector has not DAV:checked-out property value" ->
"... has no ..."
Fixed.
10.6.1 example for LABEL
In the example, there is white space around the label-name, but the
explanation says that the label "released" (not " released ") is applied
to the target version. Are servers supposed to strip away whitespace?
I'll just get rid of the white space around the label-name. I can
never remember what exactly the XML white space rules are (:-).
12.1 Baseline
The explanation should include the addition from 14.5.1: "(as well as the
target of the collection itself, if it is a version selector)"
Added.
16.11 SET-TARGET
The target of the collection itself (if it is a version selector) is
modified as well.
Added.
17.1 MKWORKSPACE
Should be "particular collections", "the locations of these collections"
(can be more than one)
Same for 17.2 MKACTIVITY
Fixed.
Thanks for catching all of these errors, Boris!
Cheers,
Geoff