Re: Inline text/html

Arnoud Galactus Engelfriet wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> In article <Pine.LNX.3.95.960908133254.4495A-100000@ns.viet.net>,
> Benjamin Franz <snowhare@netimages.com> wrote:
> > On Sun, 8 Sep 1996, Arnoud Galactus Engelfriet wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > A bit hard to formalize, IMO. Since HTML 3.2 allows you to set document
> > > colors, how can you prevent people from setting those in an "inline"
> > > document?
> >
> > Why should you try to prevent it?
> 
> If the inlined document is inlined a la server-side included data, it
> causes interesting problems. This approach has some advantages, as I
> discussed earlier.
> 
> > Ummm....Why not use inlined opaque documents plus REL and REV to specify
> > semantic relationships between the footer/header and the main document?
> > This would avoid the 'but is it legitmate semantically' problem.
> 
> <LINK rel=header HREF="myhead.html"> ... hmmm cool. :-) If only we
> could standardize some names, then most of the frames discussion could
> go away. :-)
> 
> > > Having inline text a la GIFs would make this easy.. just draw a box
> > > of the appropriate size and render the text in that. The content-type
> > > should identify it as plain text, so the < and > should not get
> > > interpreted.
> >
> > Sounds like a job for OBJECT to me.
> 
> I thought we WERE talking about OBJECT here?


I don't think many people realize inlining HTML documents can be done
by <OBJECT>, or even <IMG>. That is, complete documents, no server-side
look-a-likes.  If one can put a gif/jpg/movie/java-thingy somewhere,
why not an HTML document?  Of course, no browser has implemented it
yet, but considering frames are implemented, inline HTML documents
with <OBJECT> shouldn't be too difficult.

It has the advantage over <LINK>, that you can place <OBJECT> anywhere,
while <LINK> will have to depend on a list of standard names.


Abigail

Received on Tuesday, 10 September 1996 06:29:46 UTC