Re: draft-ietf-html-table...

Lou Montulli (
Fri, 4 Aug 95 00:32:04 EDT

In article <> Gavin Nicol <>
> >Yes, if blink is useful, as many people think it is, then it should be
> >supported somehow. Who are we to say that blinking text is completely
> >evil and should never be allowed? Others feel the same way about
> >images as blink, should they be allowed to outlaw images?
> It's not the functionality, it's the implementation. Adding a <BLINK>
> element was *not* the way to do it. Even a BLINK attibute on the <EM>
> tag would have been better...

I agree completely and shoulder all the blame. If you are familiar
with the history of <BLINK> you know that I didn't intend it as
a serious tag, but as soon as it got out, it was being used all over
the place and our users didn't want us to take it out. If the
new standard had <EM style=blink> or something similar users would
start using that and stop using <BLINK>.

> >Because it is in wide use it should be seriously considered for it's
> >merit. While considering it's merit you should try to understand the
> >point of view and intensions of the people using it. It is definatly
> >a style attribute, but does it belong in HTML or in a style sheet.
> >Opinions vary...
> They vary upon whether you think your *information* is valuable, and
> long-lived, or whether it's just a throw away. Divorcing structure
> from presentation gives you the best of both worlds, at the cost of
> some complexity.
> Ask yourself this question next time: would I give a database a field
> with this name, and semantics? In the answer is negative, do *not* add
> it to your list of extended tags. Another easy way is to see if the
> word is a noun.

HTML is alot more than a database language. It is the primary presentation
language for the web. It therefore needs to contain at least some formatting
information. Combining structure and presentation isn't always bad,
especially when your primary purpose is presentation.


Lou Montulli       
       Netscape Communications Corp.