The identifier is a name for the issue (and is unique within this document).
The type of issue is one of:
The status of the issue is one of:
The reference is an indication of where the issue was first raised.
The description is a succinct overview of the issue.
The resolution describes the specification change that resolves the issue.
| Identifier | Type / Status | Reference and Description | Proposed Resolution / Latest Change |
|---|---|---|---|
| edit |
edit open |
julian.reschke@greenbytes.de, 2005-02-27: Umbrella issue for editorial changes. | latest change in revision latest |
| update-references |
change open |
2006-09-02: Keep references up-to-date. | latest change in revision latest |
| Identifier | Type / Status | Reference and Description | Resolution / Latest Change |
|---|---|---|---|
| 7_must_be_ordered_precondition |
change closed |
Reference: <http://lists.w3.org/Archives/Public/w3c-dist-auth/2006JulSep/0021.html> julian.reschke@greenbytes.de, 2006-07-31: The DAV:collection-must-be-ordered precondition as specified prevents ORDERPATCH from setting the ordering semantics on a previously unordered collection. This doesn't make sense, because it would imply that an existing unordered collection never can be turned into an ordered collection. Proposal to relax the precondition here so that it applies only to attempts to reorder a collection which isn't ordered. |
in revision latest: Done. |
| 7_safeness_and_idempotence |
edit closed |
julian.reschke@greenbytes.de, 2005-02-27: Specify safeness and idempotence of ORDERPATCH method. | in revision latest: Done. See http://lists.w3.org/Archives/Public/w3c-dist-auth/2005JanMar/0284.html. |
| Version | Issues |
|---|---|
| latest | |||| |
Last change: 2006-09-02