Lists Home |
Date Index |
- From: Walter Underwood <email@example.com>
- To: "firstname.lastname@example.org" <email@example.com>, xml-dev <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org
- Date: Fri, 28 May 1999 09:37:51 -0700
At 10:01 AM 5/28/99 -0500, Paul Prescod wrote:
> [...] Consider the following URLs:
>Do they refer to the same resource? Let's try the answer both ways:
Dublin Core defines a Resource Identifier element, which might
be a good place to start, especially because libraries already
have to deal with various kinds of identity (different bindings,
"copy 2", same text from different publishers). The HTTP 1.1
entity tag is only meaningful for a single URL (at least in Draft 5),
so it is mostly useful to caches.
Also, some additonal complexities ...
Don't forget content negotiation. The content could exist
in many variants, with the entity delivered depending on
the Accept*: headers in the request:
format: HTML, XML, MS Word, PDF
language: en-US, en-GB, fr, de, jp
charset: 8859-1, UTF-8, EUC, Shift-JIS
and the URL is always the same.
Then there are dynamic pages--what is "identity" for a weather
station? The page is in some sense "the same page", but the
content depends on the temperature.
Duplicated content is a real issue. Our search engine detects
and rejects duplicates. The URL to unique document ratio is
usually between 1.5 and 2. We do this detection across web
servers, since we really only need to index one copy of an
organization's acceptable use policy or the GNU copyleft.
If a site has a CNAME, the entire site will be duplicates.
Finally, some systems ignore case in file names, and relative
URLs are resolved according to the URL you used in the GET,
so we see:
with combinatorial explosions on longer URLs. And a nightmare
for robots and caching proxies.
Walter R. Underwood
http://software.infoseek.com/cce/ (my product)
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)