# Re: current status of URL document...

Larry Masinter (masinter@parc.xerox.com)
Thu, 30 Jun 1994 21:43:12 PDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Larry Masinter: "Re: current status of URL document..."
- Previous message: Ulrike Reiner: "habe url eingehaengt"

    To: connolly@hal.com

    In-Reply-To: connolly@hal.com's message of Thu, 30 Jun 1994 21:04:41 -0700 <94Jun30.210445pdt.2762@golden.parc.xerox.com>

    Subject: Re: current status of URL document...

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

    Message-Id: <94Jun30.214315pdt.2760@golden.parc.xerox.com>

    Date: 	Thu, 30 Jun 1994 21:43:12 PDT

I said:
>Except that what corresponds to:
> ftp://host/dir1/dir2/file
>is it:
> access-type="ftp"; site="host"; directory="dir1"; directory="dir2"; name="fi
>le"
>
>or some other syntax? I'm afraid that the two don't map all that
>easily in many cases.

and Dan Connolly replied:

> For that example, I'd say
> access-type="ftp"; site="host"; directory="dir1/dir2"; name="file"

but it was a trick question. Since ftp://host/dir1/dir2/file means
ftp host
cd dir1
cd dir2
retr file

but

access-type="ftp"; site="host"; directory="dir1/dir2"; name="file"

apparently means

ftp host
cd dir1/dir2
retr file

although it isn't really spelled out. I'm starting to think that the
problem of resolving MIME external/body with URLs primarily lies with
the MIME specification and not the URLs. In any case, there's not much
to be done to the URL document except perhaps a footnote.

- Next message: Larry Masinter: "Re: current status of URL document..."
- Previous message: Ulrike Reiner: "habe url eingehaengt"