- From: Mark Baker <mark.baker@sympatico.ca>
- Date: Fri, 12 Apr 2002 00:14:42 -0400
- To: Miles Sabin <miles@mistral.co.uk>
- Cc: www-rdf-interest@w3.org
Miles and I were talking about this offline, so I might as well take it back online. There already exists a mechanism for helping resource publishers assert the difference between a resource and its representation, Content-Location. Using the printer example, which isn't any different than any another other example in this space (such as [1]), we could identify the printer by; http://example.org/some/printer/ and then the HTML "variant representation" (my term) of that printer could be; http://example.org/some/printer/index.html This would be communicated as follows; GET http://example.org/some/printer HTTP/1.1 response; HTTP/1.1 200 Ok Content-Type: text/html Content-Location: http://example.org/some/printer/index.html [blank line] <html [...] a GET on the index.html would return; HTTP/1.1 200 Ok Content-Type: text/html [blank line] <html [...] Oh, and [1] also makes a good example for the use of Content-Location; telnet lists.w3.org HEAD http://lists.w3.org/Archives/Public/uri/2002Jan/0027 HTTP/1.1 Host: lists.w3.org HTTP/1.1 200 OK Date: Fri, 12 Apr 2002 03:55:28 GMT Server: Apache/1.3.6 (Unix) PHP/3.0.9 Content-Location: 0027.html Vary: negotiate TCN: choice Opt: "http://www.w3.org/2000/P3Pv1";ns=11 11-PolicyRef: /server-policy/p3p-20000613.xml Last-Modified: Fri, 18 Jan 2002 06:31:33 GMT ETag: "4fd650-1d93-3c47c145;3c553b38" Accept-Ranges: bytes Content-Length: 7571 Content-Type: text/html [1] http://lists.w3.org/Archives/Public/uri/2002Jan/0027 MB -- Mark Baker, Chief Science Officer, Planetfred, Inc. Ottawa, Ontario, CANADA. mbaker@planetfred.com http://www.markbaker.ca http://www.planetfred.com
Received on Friday, 12 April 2002 00:08:35 UTC