[Bug 13240] Consider replacing <time> with <data>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13240

--- Comment #32 from Cameron Jones <cmhjones@gmail.com> 2011-08-11 13:02:13 UTC ---
(In reply to comment #28)
> But as far as elements that UAs are actually expected to do something with, I
> think that experience with the <input> element has shown that adding a generic
> element with an attribute for subtyping it into multiple subtypes (now more
> than a dozen) brings a number of hidden costs and complications. The subtyping
> essentially makes it into multiple logical abstract "elements" anyway, and the
> subtyping-by-attribute mechanism just makes it look like there's less
> complexity around it than there actually is.

It's true that there is a lot of complexity in <input> elements, and possibly
some of them shouldn't be subtypes especially when viewed in conjunction with
new form elements which are not input subtypes.

However, there is a great deal of overlap through all input elements and if
there is hidden complexity this also implies that there is a great deal of
abstraction and are incredibly powerful elements. that the complexity is hidden
just results in an interface which is easier to learn and use. 


> I think subtyping in that way is a serious design mistake and an anti-pattern
> that should not be perpetuated further -- even for an element that does nothing in UAs. We'd be better off in the long run adding nothing at all than we would
> be adding something like that.

i disagree and on the contrary i think that subtyping is probably the most
prudent mechanism for expanding the functionality of HTML without limiting it
genericity or incurring duplication.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 11 August 2011 13:02:15 UTC