> > That problem is simple to fix. It is natural to want to make statements > > about resources and about representations of resources. It is necessary > > to distinguish between the two when targeting an assertion, since most > > back in 1995. It is solved for HTTP/1.1. Now we just need to find the > > corresponding syntax for it in RDF. > Roy, would you mind explaining exactly how HTTP/1.1 solved this problem? > I think that would help. One relevant scenario is the use of the Etag header in HTTP/1.1. The URL+ETag (and maybe additionally mime-type) uniquely identifies a particular representation. In practice, an http: identifier is used to identify a representation dispenser, and the combination of http: identifier with ETag is used to identify a particular "bag of bits" returned by that dispenser.Received on Tuesday, 30 July 2002 16:58:07 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 12 September 2008 07:01:52 GMT