RFC3253
Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)

Issues List

Key:

The identifier is a name for the issue (and is unique within this document).

The type of issue is one of:
- Editorial: for example typographical errors, poor clarity, or inconsistent terminology.
- Change: an addition, deletion, or modification to the published specification.
The status of the issue is one of:
- Open: subject to ongoing discussion and not yet resolved.
- Closed: resolved by the working group.
- Editor: an editorial issue has been resolved unilaterally. Can be re-opened by the working group.

The description is a succinct overview of the issue.

The reference is an indication of where the issue was first raised.

The resolution describes the specification change that resolves the issue.

Identifier	Type	Status	Description	Reference	Resolution
1.4.5_STABLE_HREF	Editorial	Closed	Clarify that a DAV:href that refers to a version or version history must contain the stable URL.	Julian Reschke: message	Done.
2.1_CHECKOUT_IN_PLACE	Editorial	Editor	Typo: "checkout" should be "checkout-in-place"	Jeff Thompson: message	Fixed.
3.1.4_LIVE_PROPERTY_DTD	Editorial	Editor	The supported-live-property DTD in section 3. 1.4 should have “prop”, not “name”.	Julian Reschke: message	Replace “name” with “prop” in the DTD.
3.5_LOCATION	Change	Editor	Need the location of the newly created version.	Julian Reschke: message	Return the new version in a Location header.
3.6_ DEPTH_MARSHALLING	Editorial	Closed	This section states that the Depth>0 marshalling should place the report in the DAV:prop element, while 2518 states that the DAV:prop element must contain properties.	Julian Reschke: message	Clarify that 3253 extends the DAV:prop element to also contain reports.
3.6_DEPTH_LIMIT	Change	Closed	There is no postcondition that allows a server to limit the depth of a depth:Infinity request.	Julian Reschke: message	Add a DAV:acceptable-depth precondition to the REPORT method.
3.8_ATTRIBUTE_NAMESPACE	Change	Closed	Should the attributes be defined to be in the DAV: namespace.	John Vasta: message	No, that would be an incompatible change.
5.4_INCLUDE_COLLECTION	Editorial	Editor	The report should include the collection identified by the request-URL if its history is one being located.	Julian Reschke: message	Indicate that the report should include the collection identified by the request-URL if its history is one being located.
4.1.2_CHECKOUT_TYPO	Editorial	Editor	It should be DAV:checkin-fork, not DAV:checkout-fork	Geoff Clemm: message	Replace DAV:checkout-fork with DAV:checkin-fork.
5.4.1_BAD_XML	Editorial	Editor	The XML in section 5.4.1 is ill-formed.	Julian Reschke: message	Replace </D:version-history> with <D:version-history/> and <D:version-history-set/> with </D:version-history-set>.
5.5_OPTIONS_BODY	Change	Closed	Since the OPTIONS method already existed, its body should not be constrained to be DAV:options, since this could conflict with other extensions.	Julian Reschke: message	Use properties instead of OPTIONS to marshal these requests.
5.5_USE_PROPERTIES	Change	Closed	The WebDAV working group has decided to use properties instead of OPTIONS to marshal requests for this kind of information (for example, in the ACL specification).	Geoff Clemm: message	Use properties instead of OPTIONS to marshal these requests.
6.2.1_NO_WORKSPACE	Editorial	Editor	It is unclear whether the DAV:workspace of a resource with no parent collection should be empty or absent.	Julian Reschke: message	State that it should be absent.
6.7_STATUS	Editorial	Editor	Clarify that the response status must be 201.	Julian Reschke: message	Done.
7.1_MUST_BE_CHECKED_IN	Change	Closed	There is no precondition stating that UPDATE can only be applied to a checked-in VCR.	Julian Reschke: message	Add precondition.
7.1.1_INCOMPLETE_XML	Editorial	Editor	In the UPDATE method example of section 7.1.1 the response is missing the final </D:multistatus> XML element.	Julian Reschke: message	Add missing element
8.3_ LABEL_HEADER	Change	Closed	The Label header has poorly defined semantics when used with Depth header, and is inconsistent with HTTP variant processing.	Julian Reschke: message	Replace the Label header with a DAV:labeled-version report.
9.3_RESOURCETYPE	Editorial	Editor	The DAV:resourcetype of a working resource is not defined.	Girish B.H.: message	Require the DAV:resourcetype of the working resource to be that of the checked out version.
12.6.1_MISSING_ ELEMENT	Editorial	Editor	In the BASELINE_CONTROL method example of section 12.6.1 the request is missing the <D:baseline> element around the <D:hef> element.	Edgar Schwarz: message	Add missing <D:baseline> around <D:href> element.
13.1_RESOURCETYPE	Change	Closed	The DAV:resourcetype of an activity should include DAV:activity, rather than be DAV:activity.	Alison Macmillan: message	Done. Analogous change made for version-history and baseline resources.
14_MISSING_ SEMANTICS	Editorial	Editor	The semantics of UNCHECKOUT applied to a version-controlled collection is undefined.	Julian Reschke: message	Define UNCHECKOUT semantics to be those of doing an UPDATE to the DAV:checked-out version.
14.1.1_MISSING_BRACKET	Editorial	Editor	An open angle bracket is missing.	Julian Reschke: message	Add missing open angle bracket.
14.4_CLARIFY_VH_DELETE	Editorial	Editor	The deletion of a version history from a working collection could be interpreted as the deletion of that version history.	Sasha Zivkov: message	Define the DELETE semantics of the member of a working collection to just delete the binding, and not the version history resource itself.
14.4_CLARIFY_VH_DELETE_2	Editorial	Closed	What happens if a DELETE is applied to the stable URL of a version history, and there are bindings to that version history in a working collection.	Julian Reschke: message	Disallow the deletion via the stable URL while there are other bindings to a version history or version.
14.9_BINDING_NAMES	Editorial	Editor	When a working collection is created, the names of the bindings to version histories are not defined.	Girish B.H.: message	Define the binding names to be those specified in the DAV:version-controlled-binding-set property.
A.18_MISSING_METHODS	Editorial	Editor	In the resource classification section A.18, the supported methods of a checked-out version-controlled configuration should include all checked-out version-controlled resource methods.	Sasha Zivkov: message	Add checked-in resource “mixin” category. Remove checked-out VCR and checked-out VCC categories. Add checked-in and checked-out mixins to VCR category. Reorder categories so that checked-in and checked-out categories precede VCR category.

Last modified: 16-Oct-2003 by GMC