Well, I'm new to this list, I'm not a member of the official WG, but if
you're going to be revising the charter, even slightly, let me make one
request. That you at least discuss changing the language to support some
minimalist way of defining what browsers do with the standards the group
designs.
I suspect there have been great flaming debates on this point, but I truly
think there needs to be a consistent implementation of some aspects of the
standard. Not much, but small things, like what to do with character set
mappings where gaps are left in the defining specs, and other things where
differences in interpretations or using loopholes in different ways leads
to browsers that don't work alike. Things like whether to display an
<isindex> tag inline or at the base of the document.
As a web user, I want things to work about the same no matter which
browser I happen to use, or which browser was a particular webmaster's
favourite.
As a page developer, I want things to be reasonably consistent, so I don't
have to test several different browsers, under several different
configurations, to see what else I need to tweak. There are too many
browsers out there for these standards *not* to have some voice over the
ultimate presentation of the documents.
******************************************************************************
* Peter K. Sheerin Technical Editor, | Work : psheerin@mfi.com *
* CADENCE Magazine & AutoCAD Tech Journal | CompuServe: 71621,3173 *
* 600 Harrison Street, San Francisco, CA | Personal : psheerin@best.com *
* *
* <URL:http://www.mfi.com/cadence/> <URL:http://www.best.com/~psheerin/> *
* <URL:http://www.mfi.com/atj/> *
******************************************************************************