what *I* would do with Wilbur.

Charles Peyton Taylor (CTaylor@wposmtp.nps.navy.mil)
Thu, 09 May 1996 12:09:29 -0800


Message-Id: <s191e08e.060@wposmtp.nps.navy.mil>
Date: Thu, 09 May 1996 12:09:29 -0800
From: Charles Peyton Taylor <CTaylor@wposmtp.nps.navy.mil>
To: www-html@w3.org
Subject:  what *I* would do with Wilbur.

These are just suggestions dealing with Wilbur, 
and is not meant to be critical or whatever.

1) Add the class attribute It doesn't hurt
anything, it's optional, it doesn't have 
to be rendered or anything by browsers 
not capable of style.

2) Add the <acronym> element. Again, it doesn't
have to be rendered by GUI browsers, but it 
would improve HTML-to-voice translations.
(Ie. "NPS" wouldn't be pronouced "nips")

3) Add <Span>  This allows us to experiment
with styles.

4) Make <center> deprecated.

5) Add Underline. Practically everyone supports it now 
except Netscape (I just double-checked MSIE and mosaic,
and they support it) Saying that you can't do it because
links are often presented as being underlined ignores
a) that they are also often presented in different colors 
and b) that different browser display links in different 
ways.  
Underline wouldn't be necessary if Styles and <span>
were implemented, but they're not.


These would make me satisfied with wilbur.  It would
document existing pratices, and allow room for growth.

I would be *happy* with wilbur if someone could 
add the <table> spec. as defined at 
http://www.w3.org/hypertext/WWW/TR/WD-tables-960123.html ,
possibly <object> (although <object> looks pretty
new) and possibly <ul plain>.

C  h a r l e s    P e y t o n   T a y l o r        
ctaylor@nps.navy.mil

The opinions and views expressed       ##  even though we're on
our own,

are my own and do not reflect          ##        we are never all
alone,

Those of the Naval PostGraduate School ##  when we are singing,
singing.

                   http://vislab-www.nps.navy.mil/%7ectaylor/