Dan Dorman wrote:
[snip]
Just because I feel <headerone> or
<mysupercoolheadinglevela1abeachfrontavenue> is a better way to
specify a heading than <h1>, is it reasonable to expect a browser
maker to cater to my linguistic whim? And by extension, to anyone's
linguistic whim? Browsers don't handle any random tags, browsers work
with a previously defined subset. That's just how they work. Atom
feeds don't accept any old tags, either. OpenOffice.org documents,
though they be XML, handle only a specific set of tags. I'm sensing a
pattern.
[snip]
I'm going back to my original wishlist of yesterday:
Wouldn't it be nice if we could get browsers to interpret ^ (or
something) as meaning 'div id=' (and something else for 'class='). Then
we could have, xml style code, such as:
<^pageborder>
<^content>
blah blah
</content>
</pageborder>
MUCH more readable, and encouraging for semantic coding/markup?
:-)
--
Bob
www.gwelanmor-internet.co.uk
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
