Re: (marks, definitions, terms, abbreviations, and variables <m>, <dfn>, <abbr>, <term>) part of my review of 3.12 Phrase elements

On Jul 20, 2007, at 2:24 AM, Robert Burns wrote:

>
>
> On Jul 20, 2007, at 1:55 AM, Thomas Broyer wrote:
>>
>> Er, aren't you the man calling for "avoiding changing the meaning of
>> HTML4 elements because it creates namespace collisions"?
>>
>> And you're proposing:
>> - adding a *required* attribute
>> - changing the definition of DFN to contain the definition rather
>> than the term (and then introducing <TERM> instead)
>
> Touché on the required attribute. That would relate to one of the  
> type 2 name collision issues (though I've tried to say that I think  
> the type 1 is so much more important than the other). On your  
> second bullet point, that is the ambiguity that HTML5 and I am  
> trying to address. The draft mostly treats <dfn> as the definition  
> and not the term (though there are places in the draft that seem to  
> reverse that).

Incidentally, the need to add two new elements to the proposal: e.g.,  
<definition> and <term> solves the problem with the added required  
attribute since we're not messing with the existing named elements at  
all (except to deprecate <dfn>).

Take care,
Rob

Received on Friday, 20 July 2007 07:30:37 UTC