# Re: Multipart Documents

Larry Masinter (masinter@parc.xerox.com)
Mon, 13 May 1996 04:06:07 PDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Larry Masinter: "FYI: trademark names in URLs, URNs, and email"
- Previous message: Michael Seaton: "Multipart Documents"
- In reply to: Michael Seaton: "Multipart Documents"

    To: mseaton@inforamp.net

    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

    From: Larry Masinter <masinter@parc.xerox.com>

    Message-Id: <96May13.040613pdt.2733@golden.parc.xerox.com>

    Date: Mon, 13 May 1996 04:06:07 PDT

> 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.

- Next message: Larry Masinter: "FYI: trademark names in URLs, URNs, and email"
- Previous message: Michael Seaton: "Multipart Documents"
- In reply to: Michael Seaton: "Multipart Documents"