W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 1998

RE: v6: Typos

From: Yaron Goland <yarong@microsoft.com>
Date: Sat, 24 Jan 1998 15:50:36 -0800
Message-ID: <3FF8121C9B6DD111812100805F31FC0D0113C6EB@red-msg-59.dns.microsoft.com>
To: "'Jim Davis'" <jdavis@parc.xerox.com>, w3c-dist-auth@w3.org
Cc: "Saveen Reddy (Exchange)" <saveenr@exchange.microsoft.com>
7.1.2 - Fixed.

7.1.3 - Fixed.

7.2.1 - The source of the confusion is that these status codes are meant to
be used inside of the multistatus. I have changed the title of the section
to read "Status Codes for use with Multistatus" I have also changed the "not
enough space" error to a 423. I also changed the 204 No Content response
code in 7.10.5 to 200 Success. I also changed the titles of 7.10.5 and
7.11.2 to the same as 7.2.1. I also changed 204 to 200 for 7.11.2.

7.12.8 - Good point, I have added it.

12.9.1 - Yikes, both are fixed. BTW, I want to stress how important it is
that errors like these get found. Implementers, as we have found out, tend
to rely very heavily on examples. In fact we have found more than a
comfortable number of cases where implementers will ONLY rely on the
examples and give scant attention to the surrounding text. Thus ANY error in
the examples can have very serious repercussions.

12.12.1 - Sigh.. we REALLY need to feed the examples through an XML
processor with our DTD. It would have caught those errors. Hasn't someone
already volunteered to take the DTD along with the examples and run them
through?

21 - D'oh!

	Thanks again,
			Yaron



> -----Original Message-----
> From:	Jim Davis [SMTP:jdavis@parc.xerox.com]
> Sent:	Saturday, January 24, 1998 2:03 PM
> To:	w3c-dist-auth@w3.org
> Subject:	v6: Typos
> 
> A collection of minor typos, hopefully none controversial
> 
> 7.1.2 text following the example talks about the "get-*" properties,
> should
> be "get*", and about "get-content-length".
> 
> 7.1.3 likewise in the response itself, as well as the text that follows
> 
> 7.2.1 Status Codes
> 
> does not list 207, Multistatus.  By the way, I don't understand how
> PROPPATCH can return status such as 403 or 409.  Shouldn't these be inside
> the multistatus?
> 
> Likewise for 7.10.5  and 7.11.2
> 
> 7.12.8 Status Codes.  Shouldn't 200 be included?
> 
> 12.9.1 
>  the request is missing a D: for lockdiscovery in the XML entity
> 
>  the 'depth' property is capitalized in the response, and also in the text
> that follows
> 
> 12.12.1
> 
> The Response has many capitalization errors, e.g. "Write' and 'LockEntry'
> 
> 
> 21 References.  
> 
>  missing
> 
> [Franks, et al 1997]
>        J. Franks, P. Hallam-Baker, J. Hostetler, P. Leach,
>        A. Luotonen, E. Sink, and L. Stewart.
>        "An Extension to HTTP : Digest Access Authentication"
>        RFC 2069,
>        Northwestern University, CERN, Spyglass Inc., Microsoft Corp.,
>        Netscape Communications Corp., Spyglass Inc., Open Market Inc.,
>        January 1997. ftp://nic.merit.edu/documents/rfc/rfc2069.txt
> 
Received on Saturday, 24 January 1998 18:51:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:44 GMT