Re: Generalising inlined images

• Mail folder: WWW Talk Oct 93-present
• Next message: Dave_Raggett: "Re: looking for: WWW based reservation system"
• Previous message: Marc Andreessen: "Re: image/*, audio/*, etc.?"
• In-reply-to: Kevin Altis: "Re: Generalising inlined images"

X-Delivered: at request of secret on dxcern.cern.ch
From: Dave_Raggett <dsr@hplb.hpl.hp.com>
Message-id: <9310070953.AA03899@manuel.hpl.hp.com>
Subject: Re: Generalising inlined images
To: kevin@scic.intel.com
Date: Thu, 7 Oct 93 10:53:21 BST
Cc: www-talk@nxoc01.cern.ch
Mailer: Elm [revision: 66.36.1.1]

Kevin,

For this to work in general, browsers need a way of rendering arbitrary
MIME content types - the proliferation of these ensures this will remain
a problem until a standard OOP scheme is adopted to allow software re-use.

For this reason the inlined feature needs to be restricted to a very small
number of content types, e.g. XBM, GIF, plain text and HTML.

Including type info in the element is a bad idea - instead it should come
from the object itself.

Perhaps we should have INC just like IMG with ALIGN and SRC, but for plain
text and HTML only (for now).

Dave