Re: The range of the HTTP dereference function

# You could argue that the implied contract here is outside the scope of 
# the architecture, but at some point there is a *need* to represent a 
# given resource with a particular set of bits, if only for reification 
# so you can discuss the properties of that representation. 

HTTP uses ETag for this, specifically so that caching can be managed.

URIs weren't designed to be the basis for knowledge representation,
so the attempts to use them for such a purpose aren't very successful.

Larry
-- 
http://larry.masinter.net