Simpler for who? If we assume hypothetically for a moment that it's reasonable to allow developers to specify "custom" attributes, then it's obviously easier for them to just specify the syntax which adds the custom attributes, as opposed to having them do the work of defining a subclass and changing the TLD.
Either way you have to define a subclass and change the TLD. I guess it's a matter of taste whether it's simpler to have one attribute whose value is rendered as a block inside the opening tag or multiple attributes, each of which is handled separately.
I've always been sympathetic to the goal of enforcing the HTML standard, particularly for "internet" applications, as opposed to "intranet" applications. However, when it comes to supporting intranet applications, a more effective approach might be the pragmatic one.
Despite the fact that I've been answering some of the emails on this topic, this isn't something I have terribly strong feelings about. I think adhering to the standard is a good idea, but I don't think I'd veto changes that somehow supported "non-standard" attributes.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
