2 ms·
I'm so glad about this response from W3C (I do criticize the general bureaucracy of W3C though). In many aspects, I felt that the recent moves of the HTML livin
by lifthrasiir 15y ago
I'm so glad about this response from W3C (I do criticize the general bureaucracy of W3C though). In many aspects, I felt that the recent moves of the HTML living standard were much like that of XHTML2:
- Why do keep the redundant <a> element while we can add the href attribute to all elements?
- Why do keep <br> while we can generalize the line structure via <nl>? (NB: I'm not sure about the exact element name)
Is removing <time> in favor of <data> really different from these statements?
- dhx 15y agoThe problem with HTML is that it tries to simultaneously solve two completely different problems: 1) How do I provide data in a meaningful, semantic, machine-readable format? 2) How do I display data in a web browser, on a phone or in print? Do I use columns? What type of navigation options should I provide to the user in this instance? XML solves (1). XSLT/HTML (as a UI layout description format only) can solve (2). Attempts to merge the two concepts together will end in certain failure.
- petervandijck 15y agoYes, certain failure. That internet thing will never amount to anything :) There's a saying about the perfect being the enemy of something, can't remember it though.