Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol
RFC 3648

gt;
             <supported-method name="PROPPATCH" />
             <supported-method name="PUT" />
             <supported-method name="TRACE" />
             <supported-method name="UNLOCK" />
           </supported-method-set>
         </prop>
         <status>HTTP/1.1 200 OK</status>
       </propstat>
     </response>
   </multistatus>

   Note that actual responses MUST contain a complete list of supported
   live properties.

11.  Security Considerations

   This section is provided to make WebDAV implementers aware of the
   security implications of this protocol.

   All of the security considerations of HTTP/1.1 and the WebDAV
   Distributed Authoring Protocol specification also apply to this
   protocol specification.  In addition, ordered collections introduce a
   new security concern.  This issue is detailed here.

11.1.  Denial of Service and DAV:ordering-type

   There may be some risk of denial of service at sites that are
   advertised in the DAV:ordering-type property of collections.
   However, it is anticipated that widely-deployed applications will use
   hard-coded values for frequently-used ordering semantics rather than

Whitehead & Reschke         Standards Track                    [Page 23]
RFC 3648          WebDAV Ordered Collections Protocol      December 2003

   looking up the semantics at the location specified by DAV:ordering-
   type.  This risk will be further reduced if clients observe the
   recommendation of Section 5.1 that requests not be sent to the URI in
   DAV:ordering-type.

12.  Internationalization Considerations

   This specification follows the practices of [RFC2518] by encoding all
   human-readable content using [XML] and in the treatment of names.
   Consequently, this specification complies with the IETF Character Set
   Policy [RFC2277].

   WebDAV applications MUST support the character set tagging, character
   set encoding, and the language tagging functionality of the XML
   specification.  This constraint ensures that the human-readable
   content of this specification complies with [RFC2277].

   As in [RFC2518], names in this specification fall into three
   categories: names of protocol elements such as methods and headers,
   names of XML elements, and names of properties.  The naming of
   protocol elements follows the precedent of HTTP using English names
   encoded in USASCII for methods and headers.  The names of XML
   elements used in this specification are English names encoded in
   UTF-8.

   For error reporting, [RFC2518] follows the convention of HTTP/1.1
   status codes, including with each status code a short, English
   description of the code (e.g., 423 Locked).  Internationalized
   applications will ignore this message, and display an appropriate
   message in the user's language and character set.

   This specification introduces no new strings that are displayed to
   users as part of normal, error-free operation of the protocol.

   For the rationale of these decisions and advice for application
   implementers, see [RFC2518].

13.  IANA Considerations

   This document uses the namespaces defined by [RFC2518] for properties
   and XML elements.  All other IANA considerations mentioned in
   [RFC2518] also apply to this document.

Whitehead & Reschke         Standards Track                    [Page 24]
RFC 3648          WebDAV Ordered Collections Protocol      December 2003

14.  Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11.  Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.

15.  Contributors

   This document has benefited from significant contributions from Geoff
   Clemm, Jason Crawford, Jim Davis, Chuck Fay and Judith Slein.

16.  Acknowledgements

   This document has benefited from thoughtful discussion by Jim Amsden,
   Steve Carter, Tyson Chihaya, Ken Coar, Ellis Cohen, Bruce Cragun,
   Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa
   Dusseault, Roy Fielding, Yaron Goland, Fred Hitt, Alex Hopmann,
   Marcus Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Daniel
   LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Surendra
   Koduru Reddy, Max Rible, Sam Ruby, Bradley Sergeant, Nick Shelness,
   John Stracke, John Tigue, John Turner, Kevin Wiggen, and others.

Whitehead & Reschke         Standards Track                    [Page 25]
RFC 3648          WebDAV Ordered Collections Protocol      December 2003

