WebDAV Distributed Authoring Protocol
Changes from -09 to -10 Revision
Issue ID |
Type |
Issue Description |
Reference |
RDF_NAME |
Editorial |
Discussion of RDF in section 4.2 incorrectly calls RDF the Resource Definition Framework. |
Caught by Charles Wicksteed: http://lists.w3.org/Archives/Public/w3c-dist-auth/1998AprJun/0130.html |
REFS |
Editorial |
There are two references to [Lagoze, 1996], yet this reference is not in the references section. There are also two references to [Fielding et al., 1996] which should be [RFC2068]. Section 24.4.3 references [RFC2141] yet this isn't in the references section. |
None. |
UUID_NOT_GUID |
Editorial |
The ISO RPC specification uses the term UUID, not GUID. |
None. |
XML_MIME |
Change |
XML can be transported using text/xml and application/xml MIME types. DAV applications must be able to accept either. |
Change recommended by Jim Davis: http://lists.w3.org/Archives/Public/w3c-dist-auth/1998JulSep/0072.html |
NARTEN_NITS |
Editorial |
Thomas Narten, a member of the IESG, reviewed the WebDAV draft and had several nits |
Change recommended by Thomas Narten. |
LC_DAV_PROP |
Editorial |
At the end of Section 5.2, there are two property names with lower-cased "DAV:". These should be upper case. |
Caught by Greg Stein: |
URI_URL_DEF |
Editorial |
List discussion indicated some confusion about the difference between a URI and a URL. Larry Masinter suggested a better definition for URI/URL. |
List discussion starts with this by Geoff Clemm: http://lists.w3.org/Archives/Public/w3c-dist-auth/1998OctDec/0137.html |
URI_VS_RESOURCE |
Change |
The specification was unclear about the distinction between a URI and a resource, and whether all types of resources could have multiple URIs per resource. |
Initial discussion began with this message by Larry Masinter: http://lists.w3.org/Archives/Public/w3c-dist-auth/1998JulSep/0227.html |
URI_URL_USE |
Editorial |
The use of URI and URL in the specification is imprecise. |
Larry Masinter caught this: |