From: Rich Salz <rsalz@osf.org>
To: rsalz@osf.org
Message Hash: 4db79665e4d4eec8a96ccec6d0bc79be220c9b81c660ddc112d331417b847a61
Message ID: <9509151114.AA07872@sulphur.osf.org>
Reply To: N/A
UTC Datetime: 1995-09-15 11:15:11 UTC
Raw Date: Fri, 15 Sep 95 04:15:11 PDT
From: Rich Salz <rsalz@osf.org>
Date: Fri, 15 Sep 95 04:15:11 PDT
To: rsalz@osf.org
Subject: Re: Linking = Showing = Transferring?
Message-ID: <9509151114.AA07872@sulphur.osf.org>
MIME-Version: 1.0
Content-Type: text/plain
>Another even more subtle problem is inline images, can you say that a
>page with an inline image sourced from a foreign site must obey the
>foreign jurisdiction. I would assert this is so, because the web
>surfer's *browser* imports the relevant parts of the page from
>whatever locations (and jurisdictions) they are in, and displays them
>as one page.
Inline images are not references -- they are part of the page being
retrieved.
> <img src="http://www.dcs.ex.ac.uk/~aba/obscura/rsa.gif">
>So that the image is *imported* by the *viewer*, and not supplied by
>www.obscura.
Inlined images are just a convenient way of chunking. The image is imported
by the viewer because the server, as part of the base document, told it
to do so. You might be able to fool an ignorant court, but it still
doesn't change the fact that Lance has a document that in the natural
course of operation of the Web, exports crypto. I would advise him to
edit the page so it reads
Click <A HREF="http://www.dcs.ex.ac.uk/~aba/obscura/rsa.gif">here
to see a picture of the shirt.
Heck, the very word, "inline" gives it away.
/r$
Return to September 1995
Return to “Rich Salz <rsalz@osf.org>”