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, 2004-07-08: Umbrella issue for editorial fixes/enhancements. | latest change in revision latest |
| Identifier | Type / Status | Reference and Description | Resolution / Latest Change |
|---|---|---|---|
| 1_clarify_scope |
change closed |
Reference: <http://lists.w3.org/Archives/Public/w3c-dist-auth/2004JulSep/0178.html> lisa@osafoundation.org, 2004-09-14: Clarify what's in scope and what is not. |
in revision 08: Done. |
| 7_discovery |
change closed |
Reference: <http://lists.w3.org/Archives/Public/w3c-dist-auth/2004JulSep/0174.html> lisa@osafoundation.org, 2004-09-14: Should there be a way for clients to detect whether the server supports this feature? I would think that would be better. However, if there's no way, then there should be some guidance for clients along the lines of "If the client supports this draft, the client SHOULD send data typing information for all non-string data types, without even knowing whether the server supports the feature." |
in revision 08: Clarify that sending the type information to un-extended servers is harmless, thus no in-advance discovery is needed. |
| a_remove_array_example |
change closed |
Reference: <http://lists.w3.org/Archives/Public/w3c-dist-auth/2004JulSep/0213.html> julian.reschke@greenbytes.de, 2004-09-23: Remove "array" example. |
in revision 08: Done. |
| other-method-semantics |
change closed |
julian.reschke@greenbytes.de, 2004-09-15: Define semantics for other methods such as REPORT. | in revision 08: Other methods using DAV:multistatus such as REPORT SHOULD use the same extension as defined for PROPFIND. |
| strip-flags-and-displaynames |
edit closed |
julian.reschke@greenbytes.de, 2004-08-28: Remove support for property flags and displaynames and move them into a separate spec (these will be defined in a separate document). Also remove DASL extensions. | in revision 07: Done. |
| Version | Issues |
|---|---|
| latest | |||||| |
| 09 | |||||| |
| 08 | |||||| |
| 07 | || |
| 06 | |
| 05 | |
| 04 | |
| 03 | |
| 02 | |
| 01 | |
| 00 |
Last change: 2004-09-23