- From: erik <erik@inch.com>
- Date: Mon, 06 May 1996 11:14:44 -0400
- To: Paul Prescod <papresco@calum.csclub.uwaterloo.ca>
- Cc: www-html@w3.org
Paul Prescod wrote: > > At 08:00 PM 4/25/96 -0400, Michael Seaton wrote: > >Could this be done with multipart/mixed? > > I like this idea. > > I would suggest we work from > > ftp://ftp.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-mime sgml-encap-0 > > "This document describes an encapsulation of a Standard > Generalized Markup Language (SGML) document within a MIME > message. The document may be represented in the message by > some or all of its components. The MIME message may also > include auxiliary information to be used by the recipient in > processing the encapsulated SGML. This document proposes a > new content sub-type Application/SGML-notation, and a new > header, Content-SGML-Entity." You are right....Web browsers should be multipart document readers...not just HTML readers... Nescape already does this in their MAIL viewer. IE: the primary section of the MIME document could be the HTML....(which most MIME readers will display by default) And the HTML document should be able to refer to the other MIME sections as HREF targets...So a single document can contain code and images, etc. Of course adding multisectioned documents to the HTML specification wouldn't hurt. (The more important concept is allowing true context-sensitive lexing in HTML. The parser must reconfigure itself for each new section of a document, relying on section headers or DTD's before continuing the parse. Only in this way can HTML grow and become an all-encompassing document specification...allowing people to define new languages and new uses for the Web - while maintaining document integrity.)
Received on Monday, 6 May 1996 11:12:54 UTC