RE: fragment identifiers from Joshua Allen on 2002-08-01 (www-tag@w3.org from August 2002)

From: Joshua Allen <joshuaa@microsoft.com>
Date: Thu, 1 Aug 2002 14:42:45 -0700
To: "Roy T. Fielding" <fielding@apache.org>, "Mark Baker" <distobj@acm.org>
Cc: <www-tag@w3.org>
Message-ID: <4F4182C71C1FDD4BA0937A7EB7B8B4C106028F21@red-msg-08.redmond.corp.microsoft.com>

> It solved the problem by distinguishing between resources, messages,
> and the results of method invocations.  The spec doesn't say
> "representations" because the editors couldn't agree on whether
> to call them representations or instances.  Dan did a great job of

This is a bit misleading.  The "resource" that HTTP talks about is
purely imaginary.  

HTTP only ever deals with representations, messages, the results of
method invocations.  It is fine to say that HTTP distinguishes between
those various things that it actually deals with.  But HTTP ignores the
resources, and it's a bit of a stretch to say that HTTP has any advice
to offer in this regards.

HTTP never "solved" this problem.  It simply ignored it.

Received on Thursday, 1 August 2002 17:43:18 UTC