W3C home > Mailing lists > Public > www-html@w3.org > March 2005

Re: why, e.g., input/@checked="checked" ?

From: Jukka K. Korpela <jkorpela@cs.tut.fi>
Date: Sat, 26 Mar 2005 19:01:16 +0200 (EET)
To: www-html@w3.org
Cc: Robert Koberg <rob@koberg.com>
Message-ID: <Pine.GSO.4.58.0503261853450.14336@korppi.cs.tut.fi>

On Sat, 26 Mar 2005, David Dorward wrote:

> HTML was designed before XML, XSLT and XHTML were, so it didn't take
> into consideration any design implications it would cause for them.

That's correct, but in this issue, it was also designed without really
thinking in SGML terms. "Boolean attributes" (which are even called that
way in HTML specifications) don't fit into SGML philosophy, although they
were formally retrofitted into SGML formalism. It would be have been much
more SGML-like to have an attribute that takes two values, like "checked"
and "unchecked", the latter being the default, and the attribute name
being 'status' for example.

-- 
Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/
Received on Saturday, 26 March 2005 17:01:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:16:02 GMT