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

Re: HTTP 1.1 document terminology.

From: Koen Holtman <koen@win.tue.nl>
Date: Tue, 30 Apr 1996 18:43:12 +0200 (MET DST)
Message-Id: <199604301643.SAA04781@wsooti04.win.tue.nl>
To: Jim Gettys <jg@w3.org>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/396
Jim Gettys:


Your new terminology definitions look very good.  I include some minor
nitpicks below.

>A network data object or service that can be identified by a URI
>(section 7.2).  When represented electronically, a resource may be
>either a plain resource, which corresponds to only one possible
>representation, or a generic resource.

`When represented electronically' can be removed.  Better still, it
can be replaced by `At any point in time'.

>generic resource
>A resource that is a set of closely related representations of the
>same document, form, applet, etc. A generic resource is always
>identified by a URI. The individual representations may each be
>identified by a unique URI, or by the combination of the generic
>resource's URI and a variant-ID, or by the combination of the generic
>resource's URI and some "content-negotiation" mechanism.  In this
>case, other URIs may exist which identify a resource more

You probably mean `representation', not `resource', here.

Received on Tuesday, 30 April 1996 09:50:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:16 UTC