W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1995

Re: Comments on Byte range draft

From: Gavin Nicol <gtn@ebt.com>
Date: Sun, 12 Nov 1995 07:45:55 -0500
Message-Id: <199511121245.HAA04348@ebt-inc.ebt.com>
To: fielding@avron.ICS.UCI.EDU
Cc: masinter@parc.xerox.com, ari@netscape.com, john@math.nwu.edu, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
>   1) The Right Way
>      Treat all PDF files as a tree, containing a catalog of pages,
>      chapters, or whatever other components can be identified within
>      the PDF.  Assign each of these components a URL and make the server
>      smart enough to extract the right component.

If you treat data as trees (and I'll agree that it's "The Right Way"),
then the TEI locators provide a very flexible and powerful addressing
scheme based on occurence, typed occurence, and direct address. You
can browse the TEI guidelines at EBT's site.

I also have a problem with byte ranges as they have absolutely no
meaning for many data types (HTML being one). If one wants to *really*
do this the right way, one should have a general/extensible addressing
mechanism like that offered by HyTime (not that I am proposing it be
adopted as is).
Received on Sunday, 12 November 1995 04:46:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:15 UTC