I was under the impression that newer web standards emphasised the separation of content from presentation markup. This was the reason for the creation of CSS and relegating the humble table back to displaying… tabular data.
I've been an unabashed and unapologetic supporter of the web standards themselves, even if in the past my interpretations of them weren't exactly correct ;-). I'm attempting to correct this though because I see real value in everyone being on the same page on net as it were. That was a really clever and entirely unintended pun. I'm not Bill Kurtis.
What concerns me though is the removal of the
value attribute from the humble ordered list element. This attribute is vital for generating non-contiguous but ordered lists of items, or where selected items share the same value, such as this example of ranking some of the cities I grew up living in based on the amount of time I spent there:
<li value="2">Melbourne, Victoria, Australia</li>
<li value="3">Adelaide, South Australia, Australia</li>
<li value="4">Brisbane, Queensland, Australia</li>
<li value="4">Kuala Lumpur, Malaysia</li>
<li value="6">Sydney, New South Wales, Australia</li>
<li value="0">Orion’s Belt, Far Far Away!</li>
According to the W3Schools list element article, the value attribute was deprecated by the W3C for use in XHTML because you can "use styles instead". There's just one problem with this line of reasoning: The value of a list item is NOT a style attribute, it's DATA.
By removing this so called "presentation information" we're also removing an integral part of the information itself which is absolutely unacceptable.
If we were to take what they were saying as Gospel and represented these values in CSS (it is possible), then we rendered our now standards compliant document using another browser that didn't support CSS, we would be presented with a list without this data.
I urge the W3C (in my very limited capacity!) to seriously reconsider the omission of this attribute in their specifications.