Re: Multipart Documents
Larry Masinter <masinter@parc.xerox.com> Mon, 13 May 1996 11:37 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08940;
13 May 96 7:37 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08936;
13 May 96 7:37 EDT
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa05397;
13 May 96 7:37 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id
HAA07933 for uri-out; Mon, 13 May 1996 07:06:39 -0400
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by
services.bunyip.com (8.6.10/8.6.9) with SMTP id HAA07928 for
<uri@services.bunyip.com>; Mon, 13 May 1996 07:06:36 -0400
Received: from alpha.Xerox.COM by mocha.bunyip.com with SMTP
(5.65a/IDA-1.4.2b/CC-Guru-2b)
id AA09823 (mail destined for uri@services.bunyip.com);
Mon, 13 May 96 07:06:34 -0400
Received: from golden.parc.xerox.com ([13.1.100.139]) by alpha.xerox.com with
SMTP id <15465(5)>; Mon, 13 May 1996 04:06:22 PDT
Received: by golden.parc.xerox.com id <2733>; Mon, 13 May 1996 04:06:13 -0700
To: mseaton@inforamp.net
Cc: uri@bunyip.com
In-Reply-To: "Michael Seaton"'s message of Mon, 6 May 1996 18:29:16 -0700
<199605070523.BAA22408@mail.inforamp.net>
Subject: Re: Multipart Documents
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Larry Masinter <masinter@parc.xerox.com>
Fake-Sender: masinter@parc.xerox.com
Message-Id: <96May13.040613pdt.2733@golden.parc.xerox.com>
Date: Mon, 13 May 1996 04:06:07 PDT
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk
> Is there currently any proposal that would permit one to > refer to a file contained within a multipart document or > archive? > For instance, if the file rotor.gif were contained in the > archive avionics.tar, how would rotor.gif be referenced? > avionics.tar//rotor.gif? > avionics.tar#/rotor.gif? > avionics.tar||rotor.gif? There was a proposal at one time that named anchors (like what occurs after a #) might be defined per media type. text/html defines what #xxxxx means: look for <A NAME="xxxxx"> in the referenced object. so application/tar might define that #xxxxxxx means "look for a subpiece of this entity whose file name is xxxxxxx". The only tricky parts are dealing with the character set issues. None of this has been written up in an Internet-Draft or experimental RFC though.
- Multipart Documents Michael Seaton
- Re: Multipart Documents Larry Masinter