RE: more bugs in the v5 spec

Thanks, we already found and fixed the 8.12.5 example.

As previously mentioned, the propfind header is no longer a header, it is
part of the body.

		Yaron

> -----Original Message-----
> From:	Jim Davis [SMTP:jdavis@parc.xerox.com]
> Sent:	Friday, January 02, 1998 4:03 PM
> To:	Yaron Goland; w3c-dist-auth@w3.org
> Subject:	RE: more bugs in the v5 spec
> 
> At 10:00 PM 12/29/97 PST, Yaron Goland wrote:
> 
> >It [Timeout header] says "1#TimeType" which means use a "," not a SP, so
> 8.13.11 is correct.
> >However 8.13.10 is wrong and has been fixed.
> 
> Aha.  I didn't pay enough attention to the meaning of sharp-sign in RFC
> 2068's Augmented BNF.  Okay, in *that* case, then the example of the
> Lock-Token header in 8.12.5 is wrong, it lacks the comma.
> 
> How come Lock-Token and Timeout require comma separation in  list items,
> but Propfind does not?  Since lock tokens are URLs, and property names are
> URLs, why not use the same syntax for lists of them?

Received on Sunday, 4 January 1998 00:16:00 UTC