17.  Normative References

   [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
             Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
             Languages", BCP 18, RFC 2277, January 1998.

   [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
             Resource Identifiers (URI): Generic Syntax", RFC 2396,
             August 1998.

   [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D.
             Jensen, "HTTP Extensions for Distributed Authoring --
             WEBDAV", RFC 2518, February 1999.

   [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter,
             L., Leach, P. and T. Berners-Lee, "Hypertext Transfer
             Protocol -- HTTP/1.1", RFC 2616, June 1999.

   [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C. and J.
             Whitehead, "Versioning Extensions to WebDAV (Web
             Distributed Authoring and Versioning)", RFC 3253, March
             2002.

   [XML]     Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,
             "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-
             xml, October 2000, <http://www.w3.org/TR/2000/REC-xml-
             20001006>.

Whitehead & Reschke         Standards Track                    [Page 26]
RFC 3648          WebDAV Ordered Collections Protocol      December 2003

Appendix A. Extensions to the WebDAV Document Type Definition

   <!ELEMENT orderpatch (ordering-type?, order-member*) >
   <!ELEMENT order-member (segment, position) >
   <!ELEMENT ordering-type (href) >
   <!ELEMENT position (first | last | before | after)>
   <!ELEMENT first EMPTY >
   <!ELEMENT last EMPTY >
   <!ELEMENT before segment >
   <!ELEMENT after segment >
   <!ELEMENT segment (#PCDATA)>

Index

   C
      Client-Maintained Ordering  4
      Condition Names
         DAV:collection-must-be-ordered (pre)  9
         DAV:initialize-collection-version-ordering-type (post)  20
         DAV:initialize-ordering-type (post)  21
         DAV:initialize-version-controlled-bindings-ordered (post)  20
         DAV:initialize-version-history-bindings-ordered (post)  20
         DAV:ordered-collections-supported (pre)  7
         DAV:ordering-modified (post)  13
         DAV:ordering-type-set (post)  7, 13
         DAV:position-set (post)  9
         DAV:segment-must-identify-member (pre)  9
         DAV:update-version-controlled-collection-members-ordered
             (post) 21
         DAV:update-version-ordering-type (post)  21

   D
      DAV header
         compliance class 'ordered-collections'  21
      DAV:collection-must-be-ordered precondition  9
      DAV:custom ordering type  6
      DAV:initialize-collection-version-ordering-type postcondition  20
      DAV:initialize-ordering-type postcondition  21
      DAV:initialize-version-controlled-bindings-ordered
          postcondition 20
      DAV:initialize-version-history-bindings-ordered postcondition  20
      DAV:ordered-collections-supported precondition  7
      DAV:ordering-modified postcondition  13
      DAV:ordering-type property  6
      DAV:ordering-type-set postcondition  7, 13
      DAV:position-set postcondition  9
      DAV:segment-must-identify-member precondition  9
      DAV:unordered ordering type  6

Whitehead & Reschke         Standards Track                    [Page 27]
RFC 3648          WebDAV Ordered Collections Protocol      December 2003

      DAV:update-version-controlled-collection-members-ordered
          postcondition  21
      DAV:update-version-ordering-type postcondition  21

   H
      Headers
         Ordering-Type  7
         Position  9

   M
      Methods
         ORDERPATCH  11

   O
      Ordered Collection  4
      Ordering Semantics  5
      Ordering-Type header  7
      ORDERPATCH method  11

   P
      Position header  9
      Properties
         DAV:ordering-type  6

   S
      Server-Maintained Ordering  5

   U
      Unordered Collection  4

Whitehead & Reschke         Standards Track                    [Page 28]
RFC 3648          WebDAV Ordered Collections Protocol      December 2003

Authors' Addresses

   Jim Whitehead
   UC Santa Cruz, Dept. of Computer Science
   1156 High Street
   Santa Cruz, CA  95064
   US

   EMail: ejw@cse.ucsc.edu

   Julian F. Reschke, Ed.
   greenbytes GmbH
   Salzmannstrasse 152
   Muenster, NW  48159
   Germany

   Phone: +49 251 2807760
   Fax:   +49 251 2807761
   EMail: julian.reschke@greenbytes.de
   URI:   http://greenbytes.de/tech/webdav/

Whitehead & Reschke         Standards Track                    [Page 29]
RFC 3648          WebDAV Ordered Collections Protocol      December 2003

Full Copyright Statement

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assignees.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.

Whitehead & Reschke         Standards Track                    [Page 30]