WHATWG cannot purge existing ignored elements and properties but it can try avoiding adding new ones. Besides, I wonder if the promoter of the DFN element make it clear that he expected it to be ignored by the browser, as is the case with RDFa. Chris
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Toby A Inkster Sent: Friday, August 29, 2008 10:28 PM To: whatwg@lists.whatwg.org Subject: Re: [whatwg] RDFa statement consistency Kristof Zelechovski wrote: > The goal of the specification is to provide a set of rules that > conformant > user agents must obey out of the box, without any extensions. > Features that > are supposed to be ignored do not make good candidates for > including in the > specification, except as extensions to HTML that are explicitly > supported. The HTML 5 spec already includes the many features which browsers currently (mostly) ignore - the <meta> tag, the "type" attribute on most links and so on. The fact that HTML includes a <dfn> element doesn't mean that every browser has to have a built in dictionary for storing all the definitions people collect on the web, but the element is there for those people who want to use it. Browsers *could* do something useful with <dfn> if they liked, but none so far seem to have done so. -- Toby A Inkster <mailto:[EMAIL PROTECTED]> <http://tobyinkster.co.uk>
