Re: Content Sniffing impact on HTTPbis - #155

* Mark Baker wrote:
>Separately, as an editorial comment, as listed directly above, I'd
>like to see a big s/resource/resource representation/g (or just
>s/resource/representation/g as the resource is what is identified by
>the URI, not the bag-o-bits returned in an HTTP response.

When people pack their bag, they rarely arrange the items in a se-
quential order. A bag is typically a synonym for a multiset, which
is usually not ordered either. So this is not a bag of bits.

The current draft uses the term "resource" in several senses. Where
it is meant to refer to a bit stream, neither resource nor represen-
tation is appropriate; neither term makes it clear which bit stream
it referred to, e.g., whether content encodings are removed or not.
Björn Höhrmann · ·
Am Badedeich 7 · Telefon: +49(0)160/4415681 ·
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · 

Received on Tuesday, 16 June 2009 22:40:11 UTC