7Network Working Group G. Clemm
8Request for Comments: 3253 Rational Software
9Category: Standards Track J. Amsden
19 Versioning Extensions to WebDAV
20 (Web Distributed Authoring and Versioning)
24 This document specifies an Internet standards track protocol for the
25 Internet community, and requests discussion and suggestions for
26 improvements. Please refer to the current edition of the "Internet
27 Official Protocol Standards" (STD 1) for the standardization state
28 and status of this protocol. Distribution of this memo is unlimited.
32 Copyright (C) The Internet Society (2002). All Rights Reserved.
36 This document specifies a set of methods, headers, and resource types
37 that define the WebDAV (Web Distributed Authoring and Versioning)
38 versioning extensions to the HTTP/1.1 protocol. WebDAV versioning
39 will minimize the complexity of clients that are capable of
40 interoperating with a variety of versioning repository managers, to
41 facilitate widespread deployment of applications capable of utilizing
42 the WebDAV Versioning services. WebDAV versioning includes automatic
43 versioning for versioning-unaware clients, version history
44 management, workspace management, baseline management, activity
45 management, and URL namespace versioning.
49 1 Introduction.................................................... 6
50 1.1 Relationship to WebDAV........................................ 7
51 1.2 Notational Conventions........................................ 8
52 1.3 Terms......................................................... 8
53 1.4 Property Values............................................... 11
54 1.4.1 Initial Property Value..................................... 11
58Clemm, et al. Standards Track [Page 1]
60RFC 3253 Versioning Extensions to WebDAV March 2002
63 1.4.2 Protected Property Value................................... 12
64 1.4.3 Computed Property Value.................................... 12
65 1.4.4 Boolean Property Value..................................... 12
66 1.4.5 DAV:href Property Value.................................... 12
67 1.5 DAV Namespace XML Elements.................................... 12
68 1.6 Method Preconditions and Postconditions....................... 12
69 1.6.1 Example - CHECKOUT request................................. 13
70 1.7 Clarification of COPY Semantics with Overwrite:T.............. 13
71 1.8 Versioning Methods and Write Locks............................ 14
72 2 Basic Versioning Features....................................... 14
73 2.1 Basic Versioning Packages..................................... 14
74 2.2 Basic Versioning Semantics.................................... 16
75 2.2.1 Creating a Version-Controlled Resource..................... 16
76 2.2.2 Modifying a Version-Controlled Resource.................... 17
77 2.2.3 Reporting.................................................. 19
78 3 Version-Control Feature......................................... 20
79 3.1 Additional Resource Properties................................ 20
80 3.1.1 DAV:comment................................................ 20
81 3.1.2 DAV:creator-displayname.................................... 20
82 3.1.3 DAV:supported-method-set (protected)....................... 20
83 3.1.4 DAV:supported-live-property-set (protected)................ 21
84 3.1.5 DAV:supported-report-set (protected)....................... 21
85 3.2 Version-Controlled Resource Properties........................ 21
86 3.2.1 DAV:checked-in (protected)................................. 21
87 3.2.2 DAV:auto-version........................................... 22
88 3.3 Checked-Out Resource Properties............................... 22
89 3.3.1 DAV:checked-out (protected)................................ 23
90 3.3.2 DAV:predecessor-set........................................ 23
91 3.4 Version Properties............................................ 23
92 3.4.1 DAV:predecessor-set (protected)............................ 23
93 3.4.2 DAV:successor-set (computed)............................... 23
94 3.4.3 DAV:checkout-set (computed)................................ 23
95 3.4.4 DAV:version-name (protected)............................... 24
96 3.5 VERSION-CONTROL Method........................................ 24
97 3.5.1 Example - VERSION-CONTROL.................................. 25
98 3.6 REPORT Method................................................. 25
99 3.7 DAV:version-tree Report....................................... 26
100 3.7.1 Example - DAV:version-tree Report.......................... 27
101 3.8 DAV:expand-property Report.................................... 29
102 3.8.1 Example - DAV:expand-property.............................. 30
103 3.9 Additional OPTIONS Semantics.................................. 31
104 3.10 Additional PUT Semantics..................................... 31
105 3.11 Additional PROPFIND Semantics................................ 32
106 3.12 Additional PROPPATCH Semantics............................... 33
107 3.13 Additional DELETE Semantics.................................. 33
108 3.14 Additional COPY Semantics.................................... 34
109 3.15 Additional MOVE Semantics.................................... 34
110 3.16 Additional UNLOCK Semantics.................................. 35
114Clemm, et al. Standards Track [Page 2]
116RFC 3253 Versioning Extensions to WebDAV March 2002
119 4 Checkout-In-Place Feature....................................... 35
120 4.1 Additional Version Properties................................. 35
121 4.1.1 DAV:checkout-fork.......................................... 36
122 4.1.2 DAV:checkin-fork........................................... 36
123 4.2 Checked-Out Resource Properties............................... 36
124 4.2.1 DAV:checkout-fork.......................................... 36
125 4.2.2 DAV:checkin-fork........................................... 37
126 4.3 CHECKOUT Method............................................... 37
127 4.3.1 Example - CHECKOUT......................................... 38
128 4.4 CHECKIN Method................................................ 38
129 4.4.1 Example - CHECKIN.......................................... 40
130 4.5 UNCHECKOUT Method............................................. 40
131 4.5.1 Example - UNCHECKOUT....................................... 41
132 4.6 Additional OPTIONS Semantics.................................. 42
133 5 Version-History Feature......................................... 42
134 5.1 Version History Properties.................................... 42
135 5.1.1 DAV:version-set (protected)................................ 42
136 5.1.2 DAV:root-version (computed)................................ 42
137 5.2 Additional Version-Controlled Resource Properties............. 42
138 5.2.1 DAV:version-history (computed)............................. 43
139 5.3 Additional Version Properties................................. 43
140 5.3.1 DAV:version-history (computed)............................. 43
141 5.4 DAV:locate-by-history Report.................................. 43
142 5.4.1 Example - DAV:locate-by-history Report..................... 44
143 5.5 Additional OPTIONS Semantics.................................. 45
144 5.6 Additional DELETE Semantics................................... 46
145 5.7 Additional COPY Semantics..................................... 46
146 5.8 Additional MOVE Semantics..................................... 46
147 5.9 Additional VERSION-CONTROL Semantics.......................... 46
148 5.10 Additional CHECKIN Semantics................................. 47
149 6 Workspace Feature............................................... 47
150 6.1 Workspace Properties.......................................... 48
151 6.1.1 DAV:workspace-checkout-set (computed)...................... 48
152 6.2 Additional Resource Properties................................ 48
153 6.2.1 DAV:workspace (protected).................................. 48
154 6.3 MKWORKSPACE Method............................................ 48
155 6.3.1 Example - MKWORKSPACE...................................... 49
156 6.4 Additional OPTIONS Semantics.................................. 49
157 6.4.1 Example - OPTIONS.......................................... 51
158 6.5 Additional DELETE Semantics................................... 51
159 6.6 Additional MOVE Semantics..................................... 52
160 6.7 Additional VERSION-CONTROL Semantics.......................... 52
161 6.7.1 Example - VERSION-CONTROL.................................. 53
162 7 Update Feature.................................................. 53
163 7.1 UPDATE Method................................................. 53
164 7.1.1 Example - UPDATE........................................... 55
165 7.2 Additional OPTIONS Semantics.................................. 55
166 8 Label Feature................................................... 56
170Clemm, et al. Standards Track [Page 3]
172RFC 3253 Versioning Extensions to WebDAV March 2002
175 8.1 Additional Version Properties................................. 56
176 8.1.1 DAV:label-name-set (protected)............................. 56
177 8.2 LABEL Method.................................................. 56
178 8.2.1 Example - Setting a label.................................. 58
179 8.3 Label Header.................................................. 58
180 8.4 Additional OPTIONS Semantics.................................. 59
181 8.5 Additional GET Semantics...................................... 59
182 8.6 Additional PROPFIND Semantics................................. 59
183 8.7 Additional COPY Semantics..................................... 60
184 8.8 Additional CHECKOUT Semantics................................. 60
185 8.9 Additional UPDATE Semantics................................... 61
186 9 Working-Resource Feature........................................ 62
187 9.1 Additional Version Properties................................. 62
188 9.1.1 DAV:checkout-fork.......................................... 62
189 9.1.2 DAV:checkin-fork........................................... 63
190 9.2 Working Resource Properties................................... 63
191 9.2.1 DAV:auto-update (protected)................................ 63
192 9.2.2 DAV:checkout-fork.......................................... 63
193 9.2.3 DAV:checkin-fork........................................... 63
194 9.3 CHECKOUT Method (applied to a version)........................ 63
195 9.3.1 Example - CHECKOUT of a version............................ 65
196 9.4 CHECKIN Method (applied to a working resource)................ 65
197 9.4.1 Example - CHECKIN of a working resource.................... 66
198 9.5 Additional OPTIONS Semantics.................................. 67
199 9.6 Additional COPY Semantics..................................... 67
200 9.7 Additional MOVE Semantics..................................... 67
201 10 Advanced Versioning Features.................................. 67
202 10.1 Advanced Versioning Packages................................. 68
203 10.2 Advanced Versioning Terms.................................... 68
204 11 MERGE Feature................................................. 70
205 11.1 Additional Checked-Out Resource Properties................... 70
206 11.1.1 DAV:merge-set............................................. 70
207 11.1.2 DAV:auto-merge-set........................................ 71
208 11.2 MERGE Method................................................. 71
209 11.2.1 Example - MERGE........................................... 74
210 11.3 DAV:merge-preview Report..................................... 75
211 11.3.1 Example - DAV:merge-preview Report........................ 76
212 11.4 Additional OPTIONS Semantics................................. 77
213 11.5 Additional DELETE Semantics.................................. 77
214 11.6 Additional CHECKIN Semantics................................. 77
215 12 Baseline Feature.............................................. 77
216 12.1 Version-Controlled Configuration Properties.................. 78
217 12.1.1 DAV:baseline-controlled-collection (protected)............ 78
218 12.2 Checked-Out Configuration Properties......................... 78
219 12.2.1 DAV:subbaseline-set....................................... 78
220 12.3 Baseline Properties.......................................... 78
221 12.3.1 DAV:baseline-collection (protected)....................... 79
222 12.3.2 DAV:subbaseline-set (protected)........................... 79
226Clemm, et al. Standards Track [Page 4]
228RFC 3253 Versioning Extensions to WebDAV March 2002
231 12.4 Additional Resource Properties............................... 79
232 12.4.1 DAV:version-controlled-configuration (computed)........... 79
233 12.5 Additional Workspace Properties.............................. 80
234 12.5.1 DAV:baseline-controlled-collection-set (computed)......... 80
235 12.6 BASELINE-CONTROL Method...................................... 80
236 12.6.1 Example - BASELINE-CONTROL................................ 82
237 12.7 DAV:compare-baseline Report.................................. 84
238 12.7.1 Example - DAV:compare-baseline Report..................... 85
239 12.8 Additional OPTIONS Semantics................................. 86
240 12.9 Additional MKCOL Semantics................................... 86
241 12.10 Additional COPY Semantics................................... 86
242 12.11 Additional CHECKOUT Semantics............................... 86
243 12.12 Additional CHECKIN Semantics................................ 86
244 12.13 Additional UPDATE Semantics................................. 87
245 12.14 Additional MERGE Semantics.................................. 89
246 13 Activity Feature.............................................. 90
247 13.1 Activity Properties.......................................... 91
248 13.1.1 DAV:activity-version-set (computed)....................... 91
249 13.1.2 DAV:activity-checkout-set (computed)...................... 92
250 13.1.3 DAV:subactivity-set....................................... 92
251 13.1.4 DAV:current-workspace-set (computed)...................... 92
252 13.2 Additional Version Properties................................ 92
253 13.2.1 DAV:activity-set.......................................... 93
254 13.3 Additional Checked-Out Resource Properties................... 93
255 13.3.1 DAV:unreserved............................................ 93
256 13.3.2 DAV:activity-set.......................................... 93
257 13.4 Additional Workspace Properties.............................. 93
258 13.4.1 DAV:current-activity-set.................................. 94
259 13.5 MKACTIVITY Method............................................ 94
260 13.5.1 Example - MKACTIVITY...................................... 95
261 13.6 DAV:latest-activity-version Report........................... 95
262 13.7 Additional OPTIONS Semantics................................. 96
263 13.8 Additional DELETE Semantics.................................. 96
264 13.9 Additional MOVE Semantics.................................... 97
265 13.10 Additional CHECKOUT Semantics............................... 97
266 13.10.1 Example - CHECKOUT with an activity...................... 98
267 13.11 Additional CHECKIN Semantics................................ 99
268 13.12 Additional MERGE Semantics.................................. 99
269 14 Version-Controlled-Collection Feature.........................100
270 14.1 Version-Controlled Collection Properties.....................102
271 14.1.1 DAV:eclipsed-set (computed)...............................102
272 14.2 Collection Version Properties................................103
273 14.2.1 DAV:version-controlled-binding-set (protected)............103
274 14.3 Additional OPTIONS Semantics.................................103
275 14.4 Additional DELETE Semantics..................................103
276 14.5 Additional MKCOL Semantics...................................104
277 14.6 Additional COPY Semantics....................................104
278 14.7 Additional MOVE Semantics....................................104
282Clemm, et al. Standards Track [Page 5]
284RFC 3253 Versioning Extensions to WebDAV March 2002
287 14.8 Additional VERSION-CONTROL Semantics.........................104
288 14.9 Additional CHECKOUT Semantics................................105
289 14.10 Additional CHECKIN Semantics................................105
290 14.11 Additional UPDATE and MERGE Semantics.......................106
291 15 Internationalization Considerations...........................106
292 16 Security Considerations.......................................107
293 16.1 Auditing and Traceability....................................107
294 16.2 Increased Need for Access Control............................108
295 16.3 Security Through Obscurity...................................108
296 16.4 Denial of Service............................................108
297 17 IANA Considerations...........................................109
298 18 Intellectual Property.........................................109
299 19 Acknowledgements..............................................109
300 20 References....................................................110
301 Appendix A - Resource Classification..............................111
302 A.1 DeltaV-Compliant Unmapped URL.................................111
303 A.2 DeltaV-Compliant Resource.....................................111
304 A.3 DeltaV-Compliant Collection...................................112
305 A.4 Versionable Resource..........................................112
306 A.5 Version-Controlled Resource...................................112
307 A.6 Version.......................................................113
308 A.7 Checked-In Version-Controlled Resource........................113
309 A.8 Checked-Out Resource..........................................113
310 A.9 Checked-Out Version-Controlled Resource.......................114
311 A.10 Working Resource.............................................114
312 A.11 Version History..............................................114
313 A.12 Workspace....................................................115
314 A.13 Activity.....................................................115
315 A.14 Version-Controlled Collection................................115
316 A.15 Collection Version...........................................115
317 A.16 Version-Controlled Configuration.............................116
318 A.17 Baseline.....................................................116
319 A.18 Checked-Out Version-Controlled Configuration.................116
320 Authors' Addresses................................................117
321 Full Copyright Statement..........................................118
325 This document specifies a set of methods, headers, and properties
326 that define the WebDAV (Web Distributed Authoring and Versioning)
327 versioning extensions to the HTTP/1.1 protocol. Versioning is
328 concerned with tracking and accessing the history of important states
329 of a web resource, such as a standalone web page. The benefits of
330 versioning in the context of the worldwide web include:
338Clemm, et al. Standards Track [Page 6]
340RFC 3253 Versioning Extensions to WebDAV March 2002
343 - A resource has an explicit history and a persistent identity
344 across the various states it has had during the course of that
345 history. It allows browsing through past and alternative versions
346 of a resource. Frequently the modification and authorship history
347 of a resource is critical information in itself.
349 - Resource states (versions) are given stable names that can support
350 externally stored links for annotation and link server support.
351 Both annotation and link servers frequently need to store stable
352 references to portions of resources that are not under their
353 direct control. By providing stable states of resources, version
354 control systems allow not only stable pointers into those
355 resources, but also well defined methods to determine the
356 relationships of those states of a resource.
358 WebDAV Versioning defines both basic and advanced versioning
361 Basic versioning allows users to:
363 - Put a resource under version control
364 - Determine whether a resource is under version control
365 - Determine whether a resource update will automatically be captured
367 - Create and access distinct versions of a resource
369 Advanced versioning provides additional functionality for parallel
370 development and configuration management of sets of web resources.
372 This document will first define the properties and method semantics
373 for the basic versioning features, and then define the additional
374 properties and method semantics for the advanced versioning features.
375 An implementer that is only interested in basic versioning should
376 skip the advanced versioning sections (Section 10 to Section 14).
3781.1 Relationship to WebDAV
380 To maximize interoperability and the use of existing protocol
381 functionality, versioning support is designed as extensions to the
382 WebDAV protocol [RFC2518], which itself is an extension to the HTTP
383 protocol [RFC2616]. All method marshalling and postconditions
384 defined by RFC 2518 and RFC 2616 continue to hold, to ensure that
385 versioning unaware clients can interoperate successfully with
386 versioning servers. Although the versioning extensions are designed
387 to be orthogonal to most aspects of the WebDAV and HTTP protocols, a
388 clarification to RFC 2518 is required for effective interoperable
389 versioning. This clarification is described in Section 1.7.
394Clemm, et al. Standards Track [Page 7]
396RFC 3253 Versioning Extensions to WebDAV March 2002
3991.2 Notational Conventions
401 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
402 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
403 document are to be interpreted as described in RFC 2119.
405 The term "protected" is placed in parentheses following the
406 definition of a protected property (see Section 1.4.2).
408 The term "computed" is placed in parentheses following the definition
409 of a computed property (see Section 1.4.3).
411 When an XML element type in the "DAV:" namespace is referenced in
412 this document outside of the context of an XML fragment, the string
413 "DAV:" will be prefixed to the element type.
415 When a method is defined in this document, a list of preconditions
416 and postconditions will be defined for that method. If the semantics
417 of an existing method is being extended, a list of additional
418 preconditions and postconditions will be defined. A precondition or
419 postcondition is prefixed by a parenthesized XML element type that
420 identifies that precondition or postcondition (see Section 1.6).
424 This document uses the terms defined in RFC 2616, in RFC 2518, and in
425 this section. Section 2.2 defines the semantic versioning model
426 underlying this terminology.
428 Version Control, Checked-In, Checked-Out
430 "Version control" is a set of constraints on how a resource can be
431 updated. A resource under version control is either in a
432 "checked-in" or "checked-out" state, and the version control
433 constraints apply only while the resource is in the checked-in
438 A "versionable resource" is a resource that can be put under
441 Version-Controlled Resource
443 When a versionable resource is put under version control, it
444 becomes a "version-controlled resource". A version-controlled
445 resource can be "checked out" to allow modification of its content
446 or dead properties by standard HTTP and WebDAV methods.
450Clemm, et al. Standards Track [Page 8]
452RFC 3253 Versioning Extensions to WebDAV March 2002
457 A "checked-out resource" is a resource under version control that
458 is in the checked-out state.
462 A "version resource", or simply "version", is a resource that
463 contains a copy of a particular state (content and dead
464 properties) of a version-controlled resource. A version is
465 created by "checking in" a checked-out resource. The server
466 allocates a distinct new URL for each new version, and this URL
467 will never be used to identify any resource other than that
468 version. The content and dead properties of a version never
471 Version History Resource
473 A "version history resource", or simply "version history", is a
474 resource that contains all the versions of a particular version-
479 A "version name" is a string chosen by the server to distinguish
480 one version of a version history from the other versions of that
481 version history. Versions from different version histories may
482 have the same version name.
484 Predecessor, Successor, Ancestor, Descendant
486 When a version-controlled resource is checked out and then
487 subsequently checked in, the version that was checked out becomes
488 a "predecessor" of the version created by the checkin. A client
489 can specify multiple predecessors for a new version if the new
490 version is logically a merge of those predecessors. When a
491 version is connected to another version by traversing one or more
492 predecessor relations, it is called an "ancestor" of that version.
493 The inverse of the predecessor and ancestor relations are the
494 "successor" and "descendant" relations. Therefore, if X is a
495 predecessor of Y, then Y is a successor of X, and if X is an
496 ancestor of Y, then Y is a descendant of X.
498 Root Version Resource
500 The "root version resource", or simply "root version", is the
501 version in a version history that is an ancestor of every other
502 version in that version history.
506Clemm, et al. Standards Track [Page 9]
508RFC 3253 Versioning Extensions to WebDAV March 2002
513 A "workspace resource", or simply "workspace", is a collection
514 that contains at most one version-controlled resource for a given
515 version history (see Section 6).
519 A "working resource" is a checked-out resource created by the
520 server at a server-defined URL when a version (instead of a
521 version-controlled resource) is checked out. Unlike a checked-out
522 version-controlled resource, a working resource is deleted when it
527 When a second successor is added to a version, this creates a
528 "fork" in the version history. When a version is created with
529 multiple predecessors, this creates a "merge" in the version
530 history. A server may restrict the version history to be linear
531 (with no forks or merges), but an interoperable versioning client
532 should be prepared to deal with both forks and merges in the
562Clemm, et al. Standards Track [Page 10]
564RFC 3253 Versioning Extensions to WebDAV March 2002
567 The following diagram illustrates several of the previous
568 definitions. Each box represents a version and each line between two
569 boxes represents a predecessor/successor relationship. For example,
570 it shows V3 is a predecessor of V5, V7 is a successor of V5, V1 is an
571 ancestor of V4, and V7 is a descendant of V4. It also shows that
572 there is a fork at version V2 and a merge at version V7.
577 Root Version -------> | | V1
582 Version Name ----> V2 | | | Ancestor
592 | | V5 | | V6 | Descendant
602 A "label" is a name that can be used to select a version from a
603 version history. A label can be assigned by either a client or
604 the server. The same label can be used in different version
6091.4.1 Initial Property Value
611 Unless an initial value of a property of a given type is defined by
612 this document, the initial value of a property of that type is
613 implementation dependent.
618Clemm, et al. Standards Track [Page 11]
620RFC 3253 Versioning Extensions to WebDAV March 2002
6231.4.2 Protected Property Value
625 When a property of a specific kind of resource is "protected", the
626 property value cannot be updated on that kind of resource except by a
627 method explicitly defined as updating that specific property. In
628 particular, a protected property cannot be updated with a PROPPATCH
629 request. Note that a given property can be protected on one kind of
630 resource, but not protected on another kind of resource.
6321.4.3 Computed Property Value
634 When a property is "computed", its value is defined in terms of a
635 computation based on the content and other properties of that
636 resource, or even of some other resource. When the semantics of a
637 method is defined in this document, the effect of that method on
638 non-computed properties will be specified; the effect of that method
639 on computed properties will not be specified, but can be inferred
640 from the computation defined for those properties. A computed
641 property is always a protected property.
6431.4.4 Boolean Property Value
645 Some properties take a Boolean value of either "false" or "true".
6471.4.5 DAV:href Property Value
649 The DAV:href XML element is defined in RFC 2518, Section 12.3.
6511.5 DAV Namespace XML Elements in Request and Response Bodies
653 Although WebDAV request and response bodies can be extended by
654 arbitrary XML elements, which can be ignored by the message
655 recipient, an XML element in the DAV namespace MUST NOT be used in
656 the request or response body of a versioning method unless that XML
657 element is explicitly defined in an IETF RFC.
6591.6 Method Preconditions and Postconditions
661 A "precondition" of a method describes the state of the server that
662 must be true for that method to be performed. A "postcondition" of a
663 method describes the state of the server that must be true after that
664 method has been completed. If a method precondition or postcondition
665 for a request is not satisfied, the response status of the request
666 MUST be either 403 (Forbidden) if the request should not be repeated
667 because it will always fail, or 409 (Conflict) if it is expected that
668 the user might be able to resolve the conflict and resubmit the
674Clemm, et al. Standards Track [Page 12]
676RFC 3253 Versioning Extensions to WebDAV March 2002
679 In order to allow better client handling of 403 and 409 responses, a
680 distinct XML element type is associated with each method precondition
681 and postcondition of a request. When a particular precondition is
682 not satisfied or a particular postcondition cannot be achieved, the
683 appropriate XML element MUST be returned as the child of a top-level
684 DAV:error element in the response body, unless otherwise negotiated
685 by the request. In a 207 Multi-Status response, the DAV:error
686 element would appear in the appropriate DAV:responsedescription
6891.6.1 Example - CHECKOUT request with DAV:must-be-checked-in response
693 CHECKOUT /foo.html HTTP/1.1
698 HTTP/1.1 409 Conflict
699 Content-Type: text/xml; charset="utf-8"
702 <?xml version="1.0" encoding="utf-8" ?>
703 <D:error xmlns:D="DAV:">
704 <D:must-be-checked-in/>
707 In this example, the request to CHECKOUT /foo.html fails because
708 /foo.html is not checked in.
7101.7 Clarification of COPY Semantics with Overwrite:T
712 RFC 2518, Section 8.8.4 states:
714 "If a resource exists at the destination and the Overwrite header is
715 "T" then prior to performing the copy the server MUST perform a
716 DELETE with "Depth: infinity" on the destination resource."
718 The purpose of this sentence is to ensure that following a COPY, all
719 destination resources have the same content and dead properties as
720 the corresponding resources identified by the request-URL (where a
721 resource with a given name relative to the Destination URL
722 "corresponds" to a resource with the same name relative to the
723 request-URL). If at the time of the request, there already is a
724 resource at the destination that has the same resource type as the
725 corresponding resource at the request-URL, that resource MUST NOT be
726 deleted, but MUST be updated to have the content and dead properties
730Clemm, et al. Standards Track [Page 13]
732RFC 3253 Versioning Extensions to WebDAV March 2002
735 of its corresponding member. If a client wishes all resources at the
736 destination to be deleted prior to the COPY, it MUST explicitly issue
739 The difference between updating a resource and replacing a resource
740 with a new resource is especially important when resource history is
741 being maintained (the former adds to an existing history, while the
742 latter creates a new history). In addition, locking and access
743 control constraints might allow you to update a resource, but not
744 allow you to delete it and create a new one in its place.
746 Note that this clarification does not apply to a MOVE request. A
747 MOVE request with Overwrite:T MUST perform the DELETE with
748 "Depth:infinity" on the destination resource prior to performing the
7511.8 Versioning Methods and Write Locks
753 If a write-locked resource has a non-computed property defined by
754 this document, the property value MUST NOT be changed by a request
755 unless the appropriate lock token is included in the request. Since
756 every method introduced in this document other than REPORT modifies
757 at least one property defined by this document, every versioning
758 method other than REPORT is affected by a write lock. In particular,
759 the method MUST fail with a 423 (Locked) status if the resource is
760 write-locked and the appropriate token is not specified in an If
7632 Basic Versioning Features
765 Each basic versioning feature defines extensions to existing HTTP and
766 WebDAV methods, as well as new resource types, live properties, and
7692.1 Basic Versioning Packages
771 A server MAY support any combination of versioning features.
772 However, in order to minimize the complexity of a WebDAV basic
773 versioning client, a WebDAV basic versioning server SHOULD support
774 one of the following three "packages" (feature sets):
776 - Core-Versioning Package: version-control
777 - Basic-Server-Workspace Package: version-control, workspace,
778 version-history, checkout
779 - Basic-Client-Workspace Package: version-control, working-
780 resource, update, label
786Clemm, et al. Standards Track [Page 14]
788RFC 3253 Versioning Extensions to WebDAV March 2002
791 The core-versioning package supports linear versioning by both
792 versioning-aware and versioning-unaware clients. A versioning-aware
793 client can use reports and properties to access previous versions of
794 a version-controlled resource.
796 The basic workspace packages support parallel development of
797 version-controlled resources. Each client has its own configuration
798 of the shared version-controlled resources, and can make changes to
799 its configuration without disturbing that of another client.
801 In the basic-server-workspace package, all persistent state is
802 maintained on the server. Each client has its own workspace resource
803 allocated on the server, where each workspace identifies a
804 configuration of the shared version-controlled resources. Each
805 client makes changes to its workspace, and can transfer changes when
806 appropriate from one workspace to another. The server workspace
807 package is appropriate for clients with no local persistent state, or
808 for clients that wish to expose their working configurations to other
811 In the basic-client-workspace package, each client maintains in local
812 persistent storage the state for its configuration of the shared
813 version-controlled resources. When a client is ready to make its
814 changes visible to other clients, it allocates a set of "working
815 resources" on the server, updates the content and dead properties of
816 these working resources, and then uses the set of working resources
817 to update the version-controlled resources. The working resources
818 are used, instead of directly updating the version-controlled
819 resources, so that sets of consistent updates can be prepared in
820 parallel by multiple clients. Also, a working resource allows a
821 client to prepare a single update that requires multiple server
822 requests (e.g. updating both the content and dead properties of a
823 resource requires both a PUT and a PROPPATCH). The client workspace
824 package simplifies the server implementation by requiring each client
825 to maintain its own namespace, but this requires that the clients
826 have local persistent state, and does not allow clients to expose
827 their working configurations to other clients.
829 A server that supports both basic workspace packages will
830 interoperate with all basic versioning clients.
842Clemm, et al. Standards Track [Page 15]
844RFC 3253 Versioning Extensions to WebDAV March 2002
8472.2 Basic Versioning Semantics
8492.2.1 Creating a Version-Controlled Resource
851 In order to track the history of the content and dead properties of a
852 versionable resource, a user can put the resource under version
853 control with a VERSION-CONTROL request. A VERSION-CONTROL request
854 performs three distinct operations:
856 1) It creates a new "version history resource". In basic versioning,
857 a version history resource is not assigned a URL, and hence is not
858 visible in the http scheme URL space. However, when the version-
859 history feature (see Section 5) is supported, this changes, and
860 each version history resource is assigned a new distinct and
861 unique server-defined URL.
863 2) It creates a new "version resource" and adds it to the new version
864 history resource. The body and dead properties of the new version
865 resource are a copy of those of the versionable resource.
867 The server assigns the new version resource a new distinct and
870 3) It converts the versionable resource into a "version-controlled
871 resource". The version-controlled resource continues to be
872 identified by the same URL that identified it as a versionable
873 resource. As part of this conversion, it adds a DAV:checked-in
874 property, whose value contains the URL of the new version
877 Note that a versionable resource and a version-controlled resource
878 are not new types of resources (i.e. they introduce no new
879 DAV:resourcetype), but rather they are any type of resource that
880 supports the methods and live properties defined for them in this
881 document, in addition to all the methods and live properties implied
882 by their DAV:resourcetype. For example, a collection (whose
883 DAV:resourcetype is DAV:collection) is a versionable resource if it
884 supports the VERSION-CONTROL method, and is a version-controlled
885 resource if it supports the version-controlled resource methods and
888 In the following example, foo.html is a versionable resource that is
889 put under version control. After the VERSION-CONTROL request
890 succeeds, there are two additional resources: a new version history
891 resource and a new version resource in that version history. The
892 versionable resource is converted into a version-controlled resource,
893 whose DAV:checked-in property identifies the new version resource.
898Clemm, et al. Standards Track [Page 16]
900RFC 3253 Versioning Extensions to WebDAV March 2002
903 The content and dead properties of a resource are represented by the
904 symbol appearing inside the box for that resource (e.g., "S1" in the
907 ===VERSION-CONTROL==>
910 | version- | | history
911 versionable | controlled +----+ resource
912 resource | resource |
913 /foo.html | /foo.html |
915 +----+ | +----+ checked-in +----+ version
916 | S1 | | | S1 |----------->| S1 | resource
917 +----+ | +----+ +----+ /his/73/ver/1
919 Thus, whereas before the VERSION-CONTROL request there was only one,
920 non-version-controlled resource, after VERSION-CONTROL there are
921 three separate, distinct resources, each containing its own state and
922 properties: the version-controlled resource, the version resource,
923 and the version history resource. Since the version-controlled
924 resource and the version resource are separate, distinct resources,
925 when a method is applied to a version-controlled resource, it is only
926 applied to that version-controlled resource, and is not applied to
927 the version resource that is currently identified by the
928 DAV:checked-in property of that version-controlled resource.
929 Although the content and dead properties of a checked-in version-
930 controlled resource are required to be the same as those of its
931 current DAV:checked-in version, its live properties may differ. An
932 implementation may optimize storage by retrieving the content and
933 dead properties of a checked-in version-controlled resource from its
934 current DAV:checked-in version rather than storing them in the
935 version-controlled resource, but this is just an implementation
938 Normally, a resource is placed under version control with an explicit
939 VERSION-CONTROL request. A server MAY automatically place every new
940 versionable resource under version control. In this case, the
941 resulting state on the server MUST be the same as if the client had
942 explicitly applied a VERSION-CONTROL request to the versionable
9452.2.2 Modifying a Version-Controlled Resource
947 In order to use methods like PUT and PROPPATCH to directly modify the
948 content or dead properties of a version-controlled resource, the
949 version-controlled resource must first be checked out. When the
950 checked-out resource is checked in, a new version is created in the
954Clemm, et al. Standards Track [Page 17]
956RFC 3253 Versioning Extensions to WebDAV March 2002
959 version history of that version-controlled resource. The version
960 that was checked out is remembered as the predecessor of the new
963 The DAV:auto-version property (see Sections 3.2.2) of a checked-in
964 version-controlled resource determines how it responds to a method
965 that attempts to modify its content or dead properties. Possible
968 - Fail the request. The resource requires an explicit CHECKOUT
969 request for it to be modified (see Sections 4 and 9.2.1).
971 - Automatically checkout the resource, perform the modification, and
972 automatically checkin the resource. This ensures that every state
973 of the resource is tracked by the server, but can result in an
974 excessive number of versions being created.
976 - Automatically checkout the resource, perform the modification, and
977 then if the resource is not write-locked, automatically checkin
978 the resource. If the resource is write-locked, it remains
979 checked-out until the write-lock is removed (either explicitly
980 through a subsequent UNLOCK request or implicitly through a time-
981 out of the write-lock). This helps a locking client avoid the
982 proliferation of versions, while still allowing a non-locking
983 client to update the resource.
985 - Automatically checkout the resource, perform the modification, and
986 then leave the resource checked out. If the resource is write-
987 locked, it will be automatically checked in when the write-lock is
988 removed, but an explicit CHECKIN operation (see Section 4.4) is
989 required for a non-write-locked resource. This minimizes the
990 number of new versions that will be created by a versioning
991 unaware client, but only a versioning aware client can create new
992 versions of a non-write-locked resource.
994 - Fail the request unless the resource is write-locked. If it is
995 write-locked, automatically checkout the resource and perform the
996 modification. The resource is automatically checked in when the
997 write-lock is removed. This minimizes the number of new versions
998 that will be created by a versioning unaware client, but never
999 automatically checks out a resource that will not subsequently be
1000 automatically checked in.
1010Clemm, et al. Standards Track [Page 18]
1012RFC 3253 Versioning Extensions to WebDAV March 2002
1015 The following diagram illustrates the effect of the checkout/checkin
1016 process on a version-controlled resource and its version history.
1017 The symbol inside a box (S1, S2, S3) represents the current content
1018 and dead properties of the resource represented by that box. The
1019 symbol next to a box (V1, V2, V3) represents the URL for that
1022 ===checkout==> ===PUT==> ===checkin==>
1025 /foo.html (version-controlled resource)
1027 +----+ | +----+ | +----+ | +----+
1028 | S2 | | | S2 | | | S3 | | | S3 |
1029 +----+ | +----+ | +----+ | +----+
1030 Checked-In=V2|Checked-Out=V2|Checked-Out=V2|Checked-In=V3
1033 /his/73 (version history for /foo.html)
1035 +----+ | +----+ | +----+ | +----+
1036 | S1 | V1 | | S1 | V1 | | S1 | V1 | | S1 | V1
1037 +----+ | +----+ | +----+ | +----+
1040 +----+ | +----+ | +----+ | +----+
1041 | S2 | V2 | | S2 | V2 | | S2 | V2 | | S2 | V2
1042 +----+ | +----+ | +----+ | +----+
1049 Note that a version captures only a defined subset of the state of a
1050 resource. In particular, a version of a basic resource captures its
1051 content and dead properties, but not its live properties.
1055 Some versioning information about a resource requires that parameters
1056 be specified along with that request for information. Included in
1057 basic versioning is the required support for an extensible reporting
1058 mechanism, which includes a REPORT method as well as a live property
1059 for determining what reports are supported by a particular resource.
1060 The REPORT method is required by versioning, but it can be used in
1061 non-versioning WebDAV extensions.
1066Clemm, et al. Standards Track [Page 19]
1068RFC 3253 Versioning Extensions to WebDAV March 2002
1071 To allow a client to query the properties of all versions in the
1072 version history of a specified version-controlled resource, basic
1073 versioning provides the DAV:version-tree report (see Section 3.7). A
1074 more powerful version history reporting mechanism is provided by
1075 applying the DAV:expand-property report (see Section 3.8) to a
1076 version history resource (see Section 5).
10783 Version-Control Feature
1080 The version-control feature provides support for putting a resource
1081 under version control, creating an associated version-controlled
1082 resource and version history resource as described in Section 2.2.1.
1083 A server indicates that it supports the version-control feature by
1084 including the string "version-control" as a field in the DAV header
1085 in the response to an OPTIONS request. The version-control feature
1086 MUST be supported if any other versioning feature is supported.
10883.1 Additional Resource Properties
1090 The version-control feature introduces the following REQUIRED
1091 properties for any WebDAV resource.
1095 This property is used to track a brief comment about a resource that
1096 is suitable for presentation to a user. The DAV:comment of a version
1097 can be used to indicate why that version was created.
1099 <!ELEMENT comment (#PCDATA)>
1100 PCDATA value: string
11023.1.2 DAV:creator-displayname
1104 This property contains a description of the creator of the resource
1105 that is suitable for presentation to a user. The DAV:creator-
1106 displayname of a version can be used to indicate who created that
1109 <!ELEMENT creator-displayname (#PCDATA)>
1110 PCDATA value: string
11123.1.3 DAV:supported-method-set (protected)
1114 This property identifies the methods that are supported by the
1115 resource. A method is supported by a resource if there is some state
1116 of that resource for which an application of that method will
1122Clemm, et al. Standards Track [Page 20]
1124RFC 3253 Versioning Extensions to WebDAV March 2002
1127 successfully satisfy all postconditions of that method, including any
1128 additional postconditions added by the features supported by that
1131 <!ELEMENT supported-method-set (supported-method*)>
1132 <!ELEMENT supported-method ANY>
1133 <!ATTLIST supported-method name NMTOKEN #REQUIRED>
1134 name value: a method name
11363.1.4 DAV:supported-live-property-set (protected)
1138 This property identifies the live properties that are supported by
1139 the resource. A live property is supported by a resource if that
1140 property has the semantics defined for that property. The value of
1141 this property MUST identify all live properties defined by this
1142 document that are supported by the resource, and SHOULD identify all
1143 live properties that are supported by the resource.
1145 <!ELEMENT supported-live-property-set (supported-live-property*)>
1146 <!ELEMENT supported-live-property name>
1148 ANY value: a property element type
11503.1.5 DAV:supported-report-set (protected)
1152 This property identifies the reports that are supported by the
1155 <!ELEMENT supported-report-set (supported-report*)>
1156 <!ELEMENT supported-report report>
1157 <!ELEMENT report ANY>
1158 ANY value: a report element type
11603.2 Version-Controlled Resource Properties
1162 The version-control feature introduces the following REQUIRED
1163 properties for a version-controlled resource.
11653.2.1 DAV:checked-in (protected)
1167 This property appears on a checked-in version-controlled resource,
1168 and identifies a version that has the same content and dead
1169 properties as the version-controlled resource. This property is
1170 removed when the resource is checked out, and then added back
1171 (identifying a new version) when the resource is checked back in.
1173 <!ELEMENT checked-in (href)>
1178Clemm, et al. Standards Track [Page 21]
1180RFC 3253 Versioning Extensions to WebDAV March 2002
11833.2.2 DAV:auto-version
1185 If the DAV:auto-version value is DAV:checkout-checkin, when a
1186 modification request (such as PUT/PROPPATCH) is applied to a
1187 checked-in version-controlled resource, the request is automatically
1188 preceded by a checkout and followed by a checkin operation.
1190 If the DAV:auto-version value is DAV:checkout-unlocked-checkin, when
1191 a modification request is applied to a checked-in version-controlled
1192 resource, the request is automatically preceded by a checkout
1193 operation. If the resource is not write-locked, the request is
1194 automatically followed by a checkin operation.
1196 If the DAV:auto-version value is DAV:checkout, when a modification
1197 request is applied to a checked-in version-controlled resource, the
1198 request is automatically preceded by a checkout operation.
1200 If the DAV:auto-version value is DAV:locked-checkout, when a
1201 modification request is applied to a write-locked checked-in
1202 version-controlled resource, the request is automatically preceded by
1203 a checkout operation.
1205 If an update to a write-locked checked-in resource is automatically
1206 preceded by a checkout of that resource, the checkout is associated
1207 with the write lock. When this write lock is removed (e.g. from an
1208 UNLOCK or a lock timeout), if the resource has not yet been checked
1209 in, the removal of the write lock is automatically preceded by a
1212 A server MAY refuse to allow the value of the DAV:auto-version
1213 property to be modified, or MAY only support values from a subset of
1216 <!ELEMENT auto-version (checkout-checkin | checkout-unlocked-checkin
1217 | checkout | locked-checkout)? >
1218 <!ELEMENT checkout-checkin EMPTY>
1219 <!ELEMENT checkout-unlocked-checkin EMPTY>
1220 <!ELEMENT checkout EMPTY>
1221 <!ELEMENT locked-checkout EMPTY>
12233.3 Checked-Out Resource Properties
1225 The version-control feature introduces the following REQUIRED
1226 properties for a checked-out resource.
1234Clemm, et al. Standards Track [Page 22]
1236RFC 3253 Versioning Extensions to WebDAV March 2002
12393.3.1 DAV:checked-out (protected)
1241 This property identifies the version that was identified by the
1242 DAV:checked-in property at the time the resource was checked out.
1243 This property is removed when the resource is checked in.
1245 <!ELEMENT checked-out (href)>
12473.3.2 DAV:predecessor-set
1249 This property determines the DAV:predecessor-set property of the
1250 version that results from checking in this resource.
1252 A server MAY reject attempts to modify the DAV:predecessor-set of a
1253 version-controlled resource.
1255 <!ELEMENT predecessor-set (href+)>
12573.4 Version Properties
1259 The version-control feature introduces the following REQUIRED
1260 properties for a version.
12623.4.1 DAV:predecessor-set (protected)
1264 This property identifies each predecessor of this version. Except
1265 for the root version, which has no predecessors, each version has at
1266 least one predecessor.
1268 <!ELEMENT predecessor-set (href*)>
12703.4.2 DAV:successor-set (computed)
1272 This property identifies each version whose DAV:predecessor-set
1273 identifies this version.
1275 <!ELEMENT successor-set (href*)>
12773.4.3 DAV:checkout-set (computed)
1279 This property identifies each checked-out resource whose
1280 DAV:checked-out property identifies this version.
1282 <!ELEMENT checkout-set (href*)>
1290Clemm, et al. Standards Track [Page 23]
1292RFC 3253 Versioning Extensions to WebDAV March 2002
12953.4.4 DAV:version-name (protected)
1297 This property contains a server-defined string that is different for
1298 each version in a given version history. This string is intended for
1299 display for a user, unlike the URL of a version, which is normally
1300 only used by a client and not displayed for a user.
1302 <!ELEMENT version-name (#PCDATA)>
1303 PCDATA value: string
13053.5 VERSION-CONTROL Method
1307 A VERSION-CONTROL request can be used to create a version-controlled
1308 resource at the request-URL. It can be applied to a versionable
1309 resource or to a version-controlled resource.
1311 If the request-URL identifies a versionable resource, a new version
1312 history resource is created, a new version is created whose content
1313 and dead properties are copied from the versionable resource, and the
1314 resource is given a DAV:checked-in property that is initialized to
1315 identify this new version.
1317 If the request-URL identifies a version-controlled resource, the
1318 resource just remains under version-control. This allows a client to
1319 be unaware of whether or not a server automatically puts a resource
1320 under version control when it is created.
1322 If a VERSION-CONTROL request fails, the server state preceding the
1323 request MUST be restored.
1327 If a request body is included, it MUST be a DAV:version-control
1330 <!ELEMENT version-control ANY>
1332 If a response body for a successful request is included, it MUST
1333 be a DAV:version-control-response XML element. Note that this
1334 document does not define any elements for the VERSION-CONTROL
1335 response body, but the DAV:version-control-response element is
1336 defined to ensure interoperability between future extensions that
1337 do define elements for the VERSION-CONTROL response body.
1339 <!ELEMENT version-control-response ANY>
1346Clemm, et al. Standards Track [Page 24]
1348RFC 3253 Versioning Extensions to WebDAV March 2002
1353 (DAV:put-under-version-control): If the request-URL identified a
1354 versionable resource at the time of the request, the request MUST
1355 have created a new version history and MUST have created a new
1356 version resource in that version history. The resource MUST have
1357 a DAV:checked-in property that identifies the new version. The
1358 content, dead properties, and DAV:resourcetype of the new version
1359 MUST be the same as those of the resource. Note that an
1360 implementation can choose to locate the version history and
1361 version resources anywhere that it wishes. In particular, it
1362 could locate them on the same host and server as the version-
1363 controlled resource, on a different virtual host maintained by the
1364 same server, on the same host maintained by a different server, or
1365 on a different host maintained by a different server.
1367 (DAV:must-not-change-existing-checked-in-out): If the request-URL
1368 identified a resource already under version control at the time of
1369 the request, the request MUST NOT change the DAV:checked-in or
1370 DAV:checked-out property of that version-controlled resource.
13723.5.1 Example - VERSION-CONTROL
1376 VERSION-CONTROL /foo.html HTTP/1.1
1377 Host: www.webdav.org
1384 In this example, /foo.html is put under version control. A new
1385 version history is created for it, and a new version is created that
1386 has a copy of the content and dead properties of /foo.html. The
1387 DAV:checked-in property of /foo.html identifies this new version.
1391 A REPORT request is an extensible mechanism for obtaining information
1392 about a resource. Unlike a resource property, which has a single
1393 value, the value of a report can depend on additional information
1394 specified in the REPORT request body and in the REPORT request
1402Clemm, et al. Standards Track [Page 25]
1404RFC 3253 Versioning Extensions to WebDAV March 2002
1409 The body of a REPORT request specifies which report is being
1410 requested, as well as any additional information that will be used
1411 to customize the report.
1413 The request MAY include a Depth header. If no Depth header is
1414 included, Depth:0 is assumed.
1416 The response body for a successful request MUST contain the
1419 If a Depth request header is included, the response MUST be a 207
1420 Multi-Status. The request MUST be applied separately to the
1421 collection itself and to all members of the collection that
1422 satisfy the Depth value. The DAV:prop element of a DAV:response
1423 for a given resource MUST contain the requested report for that
1428 (DAV:supported-report): The specified report MUST be supported by
1429 the resource identified by the request-URL.
1433 (DAV:no-modification): The REPORT method MUST NOT have changed the
1434 content or dead properties of any resource.
14363.7 DAV:version-tree Report
1438 The DAV:version-tree report describes the requested properties of all
1439 the versions in the version history of a version. If the report is
1440 requested for a version-controlled resource, it is redirected to its
1441 DAV:checked-in or DAV:checked-out version.
1443 The DAV:version-tree report MUST be supported by all version
1444 resources and all version-controlled resources.
1448 The request body MUST be a DAV:version-tree XML element.
1450 <!ELEMENT version-tree ANY>
1451 ANY value: a sequence of zero or more elements, with at most one
1453 prop: see RFC 2518, Section 12.11
1458Clemm, et al. Standards Track [Page 26]
1460RFC 3253 Versioning Extensions to WebDAV March 2002
1463 The response body for a successful request MUST be a
1464 DAV:multistatus XML element.
1466 multistatus: see RFC 2518, Section 12.9
1468 The response body for a successful DAV:version-tree REPORT request
1469 MUST contain a DAV:response element for each version in the
1470 version history of the version identified by the request-URL.
14723.7.1 Example - DAV:version-tree Report
1474 The version history drawn below would produce the following version
1490 REPORT /foo.html HTTP/1.1
1491 Host: www.webdav.org
1492 Content-Type: text/xml; charset="utf-8"
1493 Content-Length: xxxx
1495 <?xml version="1.0" encoding="utf-8" ?>
1496 <D:version-tree xmlns:D="DAV:">
1499 <D:creator-displayname/>
1514Clemm, et al. Standards Track [Page 27]
1516RFC 3253 Versioning Extensions to WebDAV March 2002
1521 HTTP/1.1 207 Multi-Status
1522 Content-Type: text/xml; charset="utf-8"
1523 Content-Length: xxxx
1525 <?xml version="1.0" encoding="utf-8" ?>
1526 <D:multistatus xmlns:D="DAV:">
1528 <D:href>http://repo.webdav.org/his/23/ver/V1</D:href>
1531 <D:version-name>V1</D:version-name>
1532 <D:creator-displayname>Fred</D:creator-displayname>
1534 <D:href>http://repo.webdav.org/his/23/ver/V2</D:href>
1535 <D:href>http://repo.webdav.org/his/23/ver/V2.1.1</D:href>
1538 <D:status>HTTP/1.1 200 OK</D:status>
1542 <D:href>http://repo.webdav.org/his/23/ver/V2</D:href>
1545 <D:version-name>V2</D:version-name>
1546 <D:creator-displayname>Fred</D:creator-displayname>
1549 <D:status>HTTP/1.1 200 OK</D:status>
1553 <D:href>http://repo.webdav.org/his/23/ver/V2.1.1</D:href>
1556 <D:version-name>V2.1.1</D:version-name>
1557 <D:creator-displayname>Sally</D:creator-displayname>
1560 <D:status>HTTP/1.1 200 OK</D:status>
1570Clemm, et al. Standards Track [Page 28]
1572RFC 3253 Versioning Extensions to WebDAV March 2002
15753.8 DAV:expand-property Report
1577 Many property values are defined as a DAV:href, or a set of DAV:href
1578 elements. The DAV:expand-property report provides a mechanism for
1579 retrieving in one request the properties from the resources
1580 identified by those DAV:href elements. This report not only
1581 decreases the number of requests required, but also allows the server
1582 to minimize the number of separate read transactions required on the
1583 underlying versioning store.
1585 The DAV:expand-property report SHOULD be supported by all resources
1586 that support the REPORT method.
1590 The request body MUST be a DAV:expand-property XML element.
1592 <!ELEMENT expand-property (property*)>
1593 <!ELEMENT property (property*)>
1594 <!ATTLIST property name NMTOKEN #REQUIRED>
1595 name value: a property element type
1596 <!ATTLIST property namespace NMTOKEN "DAV:">
1597 namespace value: an XML namespace
1599 The response body for a successful request MUST be a
1600 DAV:multistatus XML element.
1602 multistatus: see RFC 2518, Section 12.9
1604 The properties reported in the DAV:prop elements of the
1605 DAV:multistatus element MUST be those identified by the
1606 DAV:property elements in the DAV:expand-property element. If
1607 there are DAV:property elements nested within a DAV:property
1608 element, then every DAV:href in the value of the corresponding
1609 property is replaced by a DAV:response element whose DAV:prop
1610 elements report the values of the properties identified by the
1611 nested DAV:property elements. The nested DAV:property elements
1612 can in turn contain DAV:property elements, so that multiple levels
1613 of DAV:href expansion can be requested.
1615 Note that a validating parser MUST be aware that the DAV:expand-
1616 property report effectively modifies the DTD of every property by
1617 replacing every occurrence of "href" in the DTD with "href |
1626Clemm, et al. Standards Track [Page 29]
1628RFC 3253 Versioning Extensions to WebDAV March 2002
16313.8.1 Example - DAV:expand-property
1633 This example describes how to query a version-controlled resource to
1634 determine the DAV:creator-display-name and DAV:activity-set of every
1635 version in the version history of that version-controlled resource.
1636 This example assumes that the server supports the version-history
1637 feature (see Section 5).
1641 REPORT /foo.html HTTP/1.1
1642 Host: www.webdav.org
1643 Content-Type: text/xml; charset="utf-8"
1644 Content-Length: xxxx
1646 <?xml version="1.0" encoding="utf-8" ?>
1647 <D:expand-property xmlns:D="DAV:">
1648 <D:property name="version-history">
1649 <D:property name="version-set">
1650 <D:property name="creator-displayname"/>
1651 <D:property name="activity-set"/>
1654 </D:expand-property>
1658 HTTP/1.1 207 Multi-Status
1659 Content-Type: text/xml; charset="utf-8"
1660 Content-Length: xxxx
1662 <?xml version="1.0" encoding="utf-8" ?>
1663 <D:multistatus xmlns:D="DAV:">
1665 <D:href>http://www.webdav.org/foo.html</D:href>
1670 <D:href>http://repo.webdav.org/his/23</D:href>
1675 <D:href>http://repo.webdav.org/his/23/ver/1</D:href>
1678 <D:creator-displayname>Fred</D:creator-displayname>
1682Clemm, et al. Standards Track [Page 30]
1684RFC 3253 Versioning Extensions to WebDAV March 2002
1687 <D:activity-set> <D:href>
1688 http://www.webdav.org/ws/dev/sally
1689 </D:href> </D:activity-set> </D:prop>
1690 <D:status>HTTP/1.1 200 OK</D:status>
1691 </D:propstat> </D:response>
1693 <D:href>http://repo.webdav.org/his/23/ver/2</D:href>
1696 <D:creator-displayname>Sally</D:creator-displayname>
1698 <D:href>http://repo.webdav.org/act/add-refresh-cmd</D:href>
1699 </D:activity-set> </D:prop>
1700 <D:status>HTTP/1.1 200 OK</D:status>
1701 </D:propstat> </D:response>
1702 </D:version-set> </D:prop>
1703 <D:status>HTTP/1.1 200 OK</D:status>
1704 </D:propstat> </D:response>
1705 </D:version-history> </D:prop>
1706 <D:status>HTTP/1.1 200 OK</D:status>
1707 </D:propstat> </D:response>
1710 In this example, the DAV:creator-displayname and DAV:activity-set
1711 properties of the versions in the DAV:version-set of the
1712 DAV:version-history of http://www.webdav.org/foo.html are reported.
17143.9 Additional OPTIONS Semantics
1716 If the server supports the version-control feature, it MUST include
1717 "version-control" as a field in the DAV response header from an
1718 OPTIONS request on any resource that supports any versioning
1719 properties, reports, or methods.
17213.10 Additional PUT Semantics
1723 Additional Preconditions:
1725 (DAV:cannot-modify-version-controlled-content): If the request-URL
1726 identifies a resource with a DAV:checked-in property, the request
1727 MUST fail unless DAV:auto-version semantics will automatically
1728 check out the resource.
1730 (DAV:cannot-modify-version): If the request-URL identifies a
1731 version, the request MUST fail.
1738Clemm, et al. Standards Track [Page 31]
1740RFC 3253 Versioning Extensions to WebDAV March 2002
1743 If the request creates a new resource that is automatically placed
1744 under version control, all preconditions for VERSION-CONTROL apply
1747 Additional Postconditions:
1749 (DAV:auto-checkout): If the resource was a checked-in version-
1750 controlled resource whose DAV:auto-version property indicates it
1751 should be automatically checked out but not automatically checked
1752 in for a modification request, then the server MUST have
1753 automatically checked out the resource prior to executing the
1754 request. In particular, the value of the DAV:checked-out property
1755 of the resource MUST be that of the DAV:checked-in property prior
1756 to the request, the DAV:checked-in property MUST have been
1757 removed, and the DAV:predecessor-set property MUST be initialized
1758 to be the same as the DAV:checked-out property. If any part of
1759 the checkout/update sequence failed, the status from the failed
1760 part of the request MUST be returned, and the server state
1761 preceding the request sequence MUST be restored.
1763 (DAV:auto-checkout-checkin): If the resource was a checked-in
1764 version-controlled resource whose DAV:auto-version property
1765 indicates it should be automatically checked out and automatically
1766 checked in for a modification request, then the server MUST have
1767 automatically checked out the resource prior to executing the
1768 request and automatically checked it in after the request. In
1769 particular, the DAV:checked-in property of the resource MUST
1770 identify a new version whose content and dead properties are the
1771 same as those of the resource. The DAV:predecessor-set of the new
1772 version MUST identify the version identified by the DAV:checked-in
1773 property prior to the request. If any part of the
1774 checkout/update/checkin sequence failed, the status from the
1775 failed part of the request MUST be returned, and the server state
1776 preceding the request sequence MUST be restored.
1778 If the request creates a new resource, the new resource MAY have
1779 automatically been placed under version control, and all
1780 postconditions for VERSION-CONTROL apply to the request.
17823.11 Additional PROPFIND Semantics
1784 A DAV:allprop PROPFIND request SHOULD NOT return any of the
1785 properties defined by this document. This allows a versioning server
1786 to perform efficiently when a naive client, which does not understand
1787 the cost of asking a server to compute all possible live properties,
1788 issues a DAV:allprop PROPFIND request.
1794Clemm, et al. Standards Track [Page 32]
1796RFC 3253 Versioning Extensions to WebDAV March 2002
1799 Additional Preconditions:
1801 (DAV:supported-live-property): If the request attempts to access a
1802 property defined by this document, the semantics of that property
1803 MUST be supported by the server.
18053.12 Additional PROPPATCH Semantics
1807 Additional Preconditions:
1809 (DAV:cannot-modify-version-controlled-property): If the request
1810 attempts to modify a dead property, same semantics as PUT (see
1813 (DAV:cannot-modify-version): If the request attempts to modify a
1814 dead property, same semantics as PUT (see Section 3.10).
1816 (DAV:cannot-modify-protected-property): An attempt to modify a
1817 property that is defined by this document, as being protected for
1818 that kind of resource, MUST fail.
1820 (DAV:supported-live-property): An attempt to modify a property
1821 defined by this document, but whose semantics are not enforced by
1822 the server, MUST fail. This helps ensure that a client will be
1823 notified when it is trying to use a property whose semantics are
1824 not supported by the server.
1826 Additional Postconditions:
1828 (DAV:auto-checkout): If the request modified a dead property, same
1829 semantics as PUT (see Section 3.10).
1831 (DAV:auto-checkout-checkin): If the request modified a dead
1832 property, same semantics as PUT (see Section 3.10).
18343.13 Additional DELETE Semantics
1836 Additional Preconditions:
1838 (DAV:no-version-delete): A server MAY fail an attempt to DELETE a
1841 Additional Postconditions:
1843 (DAV:update-predecessor-set): If a version was deleted, the server
1844 MUST have replaced any reference to that version in a
1845 DAV:predecessor-set by a copy of the DAV:predecessor-set of the
1850Clemm, et al. Standards Track [Page 33]
1852RFC 3253 Versioning Extensions to WebDAV March 2002
18553.14 Additional COPY Semantics
1857 Additional Preconditions:
1859 If the request creates a new resource that is automatically placed
1860 under version control, all preconditions for VERSION-CONTROL apply
1863 Additional Postconditions:
1865 (DAV:must-not-copy-versioning-property): A property defined by
1866 this document MUST NOT have been copied to the new resource
1867 created by this request, but instead that property of the new
1868 resource MUST have the default initial value it would have had if
1869 the new resource had been created by a non-versioning method such
1872 (DAV:auto-checkout): If the destination is a version-controlled
1873 resource, same semantics as PUT (see Section 3.10).
1875 (DAV:auto-checkout-checkin): If the destination is a version-
1876 controlled resource, same semantics as PUT (see Section 3.10).
1878 (DAV:copy-creates-new-resource): If the source of a COPY is a
1879 version-controlled resource or version, and if there is no
1880 resource at the destination of the COPY, then the COPY creates a
1881 new non-version-controlled resource at the destination of the
1882 COPY. The new resource MAY automatically be put under version
1883 control, but the resulting version-controlled resource MUST be
1884 associated with a new version history created for that new
1885 version-controlled resource, and all postconditions for
1886 VERSION-CONTROL apply to the request.
18883.15 Additional MOVE Semantics
1890 Additional Preconditions:
1892 (DAV:cannot-rename-version): If the request-URL identifies a
1893 version, the request MUST fail.
1895 Additional Postconditions:
1897 (DAV:preserve-versioning-properties): When a resource is moved
1898 from a source URL to a destination URL, a property defined by this
1899 document MUST have the same value at the destination URL as it had
1906Clemm, et al. Standards Track [Page 34]
1908RFC 3253 Versioning Extensions to WebDAV March 2002
19113.16 Additional UNLOCK Semantics
1913 Note that these semantics apply both to an explicit UNLOCK request,
1914 as well as to the removal of a lock because of a lock timeout. If a
1915 precondition or postcondition cannot be satisfied, the lock timeout
1918 Additional Preconditions:
1920 (DAV:version-history-is-tree): If the request-URL identifies a
1921 checked-out version-controlled resource that will be automatically
1922 checked in when the lock is removed, then the versions identified
1923 by the DAV:predecessor-set of the checked-out resource MUST be
1924 descendants of the root version of the version history for the
1925 DAV:checked-out version.
1927 Additional Postconditions:
1929 (DAV:auto-checkin): If the request-URL identified a checked-out
1930 version-controlled resource that had been automatically checked
1931 out because of its DAV:auto-version property, the request MUST
1932 have created a new version in the version history of the
1933 DAV:checked-out version. The request MUST have allocated a URL
1934 for the version that MUST NOT have previously identified any other
1935 resource, and MUST NOT ever identify a resource other than this
1936 version. The content, dead properties, DAV:resourcetype, and
1937 DAV:predecessor-set of the new version MUST be copied from the
1938 checked-out resource. The DAV:version-name of the new version
1939 MUST be set to a server-defined value distinct from all other
1940 DAV:version-name values of other versions in the same version
1941 history. The request MUST have removed the DAV:checked-out
1942 property of the version-controlled resource, and MUST have added a
1943 DAV:checked-in property that identifies the new version.
19454 CHECKOUT-IN-PLACE FEATURE
1947 With the version-control feature, WebDAV locking can be used to avoid
1948 the proliferation of versions that would result if every modification
1949 to a version-controlled resource produced a new version. The
1950 checkout-in-place feature provides an alternative mechanism that
1951 allows a client to explicitly check out and check in a resource to
1952 create a new version.
19544.1 Additional Version Properties
1956 The checkout-in-place feature introduces the following REQUIRED
1957 properties for a version.
1962Clemm, et al. Standards Track [Page 35]
1964RFC 3253 Versioning Extensions to WebDAV March 2002
19674.1.1 DAV:checkout-fork
1969 This property controls the behavior of CHECKOUT when a version
1970 already is checked out or has a successor. If the DAV:checkout-fork
1971 of a version is DAV:forbidden, a CHECKOUT request MUST fail if it
1972 would result in that version appearing in the DAV:predecessor-set or
1973 DAV:checked-out property of more than one version or checked-out
1974 resource. If DAV:checkout-fork is DAV:discouraged, such a CHECKOUT
1975 request MUST fail unless DAV:fork-ok is specified in the CHECKOUT
1978 A server MAY reject attempts to modify the DAV:checkout-fork of a
1981 <!ELEMENT checkout-fork ANY>
1982 ANY value: A sequence of elements with at most one DAV:discouraged
1983 or DAV:forbidden element.
1984 <!ELEMENT discouraged EMPTY>
1985 <!ELEMENT forbidden EMPTY>
19874.1.2 DAV:checkin-fork
1989 This property controls the behavior of CHECKIN when a version already
1990 has a successor. If the DAV:checkin-fork of a version is
1991 DAV:forbidden, a CHECKIN request MUST fail if it would result in that
1992 version appearing in the DAV:predecessor-set of more than one
1993 version. If DAV:checkin-fork is DAV:discouraged, such a CHECKIN
1994 request MUST fail unless DAV:fork-ok is specified in the CHECKIN
1997 A server MAY reject attempts to modify the DAV:checkout-fork of a
2000 <!ELEMENT checkin-fork ANY>
2001 ANY value: A sequence of elements with at most one DAV:discouraged
2002 or DAV:forbidden element.
2003 <!ELEMENT discouraged EMPTY>
2004 <!ELEMENT forbidden EMPTY>
20064.2 Checked-Out Resource Properties
2008 The checkout-in-place feature introduces the following REQUIRED
2009 properties for a checked-out resource.
20114.2.1 DAV:checkout-fork
2013 This property determines the DAV:checkout-fork property of the
2014 version that results from checking in this resource.
2018Clemm, et al. Standards Track [Page 36]
2020RFC 3253 Versioning Extensions to WebDAV March 2002
20234.2.2 DAV:checkin-fork
2025 This property determines the DAV:checkin-fork property of the version
2026 that results from checking in this resource.
20284.3 CHECKOUT Method (applied to a version-controlled resource)
2030 A CHECKOUT request can be applied to a checked-in version-controlled
2031 resource to allow modifications to the content and dead properties of
2032 that version-controlled resource.
2034 If a CHECKOUT request fails, the server state preceding the request
2039 If a request body is included, it MUST be a DAV:checkout XML
2042 <!ELEMENT checkout ANY>
2044 ANY value: A sequence of elements with at most one DAV:fork-ok
2047 <!ELEMENT fork-ok EMPTY>
2049 If a response body for a successful request is included, it MUST
2050 be a DAV:checkout-response XML element.
2052 <!ELEMENT checkout-response ANY>
2054 The response MUST include a Cache-Control:no-cache header.
2058 (DAV:must-be-checked-in): If a version-controlled resource is
2059 being checked out, it MUST have a DAV:checked-in property.
2061 (DAV:checkout-of-version-with-descendant-is-forbidden): If the
2062 DAV:checkout-fork property of the version being checked out is
2063 DAV:forbidden, the request MUST fail if a version identifies that
2064 version in its DAV:predecessor-set.
2066 (DAV:checkout-of-version-with-descendant-is-discouraged): If the
2067 DAV:checkout-fork property of the version being checked out is
2068 DAV:discouraged, the request MUST fail if a version identifies
2069 that version in its DAV:predecessor-set unless DAV:fork-ok is
2070 specified in the request body.
2074Clemm, et al. Standards Track [Page 37]
2076RFC 3253 Versioning Extensions to WebDAV March 2002
2079 (DAV:checkout-of-checked-out-version-is-forbidden): If the
2080 DAV:checkout-fork property of the version being checked out is
2081 DAV:forbidden, the request MUST fail if a checked-out resource
2082 identifies that version in its DAV:checked-out property.
2084 (DAV:checkout-of-checked-out-version-is-discouraged): If the
2085 DAV:checkout-fork property of the version being checked out is
2086 DAV:discouraged, the request MUST fail if a checked-out resource
2087 identifies that version in its DAV:checked-out property unless
2088 DAV:fork-ok is specified in the request body.
2092 (DAV:is-checked-out): The checked-out resource MUST have a
2093 DAV:checked-out property that identifies the DAV:checked-in
2094 version preceding the checkout. The version-controlled resource
2095 MUST NOT have a DAV:checked-in property.
2097 (DAV:initialize-predecessor-set): The DAV:predecessor-set property
2098 of the checked-out resource MUST be initialized to be the
2099 DAV:checked-out version.
21014.3.1 Example - CHECKOUT of a version-controlled resource
2105 CHECKOUT /foo.html HTTP/1.1
2106 Host: www.webdav.org
2112 Cache-Control: no-cache
2114 In this example, the version-controlled resource /foo.html is checked
21174.4 CHECKIN Method (applied to a version-controlled resource)
2119 A CHECKIN request can be applied to a checked-out version-controlled
2120 resource to produce a new version whose content and dead properties
2121 are copied from the checked-out resource.
2123 If a CHECKIN request fails, the server state preceding the request
2130Clemm, et al. Standards Track [Page 38]
2132RFC 3253 Versioning Extensions to WebDAV March 2002
2137 If a request body is included, it MUST be a DAV:checkin XML
2140 <!ELEMENT checkin ANY>
2141 ANY value: A sequence of elements with at most one
2142 DAV:keep-checked-out element and at most one DAV:fork-ok element.
2144 <!ELEMENT keep-checked-out EMPTY>
2145 <!ELEMENT fork-ok EMPTY>
2147 If a response body for a successful request is included, it MUST
2148 be a DAV:checkin-response XML element.
2150 <!ELEMENT checkin-response ANY>
2152 The response MUST include a Cache-Control:no-cache header.
2156 (DAV:must-be-checked-out): The request-URL MUST identify a
2157 resource with a DAV:checked-out property.
2159 (DAV:version-history-is-tree) The versions identified by the
2160 DAV:predecessor-set of the checked-out resource MUST be
2161 descendants of the root version of the version history for the
2162 DAV:checked-out version.
2164 (DAV:checkin-fork-forbidden): A CHECKIN request MUST fail if it
2165 would cause a version whose DAV:checkin-fork is DAV:forbidden to
2166 appear in the DAV:predecessor-set of more than one version.
2168 (DAV:checkin-fork-discouraged): A CHECKIN request MUST fail if it
2169 would cause a version whose DAV:checkin-fork is DAV:discouraged to
2170 appear in the DAV:predecessor-set of more than one version, unless
2171 DAV:fork-ok is specified in the request body.
2175 (DAV:create-version): The request MUST have created a new version
2176 in the version history of the DAV:checked-out version. The
2177 request MUST have allocated a distinct new URL for the new
2186Clemm, et al. Standards Track [Page 39]
2188RFC 3253 Versioning Extensions to WebDAV March 2002
2191 version, and that URL MUST NOT ever identify any resource other
2192 than that version. The URL for the new version MUST be returned in
2193 a Location response header.
2195 (DAV:initialize-version-content-and-properties): The content, dead
2196 properties, DAV:resourcetype, and DAV:predecessor-set of the new
2197 version MUST be copied from the checked-out resource. The
2198 DAV:version-name of the new version MUST be set to a server-
2199 defined value distinct from all other DAV:version-name values of
2200 other versions in the same version history.
2202 (DAV:checked-in): If the request-URL identifies a version-
2203 controlled resource and DAV:keep-checked-out is not specified in
2204 the request body, the DAV:checked-out property of the version-
2205 controlled resource MUST have been removed and a DAV:checked-in
2206 property that identifies the new version MUST have been added.
2208 (DAV:keep-checked-out): If DAV:keep-checked-out is specified in
2209 the request body, the DAV:checked-out property of the checked-out
2210 resource MUST have been updated to identify the new version.
22124.4.1 Example - CHECKIN
2216 CHECKIN /foo.html HTTP/1.1
2217 Host: www.webdav.org
2222 HTTP/1.1 201 Created
2223 Location: http://repo.webdav.org/his/23/ver/32
2224 Cache-Control: no-cache
2226 In this example, version-controlled resource /foo.html is checked in,
2227 and a new version is created at http://repo.webdav.org/his/23/ver/32.
22294.5 UNCHECKOUT Method
2231 An UNCHECKOUT request can be applied to a checked-out version-
2232 controlled resource to cancel the CHECKOUT and restore the pre-
2233 CHECKOUT state of the version-controlled resource.
2235 If an UNCHECKOUT request fails, the server MUST undo any partial
2236 effects of the UNCHECKOUT request.
2242Clemm, et al. Standards Track [Page 40]
2244RFC 3253 Versioning Extensions to WebDAV March 2002
2249 If a request body is included, it MUST be a DAV:uncheckout XML
2252 <!ELEMENT uncheckout ANY>
2254 If a response body for a successful request is included, it MUST
2255 be a DAV:uncheckout-response XML element.
2257 <!ELEMENT uncheckout-response ANY>
2259 The response MUST include a Cache-Control:no-cache header.
2263 (DAV:must-be-checked-out-version-controlled-resource): The
2264 request-URL MUST identify a version-controlled resource with a
2265 DAV:checked-out property.
2269 (DAV:cancel-checked-out): The value of the DAV:checked-in property
2270 is that of the DAV:checked-out property prior to the request, and
2271 the DAV:checked-out property has been removed.
2273 (DAV:restore-content-and-dead-properties): The content and dead
2274 properties of the version-controlled resource are copies of its
2275 DAV:checked-in version.
22774.5.1 Example - UNCHECKOUT
2281 UNCHECKOUT /foo.html HTTP/1.1
2282 Host: www.webdav.org
2288 Cache-Control: no-cache
2290 In this example, the content and dead properties of the version-
2291 controlled resource identified by http://www.webdav.org/foo.html are
2292 restored to their values preceding the most recent CHECKOUT of that
2293 version-controlled resource.
2298Clemm, et al. Standards Track [Page 41]
2300RFC 3253 Versioning Extensions to WebDAV March 2002
23034.6 Additional OPTIONS Semantics
2305 If a server supports the checkout-in-place feature, it MUST include
2306 "checkout-in-place" as a field in the DAV response header from an
2307 OPTIONS request on any resource that supports any versioning
2308 properties, reports, or methods.
23105 Version-History Feature
2312 It is often useful to have access to a version history even after all
2313 version-controlled resources for that version history have been
2314 deleted. A server can provide this functionality by supporting
2315 version history resources. A version history resource is a resource
2316 that exists in a server defined namespace and therefore is unaffected
2317 by any deletion or movement of version-controlled resources. A
2318 version history resource is an appropriate place to add a property
2319 that logically applies to all states of a resource. The DAV:expand-
2320 property report (see Section 3.8) can be applied to the DAV:version-
2321 set of a version history resource to provide a variety of useful
2322 reports on all versions in that version history.
23245.1 Version History Properties
2326 The DAV:resourcetype of a version history MUST be DAV:version-
2329 The version-history feature introduces the following REQUIRED
2330 properties for a version history.
23325.1.1 DAV:version-set (protected)
2334 This property identifies each version of this version history.
2336 <!ELEMENT version-set (href+)>
23385.1.2 DAV:root-version (computed)
2340 This property identifies the root version of this version history.
2342 <!ELEMENT root-version (href)>
23445.2 Additional Version-Controlled Resource Properties
2346 The version-history feature introduces the following REQUIRED
2347 property for a version-controlled resource.
2354Clemm, et al. Standards Track [Page 42]
2356RFC 3253 Versioning Extensions to WebDAV March 2002
23595.2.1 DAV:version-history (computed)
2361 This property identifies the version history resource for the
2362 DAV:checked-in or DAV:checked-out version of this version-controlled
2365 <!ELEMENT version-history (href)>
23675.3 Additional Version Properties
2369 The version-history feature introduces the following REQUIRED
2370 property for a version.
23725.3.1 DAV:version-history (computed)
2374 This property identifies the version history that contains this
2377 <!ELEMENT version-history (href)>
23795.4 DAV:locate-by-history Report
2381 Many properties identify a version from some version history. It is
2382 often useful to be able to efficiently locate a version-controlled
2383 resource for that version history. The DAV:locate-by-history report
2384 can be applied to a collection to locate the collection member that
2385 is a version-controlled resource for a specified version history
2390 The request body MUST be a DAV:locate-by-history XML element.
2392 <!ELEMENT locate-by-history (version-history-set, prop)>
2393 <!ELEMENT version-history-set (href+)>
2394 prop: see RFC 2518, Section 12.11
2396 The response body for a successful request MUST be a
2397 DAV:multistatus XML element containing every version-controlled
2398 resource that is a member of the collection identified by the
2399 request-URL, and whose DAV:version-history property identifies one
2400 of the version history resources identified by the request body.
2401 The DAV:prop element in the request body identifies which
2402 properties should be reported in the DAV:prop elements in the
2410Clemm, et al. Standards Track [Page 43]
2412RFC 3253 Versioning Extensions to WebDAV March 2002
2417 (DAV:must-be-version-history): Each member of the DAV:version-
2418 history-set element in the request body MUST identify a version
24215.4.1 Example - DAV:locate-by-history Report
2425 REPORT /ws/public HTTP/1.1
2426 Host: www.webdav.org
2427 Content-Type: text/xml; charset="utf-8"
2428 Content-Length: xxxx
2430 <?xml version="1.0" encoding="utf-8" ?>
2431 <D:locate-by-history xmlns:D="DAV:">
2432 <D:version-history-set>
2433 <D:href>http://repo.webdav.org/his/23</D:href>
2434 <D:href>http://repo.webdav.org/his/84</D:href>
2435 <D:href>http://repo.webdav.org/his/129</D:href>
2436 <D:version-history-set/>
2438 </D:version-history>
2440 </D:locate-by-history>
2444 HTTP/1.1 207 Multi-Status
2445 Content-Type: text/xml; charset="utf-8"
2446 Content-Length: xxxx
2448 <?xml version="1.0" encoding="utf-8" ?>
2449 <D:multistatus xmlns:D="DAV:">
2451 <D:href>http://www.webdav.org/ws/public/x/test.html</D:href>
2455 <D:href>http://repo.webdav.org/his/23</D:href>
2456 </D:version-history>
2458 <D:status>HTTP/1.1 200 OK</D:status>
2466Clemm, et al. Standards Track [Page 44]
2468RFC 3253 Versioning Extensions to WebDAV March 2002
2471 In this example, there is only one version-controlled member of
2472 /ws/public that is a version-controlled resource for one of the three
2473 specified version history resources. In particular,
2474 /ws/public/x/test.html is the version-controlled resource for
2475 http://repo.webdav.org/his/23.
24775.5 Additional OPTIONS Semantics
2479 If the server supports the version-history feature, it MUST include
2480 "version-history" as a field in the DAV response header from an
2481 OPTIONS request on any resource that supports any versioning
2482 properties, reports, or methods.
2484 A DAV:version-history-collection-set element MAY be included in the
2485 request body to identify collections that may contain version history
2488 Additional Marshalling:
2490 If an XML request body is included, it MUST be a DAV:options XML
2493 <!ELEMENT options ANY>
2494 ANY value: A sequence of elements with at most one
2495 DAV:version-history-collection-set element.
2497 If an XML response body for a successful request is included, it
2498 MUST be a DAV:options-response XML element.
2500 <!ELEMENT options-response ANY>
2501 ANY value: A sequence of elements with at most one
2502 DAV:version-history-collection-set element.
2504 <!ELEMENT version-history-collection-set (href*)>
2506 If DAV:version-history-collection-set is included in the request
2507 body, the response body for a successful request MUST contain a
2508 DAV:version-history-collection-set element identifying collections
2509 that may contain version histories. An identified collection MAY
2510 be the root collection of a tree of collections, all of which may
2511 contain version histories. Since different servers can control
2512 different parts of the URL namespace, different resources on the
2513 same host MAY have different DAV:version-history-collection-set
2514 values. The identified collections MAY be located on different
2515 hosts from the resource.
2522Clemm, et al. Standards Track [Page 45]
2524RFC 3253 Versioning Extensions to WebDAV March 2002
25275.6 Additional DELETE Semantics
2529 Additional Postconditions:
2531 (DAV:delete-version-set): If the request deleted a version
2532 history, the request MUST have deleted all versions in the
2533 DAV:version-set of that version history, and MUST have satisfied
2534 the postconditions for version deletion (see Section 3.13).
2536 (DAV:version-history-has-root): If the request deleted the root
2537 version of a version history, the request MUST have updated the
2538 DAV:root-version of the version history to refer to another
2539 version that is an ancestor of all other remaining versions in
2540 that version history. A result of this postcondition is that
2541 every version history will have at least one version, and the only
2542 way to delete all versions is to delete the version history
25455.7 Additional COPY Semantics
2547 Additional Preconditions:
2549 (DAV:cannot-copy-history): If the request-URL identifies a version
2550 history, the request MUST fail. In order to create another
2551 version history whose versions have the same content and dead
2552 properties, the appropriate sequence of VERSION-CONTROL, CHECKOUT,
2553 PUT, PROPPATCH, and CHECKIN requests must be made.
25555.8 Additional MOVE Semantics
2557 Additional Preconditions:
2559 (DAV:cannot-rename-history): If the request-URL identifies a
2560 version history, the request MUST fail.
25625.9 Additional VERSION-CONTROL Semantics
2564 Additional Postconditions:
2566 (DAV:new-version-history): If the request created a new version
2567 history, the request MUST have allocated a new server-defined URL
2568 for that version history that MUST NOT have previously identified
2569 any other resource, and MUST NOT ever identify a resource other
2570 than this version history.
2578Clemm, et al. Standards Track [Page 46]
2580RFC 3253 Versioning Extensions to WebDAV March 2002
25835.10 Additional CHECKIN Semantics
2585 Additional Postconditions:
2587 (DAV:add-to-history): A URL for the new version resource MUST have
2588 been added to the DAV:version-set of the version history of the
2589 DAV:checked-out version.
2593 In order to allow multiple users to work concurrently on adding
2594 versions to the same version history, it is necessary to allocate on
2595 the server multiple checked-out resources for the same version
2596 history. Even if only one user is making changes to a resource, that
2597 user will sometimes wish to create a "private" version, and then to
2598 expose that version at a later time. One way to provide this
2599 functionality depends on the client keeping track of its current set
2600 of checked-out resources. This is the working-resource feature
2601 defined in Section 8. The other way to provide this functionality
2602 avoids the need for persistent state on the client, and instead has
2603 the server maintain a human meaningful namespace for related sets of
2604 checked-out resources. This is the workspace feature defined in this
2607 The workspace feature introduces a "workspace resource". A workspace
2608 resource is a collection whose members are related version-controlled
2609 and non-version-controlled resources. Multiple workspaces may be
2610 used to expose different versions and configurations of a set of
2611 version-controlled resources concurrently. In order to make changes
2612 to a version-controlled resource in one workspace visible in another
2613 workspace, that version-controlled resource must be checked in, and
2614 then the corresponding version-controlled resource in the other
2615 workspace can be updated to display the content and dead properties
2618 In order to ensure unambiguous merging (see Section 11) and
2619 baselining (see Section 12) semantics, a workspace may contain at
2620 most one version-controlled resource for a given version history.
2621 This is required for unambiguous merging because the MERGE method
2622 must identify which version-controlled resource is to be the merge
2623 target of a given version. This is required for unambiguous
2624 baselining because a baseline can only select one version for a given
2625 version-controlled resource.
2627 Initially, an empty workspace can be created. Non-version-controlled
2628 resources can then be added to the workspace with standard WebDAV
2629 requests such as PUT and MKCOL. Version-controlled resources can be
2630 added to the workspace with VERSION-CONTROL requests. If the
2634Clemm, et al. Standards Track [Page 47]
2636RFC 3253 Versioning Extensions to WebDAV March 2002
2639 baseline feature is supported, collections in the workspace can be
2640 placed under baseline control, and then initialized by existing
26436.1 Workspace Properties
2645 The workspace feature introduces the following REQUIRED property for
26486.1.1 DAV:workspace-checkout-set (computed)
2650 This property identifies each checked-out resource whose
2651 DAV:workspace property identifies this workspace.
2653 <!ELEMENT workspace-checkout-set (href*)>
26556.2 Additional Resource Properties
2657 The workspace feature introduces the following REQUIRED property for
26606.2.1 DAV:workspace (protected)
2662 The DAV:workspace property of a workspace resource MUST identify
2663 itself. The DAV:workspace property of any other type of resource
2664 MUST be the same as the DAV:workspace of its parent collection.
2666 <!ELEMENT workspace (href)>
26686.3 MKWORKSPACE Method
2670 A MKWORKSPACE request creates a new workspace resource. A server MAY
2671 restrict workspace creation to particular collections, but a client
2672 can determine the location of these collections from a
2673 DAV:workspace-collection-set OPTIONS request (see Section 6.4).
2675 If a MKWORKSPACE request fails, the server state preceding the
2676 request MUST be restored.
2680 If a request body is included, it MUST be a DAV:mkworkspace XML
2683 <!ELEMENT mkworkspace ANY>
2685 If a response body for a successful request is included, it MUST
2686 be a DAV:mkworkspace-response XML element.
2690Clemm, et al. Standards Track [Page 48]
2692RFC 3253 Versioning Extensions to WebDAV March 2002
2695 <!ELEMENT mkworkspace-response ANY>
2697 The response MUST include a Cache-Control:no-cache header.
2701 (DAV:resource-must-be-null): A resource MUST NOT exist at the
2704 (DAV:workspace-location-ok): The request-URL MUST identify a
2705 location where a workspace can be created.
2709 (DAV:initialize-workspace): A new workspace exists at the
2710 request-URL. The DAV:resourcetype of the workspace MUST be
2711 DAV:collection. The DAV:workspace of the workspace MUST identify
27146.3.1 Example - MKWORKSPACE
2718 MKWORKSPACE /ws/public HTTP/1.1
2719 Host: www.webdav.org
2724 HTTP/1.1 201 Created
2725 Cache-Control: no-cache
2727 In this example, a new workspace is created at
2728 http://www.webdav.org/ws/public.
27306.4 Additional OPTIONS Semantics
2732 If a server supports the workspace feature, it MUST include
2733 "workspace" as a field in the DAV response header from an OPTIONS
2734 request on any resource that supports any versioning properties,
2735 reports, or methods.
2737 If a server supports the workspace feature, it MUST also support the
2738 checkout-in-place feature and the version-history feature.
2740 A DAV:workspace-collection-set element MAY be included in the request
2741 body to identify collections that may contain workspace resources.
2746Clemm, et al. Standards Track [Page 49]
2748RFC 3253 Versioning Extensions to WebDAV March 2002
2751 Additional Marshalling:
2753 If an XML request body is included, it MUST be a DAV:options XML
2756 <!ELEMENT options ANY>
2757 ANY value: A sequence of elements with at most one
2758 DAV:workspace-collection-set element.
2760 If an XML response body for a successful request is included, it
2761 MUST be a DAV:options-response XML element.
2763 <!ELEMENT options-response ANY>
2764 ANY value: A sequence of elements with at most one
2765 DAV:workspace-collection-set element.
2767 <!ELEMENT workspace-collection-set (href*)>
2769 If DAV:workspace-collection-set is included in the request body,
2770 the response body for a successful request MUST contain a
2771 DAV:workspace-collection-set element identifying collections that
2772 may contain workspaces. An identified collection MAY be the root
2773 collection of a tree of collections, all of which may contain
2774 workspaces. Since different servers can control different parts
2775 of the URL namespace, different resources on the same host MAY
2776 have different DAV:workspace-collection-set values. The
2777 identified collections MAY be located on different hosts from the
2802Clemm, et al. Standards Track [Page 50]
2804RFC 3253 Versioning Extensions to WebDAV March 2002
28076.4.1 Example - OPTIONS
2811 OPTIONS /doc HTTP/1.1
2812 Host: www.webdav.org
2813 Content-Type: text/xml; charset="utf-8"
2814 Content-Length: xxxx
2816 <?xml version="1.0" encoding="utf-8" ?>
2817 <D:options xmlns:D="DAV:">
2818 <D:version-history-collection-set/>
2819 <D:workspace-collection-set/>
2826 DAV: version-control,checkout-in-place,version-history,workspace
2827 Content-Type: text/xml; charset="utf-8"
2828 Content-Length: xxxx
2830 <?xml version="1.0" encoding="utf-8" ?>
2831 <D:options-response xmlns:D="DAV:">
2832 <D:version-history-collection-set>
2833 <D:href>http://repo.webdav.org/his</D:href>
2834 </D:version-history-collection-set>
2835 <D:workspace-collection-set>
2836 <D:href>http://www.webdav.org/public/ws</D:href>
2837 <D:href>http://www.webdav.org/private/ws</D:href>
2838 </D:workspace-collection-set>
2839 </D:options-response>
2841 In this example, the server indicates that it provides Class 1 DAV
2842 support and basic-server-workspace versioning support. In addition,
2843 the server indicates the requested locations of the version history
2844 resources and the workspace resources.
28466.5 Additional DELETE Semantics
2848 Additional Postconditions:
2850 (DAV:delete-workspace-members): If a workspace is deleted, any
2851 resource that identifies that workspace in its DAV:workspace
2852 property MUST be deleted.
2858Clemm, et al. Standards Track [Page 51]
2860RFC 3253 Versioning Extensions to WebDAV March 2002
28636.6 Additional MOVE Semantics
2865 Additional Postconditions:
2867 (DAV:workspace-member-moved): If the request-URL did not identify
2868 a workspace, the DAV:workspace of the destination MUST have been
2869 updated to have the same value as the DAV:workspace of the parent
2870 collection of the destination.
2872 (DAV:workspace-moved): If the request-URL identified a workspace,
2873 any reference to that workspace in a DAV:workspace property MUST
2874 have been updated to refer to the new location of that workspace.
28766.7 Additional VERSION-CONTROL Semantics
2878 A VERSION-CONTROL request can be used to create a new version-
2879 controlled resource for an existing version history. This allows the
2880 creation of version-controlled resources for the same version history
2881 in multiple workspaces.
2883 Additional Marshalling:
2885 <!ELEMENT version-control ANY>
2886 ANY value: A sequence of elements with at most one DAV:version
2889 <!ELEMENT version (href)>
2891 Additional Preconditions:
2893 (DAV:cannot-add-to-existing-history): If the DAV:version-control
2894 request body element contains a DAV:version element, the request-
2895 URL MUST NOT identify a resource.
2897 (DAV:must-be-version): The DAV:href of the DAV:version element
2898 MUST identify a version.
2900 (DAV:one-version-controlled-resource-per-history-per-workspace):
2901 If the DAV:version-control request body specifies a version, and
2902 if the request-URL is a member of a workspace, then there MUST NOT
2903 already be a version-controlled member of that workspace whose
2904 DAV:checked-in or DAV:checked-out property identifies any version
2905 from the version history of the version specified in the request
2914Clemm, et al. Standards Track [Page 52]
2916RFC 3253 Versioning Extensions to WebDAV March 2002
2919 Additional Postconditions:
2921 (DAV:new-version-controlled-resource): If the request-URL did NOT
2922 identify a resource, a new version-controlled resource exists at
2923 the request-URL whose content and dead properties are initialized
2924 by those of the version in the request body, and whose
2925 DAV:checked-in property identifies that version.
29276.7.1 Example - VERSION-CONTROL (using an existing version history)
2931 VERSION-CONTROL /ws/public/bar.html HTTP/1.1
2932 Host: www.webdav.org
2933 Content-Type: text/xml; charset="utf-8"
2934 Content-Length: xxxx
2936 <?xml version="1.0" encoding="utf-8" ?>
2937 <D:version-control xmlns:D="DAV:">
2939 <D:href>http://repo.webdav.org/his/12/ver/V3</D:href>
2941 </D:version-control>
2945 HTTP/1.1 201 Created
2946 Cache-Control: no-cache
2948 In this example, a new version-controlled resource is created at
2949 /ws/public/bar.html. The content and dead properties of the new
2950 version-controlled resource are initialized to be the same as those
2951 of the version identified by http://repo.webdav.org/his/12/ver/V3.
2955 The update feature provides a mechanism for changing the state of a
2956 checked-in version-controlled resource to be that of another version
2957 from the version history of that resource.
2961 The UPDATE method modifies the content and dead properties of a
2962 checked-in version-controlled resource (the "update target") to be
2963 those of a specified version (the "update source") from the version
2964 history of that version-controlled resource.
2970Clemm, et al. Standards Track [Page 53]
2972RFC 3253 Versioning Extensions to WebDAV March 2002
2975 The response to an UPDATE request identifies the resources modified
2976 by the request, so that a client can efficiently update any cached
2977 state it is maintaining. Extensions to the UPDATE method allow
2978 multiple resources to be modified from a single UPDATE request (see
2983 The request body MUST be a DAV:update element.
2985 <!ELEMENT update ANY>
2986 ANY value: A sequence of elements with at most one DAV:version
2987 element and at most one DAV:prop element.
2988 <!ELEMENT version (href)>
2989 prop: see RFC 2518, Section 12.11
2991 The response for a successful request MUST be a 207 Multi-Status,
2992 where the DAV:multistatus XML element in the response body
2993 identifies all resources that have been modified by the request.
2995 multistatus: see RFC 2518, Section 12.9
2997 The response MUST include a Cache-Control:no-cache header.
3001 (DAV:update-content-and-properties): If the DAV:version element in
3002 the request body identified a version that is in the same version
3003 history as the DAV:checked-in version of a version-controlled
3004 resource identified by the request-URL, then the content and dead
3005 properties of that version-controlled resource MUST be the same as
3006 those of the version specified by the DAV:version element, and the
3007 DAV:checked-in property of the version-controlled resource MUST
3008 identify that version. The request-URL MUST appear in a
3009 DAV:response element in the response body.
3011 (DAV:report-properties): If DAV:prop is specified in the request
3012 body, the properties specified in the DAV:prop element MUST be
3013 reported in the DAV:response elements in the response body.
3026Clemm, et al. Standards Track [Page 54]
3028RFC 3253 Versioning Extensions to WebDAV March 2002
30317.1.1 Example - UPDATE
3035 UPDATE /foo.html HTTP/1.1
3036 Host: www.webdav.org
3037 Content-type: text/xml; charset="utf-8"
3038 Content-Length: xxxx
3040 <?xml version="1.0" encoding="utf-8" ?>
3041 <D:update xmlns:D="DAV:">
3043 <D:href>http://repo.webdav.org/his/23/ver/33</D:href>
3049 HTTP/1.1 207 Multi-Status
3050 Content-Type: text/xml; charset="utf-8"
3051 Content-Length: xxxx
3052 Cache-Control: no-cache
3054 <?xml version="1.0" encoding="utf-8" ?>
3055 <D:multistatus xmlns:D="DAV:">
3057 <D:href>http://www.webdav.org/foo.html</D:href>
3058 <D:status>HTTP/1.1 200 OK</D:status>
3061 In this example, the content and dead properties of
3062 http://repo.webdav.org/his/23/ver/33 are copied to the version-
3063 controlled resource /foo.html, and the DAV:checked-in property of
3064 /foo.html is updated to refer to
3065 http://repo.webdav.org/his/23/ver/33.
30677.2 Additional OPTIONS Semantics
3069 If the server supports the update feature, it MUST include "update"
3070 as a field in the DAV response header from an OPTIONS request on any
3071 resource that supports any versioning properties, reports, or
3082Clemm, et al. Standards Track [Page 55]
3084RFC 3253 Versioning Extensions to WebDAV March 2002
3089 A version "label" is a string that distinguishes one version in a
3090 version history from all other versions in that version history. A
3091 label can automatically be assigned by a server, or it can be
3092 assigned by a client in order to provide a meaningful name for that
3093 version. A given version label can be assigned to at most one
3094 version of a given version history, but client assigned labels can be
3095 reassigned to another version at any time. Note that although a
3096 given label can be applied to at most one version from the same
3097 version history, the same label can be applied to versions from
3098 different version histories.
3100 For certain methods, if the request-URL identifies a version-
3101 controlled resource, a label can be specified in a Label request
3102 header (see Section 8.3) to cause the method to be applied to the
3103 version selected by that label from the version history of that
3104 version-controlled resource.
31068.1 Additional Version Properties
3108 The label feature introduces the following REQUIRED property for a
31118.1.1 DAV:label-name-set (protected)
3113 This property contains the labels that currently select this version.
3115 <!ELEMENT label-name-set (label-name*)>
3116 <!ELEMENT label-name (#PCDATA)>
3117 PCDATA value: string
3121 A LABEL request can be applied to a version to modify the labels that
3122 select that version. The case of a label name MUST be preserved when
3123 it is stored and retrieved. When comparing two label names to decide
3124 if they match or not, a server SHOULD use a case-sensitive URL-
3125 escaped UTF-8 encoded comparison of the two label names.
3127 If a LABEL request is applied to a checked in version-controlled
3128 resource, the operation MUST be applied to the DAV:checked-in version
3129 of that version-controlled resource.
3138Clemm, et al. Standards Track [Page 56]
3140RFC 3253 Versioning Extensions to WebDAV March 2002
3145 The request body MUST be a DAV:label element.
3147 <!ELEMENT label ANY>
3148 ANY value: A sequence of elements with at most one DAV:add,
3149 DAV:set, or DAV:remove element.
3151 <!ELEMENT add (label-name)>
3152 <!ELEMENT set (label-name)>
3153 <!ELEMENT remove (label-name)>
3154 <!ELEMENT label-name (#PCDATA)>
3155 PCDATA value: string
3157 The request MAY include a Label header.
3159 The request MAY include a Depth header. If no Depth header is
3160 included, Depth:0 is assumed. Standard depth semantics apply, and
3161 the request is applied to the collection identified by the
3162 request-URL and to all members of the collection that satisfy the
3163 Depth value. If a Depth header is included and the request fails
3164 on any resource, the response MUST be a 207 Multi-Status that
3165 identifies all resources for which the request has failed.
3167 If a response body for a successful request is included, it MUST
3168 be a DAV:label-response XML element.
3170 <!ELEMENT label-response ANY>
3172 The response MUST include a Cache-Control:no-cache header.
3176 (DAV:must-be-checked-in): If the request-URL identifies a
3177 version-controlled resource, the version-controlled resource MUST
3180 (DAV:must-select-version-in-history): If a Label request header is
3181 included and the request-URL identifies a version-controlled
3182 resource, the specified label MUST select a version in the version
3183 history of the version-controlled resource.
3185 (DAV:add-must-be-new-label): If DAV:add is specified in the
3186 request body, the specified label MUST NOT appear in the
3187 DAV:label-name-set of any version in the version history of that
3188 version-controlled resource.
3194Clemm, et al. Standards Track [Page 57]
3196RFC 3253 Versioning Extensions to WebDAV March 2002
3199 (DAV:label-must-exist): If DAV:remove is specified in the request
3200 body, the specified label MUST appear in the DAV:label-name-set of
3205 (DAV:add-or-set-label): If DAV:add or DAV:set is specified in the
3206 request body, the specified label MUST appear in the DAV:label-
3207 name-set of the specified version, and MUST NOT appear in the
3208 DAV:label-name-set of any other version in the version history of
3211 (DAV:remove-label): If DAV:remove is specified in the request
3212 body, the specified label MUST NOT appear in the DAV:label-name-
3213 set of any version in the version history of that version.
32158.2.1 Example - Setting a label
3219 LABEL /foo.html HTTP/1.1
3220 Host: www.webdav.org
3221 Content-type: text/xml; charset="utf-8"
3222 Content-Length: xxxx
3224 <?xml version="1.0" encoding="utf-8" ?>
3225 <D:label xmlns:D="DAV:">
3227 <D:label-name>default</D:label-name>
3234 Cache-Control: no-cache
3236 In this example, the label "default" is applied to the DAV:checked-in
3237 version of /foo.html.
3241 For certain methods (e.g. GET, PROPFIND), if the request-URL
3242 identifies a version-controlled resource, a label can be specified in
3243 a Label request header to cause the method to be applied to the
3244 version selected by that label from the version history of that
3245 version-controlled resource.
3250Clemm, et al. Standards Track [Page 58]
3252RFC 3253 Versioning Extensions to WebDAV March 2002
3255 The value of a label header is the name of a label, encoded using
3256 URL-escaped UTF-8. For example, the label "release B.3" is
3257 identified by the following header:
3259 Label: release%20B.3
3261 A Label header MUST have no effect on a request whose request-URL
3262 does not identify a version-controlled resource. In particular, it
3263 MUST have no effect on a request whose request-URL identifies a
3264 version or a version history.
3266 A server MUST return an HTTP-1.1 Vary header containing Label in a
3267 successful response to a cacheable request (e.g., GET) that includes
32708.4 Additional OPTIONS Semantics
3272 If the server supports the label feature, it MUST include "label" as
3273 a field in the DAV response header from an OPTIONS request on any
3274 resource that supports any versioning properties, reports, or
32778.5 Additional GET Semantics
3279 Additional Marshalling:
3281 The request MAY include a Label header.
3283 Additional Preconditions:
3285 (DAV:must-select-version-in-history): If a Label request header is
3286 included and the request-URL identifies a version-controlled
3287 resource, the specified label MUST select a version in the version
3288 history of the version-controlled resource.
3290 Additional Postconditions:
3292 (DAV:apply-request-to-labeled-version): If the request-URL
3293 identifies a version-controlled resource and a Label request
3294 header is included, the response MUST contain the content of the
3295 specified version rather than that of the version-controlled
32988.6 Additional PROPFIND Semantics
3300 Additional Marshalling:
3302 The request MAY include a Label header.
3306Clemm, et al. Standards Track [Page 59]
3308RFC 3253 Versioning Extensions to WebDAV March 2002
3311 Additional Preconditions:
3313 (DAV:must-select-version-in-history): If a Label request header is
3314 included and the request-URL identifies a version-controlled
3315 resource, the specified label MUST select a version in the version
3316 history of the version-controlled resource.
3318 Additional Postconditions:
3320 (DAV:apply-request-to-labeled-version): If the request-URL
3321 identifies a version-controlled resource and a Label request
3322 header is included, the response MUST contain the properties of
3323 the specified version rather than that of the version-controlled
33268.7 Additional COPY Semantics
3328 Additional Marshalling:
3330 The request MAY include a Label header.
3332 Additional Preconditions:
3334 (DAV:must-select-version-in-history): If a Label request header is
3335 included and the request-URL identifies a version-controlled
3336 resource, the specified label MUST select a version in the version
3337 history of the version-controlled resource.
3339 Additional Postconditions:
3341 (DAV:apply-request-to-labeled-version): If the request-URL
3342 identifies a version-controlled resource and a Label request
3343 header is included, the request MUST have copied the properties
3344 and content of the specified version rather than that of the
3345 version-controlled resource.
33478.8 Additional CHECKOUT Semantics
3349 If the server supports the working-resource option, a LABEL header
3350 may be included to check out the version selected by the specified
3353 Additional Marshalling:
3355 The request MAY include a Label header.
3362Clemm, et al. Standards Track [Page 60]
3364RFC 3253 Versioning Extensions to WebDAV March 2002
3367 Additional Preconditions:
3369 (DAV:must-select-version-in-history): If a Label request header is
3370 included and the request-URL identifies a version-controlled
3371 resource, the specified label MUST select a version in the version
3372 history of the version-controlled resource.
3374 (DAV:must-not-have-label-and-apply-to-version): If a Label request
3375 header is included, the request body MUST NOT contain a
3376 DAV:apply-to-version element.
3378 Additional Postconditions:
3380 (DAV:apply-request-to-labeled-version): If the request-URL
3381 identifies a checked-in version-controlled resource, and a Label
3382 request header is included, the CHECKOUT MUST have been applied to
3383 the version selected by the specified label, and not to the
3384 version-controlled resource itself.
33868.9 Additional UPDATE Semantics
3388 If the request body of an UPDATE request contains a DAV:label-name
3389 element, the update target is the resource identified by the
3390 request-URL, and the update source is the version selected by the
3391 specified label from the version history of the update target.
3393 Additional Marshalling:
3395 <!ELEMENT update ANY>
3396 ANY value: A sequence of elements with at most one DAV:label-name
3397 or DAV:version element (but not both).
3398 <!ELEMENT label-name (#PCDATA)>
3399 PCDATA value: string
3401 The request MAY include a Depth header. If no Depth header is
3402 included, Depth:0 is assumed. Standard depth semantics apply, and
3403 the request is applied to the collection identified by the
3404 request-URL and to all members of the collection that satisfy the
3405 Depth value. If a Depth header is included and the request fails
3406 on any resource, the response MUST be a 207 Multi-Status that
3407 identifies all resources for which the request has failed.
3409 Additional Preconditions:
3411 (DAV:must-select-version-in-history): If the request includes a
3412 DAV:label-name element in the request body, the label MUST select
3413 a version in the version history of the version-controlled
3414 resource identified by the request-URL.
3418Clemm, et al. Standards Track [Page 61]
3420RFC 3253 Versioning Extensions to WebDAV March 2002
3423 (DAV:depth-update): If the request includes a Depth header,
3424 standard depth semantics apply, and the request is applied to the
3425 collection identified by the request-URL and to all members of the
3426 collection that satisfy the Depth value. The request MUST be
3427 applied to a collection before being applied to any members of
3428 that collection, since an update of a version-controlled
3429 collection might change the membership of that collection.
3431 Additional Postconditions:
3433 (DAV:apply-request-to-labeled-version): If a DAV:label-name
3434 element appears in the request body, the content and dead
3435 properties of the version-controlled resource must have been
3436 updated to be those of the version selected by that label.
34389 Working-Resource Feature
3440 The working-resource feature provides an alternative to the workspace
3441 feature for supporting parallel development. Unlike the workspace
3442 feature, where the desired configuration of versions and checked-out
3443 resources is maintained on the server, the working-resource feature
3444 maintains the configuration on the client. This simplifies the
3445 server implementation, but does not allow a user to access the
3446 configuration from clients in different physical locations, such as
3447 from another office, from home, or while traveling. Another
3448 difference is that the workspace feature isolates clients from a
3449 logical change that involves renaming shared resources, until that
3450 logical change is complete and tested; with the working resource
3451 feature, all clients use a common set of shared version-controlled
3452 resources and every client sees the result of a MOVE as soon as it
3455 If a server supports the working-resource feature but not the
3456 checkout-in-place feature, a CHECKOUT request can only be used to
3457 create a working resource, and cannot be used to check out a
3458 version-controlled resource. If a server supports the checkout-in-
3459 place feature, but not the working-resource feature, a CHECKOUT can
3460 only be used to change the state of a version-controlled resource
3461 from checked-in to checked-out.
34639.1 Additional Version Properties
3465 The working-resource feature introduces the following REQUIRED
3466 properties for a version.
34689.1.1 DAV:checkout-fork
3470 This property is defined in Section 4.1.1.
3474Clemm, et al. Standards Track [Page 62]
3476RFC 3253 Versioning Extensions to WebDAV March 2002
34799.1.2 DAV:checkin-fork
3481 This property is defined in Section 4.1.2.
34839.2 Working Resource Properties
3485 The working-resource feature introduces the following REQUIRED
3486 properties for a working resource. Since a working resource is a
3487 checked-out resource, it also has any property defined in this
3488 document for a checked-out resource.
34909.2.1 DAV:auto-update (protected)
3492 This property identifies the version-controlled resource that will be
3493 updated when the working resource is checked in.
3495 <!ELEMENT auto-update (href)>
34979.2.2 DAV:checkout-fork
3499 This property is defined in Section 4.2.1.
35019.2.3 DAV:checkin-fork
3503 This property is defined in Section 4.2.2.
35059.3 CHECKOUT Method (applied to a version)
3507 A CHECKOUT request can be applied to a version to create a new
3508 working resource. The content and dead properties of the working
3509 resource are a copy of the version that was checked out.
3513 If a request body is included, it MUST be a DAV:checkout XML
3516 <!ELEMENT checkout ANY>
3518 ANY value: A sequence of elements with at most one DAV:apply-to-
3519 version and at most one DAV:fork-ok element.
3521 <!ELEMENT apply-to-version EMPTY>
3522 <!ELEMENT fork-ok EMPTY>
3524 If a response body for a successful request is included,
3525 it MUST be a DAV:checkout-response XML element.
3530Clemm, et al. Standards Track [Page 63]
3532RFC 3253 Versioning Extensions to WebDAV March 2002
3535 <!ELEMENT checkout-response ANY>
3537 The response MUST include a Location header.
3539 The response MUST include a Cache-Control:no-cache header.
3543 (DAV:checkout-of-version-with-descendant-is-forbidden): See
3546 (DAV:checkout-of-version-with-descendant-is-discouraged): See
3549 (DAV:checkout-of-checked-out-version-is-forbidden): See Section
3552 (DAV:checkout-of-checked-out-version-is-discouraged): See Section
3557 (DAV:create-working-resource): If the request-URL identified a
3558 version, the Location response header MUST contain the URL of a
3559 new working resource. The DAV:checked-out property of the new
3560 working resource MUST identify the version that was checked out.
3561 The content and dead properties of the working resource MUST be
3562 copies of the content and dead properties of the DAV:checked-out
3563 version. The DAV:predecessor-set property of the working resource
3564 MUST be initialized to be the version identified by the request-
3565 URL. The DAV:auto-update property of the working resource MUST
3568 (DAV:create-working-resource-from-checked-in-version): If the
3569 request-URL identified a version-controlled resource, and
3570 DAV:apply-to-version is specified in the request body, the
3571 CHECKOUT is applied to the DAV:checked-in version of the version-
3572 controlled resource, and not the version-controlled resource
3573 itself. A new working resource is created and the version-
3574 controlled resource remains checked-in. The DAV:auto-update
3575 property of the working resource MUST identify the version-
3576 controlled resource.
3586Clemm, et al. Standards Track [Page 64]
3588RFC 3253 Versioning Extensions to WebDAV March 2002
35919.3.1 Example - CHECKOUT of a version
3595 CHECKOUT /his/12/ver/V3 HTTP/1.1
3596 Host: repo.webdav.org
3601 HTTP/1.1 201 Created
3602 Location: http://repo.webdav.org/wr/157
3603 Cache-Control: no-cache
3605 In this example, the version identified by
3606 http://repo.webdav.org/his/12/ver/V3 is checked out, and the new
3607 working resource is located at http://repo.webdav.org/wr/157.
36099.4 CHECKIN Method (applied to a working resource)
3611 A CHECKIN request can be applied to a working resource to produce a
3612 new version whose content and dead properties are a copy of those of
3613 the working resource. If the DAV:auto-update property of the working
3614 resource was set because the working resource was created by applying
3615 a CHECKOUT with the DAV:apply-to-version flag to a version-controlled
3616 resource, the CHECKIN request will also update the content and dead
3617 properties of that version-controlled resource to be those of the new
3622 If a request body is included, it MUST be a DAV:checkin XML
3625 <!ELEMENT checkin ANY>
3626 ANY value: A sequence of elements with at most one DAV:fork-ok
3629 <!ELEMENT fork-ok EMPTY>
3631 If a response body for a successful request is included, it MUST
3632 be a DAV:checkin-response XML element.
3634 <!ELEMENT checkin-response ANY>
3636 The response MUST include a Cache-Control:no-cache header.
3642Clemm, et al. Standards Track [Page 65]
3644RFC 3253 Versioning Extensions to WebDAV March 2002
3649 (DAV:must-be-checked-out): See Section 4.4.
3651 (DAV:version-history-is-tree) See Section 4.4.
3653 (DAV:checkin-fork-forbidden): See Section 4.4.
3655 (DAV:checkin-fork-discouraged): See Section 4.4.
3657 (DAV:no-overwrite-by-auto-update): If the DAV:auto-update property
3658 for the checked-out resource identifies a version-controlled
3659 resource, at least one of the versions identified by the
3660 DAV:predecessor-set property of the checked-out resource MUST
3661 identify a version that is either the same as or a descendant of
3662 the version identified by the DAV:checked-in property of that
3663 version-controlled resource.
3667 (DAV:create-version): See Section 4.4.
3669 (DAV:initialize-version-content-and-properties): See Section 4.4.
3671 (DAV:auto-update): If the DAV:auto-update property of the
3672 checked-out resource identified a version-controlled resource, an
3673 UPDATE request with the new version MUST have been applied to that
3674 version-controlled resource.
3676 (DAV:delete-working-resource): If the request-URL identifies a
3677 working resource and if DAV:keep-checked-out is not specified in
3678 the request body, the working resource is deleted.
36809.4.1 Example - CHECKIN of a working resource
3684 CHECKIN /wr/157 HTTP/1.1
3685 Host: repo.webdav.org
3690 HTTP/1.1 201 Created
3691 Location: http://repo.webdav.org/his/23/ver/15
3692 Cache-Control: no-cache
3698Clemm, et al. Standards Track [Page 66]
3700RFC 3253 Versioning Extensions to WebDAV March 2002
3703 In this example, the working resource /wr/157 checked in, and a new
3704 version is created at http://repo.webdav.org/his/23/ver/15.
37069.5 Additional OPTIONS Semantics
3708 If the server supports the working-resource feature, it MUST include
3709 "working-resource" as a field in the DAV response header from an
3710 OPTIONS request on any resource that supports any versioning
3711 properties, reports, or methods.
37139.6 Additional COPY Semantics
3715 Additional Postconditions:
3717 (DAV:copy-creates-new-resource): The result of copying a working
3718 resource is a new non-version-controlled resource at the
3719 destination of the COPY. The new resource MAY automatically be
3720 put under version control, but the resulting version-controlled
3721 resource MUST be associated with a new version history created for
3722 that new version-controlled resource.
37249.7 Additional MOVE Semantics
3726 Additional Preconditions:
3728 (DAV:cannot-rename-working-resource): If the request-URL
3729 identifies a working resource, the request MUST fail.
3731 Additional Postconditions:
3733 (DAV:update-auto-update): If the request-URL identified a
3734 version-controlled resource, any DAV:auto-update properties that
3735 identified that version-controlled resource MUST have been updated
3736 to contain the new location of that version-controlled resource.
373810 Advanced Versioning Features
3740 Advanced versioning addresses the problems of parallel development
3741 and configuration management of multiple sets of interrelated
3742 resources. Traditionally, artifacts of software development,
3743 including requirements, design documents, code, and test cases, have
3744 been a focus of configuration management. Web sites, comprising
3745 multiple inter-linked resources (HTML, graphics, sound, CGI, and
3746 others), are another class of complex information artifacts that
3747 benefit from the application of configuration management. The
3748 advanced versioning capabilities for coordinating concurrent change
3749 provide the infrastructure for efficient and controlled management of
3750 large evolving web sites.
3754Clemm, et al. Standards Track [Page 67]
3756RFC 3253 Versioning Extensions to WebDAV March 2002
375910.1 Advanced Versioning Packages
3761 Although a server MAY support any combination of advanced versioning
3762 features, in order to minimize the complexity of a WebDAV advanced
3763 versioning client, a WebDAV advanced versioning server SHOULD support
3764 one of the following packages:
3766 Advanced-Server-Workspace Package: basic-server-workspace package
3767 plus all advanced features
3769 Advanced-Client-Workspace Package: basic-client-workspace package
3770 plus all advanced features
3772 The advanced-server-workspace package supports advanced versioning
3773 capabilities for a client with no persistent state. The advanced-
3774 client-workspace package supports advanced versioning capabilities
3775 for a client that maintains configuration state on the client. A
3776 server that supports both advanced workspace packages will
3777 interoperate with all versioning clients.
377910.2 Advanced Versioning Terms
3781 The following additional terms are used by the advanced versioning
3786 A "collection" is a resource whose state consists of not only
3787 content and properties, but also a set of named "bindings", where
3788 a binding identifies what RFC 2518 calls an "internal member" of
3789 the collection. Note that a binding is not a resource, but rather
3790 is a part of the state of a collection that defines a mapping from
3791 a binding name (a URL segment) to a resource (an internal member
3794 Collection Version Resource
3796 A "collection version resource", or simply "collection version",
3797 captures the dead properties of a version-controlled collection,
3798 as well as the names of its version-controlled bindings (see
3799 Section 14). A version-controlled binding is a binding to a
3800 version-controlled resource. If the checkout-in-place feature is
3801 supported, a collection version can be created by checking out and
3802 then checking in a version-controlled collection. If the
3803 working-resource feature is supported, a collection version can be
3804 created by checking out a collection version (to create a "working
3805 collection") and then checking in the working collection.
3810Clemm, et al. Standards Track [Page 68]
3812RFC 3253 Versioning Extensions to WebDAV March 2002
3817 A "configuration" is a set of resources that consists of a root
3818 collection and all members (not just internal members) of that
3819 root collection that are not members of another configuration.
3820 The root collection is called the "configuration root", and the
3821 members of this set are called the "members of the configuration".
3822 Note that a collection (which is a single resource) is very
3823 different from a configuration (which is a set of resources).
3827 A "baseline resource", or simply "baseline", of a collection is a
3828 version of the configuration that is rooted at that collection
3829 (see Section 12). In particular, a baseline captures the
3830 DAV:checked-in version of every version-controlled member of that
3831 configuration. Note that a collection version (which captures the
3832 state of a single resource) is very different from a collection
3833 baseline (which captures the state of a set of resources).
3835 Baseline-Controlled Collection
3837 A "baseline-controlled collection" is a collection from which
3838 baselines can be created (see Section 12).
3840 Version-Controlled Configuration Resource
3842 A "version-controlled configuration resource", or simply
3843 "version-controlled configuration", is a special kind of version-
3844 controlled resource that is associated with a baseline-controlled
3845 collection, and is used to create and access baselines of that
3846 collection (see Section 12). When a collection is both version-
3847 controlled and baseline-controlled, a client can create a new
3848 version of the collection by checking out and checking in that
3849 collection, and it can create a new baseline of that collection by
3850 checking out and checking in the version-controlled configuration
3855 An "activity resource", or simply "activity", is a resource that
3856 selects a set of versions that correspond to a single logical
3857 change, where the versions selected from a given version history
3858 form a single line of descent through that version history (see
3866Clemm, et al. Standards Track [Page 69]
3868RFC 3253 Versioning Extensions to WebDAV March 2002
3873 When a user wants to accept the changes (new versions) created by
3874 someone else, it is important not just to update the version-
3875 controlled resources in the user's workspace with those new versions,
3876 since this could result in "backing out" changes the user has made to
3877 those version-controlled resources. Instead, the versions created in
3878 another workspace should be "merged" into the user's version-
3879 controlled resources.
3881 The version history of a version-controlled resource provides the
3882 information needed to determine the result of the merge. In
3883 particular, the merge should select whichever version is later in the
3884 line of descent from the root version. In case the versions to be
3885 merged are on different lines of descent (neither version is a
3886 descendant of the other), neither version should be selected, but
3887 instead, a new version should be created that contains the logical
3888 merge of the content and dead properties of those versions. The
3889 MERGE request can be used to check out each version-controlled
3890 resource that requires such a merge, and set the DAV:merge-set
3891 property of each checked-out resource to identify the version to be
3892 merged. The user is responsible for modifying the content and dead
3893 properties of the checked-out resource so that it represents the
3894 logical merge of that version, and then adding that version to the
3895 DAV:predecessor-set of the checked-out resource.
3897 If the server is capable of automatically performing the merge, it
3898 MAY update the content, dead properties, and DAV:predecessor-set of
3899 the checked-out resource itself. Before checking in the
3900 automatically merged resource, the user is responsible for verifying
3901 that the automatic merge is correct.
390311.1 Additional Checked-Out Resource Properties
3905 The merge feature introduces the following REQUIRED properties for a
3906 checked-out resource.
3910 This property identifies each version that is to be merged into this
3911 checked-out resource.
3913 <!ELEMENT merge-set (href*)>
3922Clemm, et al. Standards Track [Page 70]
3924RFC 3253 Versioning Extensions to WebDAV March 2002
392711.1.2 DAV:auto-merge-set
3929 This property identifies each version that the server has merged into
3930 this checked-out resource. The client should confirm that the merge
3931 has been performed correctly before moving a URL from the DAV:auto-
3932 merge-set to the DAV:predecessor-set of a checked-out resource.
3934 <!ELEMENT auto-merge-set (href*)>
3938 The MERGE method performs the logical merge of a specified version
3939 (the "merge source") into a specified version-controlled resource
3940 (the "merge target"). If the merge source is neither an ancestor nor
3941 a descendant of the DAV:checked-in or DAV:checked-out version of the
3942 merge target, the MERGE checks out the merge target (if it is not
3943 already checked out) and adds the URL of the merge source to the
3944 DAV:merge-set of the merge target. It is then the client's
3945 responsibility to update the content and dead properties of the
3946 checked-out merge target so that it reflects the logical merge of the
3947 merge source into the current state of the merge target. The client
3948 indicates that it has completed the update of the merge target, by
3949 deleting the merge source URL from the DAV:merge-set of the checked-
3950 out merge target, and adding it to the DAV:predecessor-set. As an
3951 error check for a client forgetting to complete a merge, the server
3952 MUST fail an attempt to CHECKIN a version-controlled resource with a
3953 non-empty DAV:merge-set.
3955 When a server has the ability to automatically update the content and
3956 dead properties of the merge target to reflect the logical merge of
3957 the merge source, it may do so unless DAV:no-auto-merge is specified
3958 in the MERGE request body. In order to notify the client that a
3959 merge source has been automatically merged, the MERGE request MUST
3960 add the URL of the auto-merged source to the DAV:auto-merge-set
3961 property of the merge target, and not to the DAV:merge-set property.
3962 The client indicates that it has verified that the auto-merge is
3963 valid, by deleting the merge source URL from the DAV:auto-merge-set,
3964 and adding it to the DAV:predecessor-set.
3966 Multiple merge sources can be specified in a single MERGE request.
3967 The set of merge sources for a MERGE request is determined from the
3968 DAV:source element of the MERGE request body as follows:
3970 - If DAV:source identifies a version, that version is a merge
3972 - If DAV:source identifies a version-controlled resource, the
3973 DAV:checked-in version of that version-controlled resource is a
3978Clemm, et al. Standards Track [Page 71]
3980RFC 3253 Versioning Extensions to WebDAV March 2002
3983 - If DAV:source identifies a collection, the DAV:checked-in version
3984 of each version-controlled resource that is a member of that
3985 collection is a merge source.
3987 The request-URL identifies the set of possible merge targets. If the
3988 request-URL identifies a collection, any member of the configuration
3989 rooted at the request-URL is a possible merge target. The merge
3990 target of a particular merge source is the version-controlled or
3991 checked-out resource whose DAV:checked-in or DAV:checked-out version
3992 is from the same version history as the merge source. If a merge
3993 source has no merge target, that merge source is ignored.
3995 The MERGE response identifies the resources that a client must modify
3996 to complete the merge. It also identifies the resources modified by
3997 the request, so that a client can efficiently update any cached state
4002 The request body MUST be a DAV:merge element.
4004 The set of merge sources is determined by the DAV:source element
4005 in the request body.
4007 <!ELEMENT merge ANY>
4008 ANY value: A sequence of elements with one DAV:source element, at
4009 most one DAV:no-auto-merge element, at most one DAV:no-checkout
4010 element, at most one DAV:prop element, and any legal set of
4011 elements that can occur in a DAV:checkout element.
4012 <!ELEMENT source (href+)>
4013 <!ELEMENT no-auto-merge EMPTY>
4014 <!ELEMENT no-checkout EMPTY>
4015 prop: see RFC 2518, Section 12.11
4017 The response for a successful request MUST be a 207 Multi-Status,
4018 where the DAV:multistatus XML element in the response body
4019 identifies all resources that have been modified by the request.
4021 multistatus: see RFC 2518, Section 12.9
4023 The response to a successful request MUST include a Location
4024 header containing the URL for the new version created by the
4027 The response MUST include a Cache-Control:no-cache header.
4034Clemm, et al. Standards Track [Page 72]
4036RFC 3253 Versioning Extensions to WebDAV March 2002
4041 (DAV:cannot-merge-checked-out-resource): The DAV:source element
4042 MUST NOT identify a checked-out resource. If the DAV:source
4043 element identifies a collection, the collection MUST NOT have a
4044 member that is a checked-out resource.
4046 (DAV:checkout-not-allowed): If DAV:no-checkout is specified in the
4047 request body, it MUST be possible to perform the merge without
4048 checking out any of the merge targets.
4050 All preconditions of the CHECKOUT operation apply to the checkouts
4051 performed by the request.
4055 (DAV:ancestor-version): If a merge target is a version-controlled
4056 or checked-out resource whose DAV:checked-in version or
4057 DAV:checked-out version is the merge source or is a descendant of
4058 the merge source, the merge target MUST NOT have been modified by
4061 (DAV:descendant-version): If the merge target was a checked-in
4062 version-controlled resource whose DAV:checked-in version was an
4063 ancestor of the merge source, an UPDATE operation MUST have been
4064 applied to the merge target to set its content and dead properties
4065 to be those of the merge source. If the UPDATE method is not
4066 supported, the merge target MUST have been checked out, the
4067 content and dead properties of the merge target MUST have been set
4068 to those of the merge source, and the merge source MUST have been
4069 added to the DAV:auto-merge-set of the merge target. The merge
4070 target MUST appear in a DAV:response XML element in the response
4073 (DAV:checked-out-for-merge): If the merge target was a checked-in
4074 version-controlled resource whose DAV:checked-in version was
4075 neither a descendant nor an ancestor of the merge source, a
4076 CHECKOUT MUST have been applied to the merge target. All XML
4077 elements in the DAV:merge XML element that could appear in a
4078 DAV:checkout XML element MUST have been used as arguments to the
4079 CHECKOUT request. The merge target MUST appear in a DAV:response
4080 XML element in the response body.
4082 (DAV:update-merge-set): If the DAV:checked-out version of the
4083 merge target is neither equal to nor a descendant of the merge
4084 source, the merge source MUST be added to either the DAV:merge-set
4085 or the DAV:auto-merge-set of the merge target. The merge target
4086 MUST appear in a DAV:response XML element in the response body.
4090Clemm, et al. Standards Track [Page 73]
4092RFC 3253 Versioning Extensions to WebDAV March 2002
4095 If a merge source has been added to the DAV:auto-merge-set, the
4096 content and dead properties of the merge target MUST have been
4097 modified by the server to reflect the result of a logical merge of
4098 the merge source and the merge target. If a merge source has been
4099 added to the DAV:merge-set, the content and dead properties of the
4100 merge target MUST NOT have been modified by the server. If
4101 DAV:no-auto-merge is specified in the request body, the merge
4102 source MUST NOT have been added to the DAV:auto-merge-set.
4104 (DAV:report-properties): If DAV:prop is specified in the request
4105 body, the properties specified in the DAV:prop element MUST be
4106 reported in the DAV:response elements in the response body.
410811.2.1 Example - MERGE
4112 MERGE /ws/public HTTP/1.1
4113 Host: www.webdav.org
4114 Content-type: text/xml; charset="utf-8"
4115 Content-Length: xxxx
4117 <?xml version="1.0" encoding="utf-8" ?>
4118 <D:merge xmlns:D="DAV:">
4120 <D:href>http://www.webdav.org/ws/dev/sally</D:href>
4126 HTTP/1.1 207 Multi-Status
4127 Content-Type: text/xml; charset="utf-8"
4128 Content-Length: xxxx
4129 Cache-Control: no-cache
4131 <?xml version="1.0" encoding="utf-8" ?>
4132 <D:multistatus xmlns:D="DAV:">
4134 <D:href>http://www.webdav.org/ws/public/src/parse.c</D:href>
4135 <D:status>HTTP/1.1 200 OK</D:status>
4138 <D:href>http://www.webdav.org/ws/public/doc/parse.html</D:href>
4139 <D:status>HTTP/1.1 200 OK</D:status>
4146Clemm, et al. Standards Track [Page 74]
4148RFC 3253 Versioning Extensions to WebDAV March 2002
4151 In this example, the DAV:checked-in versions from the workspace
4152 http://www.webdav.org/ws/dev/sally are merged into the version-
4153 controlled resources in the workspace
4154 http://www.webdav.org/ws/public. The resources
4155 /ws/public/src/parse.c and /ws/public/doc/parse.html were modified by
415811.3 DAV:merge-preview Report
4160 A merge preview describes the changes that would result if the
4161 versions specified by the DAV:source element in the request body were
4162 to be merged into the resource identified by the request-URL
4163 (commonly, a collection).
4167 The request body MUST be a DAV:merge-preview XML element.
4169 <!ELEMENT merge-preview (source)>
4170 <!ELEMENT source (href)>
4172 The response body for a successful request MUST be a
4173 DAV:merge-preview-report XML element.
4175 <!ELEMENT merge-preview-report
4176 (update-preview | conflict-preview | ignore-preview)*>
4178 A DAV:update-preview element identifies a merge target whose
4179 DAV:checked-in property would change as a result of the MERGE, and
4180 identifies the merge source for that merge target.
4182 <!ELEMENT update-preview (target, version)>
4183 <!ELEMENT target (href)>
4184 <!ELEMENT version (href)>
4186 A DAV:conflict-preview element identifies a merge target that
4189 <!ELEMENT conflict-preview (target, common-ancestor, version)>
4191 A DAV:common-ancestor element identifies the version that is a
4192 common ancestor of both the merge source and the DAV:checked-in or
4193 DAV:checked-out version of the merge target.
4195 <!ELEMENT common-ancestor (href)>
4197 A DAV:ignore-preview element identifies a version that has no
4198 merge target and therefore would be ignored by the merge.
4202Clemm, et al. Standards Track [Page 75]
4204RFC 3253 Versioning Extensions to WebDAV March 2002
4207 <!ELEMENT ignore-preview (version)>
420911.3.1 Example - DAV:merge-preview Report
4213 REPORT /ws/public HTTP/1.1
4214 Host: www.webdav.org
4215 Content-type: text/xml; charset="utf-8"
4216 Content-Length: xxxx
4218 <?xml version="1.0" encoding="utf-8" ?>
4219 <D:merge-preview xmlns:D="DAV:">
4221 <D:href>http://www.webdav.org/ws/dev/fred</D:href>
4228 Content-Type: text/xml; charset="utf-8"
4229 Content-Length: xxxx
4231 <?xml version="1.0" encoding="utf-8" ?>
4232 <D:merge-preview-report xmlns:D="DAV:">
4233 <D:conflict-preview>
4235 <D:href>http://www.webdav.org/ws/public/foo.html</D:href>
4238 <D:href>http://repo.webdav.org/his/23/ver/18</D:href>
4239 </D:common-ancestor>
4241 <D:href>http://repo.webdav.org/his/23/ver/42</D:href>
4243 </D:conflict-preview>
4246 <D:href>http://www.webdav.org/ws/public/bar.html</D:href>
4249 <D:href>http://www.repo/his/42/ver/3</D:href>
4252 </D:merge-preview-report>
4258Clemm, et al. Standards Track [Page 76]
4260RFC 3253 Versioning Extensions to WebDAV March 2002
4263 In this example, the merge preview report indicates that version
4264 /his/23/ver/42 would be merged in /ws/public/foo.html, and version
4265 /his/42/ver/3 would update /ws/public/bar.html if the workspace
4266 http://www.webdav.org/ws/dev/fred was merged into the workspace
4267 http://www.webdav.org/ws/public.
426911.4 Additional OPTIONS Semantics
4271 If the server supports the merge feature, it MUST include "merge" as
4272 a field in the DAV response header from an OPTIONS request on any
4273 resource that supports any versioning properties, reports, or
427611.5 Additional DELETE Semantics
4278 Additional Postconditions:
4280 (DAV:delete-version-reference): If a version is deleted, any
4281 reference to that version in a DAV:merge-set or DAV:auto-merge-set
4282 property MUST be removed.
428411.6 Additional CHECKIN Semantics
4286 Additional Preconditions:
4288 (DAV:merge-must-be-complete): The DAV:merge-set and DAV:auto-
4289 merge-set of the checked-out resource MUST be empty or not exist.
4293 A configuration is a set of resources that consists of a root
4294 collection and all members of that root collection except those
4295 resources that are members of another configuration. A configuration
4296 that contains a large number of resources can consume a large amount
4297 of space on a server. This can make it prohibitively expensive to
4298 remember the state of an existing configuration by creating a
4299 Depth:infinity copy of its root collection.
4301 A baseline is a version resource that captures the state of each
4302 version-controlled member of a configuration. A baseline history is
4303 a version history whose versions are baselines. New baselines are
4304 created by checking out and then checking in a special kind of
4305 version-controlled resource called a version-controlled
4308 A collection that is under baseline control is called a baseline-
4309 controlled collection. In order to allow efficient baseline
4310 implementation, the state of a baseline of a collection is limited to
4314Clemm, et al. Standards Track [Page 77]
4316RFC 3253 Versioning Extensions to WebDAV March 2002
4319 be a set of versions and their names relative to the collection, and
4320 the operations on a baseline are limited to the creation of a
4321 baseline from a collection, and restoring or merging the baseline
4322 back into a collection. A server MAY automatically put a collection
4323 under baseline control when it is created, or a client can use the
4324 BASELINE-CONTROL method to put a specified collection under baseline
4327 As a configuration gets large, it is often useful to break it up into
4328 a set of smaller configurations that form the logical "components" of
4329 that configuration. In order to capture the fact that a baseline of
4330 a configuration is logically extended by a component configuration
4331 baseline, the component configuration baseline is captured as a
4332 "subbaseline" of the baseline.
4334 The root collection of a configuration is unconstrained with respect
4335 to its relationship to the root collection of any of its components.
4336 In particular, the root collection of a configuration can have a
4337 member that is the root collection of one of its components (e.g.,
4338 configuration /sys/x can have a component /sys/x/foo), can be a
4339 member of the root collection of one of its components (e.g.,
4340 configuration /sys/y/z can have a component /sys/y), or neither
4341 (e.g., configuration /sys/x can have a component /comp/bar).
434312.1 Version-Controlled Configuration Properties
4345 Since a version-controlled configuration is a version-controlled
4346 resource, it has all the properties of a version-controlled resource.
4347 In addition, the baseline feature introduces the following REQUIRED
4348 property for a version-controlled configuration.
435012.1.1 DAV:baseline-controlled-collection (protected)
4352 This property identifies the collection that contains the version-
4353 controlled resources whose DAV:checked-in versions are being tracked
4354 by this version-controlled configuration. The DAV:version-
4355 controlled-configuration of the DAV:baseline-controlled-collection of
4356 a version-controlled configuration MUST identify that version-
4357 controlled configuration.
4359 <!ELEMENT baseline-controlled-collection (href)>
436112.2 Checked-Out Configuration Properties
4363 Since a checked-out configuration is a checked-out resource, it has
4364 all the properties of a checked-out resource. In addition, the
4365 baseline feature introduces the following REQUIRED property for a
4366 checked-out configuration.
4370Clemm, et al. Standards Track [Page 78]
4372RFC 3253 Versioning Extensions to WebDAV March 2002
437512.2.1 DAV:subbaseline-set
4377 This property determines the DAV:subbaseline-set property of the
4378 baseline that results from checking in this resource.
4380 A server MAY reject attempts to modify the DAV:subbaseline-set of a
4381 checked-out configuration.
4383 <!ELEMENT subbaseline-set (href*)>
438512.3 Baseline Properties
4387 The DAV:resourcetype of a baseline MUST be DAV:baseline. Since a
4388 baseline is a version resource, it has all the properties of a
4389 version resource. In addition, the baseline feature introduces the
4390 following REQUIRED properties for a baseline.
439212.3.1 DAV:baseline-collection (protected)
4394 This property contains a server-defined URL for a collection, where
4395 each member of this collection MUST either be a version-controlled
4396 resource with the same DAV:checked-in version and relative name as a
4397 version-controlled member of the baseline-controlled collection at
4398 the time the baseline was created, or be a collection needed to
4399 provide the relative name for a version-controlled resource.
4401 <!ELEMENT baseline-collection (href)>
440312.3.2 DAV:subbaseline-set (protected)
4405 The URLs in the DAV:subbaseline-set property MUST identify a set of
4406 other baselines. The subbaselines of a baseline are the baselines
4407 identified by its DAV:subbaseline-set and all subbaselines of the
4408 baselines identified by its DAV:subbaseline-set.
4410 <!ELEMENT subbaseline-set (href*)>
441212.4 Additional Resource Properties
4414 The baseline feature introduces the following REQUIRED property for a
441712.4.1 DAV:version-controlled-configuration (computed)
4419 If the resource is a member of a version-controlled configuration
4420 (i.e. the resource is a collection under baseline control or is a
4421 member of a collection under baseline control), this property
4422 identifies that version-controlled configuration.
4426Clemm, et al. Standards Track [Page 79]
4428RFC 3253 Versioning Extensions to WebDAV March 2002
4431 <!ELEMENT version-controlled-configuration (href)>
443312.5 Additional Workspace Properties
4435 The baseline feature introduces the following REQUIRED property for a
443812.5.1 DAV:baseline-controlled-collection-set (computed)
4440 This property identifies each member of the workspace that is a
4441 collection under baseline control (as well as the workspace itself,
4442 if it is under baseline control).
4444 <!ELEMENT baseline-controlled-collection-set (href*)>
444612.6 BASELINE-CONTROL Method
4448 A collection can be placed under baseline control with a
4449 BASELINE-CONTROL request. When a collection is placed under baseline
4450 control, the DAV:version-controlled-configuration property of the
4451 collection is set to identify a new version-controlled configuration.
4452 This version-controlled configuration can be checked out and then
4453 checked in to create a new baseline for that collection.
4455 If a baseline is specified in the request body, the DAV:checked-in
4456 version of the new version-controlled configuration will be that
4457 baseline, and the collection is initialized to contain version-
4458 controlled members whose DAV:checked-in versions and relative names
4459 are determined by the specified baseline.
4461 If no baseline is specified, a new baseline history is created
4462 containing a baseline that captures the state of the version-
4463 controlled members of the collection, and the DAV:checked-in version
4464 of the version-controlled configuration will be that baseline.
4468 If a request body is included, it MUST be a DAV:baseline-control
4471 <!ELEMENT baseline-control ANY>
4472 ANY value: A sequence of elements with at most one DAV:baseline
4475 <!ELEMENT baseline (href)>
4477 If a response body for a successful request is included, it MUST
4478 be a DAV:baseline-control-response XML element.
4482Clemm, et al. Standards Track [Page 80]
4484RFC 3253 Versioning Extensions to WebDAV March 2002
4487 <!ELEMENT baseline-control-response ANY>
4489 The response MUST include a Cache-Control:no-cache header.
4493 (DAV:version-controlled-configuration-must-not-exist): The
4494 DAV:version-controlled-configuration property of the collection
4495 identified by the request-URL MUST not exist.
4497 (DAV:must-be-baseline): The DAV:href of the DAV:baseline element
4498 in the request body MUST identify a baseline.
4500 (DAV:must-have-no-version-controlled-members): If a DAV:baseline
4501 element is specified in the request body, the collection
4502 identified by the request-URL MUST have no version-controlled
4505 (DAV:one-baseline-controlled-collection-per-history-per-
4506 workspace): If the request-URL identifies a workspace or a member
4507 of a workspace, and if a baseline is specified in a DAV:baseline
4508 element in the request body, then there MUST NOT be another
4509 collection in that workspace whose DAV:version-controlled-
4510 configuration property identifies a version-controlled
4511 configuration for the baseline history of that baseline.
4515 (DAV:create-version-controlled-configuration): A new version-
4516 controlled configuration is created, whose DAV:baseline-
4517 controlled-collection property identifies the collection.
4519 (DAV:reference-version-controlled-configuration): The
4520 DAV:version-controlled-configuration of the collection identifies
4521 the new version-controlled configuration.
4523 (DAV:select-existing-baseline): If the request body specifies a
4524 baseline, the DAV:checked-in property of the new version-
4525 controlled configuration MUST have been set to identify this
4526 baseline. A version-controlled member of the collection will be
4527 created for each version in the baseline, where the version-
4528 controlled member will have the content and dead properties of
4529 that version, and will have the same name relative to the
4530 collection as the corresponding version-controlled resource had
4531 when the baseline was created. Any nested collections that are
4532 needed to provide the appropriate name for a version-controlled
4533 member will be created.
4538Clemm, et al. Standards Track [Page 81]
4540RFC 3253 Versioning Extensions to WebDAV March 2002
4543 (DAV:create-new-baseline): If no baseline is specified in the
4544 request body, the request MUST have created a new baseline history
4545 at a server-defined URL, and MUST have created a new baseline in
4546 that baseline history. The DAV:baseline-collection of the new
4547 baseline MUST identify a collection whose members have the same
4548 relative name and DAV:checked-in version as the version-controlled
4549 members of the request collection. The DAV:checked-in property of
4550 the new version-controlled configuration MUST identify the new
455312.6.1 Example - BASELINE-CONTROL
4557 BASELINE-CONTROL /src HTTP/1.1
4558 Host: www.webdav.org
4559 Content-Type: text/xml; charset="utf-8"
4560 Content-Length: xxxx
4562 <?xml version="1.0" encoding="utf-8" ?>
4563 <D:baseline-control xmlns:D="DAV:">
4564 <D:href>http://www.webdav.org/repo/blh/13/ver/8</D:href>
4565 </D:baseline-control>
4570 Cache-Control: no-cache
4594Clemm, et al. Standards Track [Page 82]
4596RFC 3253 Versioning Extensions to WebDAV March 2002
4599 In this example, the collection /src is placed under baseline
4600 control, and is populated with members from an existing baseline. A
4601 new version-controlled configuration (/repo/vcc/128) is created and
4602 associated with /src, and /src is initialized with version-controlled
4603 members whose DAV:checked-in versions are those selected by the
4604 DAV:baseline-collection (/repo/bc/15) of the specified baseline
4605 (/repo/blh/13/ver/8). The following diagram illustrates the
4606 resulting state on the server.
4608 +-------------------------------------+
4609 |Baseline-Controlled Collection |<------+
4611 |-------------------------------------| |
4612 |DAV:version-controlled-configuration +---+ |
4613 +-------------------------------------+ | |
4616 +-------------------------------------+ | |
4617 |Version-Controlled Configuration |<--+ |
4619 |-------------------------------------| |
4620 |DAV:baseline-controlled-collection +-------+
4621 |-------------------------------------|
4622 |DAV:checked-in +-------+
4623 +-------------------------------------+ |
4624 |DAV:version-history +---+ |
4625 +-------------------------------------+ | |
4628 +------------------------+ | |
4629 |Baseline History |<---------------+ |
4631 |------------------------+ |
4632 |DAV:version-set +----------------+ |
4633 +------------------------+ | | | | |
4636 +------------------------+ | |
4637 |Baseline |<-------+-----------+
4638 |/repo/blh/13/ver/8 |
4639 |------------------------+ +--------------+
4640 |DAV:baseline-collection +---->|Collection |
4641 +------------------------+ |/repo/bc/15 |
4650Clemm, et al. Standards Track [Page 83]
4652RFC 3253 Versioning Extensions to WebDAV March 2002
4655 In order to create new baselines of /src, /repo/vcc/128 can be
4656 checked out, new versions can be created or selected by the version-
4657 controlled members of /src, and then /repo/vcc/128 can be checked in
4658 to capture the current state of those version-controlled members.
466012.7 DAV:compare-baseline Report
4662 A DAV:compare-baseline report contains the differences between the
4663 baseline identified by the request-URL (the "request baseline") and
4664 the baseline specified in the request body (the "compare baseline").
4668 The request body MUST be a DAV:compare-baseline XML element.
4670 <!ELEMENT compare-baseline (href)>
4672 The response body for a successful request MUST be a DAV:compare-
4673 baseline-report XML element.
4675 <!ELEMENT compare-baseline-report
4676 (added-version | deleted-version | changed-version)*>
4678 A DAV:added-version element identifies a version that is the
4679 DAV:checked-in version of a member of the DAV:baseline-collection
4680 of the compare baseline, but no version in the version history of
4681 that version is the DAV:checked-in version of a member of the
4682 DAV:baseline-collection of the request baseline.
4684 <!ELEMENT added-version (href)>
4686 A DAV:deleted-version element identifies a version that is the
4687 DAV:checked-in version of a member of the DAV:baseline-collection
4688 of the request baseline, but no version in the version history of
4689 that version is the DAV:checked-in version of a member of the
4690 DAV:baseline-collection of the compare baseline.
4692 <!ELEMENT deleted-version (href)>
4694 A DAV:changed-version element identifies two different versions
4695 from the same version history that are the DAV:checked-in version
4696 of the DAV:baseline-collection of the request baseline and the
4697 compare baseline, respectively.
4699 <!ELEMENT changed-version (href, href)>
4706Clemm, et al. Standards Track [Page 84]
4708RFC 3253 Versioning Extensions to WebDAV March 2002
4713 (DAV:must-be-baseline): The DAV:href in the request body MUST
4714 identify a baseline.
4716 (DAV:baselines-from-same-history): A server MAY require that the
4717 baselines being compared be from the same baseline history.
471912.7.1 Example - DAV:compare-baseline Report
4723 REPORT /bl-his/12/bl/14 HTTP/1.1
4724 Host: repo.webdav.com
4725 Content-Type: text/xml; charset="utf-8"
4726 Content-Length: xxxx
4728 <?xml version="1.0" encoding="utf-8" ?>
4729 <D:compare-baseline xmlns:D="DAV:">
4730 <D:href>http://repo.webdav.org/bl-his/12/bl/15</D:href>
4731 </D:compare-baseline>
4736 Content-Type: text/xml; charset="utf-8"
4737 Content-Length: xxxx
4739 <?xml version="1.0" encoding="utf-8" ?>
4740 <D:compare-baseline-report xmlns:D="DAV:">
4742 <D:href>http://repo.webdav.org/his/23/ver/8</D:href>
4745 <D:href>http://repo.webdav.org/his/29/ver/12</D:href>
4746 <D:href>http://repo.webdav.org/his/29/ver/19</D:href>
4747 </D:changed-version>
4749 <D:href>http://repo.webdav.org/his/12/ver/4</D:href>
4750 </D:deleted-version>
4751 </D:compare-baseline-report>
4753 In this example, the differences between baseline 14 and baseline 15
4754 of http://repo.webdav.org/bl-his/12 are identified.
4762Clemm, et al. Standards Track [Page 85]
4764RFC 3253 Versioning Extensions to WebDAV March 2002
476712.8 Additional OPTIONS Semantics
4769 If a server supports the baseline feature, it MUST include "baseline"
4770 as a field in the DAV response header from an OPTIONS request on any
4771 resource that supports any versioning properties, reports, or
477412.9 Additional MKCOL Semantics
4776 Additional Postconditions:
4778 If a server automatically puts a newly created collection under
4779 baseline control, all postconditions for BASELINE-CONTROL apply to
478212.10 Additional COPY Semantics
4784 Additional Postconditions:
4786 If the request creates a new collection at the Destination, and a
4787 server automatically puts a newly created collection under
4788 baseline control, all postconditions for BASELINE-CONTROL apply to
479112.11 Additional CHECKOUT Semantics
4793 Additional Preconditions:
4795 (DAV:must-not-update-baseline-collection): If the request-URL
4796 identifies a member of the configuration rooted at the
4797 DAV:baseline-collection of a baseline, the request MUST fail.
479912.12 Additional CHECKIN Semantics
4801 Additional Preconditions:
4803 (DAV:no-checked-out-baseline-controlled-collection-members): If
4804 the request-URL identifies a version-controlled configuration, all
4805 version-controlled members of the DAV:baseline-controlled-
4806 collection of the version-controlled configuration MUST be
4809 (DAV:one-version-per-history-per-baseline): If the request-URL
4810 identifies a version-controlled configuration, the set of versions
4811 selected by that version-controlled configuration MUST contain at
4812 most one version from any version history, where a version is
4813 selected by a version-controlled configuration if the version is
4814 identified by the DAV:checked-in property of any member of the
4818Clemm, et al. Standards Track [Page 86]
4820RFC 3253 Versioning Extensions to WebDAV March 2002
4823 configuration rooted at the DAV:baseline-controlled collection of
4824 that version-controlled configuration, or is identified by the
4825 DAV:checked-in property of any member of the configuration rooted
4826 at the DAV:baseline-collection of any subbaseline of that
4827 version-controlled configuration.
4829 (DAV:cannot-modify-version-controlled-configuration): If the
4830 request-URL identifies a version-controlled member of a baseline-
4831 controlled collection whose version-controlled configuration is
4832 checked-in, the request MUST fail unless the DAV:auto-version
4833 property of the version-controlled configuration will
4834 automatically check out that version-controlled configuration when
4837 Additional Postconditions:
4839 (DAV:create-baseline-collection): If the request-URL identifies a
4840 version-controlled configuration, the DAV:baseline-collection of
4841 the new baseline identifies a collection whose members have the
4842 same relative name and DAV:checked-in version as the members of
4843 the DAV:baseline-controlled-collection of the version-controlled
4844 configuration at the time of the request.
4846 (DAV:modify-configuration): If the request-URL identifies a
4847 version-controlled member of a baseline-controlled collection,
4848 this is a modification to the version-controlled configuration of
4849 that baseline-controlled collection, and standard auto-versioning
485212.13 Additional UPDATE Semantics
4854 Additional Preconditions:
4856 (DAV:baseline-controlled-members-must-be-checked-in): If the
4857 request-URL identifies a version-controlled configuration, then
4858 all version-controlled members of the DAV:baseline-controlled-
4859 collection of that version-controlled configuration MUST be
4862 (DAV:must-not-update-baseline-collection): If the request-URL
4863 identifies a member of the configuration rooted at the
4864 DAV:baseline-collection of a baseline, the request MUST fail.
4866 (DAV:cannot-modify-version-controlled-configuration): If the
4867 request updates the DAV:checked-in property of any version-
4868 controlled member of a baseline-controlled collection whose
4869 version-controlled configuration is checked-in, the request MUST
4874Clemm, et al. Standards Track [Page 87]
4876RFC 3253 Versioning Extensions to WebDAV March 2002
4879 fail unless the DAV:auto-version property of the version-
4880 controlled configuration will automatically check out that
4881 version-controlled configuration when it is modified.
4883 Additional Postconditions:
4885 (DAV:set-baseline-controlled-collection-members): If the request
4886 updated the DAV:checked-in property of a version-controlled
4887 configuration, then the version-controlled members of the
4888 DAV:baseline-controlled-collection of that version-controlled
4889 configuration MUST have been updated so that they have the same
4890 relative name, content, and dead properties as the members of the
4891 DAV:baseline-collection of the baseline. In particular:
4893 - A version-controlled member for a given version history MUST
4894 have been deleted if there is no version-controlled member for
4895 that version history in the DAV:baseline-collection of the
4897 - A version-controlled member for a given version history MUST
4898 have been renamed if its name relative to the baseline-
4899 controlled collection is different from that of the version-
4900 controlled member for that version history in the
4901 DAV:baseline-collection of the baseline.
4902 - A new version-controlled member MUST have been created for each
4903 member of the DAV:baseline-collection of the baseline for which
4904 there is no corresponding version-controlled member in the
4905 baseline-controlled collection.
4906 - An UPDATE request MUST have been applied to each version-
4907 controlled member for a given version history whose
4908 DAV:checked-in version is not the same as that of the version-
4909 controlled member for that version history in the
4910 DAV:baseline-collection of the baseline.
4912 (DAV:update-subbaselines): If the request updated a version-
4913 controlled configuration whose DAV:baseline-controlled-collection
4914 contains a baseline-controlled member for one of the subbaselines
4915 of the request baseline, then the DAV:checked-in property of the
4916 version-controlled configuration of that baseline-controlled
4917 member MUST have been updated to be that subbaseline. If the
4918 request updated a version-controlled configuration whose
4919 DAV:baseline-controlled-collection is a member of a workspace that
4920 contains a baseline-controlled member for one of the subbaselines
4921 of the request baseline, then the DAV:checked-in property of the
4922 version-controlled configuration of that baseline-controlled
4923 member MUST have been updated to be that subbaseline.
4930Clemm, et al. Standards Track [Page 88]
4932RFC 3253 Versioning Extensions to WebDAV March 2002
4935 (DAV:modify-configuration): If the request updated the
4936 DAV:checked-in property of any version-controlled member of a
4937 baseline-controlled collection, and if this DAV:checked-in
4938 property differs from the DAV:checked-in property of the
4939 corresponding version-controlled member of the DAV:baseline-
4940 collection of the DAV:checked-in baseline of the DAV:version-
4941 controlled-configuration of the baseline-controlled collection,
4942 then this is a modification to that version-controlled
4943 configuration, and standard auto-versioning semantics apply.
494512.14 Additional MERGE Semantics
4947 If the merge source is a baseline, the merge target is a version-
4948 controlled configuration for the baseline history of that baseline,
4949 where the baseline-controlled collection of that version-controlled
4950 configuration is a member of the collection identified by the
4953 Additional Preconditions:
4955 (DAV:must-not-update-baseline-collection): Same semantics as
4956 UPDATE (see Section 12.13).
4958 (DAV:cannot-modify-version-controlled-configuration): Same
4959 semantics as UPDATE (see Section 12.13).
4961 Additional Postconditions:
4963 (DAV:merge-baseline): If the merge target is a version-controlled
4964 configuration whose DAV:checked-out baseline is not a descendant
4965 of the merge baseline, then the merge baseline MUST have been
4966 added to the DAV:auto-merge-set of a version-controlled
4967 configuration. The DAV:checked-in version of each member of the
4968 DAV:baseline-collection of that baseline MUST have been merged
4969 into the DAV:baseline-controlled-collection of that version-
4970 controlled configuration.
4972 (DAV:merge-subbaselines): If the merge target is a version-
4973 controlled configuration whose DAV:baseline-controlled-collection
4974 contains a baseline-controlled member for one of the subbaselines
4975 of the merge baseline, then that subbaseline MUST have been merged
4976 into the version-controlled configuration of that baseline-
4977 controlled member. If the merge target is a version-controlled
4978 configuration whose DAV:baseline-controlled-collection is a member
4979 of a workspace that contains a baseline-controlled member for one
4980 of the subbaselines of the merge baseline, then that subbaseline
4981 MUST have been merged into the version-controlled configuration of
4982 that baseline-controlled member.
4986Clemm, et al. Standards Track [Page 89]
4988RFC 3253 Versioning Extensions to WebDAV March 2002
4991 (DAV:set-baseline-controlled-collection-members): Same semantics
4992 as UPDATE (see Section 12.13).
4994 (DAV:modify-configuration): Same semantics as UPDATE (see Section
4999 An activity is a resource that selects a set of versions that are on
5000 a single "line of descent", where a line of descent is a sequence of
5001 versions connected by successor relationships. If an activity
5002 selects versions from multiple version histories, the versions
5003 selected in each version history must be on a single line of descent.
5005 A common problem that motivates the use of activities is that it is
5006 often desirable to perform several different logical changes in a
5007 single workspace, and then selectively merge a subset of those
5008 logical changes to other workspaces. An activity can be used to
5009 represent a single logical change, where an activity tracks all the
5010 resources that were modified to effect that single logical change.
5011 When a version-controlled resource is checked out, the user specifies
5012 which activity should be associated with a new version that will be
5013 created when that version-controlled resource is checked in. It is
5014 then possible to select a particular logical change for merging into
5015 another workspace, by specifying the appropriate activity in a MERGE
5018 Another common problem is that although a version-controlled resource
5019 may need to have multiple lines of descent, all work done by members
5020 of a given team must be on a single line of descent (to avoid merging
5021 between team members). An activity resource provides the mechanism
5022 for addressing this problem. When a version-controlled resource is
5023 checked out, a client can request that an existing activity be used
5024 or that a new activity be created. Activity semantics then ensure
5025 that all versions in a given version history that are associated with
5026 an activity are on a single line of descent. If all members of a
5027 team share a common activity (or sub-activities of a common
5028 activity), then all changes made by members of that team will be on a
5029 single line of descent.
5042Clemm, et al. Standards Track [Page 90]
5044RFC 3253 Versioning Extensions to WebDAV March 2002
5047 The following diagram illustrates activities. Version V5 is the
5048 latest version of foo.html selected by activity Act-2, and version V8
5049 is the latest version of bar.html selected by activity Act-2.
5051 foo.html History bar.html History
5054 Act-1| |V1 Act-1| |V6
5059 Act-1| |V2 Act-2| |V7
5064 Act-1| |V3 Act-2| |V4 Act-2| |V8
5069 Act-2| |V5 Act-3| |V9
5072 Activities appear under a variety of names in existing versioning
5073 systems. When an activity is used to capture a logical change, it is
5074 commonly called a "change set". When an activity is used to capture
5075 a line of descent, it is commonly called a "branch". When a system
5076 supports both branches and change sets, it is often useful to require
5077 that a particular change set occur on a particular branch. This
5078 relationship can be captured by making the change set activity be a
5079 "subactivity" of the branch activity.
508113.1 Activity Properties
5083 The DAV:resourcetype of an activity MUST be DAV:activity.
5085 The activity feature introduces the following REQUIRED properties for
508813.1.1 DAV:activity-version-set (computed)
5090 This property identifies each version whose DAV:activity-set property
5091 identifies this activity. Multiple versions of a single version
5092 history can be selected by an activity's DAV:activity-version-set
5098Clemm, et al. Standards Track [Page 91]
5100RFC 3253 Versioning Extensions to WebDAV March 2002
5103 property, but all DAV:activity-version-set versions from a given
5104 version history must be on a single line of descent from the root
5105 version of that version history.
5107 <!ELEMENT activity-version-set (href*)>
510913.1.2 DAV:activity-checkout-set (computed)
5111 This property identifies each checked-out resource whose
5112 DAV:activity-set identifies this activity.
5114 <!ELEMENT activity-checkout-set (href*)>
511613.1.3 DAV:subactivity-set
5118 This property identifies each activity that forms a part of the
5119 logical change being captured by this activity. An activity behaves
5120 as if its DAV:activity-version-set is extended by the DAV:activity-
5121 version-set of each activity identified in the DAV:subactivity-set.
5122 In particular, the versions in this extended set MUST be on a single
5123 line of descent, and when an activity selects a version for merging,
5124 the latest version in this extended set is the one that will be
5127 A server MAY reject attempts to modify the DAV:subactivity-set of an
5130 <!ELEMENT subactivity-set (href*)>
513213.1.4 DAV:current-workspace-set (computed)
5134 This property identifies each workspace whose DAV:current-activity-
5135 set identifies this activity.
5137 <!ELEMENT current-workspace-set (href*)>
513913.2 Additional Version Properties
5141 The activity feature introduces the following REQUIRED property for a
5154Clemm, et al. Standards Track [Page 92]
5156RFC 3253 Versioning Extensions to WebDAV March 2002
515913.2.1 DAV:activity-set
5161 This property identifies the activities that determine to which
5162 logical changes this version contributes, and on which lines of
5163 descent this version appears. A server MAY restrict the
5164 DAV:activity-set to identify a single activity. A server MAY refuse
5165 to allow the value of the DAV:activity-set property of a version to
5168 <!ELEMENT activity-set (href*)>
517013.3 Additional Checked-Out Resource Properties
5172 The activity feature introduces the following REQUIRED properties for
5173 a checked-out resource.
517513.3.1 DAV:unreserved
5177 This property of a checked-out resource indicates whether the
5178 DAV:activity-set of another checked-out resource associated with the
5179 version history of this version-controlled resource can have an
5180 activity that is in the DAV:activity-set property of this checked-out
5183 A result of the requirement that an activity must form a single line
5184 of descent through a given version history is that if multiple
5185 checked-out resources for a given version history are checked out
5186 unreserved into a single activity, only the first CHECKIN will
5187 succeed. Before another of these checked-out resources can be
5188 checked in, the user will first have to merge into that checked-out
5189 resource the latest version selected by that activity from that
5190 version history, and then modify the DAV:predecessor-set of that
5191 checked-out resource to identify that version.
5193 <!ELEMENT unreserved (#PCDATA)>
5194 PCDATA value: boolean
519613.3.2 DAV:activity-set
5198 This property of a checked-out resource determines the DAV:activity-
5199 set property of the version that results from checking in this
520213.4 Additional Workspace Properties
5204 The activity feature introduces the following REQUIRED property for a
5210Clemm, et al. Standards Track [Page 93]
5212RFC 3253 Versioning Extensions to WebDAV March 2002
521513.4.1 DAV:current-activity-set
5217 This property identifies the activities that currently are being
5218 performed in this workspace. When a member of this workspace is
5219 checked out, if no activity is specified in the checkout request, the
5220 DAV:current-activity-set will be used. This allows an activity-
5221 unaware client to update a workspace in which activity tracking is
5222 required. The DAV:current-activity-set MAY be restricted to identify
5223 at most one activity.
5225 <!ELEMENT current-activity-set (href*)>
522713.5 MKACTIVITY Method
5229 A MKACTIVITY request creates a new activity resource. A server MAY
5230 restrict activity creation to particular collections, but a client
5231 can determine the location of these collections from a DAV:activity-
5232 collection-set OPTIONS request.
5236 If a request body is included, it MUST be a DAV:mkactivity XML
5239 <!ELEMENT mkactivity ANY>
5241 If a response body for a successful request is included, it MUST
5242 be a DAV:mkactivity-response XML element.
5244 <!ELEMENT mkactivity-response ANY>
5246 The response MUST include a Cache-Control:no-cache header.
5250 (DAV:resource-must-be-null): A resource MUST NOT exist at the
5253 (DAV:activity-location-ok): The request-URL MUST identify a
5254 location where an activity can be created.
5258 (DAV:initialize-activity): A new activity exists at the request-
5259 URL. The DAV:resourcetype of the activity MUST be DAV:activity.
5266Clemm, et al. Standards Track [Page 94]
5268RFC 3253 Versioning Extensions to WebDAV March 2002
527113.5.1 Example - MKACTIVITY
5275 MKACTIVITY /act/test-23 HTTP/1.1
5276 Host: repo.webdav.org
5281 HTTP/1.1 201 Created
5282 Cache-Control: no-cache
5284 In this example, a new activity is created at
5285 http://repo.webdav.org/act/test-23.
528713.6 DAV:latest-activity-version Report
5289 The DAV:latest-activity-version report can be applied to a version
5290 history to identify the latest version that is selected from that
5291 version history by a given activity.
5295 The request body MUST be a DAV:latest-activity-version XML
5298 <!ELEMENT latest-activity-version (href)>
5300 The response body for a successful request MUST be a DAV:latest-
5301 activity-version-report XML element.
5303 <!ELEMENT latest-activity-version-report (href)>
5305 The DAV:href of the response body MUST identify the version of the
5306 given version history that is a member of the DAV:activity-
5307 version-set of the given activity and has no descendant that is a
5308 member of the DAV:activity-version-set of that activity.
5312 (DAV:must-be-activity): The DAV:href in the request body MUST
5313 identify an activity.
5322Clemm, et al. Standards Track [Page 95]
5324RFC 3253 Versioning Extensions to WebDAV March 2002
532713.7 Additional OPTIONS Semantics
5329 If the server supports the activity feature, it MUST include
5330 "activity" as a field in the DAV response header from an OPTIONS
5331 request on any resource that supports any versioning properties,
5332 reports, or methods.
5334 A DAV:activity-collection-set element MAY be included in the request
5335 body to identify collections that may contain activity resources.
5337 Additional Marshalling:
5339 If an XML request body is included, it MUST be a DAV:options XML
5342 <!ELEMENT options ANY>
5343 ANY value: A sequence of elements with at most one
5344 DAV:activity-collection-set element.
5346 If an XML response body for a successful request is included, it
5347 MUST be a DAV:options-response XML element.
5349 <!ELEMENT options-response ANY>
5350 ANY value: A sequence of elements with at most one
5351 DAV:activity-collection-set element.
5353 <!ELEMENT activity-collection-set (href*)>
5355 If DAV:activity-collection-set is included in the request body,
5356 the response body for a successful request MUST contain a
5357 DAV:activity-collection-set element identifying collections that
5358 may contain activities. An identified collection MAY be the root
5359 collection of a tree of collections, all of which may contain
5360 activities. Since different servers can control different parts
5361 of the URL namespace, different resources on the same host MAY
5362 have different DAV:activity-collection-set values. The identified
5363 collections MAY be located on different hosts from the resource.
536513.8 Additional DELETE Semantics
5367 Additional Postconditions:
5369 (DAV:delete-activity-reference): If an activity is deleted, any
5370 reference to that activity in a DAV:activity-set,
5371 DAV:subactivity-set, or DAV:current-activity-set MUST be removed.
5378Clemm, et al. Standards Track [Page 96]
5380RFC 3253 Versioning Extensions to WebDAV March 2002
538313.9 Additional MOVE Semantics
5385 Additional Postconditions:
5387 (DAV:update-checked-out-reference): If a checked-out resource is
5388 moved, any reference to that resource in a DAV:activity-checkout-
5389 set property MUST be updated to refer to the new location of that
5392 (DAV:update-activity-reference): If the request-URL identifies an
5393 activity, any reference to that activity in a DAV:activity-set,
5394 DAV:subactivity-set, or DAV:current-activity-set MUST be updated
5395 to refer to the new location of that activity.
5397 (DAV:update-workspace-reference): If the request-URL identifies a
5398 workspace, any reference to that workspace in a DAV:current-
5399 workspace-set property MUST be updated to refer to the new
5400 location of that workspace.
540213.10 Additional CHECKOUT Semantics
5404 A CHECKOUT request MAY specify the DAV:activity-set for the checked-
5407 Additional Marshalling:
5409 <!ELEMENT checkout ANY> ANY value: A sequence of elements with at
5410 most one DAV:activity-set and at most one DAV:unreserved.
5412 <!ELEMENT activity-set (href+ | new)>
5413 <!ELEMENT new EMPTY>
5414 <!ELEMENT unreserved EMPTY>
5416 Additional Preconditions:
5418 (DAV:one-checkout-per-activity-per-history): If there is a request
5419 activity set, unless DAV:unreserved is specified, another checkout
5420 from a version of that version history MUST NOT select an activity
5421 in that activity set.
5423 (DAV:linear-activity): If there is a request activity set, unless
5424 DAV:unreserved is specified, the selected version MUST be a
5425 descendant of all other versions of that version history that
5426 select that activity.
5434Clemm, et al. Standards Track [Page 97]
5436RFC 3253 Versioning Extensions to WebDAV March 2002
5439 Additional Postconditions:
5441 (DAV:initialize-activity-set): The DAV:activity-set of the
5442 checked-out resource is set as follows:
5444 - If DAV:new is specified as the DAV:activity-set in the request
5445 body, then a new activity created by the server is used.
5446 - Otherwise, if activities are specified in the request body,
5447 then those activities are used.
5448 - Otherwise, if the version-controlled resource is a member of a
5449 workspace and the DAV:current-activity-set of the workspace is
5450 set, then those activities are used.
5451 - Otherwise, the DAV:activity-set of the DAV:checked-out version
5454 (DAV:initialize-unreserved): If DAV:unreserved was specified in
5455 the request body, then the DAV:unreserved property of the
5456 checked-out resource MUST be "true".
545813.10.1 Example - CHECKOUT with an activity
5462 CHECKOUT /ws/public/foo.html HTTP/1.1
5463 Host: www.webdav.org
5464 Content-Type: text/xml; charset="utf-8"
5465 Content-Length: xxxx
5467 <?xml version="1.0" encoding="utf-8" ?>
5468 <D:checkout xmlns:D="DAV:">
5470 <D:href>http://repo.webdav.org/act/fix-bug-23</D:href>
5477 Cache-Control: no-cache
5479 In this example, the CHECKOUT is being performed in the
5480 http://repo.webdav.org/act/fix-bug-23 activity.
5490Clemm, et al. Standards Track [Page 98]
5492RFC 3253 Versioning Extensions to WebDAV March 2002
549513.11 Additional CHECKIN Semantics
5497 Additional Preconditions:
5499 (DAV:linear-activity): Any version which is in the version history
5500 of the checked-out resource and whose DAV:activity-set identifies
5501 an activity from the DAV:activity-set of the checked-out resource
5502 MUST be an ancestor of the checked-out resource.
5504 (DAV:atomic-activity-checkin): If the request-URL identifies an
5505 activity, the server MAY fail the request if any of the checked-
5506 out resources in the DAV:activity-checkout-set of either that
5507 activity or any subactivity of that activity cannot be checked in.
5509 Additional Postconditions:
5511 (DAV:initialize-activity-set): The DAV:activity-set of the new
5512 version MUST have been initialized to be the same as the
5513 DAV:activity-set of the checked-out resource.
5515 (DAV:activity-checkin): If the request-URL identified an activity,
5516 the server MUST have successfully applied the CHECKIN request to
5517 each checked-out resource in the DAV:activity-checkout-set of both
5518 that activity and any subactivity of that activity.
552013.12 Additional MERGE Semantics
5522 If the DAV:source element of the request body identifies an activity,
5523 then for each version history containing a version selected by that
5524 activity, the latest version selected by that activity is a merge
5525 source. Note that the versions selected by an activity are the
5526 versions in its DAV:activity-version-set unioned with the versions
5527 selected by the activities in its DAV:subactivity-set.
5529 Additional Marshalling:
5531 <!ELEMENT checkin-activity EMPTY>
5533 Additional Postconditions:
5535 (DAV:checkin-activity): If DAV:checkin-activity is specified in
5536 the request body, and if the DAV:source element in the request
5537 body identifies an activity, a CHECKIN request MUST have been
5538 successfully applied to that activity before the merge sources
5546Clemm, et al. Standards Track [Page 99]
5548RFC 3253 Versioning Extensions to WebDAV March 2002
555114 Version-Controlled-Collection Feature
5553 As with any versionable resource, when a collection is put under
5554 version control, a version history resource is created to contain
5555 versions for that version-controlled collection. In order to
5556 preserve standard versioning semantics (a version of a collection
5557 should not be modifiable), a collection version only records
5558 information about the version-controlled bindings of that collection.
5560 In order to cleanly separate a modification to the namespace from a
5561 modification to content or dead properties, a version of a collection
5562 has no members, but instead records in its DAV:version-controlled-
5563 binding-set property the binding name and version history resource of
5564 each version-controlled internal member of that collection. If,
5565 instead, a collection version contained bindings to other versions,
5566 creating a new version of a resource would require creating a new
5567 version of all the collection versions that contain that resource,
5568 which would cause activities to become entangled. For example,
5569 suppose a "feature-12" activity created a new version of /x/y/a.html.
5570 If a collection version contained bindings to versions of its
5571 members, a new version of /x/y would have to be created to contain
5572 the new version of /x/y/a.html, and a new version of /x would have to
5573 be created to contain the new version of /x/y. Now suppose a
5574 "bugfix-47" activity created a new version of /x/z/b.html. Again, a
5575 new version of /x/z and a new version of /x would have to be created
5576 to contain the new version of /x/y/b.html. But now it is impossible
5577 to merge just "bugfix-47" into another workspace without "feature-
5578 12", because the version of /x that contains the desired version of
5579 /x/z/b.html also contains version of /x/y/a.html created for
5580 "feature-12". If, instead, a collection version just records the
5581 binding name and version history resource of each version-controlled
5582 internal member, changing the version selected by a member of that
5583 collection would not require a new version of the collection. The
5584 new version is still in the same version history so no new collection
5585 version is required, and "feature-12" and "bugfix-47" would not
5588 In the following example, there are three version histories, named
5589 VH14, VH19, and VH24, where VH14 contains versions of a collection.
5590 The version-controlled collection /x has version V2 of version
5591 history VH14 as its DAV:checked-in version. Since V2 has recorded
5592 two version controlled bindings, one with binding name "a" to version
5593 history VH19, and the other with binding name "b" to version history
5594 VH24, /x MUST have two version-controlled bindings, one named "a" to
5595 a version-controlled resource for history VH19, and the other named
5596 "b" to a version-controlled resource for history VH24. The version-
5602Clemm, et al. Standards Track [Page 100]
5604RFC 3253 Versioning Extensions to WebDAV March 2002
5607 controlled resource /x/a currently has V4 of VH19 as its
5608 DAV:checked-in version, while /x/b has V8 of VH24 as its
5609 DAV:checked-in version.
5623 a +---+ | | |V1 | | +---+ |
5624 ---->| |checked-in=V4 | +---+ | a | | |V6 |
5625 / +---+ | | ------>| +---+ |
5626 / | | / | +---------+
5628 /x | |checked-in=V2 | | |V2 |
5629 +---+ | +---+ | VH24
5630 \ | | \ | b +---------+
5631 \ b +---+ | | ------>| +---+ |
5632 ---->| |checked-in=V8 | +---+ | | | |V7 |
5633 +---+ | | |V3 | | +---+ |
5646 For any request (e.g., DELETE, MOVE, COPY) that modifies a version-
5647 controlled binding of a checked-in version-controlled collection, the
5648 request MUST fail unless the version-controlled collection has a
5649 DAV:auto-version property that will automatically check out the
5650 version-controlled collection when it is modified.
5652 Although a collection version only records the version-controlled
5653 bindings of a collection, a version-controlled collection MAY contain
5654 both version-controlled and non-version-controlled bindings. Non-
5658Clemm, et al. Standards Track [Page 101]
5660RFC 3253 Versioning Extensions to WebDAV March 2002
5663 version-controlled bindings are not under version control, and
5664 therefore can be added or deleted without checking out the version-
5665 controlled collection.
5667 Note that a collection version captures only a defined subset of the
5668 state of a collection. In particular, a version of a collection
5669 captures its dead properties and its bindings to version-controlled
5670 resources, but not its live properties or bindings to non-version-
5671 controlled resources.
5673 When a server supports the working-resource feature, a client can
5674 check out a collection version to create a working collection.
5675 Unlike a version-controlled collection, which contains bindings to
5676 version-controlled resources and non-version-controlled resources, a
5677 working collection contains bindings to version history resources and
5678 non-version-controlled resources. In particular, a working
5679 collection is initialized to contain bindings to the version history
5680 resources specified by the DAV:version-controlled-binding-set of the
5681 checked out collection version. The members of a working collection
5682 can then be deleted or moved to another working collection. Non-
5683 version-controlled resources can be added to a working collection
5684 with methods such as PUT, COPY, and MKCOL. When a working collection
5685 is checked in, a VERSION-CONTROL request is automatically applied to
5686 every non-version-controlled member of the working collection, and
5687 each non-version-controlled member is replaced by its newly created
5688 version history. The DAV:version-controlled-binding-set of the new
5689 version resulting from checking in a working collection contains the
5690 binding name and version history URL for each member of the working
569314.1 Version-Controlled Collection Properties
5695 A version-controlled collection has all the properties of a
5696 collection and of a version-controlled resource. In addition, the
5697 version-controlled-collection feature introduces the following
5698 REQUIRED property for a version-controlled collection.
570014.1.1 DAV:eclipsed-set (computed)
5702 This property identifies the non-version-controlled internal members
5703 of the collection that currently are eclipsing a version-controlled
5704 internal member of the collection.
5706 !ELEMENT eclipsed-set (binding-name*)>
5707 <!ELEMENT binding-name (#PCDATA)>
5708 PCDATA value: URL segment
5714Clemm, et al. Standards Track [Page 102]
5716RFC 3253 Versioning Extensions to WebDAV March 2002
5719 An UPDATE or MERGE request can give a version-controlled collection a
5720 version-controlled internal member that has the same name as an
5721 existing non-version-controlled internal member. In this case, the
5722 non-version-controlled internal member takes precedence and is said
5723 to "eclipse" the new versioned-controlled internal member. If the
5724 non-version-controlled internal member is removed (e.g., by a DELETE
5725 or MOVE), the version-controlled internal member is exposed.
572714.2 Collection Version Properties
5729 A collection version has all the properties of a version. In
5730 addition, the version-controlled-collection feature introduces the
5731 following REQUIRED property for a collection version.
573314.2.1 DAV:version-controlled-binding-set (protected)
5735 This property captures the name and version-history of each version-
5736 controlled internal member of a collection.
5738 <!ELEMENT version-controlled-binding-set
5739 (version-controlled-binding*)>
5740 <!ELEMENT version-controlled-binding
5741 (binding-name, version-history)>
5742 <!ELEMENT binding-name (#PCDATA)>
5743 PCDATA value: URL segment
5744 <!ELEMENT version-history (href)>
574614.3 Additional OPTIONS Semantics
5748 If the server supports the version-controlled-collection feature, it
5749 MUST include "version-controlled-collection" as a field in the DAV
5750 response header from an OPTIONS request on any resource that supports
5751 any versioning properties, reports, or methods.
575314.4 Additional DELETE Semantics
5755 Additional Preconditions:
5757 (DAV:cannot-modify-checked-in-parent): If the request-URL
5758 identifies a version-controlled resource, the DELETE MUST fail
5759 when the collection containing the version-controlled resource is
5760 a checked-in version-controlled collection, unless DAV:auto-
5761 version semantics will automatically check out the version-
5762 controlled collection.
5770Clemm, et al. Standards Track [Page 103]
5772RFC 3253 Versioning Extensions to WebDAV March 2002
577514.5 Additional MKCOL Semantics
5777 Additional Preconditions:
5779 If the request creates a new resource that is automatically placed
5780 under version control, all preconditions for VERSION-CONTROL apply
5783 Additional Postconditions:
5785 If the new collection is automatically put under version control,
5786 all postconditions for VERSION-CONTROL apply to the request.
578814.6 Additional COPY Semantics
5790 Additional Preconditions:
5792 (DAV:cannot-copy-collection-version): If the source of the request
5793 is a collection version, the request MUST fail.
579514.7 Additional MOVE Semantics
5797 Additional Preconditions:
5799 (DAV:cannot-modify-checked-in-parent): If the source of the
5800 request is a version-controlled resource, the request MUST fail
5801 when the collection containing the source is a checked-in
5802 version-controlled collection, unless DAV:auto-version semantics
5803 will automatically check out that version-controlled collection.
5805 (DAV:cannot-modify-destination-checked-in-parent): If the source
5806 of the request is a version-controlled resource, the request MUST
5807 fail when the collection containing the destination is a checked-
5808 in version-controlled collection, unless DAV:auto-version
5809 semantics will automatically check out that version-controlled
581214.8 Additional VERSION-CONTROL Semantics
5814 Additional Preconditions:
5816 (DAV:cannot-modify-checked-in-parent): If the parent of the
5817 request-URL is a checked-in version-controlled collection, the
5818 request MUST fail unless DAV:auto-version semantics will
5819 automatically check out that version-controlled collection.
5826Clemm, et al. Standards Track [Page 104]
5828RFC 3253 Versioning Extensions to WebDAV March 2002
5831 Additional Postconditions:
5833 (DAV:new-version-controlled-collection): If the request body
5834 identified a collection version, the collection at the request-URL
5835 MUST contain a version-controlled internal member for each
5836 DAV:version-controlled-binding specified in the DAV:version-
5837 controlled-binding-set of the collection version, where the name
5838 and DAV:version-history of the internal member MUST be the
5839 DAV:binding-name and the DAV:version-history specified by the
5840 DAV:version-controlled-binding. If the internal member is a
5841 member of a workspace, and there is another member of the
5842 workspace for the same version history, those two members MUST
5843 identify the same version-controlled resource; otherwise, a
5844 VERSION-CONTROL request with a server selected version of the
5845 version history MUST have been applied to the URL for that
584814.9 Additional CHECKOUT Semantics
5850 Additional Postconditions:
5852 (DAV:initialize-version-history-bindings): If the request has been
5853 applied to a collection version, the new working collection MUST
5854 be initialized to contain a binding to each of the history
5855 resources identified in the DAV:version-controlled-binding-set of
5856 that collection version.
585814.10 Additional CHECKIN Semantics
5860 Additional Postconditions:
5862 (DAV:initialize-version-controlled-bindings): If the request-URL
5863 identified a version-controlled collection, then the DAV:version-
5864 controlled-binding-set of the new collection version MUST contain
5865 a DAV:version-controlled-binding that identifies the binding name
5866 and version history for each version-controlled binding of the
5867 version- controlled collection.
5869 (DAV:version-control-working-collection-members): If the request-
5870 URL identified a working collection, a VERSION-CONTROL request
5871 MUST have been automatically applied to every non-version-
5872 controlled member of the working collection, and each non-
5873 version-controlled member MUST have been replaced by its newly
5874 created version history. If a working collection member was a
5875 non-version-controlled collection, every member of the non-
5876 version-controlled collection MUST have been placed under version
5882Clemm, et al. Standards Track [Page 105]
5884RFC 3253 Versioning Extensions to WebDAV March 2002
5887 control before the non-version-controlled collection was placed
5888 under version control. The DAV:version-controlled-binding-set of
5889 the new collection version MUST contain a DAV:version-controlled-
5890 binding that identifies the binding name and the version history
5891 URL for each member of the working collection.
589314.11 Additional UPDATE and MERGE Semantics
5895 Additional Postconditions:
5897 (DAV:update-version-controlled-collection-members): If the request
5898 modified the DAV:checked-in version of a version-controlled
5899 collection, then the version-controlled members of that version-
5900 controlled collection MUST have been updated. In particular:
5902 - A version-controlled internal member MUST have been deleted if
5903 its version history is not identified by the DAV:version-
5904 controlled-binding-set of the new DAV:checked-in version.
5905 - A version-controlled internal member for a given version
5906 history MUST have been renamed if its binding name differs from
5907 the DAV:binding-name for that version history in the
5908 DAV:version-controlled-binding-set of the new DAV:checked-in
5910 - A new version-controlled internal member MUST have been created
5911 when a version history is identified by the DAV:version-
5912 controlled-binding-set of the DAV:checked-in version, but there
5913 was no member of the version-controlled collection for that
5914 version history. If a new version-controlled member is in a
5915 workspace that already has a version-controlled resource for
5916 that version history, then the new version-controlled member
5917 MUST be just a binding (i.e., another name for) that existing
5918 version-controlled resource. Otherwise, the content and dead
5919 properties of the new version-controlled member MUST have been
5920 initialized to be those of the version specified for that
5921 version history by the request. If no version is specified for
5922 that version history by the request, the version selected is
592515 Internationalization Considerations
5927 This specification has been designed to be compliant with the IETF
5928 Policy on Character Sets and Languages [RFC2277]. Specifically,
5929 where human-readable strings exist in the protocol, either their
5930 charset is explicitly stated, or XML mechanisms are used to specify
5931 the charset used. Additionally, these human-readable strings all
5932 have the ability to express the natural language of the string.
5938Clemm, et al. Standards Track [Page 106]
5940RFC 3253 Versioning Extensions to WebDAV March 2002
5943 Most of the human-readable strings in this protocol appear in
5944 properties, such as DAV:creator-displayname. As defined by RFC 2518,
5945 properties have their values marshaled as XML. XML has explicit
5946 provisions for character set tagging and encoding, and requires that
5947 XML processors read XML elements encoded, at minimum, using the UTF-8
5948 [RFC2279] encoding of the ISO 10646 multilingual plane. The charset
5949 parameter of the Content-Type header, together with the XML
5950 "encoding" attribute, provide charset identification information for
5951 MIME and XML processors. Proper use of the charset header with XML
5952 is described in RFC 3023. XML also provides a language tagging
5953 capability for specifying the language of the contents of a
5954 particular XML element. XML uses either IANA registered language
5955 tags (see RFC 3066) or ISO 639 language tags in the "xml:lang"
5956 attribute of an XML element to identify the language of its content
5959 DeltaV applications, since they build upon WebDAV, are subject to the
5960 internationalization requirements specified in RFC 2518, Section 16.
5961 In brief, these requirements mandate the use of XML character set
5962 tagging, character set encoding, and language tagging capabilities.
5963 Additionally, they strongly recommend reading RFC 3023 for
5964 instruction on the use of MIME media types for XML transport and the
5965 use of the charset header.
5967 Within this specification, a label is a human-readable string that is
5968 marshaled in the Label header and as XML in request entity bodies.
5969 When used in the Label header, the value of the label is URL-escaped
5970 and encoded using UTF-8.
597216 Security Considerations
5974 All of the security considerations of WebDAV discussed in RFC 2518,
5975 Section 17 also apply to WebDAV versioning. Some aspects of the
5976 versioning protocol help address security risks introduced by WebDAV,
5977 but other aspects can increase these security risks. These issues
598016.1 Auditing and Traceability
5982 WebDAV increases the ease with which a remote client can modify
5983 resources on a web site, but this also increases the risk of
5984 important information being overwritten and lost, either through user
5985 error or user maliciousness. The use of WebDAV versioning can help
5986 address this problem by guaranteeing that previous information is
5987 saved in the form of immutable versions, and therefore is easily
5988 available for retrieval or restoration. In addition, the version
5989 history provides a log of when changes were made, and by whom. When
5990 requests are appropriately authenticated, the history mechanism
5994Clemm, et al. Standards Track [Page 107]
5996RFC 3253 Versioning Extensions to WebDAV March 2002
5999 provides a clear audit trail for changes to web resources. This can
6000 often significantly improve the ability to identify the source of the
6001 security problem, and thereby help guard against it in the future.
600316.2 Increased Need for Access Control
6005 WebDAV versioning provides a variety of links between related pieces
6006 of information. This can increase the risk that authentication or
6007 authorization errors allow a client to locate sensitive information.
6008 For example, if version history is not appropriately protected by
6009 access control, a client can use the version history of a public
6010 resource to identify later versions of that resource that the user
6011 intended to keep private. This increases the need for reliable
6012 authentication and accurate authorization.
6014 A WebDAV versioning client should be designed to handle a mixture of
6015 200 (OK) and 403 (Forbidden) responses on attempts to access the
6016 properties and reports that are supported by a resource. For
6017 example, a particular user may be authorized to access the content
6018 and dead properties of a version-controlled resource, but not be
6019 authorized to access the DAV:checked-in, DAV:checked-out, or
6020 DAV:version-history properties of that resource.
602216.3 Security Through Obscurity
6024 While it is acknowledged that "obscurity" is not an effective means
6025 of security, it is often a good technique to keep honest people
6026 honest. Within this protocol, version URLs, version history URLs,
6027 and working resource URLs are generated by the server and can be
6028 properly obfuscated so as not to draw attention to them. For
6029 example, a version of "http://foobar.com/reviews/salaries.html" might
6030 be assigned a URL such as "http://foobar.com/repo/4934943".
603216.4 Denial of Service
6034 The auto-versioning mechanism provided by WebDAV can result in a
6035 large number of resources being created on the server, since each
6036 update to a resource could potentially result in the creation of a
6037 new version resource. This increases the risk of a denial of service
6038 attack that exhausts the storage capability of a server. This risk
6039 is especially significant because it can be an unintentional result
6040 of something like an aggressive auto-save feature provided by an
6041 editing client. A server can decrease this risk by using delta
6042 storage techniques to minimize the cost of additional versions, and
6043 by limiting auto-versioning to a locking client, and thereby
6044 decreasing the number of inadvertent version creations.
6050Clemm, et al. Standards Track [Page 108]
6052RFC 3253 Versioning Extensions to WebDAV March 2002
605517 IANA Considerations
6057 This document uses the namespace defined by RFC 2518 for XML
6058 elements. All other IANA considerations from RFC 2518 are also
6059 applicable to WebDAV Versioning.
606118 Intellectual Property
6063 The following notice is copied from RFC 2026, Section 10.4, and
6064 describes the position of the IETF concerning intellectual property
6065 claims made against this document.
6067 The IETF takes no position regarding the validity or scope of any
6068 intellectual property or other rights that might be claimed to
6069 pertain to the implementation or use other technology described in
6070 this document or the extent to which any license under such rights
6071 might or might not be available; neither does it represent that it
6072 has made any effort to identify any such rights. Information on the
6073 procedures of the IETF with respect to rights in standards-track and
6074 standards-related documentation can be found in BCP-11. Copies of
6075 claims of rights made available for publication and any assurances of
6076 licenses to be made available, or the result of an attempt made to
6077 obtain a general license or permission for the use of such
6078 proprietary rights by implementers or users of this specification can
6079 be obtained from the IETF Secretariat.
6081 The IETF invites any interested party to bring to its attention any
6082 copyrights, patents or patent applications, or other proprietary
6083 rights that may cover technology that may be required to practice
6084 this standard. Please address the information to the IETF Executive
6089 This protocol is the collaborative product of the authors and the
6090 rest of the DeltaV design team: Boris Bokowski, Bruce Cragun
6091 (Novell), Jim Doubek (Macromedia), David Durand (INSO), Lisa
6092 Dusseault (Xythos), Chuck Fay (FileNet), Yaron Goland, Mark Hale
6093 (Interwoven), Henry Harbury (Merant), James Hunt, Jeff McAffer (OTI),
6094 Peter Raymond (Merant), Juergen Reuter, Edgar Schwarz (Marconi), Eric
6095 Sedlar (Oracle), Bradley Sergeant, Greg Stein, and John Vasta
6096 (Rational). We would like to acknowledge the foundation laid for us
6097 by the authors of the WebDAV and HTTP protocols upon which this
6098 protocol is layered, and the invaluable feedback from the WebDAV and
6099 DeltaV working groups.
6106Clemm, et al. Standards Track [Page 109]
6108RFC 3253 Versioning Extensions to WebDAV March 2002
6113 [ISO639] ISO, "Code for the representation of names of languages",
6116 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
6117 3", BCP 9, RFC 2026, October 1996.
6119 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
6120 Requirement Levels", BCP 14, RFC 2119, March 1997.
6122 [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
6123 Languages", BCP 18, RFC 2277, January 1998.
6125 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
6126 RFC 2279, January 1998.
6128 [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
6129 Resource Identifiers (URI): Generic Syntax", RFC 2396,
6132 [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D.
6133 Jensen, "HTTP Extensions for Distributed Authoring -
6134 WEBDAV", RFC 2518, February 1999.
6136 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter,
6137 L., Leach, P. and T.Berners-Lee, "Hypertext Transfer
6138 Protocol -- HTTP/1.1", RFC 2616, June 1999.
6140 [RFC3023] Murata, M., St.Laurent, S. and D. Kohn, "XML Media Types",
6141 RFC 3023, January 2001.
6143 [RFC3066] Alvestrand, H., "Tags for the Identification of Languages",
6144 BCP 47, RFC 3066, January 2001.
6162Clemm, et al. Standards Track [Page 110]
6164RFC 3253 Versioning Extensions to WebDAV March 2002
6167Appendix A - Resource Classification
6169 This document introduces several different kinds of versioning
6170 resources, such as version-controlled resources, versions, checked-
6171 out resources, and version history resources. As clients discover
6172 resources on a server, they may find it useful to classify those
6173 resources (for example, to make UI decisions on choice of icon and
6176 Clients should classify a resource by examining the values of the
6177 DAV:supported-method-set (see Section 3.1.3) and DAV:supported-live-
6178 property-set (see Section 3.1.4) properties of that resource.
6180 The following list shows the supported live properties and methods
6181 for each kind of versioning resource. Where an optional feature
6182 introduces a new kind of versioning resource, that feature is noted
6183 in parentheses following the name of that kind of versioning
6184 resource. If a live property or method is optional for a kind of
6185 versioning resource, the feature that introduces that live property
6186 or method is noted in parentheses following the live property or
6189A.1 DeltaV-Compliant Unmapped URL (a URL that identifies no resource)
6195 - MKACTIVITY (activity)
6196 - VERSION-CONTROL (workspace)
6197 - MKWORKSPACE (workspace)
6199A.2 DeltaV-Compliant Resource
6201 Supported live properties:
6204 - DAV:creator-displayname
6205 - DAV:supported-method-set
6206 - DAV:supported-live-property-set
6207 - DAV:supported-report-set
6208 - all properties defined in WebDAV [RFC2518].
6218Clemm, et al. Standards Track [Page 111]
6220RFC 3253 Versioning Extensions to WebDAV March 2002
6226 - all methods defined in WebDAV [RFC2518]
6227 - all methods defined in HTTP/1.1 [RFC2616].
6229A.3 DeltaV-Compliant Collection
6231 Supported live properties:
6233 - all DeltaV-compliant resource properties.
6237 - BASELINE-CONTROL (baseline)
6238 - all DeltaV-compliant resource methods.
6240A.4 Versionable Resource
6242 Supported live properties:
6244 - DAV:workspace (workspace)
6245 - DAV:version-controlled-configuration (baseline)
6246 - all DeltaV-compliant resource properties.
6251 - all DeltaV-compliant resource methods.
6253A.5 Version-Controlled Resource
6255 Supported live properties:
6258 - DAV:version-history (version-history)
6259 - DAV:workspace (workspace)
6260 - DAV:version-controlled-configuration (baseline)
6261 - all DeltaV-compliant resource properties.
6267 - all DeltaV-compliant resource methods.
6274Clemm, et al. Standards Track [Page 112]
6276RFC 3253 Versioning Extensions to WebDAV March 2002
6281 Supported live properties:
6283 - DAV:predecessor-set
6287 - DAV:checkout-fork (in-place-checkout or working resource)
6288 - DAV:checkin-fork (in-place-checkout or working resource)
6289 - DAV:version-history (version-history)
6290 - DAV:label-name-set (label)
6291 - DAV:activity-set (activity)
6292 - all DeltaV-compliant resource properties.
6297 - CHECKOUT (working-resource)
6298 - all DeltaV-compliant resource methods.
6300A.7 Checked-In Version-Controlled Resource
6302 Supported live properties:
6305 - all version-controlled resource properties.
6309 - CHECKOUT (checkout-in-place)
6311 - all version-controlled resource methods.
6313A.8 Checked-Out Resource
6315 Supported live properties:
6318 - DAV:predecessor-set
6319 - DAV:checkout-fork (in-place-checkout or working resource)
6320 - DAV:checkin-fork (in-place-checkout or working resource)
6321 - DAV:merge-set (merge)
6322 - DAV:auto-merge-set (merge)
6323 - DAV:unreserved (activity)
6324 - DAV:activity-set (activity)
6330Clemm, et al. Standards Track [Page 113]
6332RFC 3253 Versioning Extensions to WebDAV March 2002
6337 - CHECKIN (checkout-in-place or working-resource)
6338 - all DeltaV-compliant resource methods.
6340A.9 Checked-Out Version-Controlled Resource (checkout-in-place)
6342 Supported live properties:
6344 - all version-controlled resource properties.
6345 - all checked-out resource properties.
6350 - all version-controlled resource methods.
6351 - all checked-out resource methods.
6353A.10 Working Resource (working-resource)
6355 Supported live properties:
6357 - all DeltaV-compliant resource properties
6358 - all checked-out resource properties
6363 - all checked-out resource methods.
6365A.11 Version History (version-history)
6367 Supported live properties:
6371 - all DeltaV-compliant resource properties.
6375 - all DeltaV-compliant resource methods.
6386Clemm, et al. Standards Track [Page 114]
6388RFC 3253 Versioning Extensions to WebDAV March 2002
6391A.12 Workspace (workspace)
6393 Supported live properties:
6395 - DAV:workspace-checkout-set
6396 - DAV:baseline-controlled-collection-set (baseline)
6397 - DAV:current-activity-set (activity)
6398 - all DeltaV-compliant collection properties.
6402 - all DeltaV-compliant collection methods.
6404A.13 Activity (activity)
6406 Supported live properties:
6408 - DAV:activity-version-set
6409 - DAV:activity-checkout-set
6410 - DAV:subactivity-set
6411 - DAV:current-workspace-set
6412 - all DeltaV-compliant resource properties.
6416 - all DeltaV-compliant resource methods.
6418A.14 Version-Controlled Collection (version-controlled-collection)
6420 Supported live properties:
6423 - all version-controlled resource properties.
6427 - all version-controlled resource methods.
6429A.15 Collection Version (version-controlled-collection)
6431 Supported live properties:
6433 - DAV:version-controlled-binding-set
6434 - all version properties.
6438 - all version methods.
6442Clemm, et al. Standards Track [Page 115]
6444RFC 3253 Versioning Extensions to WebDAV March 2002
6447A.16 Version-Controlled Configuration (baseline)
6449 Supported live properties:
6451 - DAV:baseline-controlled-collection
6452 - all version-controlled resource properties.
6456 - all version-controlled resource methods.
6458A.17 Baseline (baseline)
6460 Supported live properties:
6462 - DAV:baseline-collection
6463 - DAV:subbaseline-set
6464 - all version properties.
6468 - all version methods.
6470A.18 Checked-Out Version-Controlled Configuration (baseline)
6472 Supported live properties:
6474 - DAV:subbaseline-set
6475 - all version-controlled configuration properties.
6479 - all version-controlled configuration methods.
6498Clemm, et al. Standards Track [Page 116]
6500RFC 3253 Versioning Extensions to WebDAV March 2002
6507 20 Maguire Road, Lexington, MA 02421
6509 EMail: geoffrey.clemm@rational.com
6514 3039 Cornwallis, Research Triangle Park, NC 27709
6516 EMail: jamsden@us.ibm.com
6521 Hursley Park, Winchester, UK S021 2JN
6523 EMail: tim_ellison@uk.ibm.com
6528 One Microsoft Way, Redmond, WA 90852
6530 EMail: ckaler@microsoft.com
6534 UC Santa Cruz, Dept. of Computer Science
6535 1156 High Street, Santa Cruz, CA 95064
6537 EMail: ejw@cse.ucsc.edu
6554Clemm, et al. Standards Track [Page 117]
6556RFC 3253 Versioning Extensions to WebDAV March 2002
6559Full Copyright Statement
6561 Copyright (C) The Internet Society (2002). All Rights Reserved.
6563 This document and translations of it may be copied and furnished to
6564 others, and derivative works that comment on or otherwise explain it
6565 or assist in its implementation may be prepared, copied, published
6566 and distributed, in whole or in part, without restriction of any
6567 kind, provided that the above copyright notice and this paragraph are
6568 included on all such copies and derivative works. However, this
6569 document itself may not be modified in any way, such as by removing
6570 the copyright notice or references to the Internet Society or other
6571 Internet organizations, except as needed for the purpose of
6572 developing Internet standards in which case the procedures for
6573 copyrights defined in the Internet Standards process must be
6574 followed, or as required to translate it into languages other than
6577 The limited permissions granted above are perpetual and will not be
6578 revoked by the Internet Society or its successors or assigns.
6580 This document and the information contained herein is provided on an
6581 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
6582 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
6583 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
6584 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
6585 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
6589 Funding for the RFC Editor function is currently provided by the
6610Clemm, et al. Standards Track [Page 118]