draft-ietf-webdav-ordering-protocol-09.txt   draft-ietf-webdav-ordering-protocol-10.txt 
WEBDAV Working Group J. Whitehead WEBDAV Working Group J. Whitehead
Internet-Draft U.C. Santa Cruz Internet-Draft U.C. Santa Cruz
Expires: December 19, 2003 J. Reschke, Ed. Expires: February 6, 2004 J. Reschke, Ed.
greenbytes greenbytes
June 20, 2003 August 8, 2003
WebDAV Ordered Collections Protocol WebDAV Ordered Collections Protocol
draft-ietf-webdav-ordering-protocol-09 draft-ietf-webdav-ordering-protocol-10
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 19, 2003. This Internet-Draft will expire on February 6, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This specification extends the WebDAV Distributed Authoring Protocol This specification extends the WebDAV Distributed Authoring Protocol
to support server-side ordering of collection members. Of particular to support server-side ordering of collection members. Of particular
interest are orderings that are not based on property values, and so interest are orderings that are not based on property values, and so
skipping to change at page 2, line 47 skipping to change at page 2, line 47
9.4 Additional UNCHECKOUT, UPDATE, and MERGE Semantics . . . . . 24 9.4 Additional UNCHECKOUT, UPDATE, and MERGE Semantics . . . . . 24
10. Capability Discovery . . . . . . . . . . . . . . . . . . . . 25 10. Capability Discovery . . . . . . . . . . . . . . . . . . . . 25
10.1 Example: Using OPTIONS for the Discovery of Support for 10.1 Example: Using OPTIONS for the Discovery of Support for
Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.2 Example: Using Live Properties for the Discovery of 10.2 Example: Using Live Properties for the Discovery of
Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . 26
11. Security Considerations . . . . . . . . . . . . . . . . . . 28 11. Security Considerations . . . . . . . . . . . . . . . . . . 28
11.1 Denial of Service and DAV:ordering-type . . . . . . . . . . 28 11.1 Denial of Service and DAV:ordering-type . . . . . . . . . . 28
12. Internationalization Considerations . . . . . . . . . . . . 29 12. Internationalization Considerations . . . . . . . . . . . . 29
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . 30 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . 30
14. Copyright . . . . . . . . . . . . . . . . . . . . . . . . . 31 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 31
15. Intellectual Property . . . . . . . . . . . . . . . . . . . 32 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32
16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 33 Normative References . . . . . . . . . . . . . . . . . . . . 33
17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 33
Normative References . . . . . . . . . . . . . . . . . . . . 35 A. Extensions to the WebDAV Document Type Definition . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 35 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
A. Extensions to the WebDAV Document Type Definition . . . . . 37 Intellectual Property and Copyright Statements . . . . . . . 38
B. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 38
B.1 Since draft-ietf-webdav-ordering-protocol dated December
1999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
B.2 Since draft-ietf-webdav-ordering-protocol-02 . . . . . . . . 38
B.3 Since draft-ietf-webdav-ordering-protocol-03 . . . . . . . . 38
B.4 Since draft-ietf-webdav-ordering-protocol-04 . . . . . . . . 38
B.5 Since draft-ietf-webdav-ordering-protocol-05 . . . . . . . . 39
B.6 Since draft-ietf-webdav-ordering-protocol-06 . . . . . . . . 39
B.7 Since draft-ietf-webdav-ordering-protocol-07 . . . . . . . . 39
B.8 Since draft-ietf-webdav-ordering-protocol-08 . . . . . . . . 39
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Intellectual Property and Copyright Statements . . . . . . . 42
1. Notational Conventions 1. Notational Conventions
Since this document describes a set of extensions to the WebDAV Since this document describes a set of extensions to the WebDAV
Distributed Authoring Protocol [RFC2518], itself an extension to the Distributed Authoring Protocol [RFC2518], itself an extension to the
HTTP/1.1 protocol, the augmented BNF used here to describe protocol HTTP/1.1 protocol, the augmented BNF used here to describe protocol
elements is exactly the same as described in Section 2.1 of HTTP elements is exactly the same as described in Section 2.1 of HTTP
[RFC2616]. Since this augmented BNF uses the basic production rules [RFC2616]. Since this augmented BNF uses the basic production rules
provided in Section 2.2 of HTTP, these rules apply to this document provided in Section 2.2 of HTTP, these rules apply to this document
as well. as well.
skipping to change at page 6, line 32 skipping to change at page 6, line 32
An ordering of collection members that is maintained on the server An ordering of collection members that is maintained on the server
based on client requests specifying the position of each based on client requests specifying the position of each
collection member in the ordering collection member in the ordering
Server-Maintained Ordering Server-Maintained Ordering
An ordering of collection members that is maintained automatically An ordering of collection members that is maintained automatically
by the server, based on a client's choice of ordering semantics by the server, based on a client's choice of ordering semantics
Ordering Semantics
In general, ordering semantics are the set of structures or
meanings applied to the ordering of the member of a specific
collection. Within this document, "ordering semantics" refers
specifically to the structure specified in the DAV:ordering-type
property. See Section 4.1.1 for more information on
DAV:ordering-type.
This document uses the terms "precondition", "postcondition" and This document uses the terms "precondition", "postcondition" and
"protected property" as defined in [RFC3253]. Servers MUST report "protected property" as defined in [RFC3253]. Servers MUST report
pre-/postcondition failures as described in section 1.6 of this pre-/postcondition failures as described in section 1.6 of this
document. document.
4. Overview of Ordered Collections 4. Overview of Ordered Collections
If a collection is unordered, the client cannot depend on the If a collection is unordered, the client cannot depend on the
repeatability of the ordering of results from a PROPFIND request. By repeatability of the ordering of results from a PROPFIND request. By
specifying an ordering for a collection, a client requires the server specifying an ordering for a collection, a client requires the server
skipping to change at page 31, line 5 skipping to change at page 31, line 5
For rationales for these decisions and advice for application For rationales for these decisions and advice for application
implementors, see [RFC2518]. implementors, see [RFC2518].
13. IANA Considerations 13. IANA Considerations
This document uses the namespaces defined by [RFC2518] for properties This document uses the namespaces defined by [RFC2518] for properties
and XML elements. All other IANA considerations mentioned in and XML elements. All other IANA considerations mentioned in
[RFC2518] also apply to this document. [RFC2518] also apply to this document.
14. Copyright 14. Contributors
To be supplied by the RFC Editor.
15. Intellectual Property
To be supplied by the RFC Editor.
16. Contributors
This document has benefited from significant contributions from Geoff This document has benefited from significant contributions from Geoff
Clemm, Jason Crawford, Jim Davis, Chuck Fay and Judith Slein. Clemm, Jason Crawford, Jim Davis, Chuck Fay and Judith Slein.
17. Acknowledgements 15. Acknowledgements
This document has benefited from thoughtful discussion by Jim Amsden, This document has benefited from thoughtful discussion by Jim Amsden,
Steve Carter, Tyson Chihaya, Ken Coar, Ellis Cohen, Bruce Cragun, Steve Carter, Tyson Chihaya, Ken Coar, Ellis Cohen, Bruce Cragun,
Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa
Dusseault, Roy Fielding, Yaron Goland, Fred Hitt, Alex Hopmann, Dusseault, Roy Fielding, Yaron Goland, Fred Hitt, Alex Hopmann,
Marcus Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Daniel Marcus Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Daniel
LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Surendra LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Surendra
Koduru Reddy, Max Rible, Sam Ruby, Bradley Sergeant, Nick Shelness, Koduru Reddy, Max Rible, Sam Ruby, Bradley Sergeant, Nick Shelness,
John Stracke, John Tigue, John Turner, Kevin Wiggen, and others. John Stracke, John Tigue, John Turner, Kevin Wiggen, and others.
skipping to change at page 38, line 5 skipping to change at page 36, line 5
<!ELEMENT orderpatch (ordering-type?, order-member*) > <!ELEMENT orderpatch (ordering-type?, order-member*) >
<!ELEMENT order-member (segment, position) > <!ELEMENT order-member (segment, position) >
<!ELEMENT ordering-type (href) > <!ELEMENT ordering-type (href) >
<!ELEMENT position (first | last | before | after)> <!ELEMENT position (first | last | before | after)>
<!ELEMENT first EMPTY > <!ELEMENT first EMPTY >
<!ELEMENT last EMPTY > <!ELEMENT last EMPTY >
<!ELEMENT before segment > <!ELEMENT before segment >
<!ELEMENT after segment > <!ELEMENT after segment >
<!ELEMENT segment (#PCDATA)> <!ELEMENT segment (#PCDATA)>
Appendix B. Change Log
B.1 Since draft-ietf-webdav-ordering-protocol dated December 1999
Updated contact information for all previous authors.
Specify charset when using text/xml media type.
Made sure artwork fits into 72 columns.
Removed "Public" header from OPTIONS example.
Added Julian Reschke to list of authors.
Fixed broken XML in PROPFIND example and added DAV:orderingtype to
list of requested properties.
Added support for DAV:supported-live-property-set and
DAV:supported-method-set as mandatory features.
B.2 Since draft-ietf-webdav-ordering-protocol-02
Updated change log to refer to expired draft version as "December
1999" version.
Started rewrite marshalling in RFC3253-style and added precondition
and postcondition definitions.
On his request, removed Geoff Clemm's name from the author list
(moved to Acknowledgments).
Renamed "References" to "Normative References".
Removed reference to "MKREF" method.
B.3 Since draft-ietf-webdav-ordering-protocol-03
Added a set of issues regarding marshalling.
Changed host names to use proper "example" domain names (no change
tracking). Fixed host/destination header conflicts. Fixed "allow"
header (multiline). Removed irrelevant response headers. Abbreviated
some URIs (no change tracking).
Removed Jim Davis and Chuck Fay from the author list (and added them
to the Acknowledgements section).
Updated section on setting the position when adding new members,
removed old section on Position header.
Started work on Index section.
Changed structure for section 7 (no change tracking).
Removed header and XML elements section (contents moved to other
sections).
Started new section on relation to versioned collections as per
RFC3253.
Do not return 424's for in ORDERPATCH multistatus (it's atomic
anyway).
B.4 Since draft-ietf-webdav-ordering-protocol-04
Added proper reference to definition of "Coded-URL".
Closed issue ordering-type-values (content model simplified and XML
element / DAV property renamed) and updated examples.
Renamed precondition DAV:orderingtype-set to DAV:ordering-type-set
(no change tracking).
Closed issue ordered-header-name (header name changed to
"ordering-type", contents matches live property).
Closed issue ordermember-format (now takes segment instead of href).
Renamed compliance class to "ordered-collections" for consistency
with newer specs, and to allow detection of compliance to final
version of spec.
Updated reference to XML spec to 1.0, 2nd edition.
B.5 Since draft-ietf-webdav-ordering-protocol-05
Typos fixed.
Renamed DAV:ordermember to DAV:order-member.
Made RFC3253-compatible pre/postcondition handling a MUST
requirement.
Reference definition of "protected property" from RFC3253.
Added explanation of role of DTD fragments to Notation section.
Clarified semantics for operations on versioned collections and
collection versions.
B.6 Since draft-ietf-webdav-ordering-protocol-06
Added atomicity statement for ORDERPATCH method.
B.7 Since draft-ietf-webdav-ordering-protocol-07
Added issues "4.1-DELETE-behaviour", "6.1-safe-update",
"6.1-when-are-members-added" and
"9.4-UPDATE-non-version-controlled-members" and resolved them. Added
new "contributors" section, and mention original authors such as
Judith Slein there.
B.8 Since draft-ietf-webdav-ordering-protocol-08
Typos fixed. Added and resolved issues
"6-position-preserving-rename",
"7-clarify-positions-for-not-explicitly-mentioned-members",
"7.1-surprising-ordering-type-in-DAV-ns" and
"8-order-for-unordered-subcollections".
Index Index
C C
Client-Maintained Ordering 6 Client-Maintained Ordering 6
D D
DAV:collection-must-be-ordered precondition 12 DAV:collection-must-be-ordered precondition 12
DAV:custom ordering type 8 DAV:custom ordering type 8
DAV:initialize-collection-version-ordering-type 23 DAV:initialize-collection-version-ordering-type 23
DAV:initialize-ordering-type 24 DAV:initialize-ordering-type 24
skipping to change at page 40, line 33 skipping to change at page 36, line 33
DAV:unordered ordering type 8 DAV:unordered ordering type 8
DAV:update-version-controlled-collection-members-ordered 24 DAV:update-version-controlled-collection-members-ordered 24
DAV:update-version-ordering-type 24 DAV:update-version-ordering-type 24
H H
Headers Headers
Ordering-Type 9 Ordering-Type 9
O O
Ordered Collection 6 Ordered Collection 6
Ordering Semantics 6
Ordering-Type header 9 Ordering-Type header 9
ORDERPATCH method 14 ORDERPATCH method 14
P P
Postconditions Postconditions
DAV:initialize-collection-version-ordering-type 23 DAV:initialize-collection-version-ordering-type 23
DAV:initialize-ordering-type 24 DAV:initialize-ordering-type 24
DAV:initialize-version-controlled-bindings-ordered 23 DAV:initialize-version-controlled-bindings-ordered 23
DAV:initialize-version-history-bindings-ordered 24 DAV:initialize-version-history-bindings-ordered 24
DAV:ordering-modified 15 DAV:ordering-modified 15
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/