W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Re: WORKING GROUP LAST CALL

From: David J. Fiander <davidf@worf.mks.com>
Date: Thu, 30 May 1996 23:07:56 -0400
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <19558.833512076@worf.mks.com>
These aren't, for the most part technical comments on the draft,
but editorial.

section 1.3: Terminology

How about sorting the terms alphabetically, the way other
standards do?  While separating related terms will be a pain,
looking them up will be a lot simpler.


section 1.3: Terminology: definition of proxy

Last sentence: replace "A proxy must" with "A proxy MUST"

section 5.1.1 Method

Last paragraph: figure out what's generating the message "Error!
Reference source not found.".

section 5.1.2: Request-URI

Last paragraph, before terminal "Note":  replace

	Invalid Request-URIs SHOULD be responded to with an
	appropriate status code.

with

	Proxies SHOULD respond to invalid Request-URIs with an
	appropriate status code.

unless, of course, that the original sentence should apply to
both proxies _and_ origin servers.  In that case, the sentence
should be moved up a sentence or two, so it's not buried between
to requirements on proxies, and it should still be reworded to
include an active agent.

section 8.2: Entity Transmission Requirements

third paragraph:  move the parenthetical remark "(clients
SHOULD remember ...)", which imposes a conformance requirement on
clients to the end of the bulletted list which begins the
section.  Hiding conformance statements in asides is a Bad Thing.

section 13.2.5: Disambiguating Expiration Values

Delete the second period at the end of the last sentence in the
section.

section 13.3.1: Last-modified Dates

Insert a space between "the" and "Last-modified value." at the
end of the sentence.

section 13.3.3: Weak and Strong Validators

This section states that

       	The weak comparison function SHOULD be used for simple
	(non-subrange) GET requests.  The strong comparison
	function MUST be used in all other cases.

However, section 3.11, Entity Tags, states that

	The weak comparison function MAY be used for simple
	(non-subrange) GET or HEAD requests.  The strong
	comparison function MUST be used in all other cases.

Which one is correct?

section 13.3.3: Weak and Strong Validators

This section states that "Section 13.3 gives the syntax for
entity tags."  That should be "Section 3.11 gives ...."

section 13.3.4: Rules for When to Use Entity Tags ...

The first list entry claims that servers "SHOULD send an entity
tag validator unless performance considerations support the use
of weak entity tags".  That should probably be "SHOULD send a
strong entity tag validator".

section 13.4.2: Non-modifiable Headers

The phrase "SHOULD NOT" should not be in courier font.

- David
Received on Thursday, 30 May 1996 20:12:33 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:00 EDT