Please leave your sense of logic at the door, thanks!

WHATWG Weekly: Now it’s <time> for <data>

by Anne van Kesteren in Weekly Review

Revision 6695 made HTML attribute values match in a case-sensitive manner as far as Selectors are concerned. This approach was favored over having a hardcoded list of HTML attributes whose values had to be matched case-insensitively. Revision 6701 removed selectedOptions from the input element, a vestige from the Web Forms 2.0 era. Welcome to the weekend (jetlag) edition of the WHATWG Weekly.

New element: data

The major news today is that since revision 6783 we have a new element: data. We also lost an element: time. The data element represents a piece of human readable data that is made machine readable by its required value attribute. It can either be used for Microdata or as an element to help out scripts, in similar fashion to the data-* attributes.

The reason the time element has been replaced is that its primary use has been for marking up machine-readable times and dates in Microdata vocabularies, which is a use that has been requested for many other types of data as well (currency, numbers, location). The data element addresses these use cases in a generic fashion and provides yet another hook for scripts to play with.

The same revision also removed the HTML-to-Atom conversion algorithm. Authors can use a Microdata vocabulary instead.

WebVTT update

As reported earlier Simon Pieters did some research into timestamps. He now complemented that with research into separating cues. As a result of this parsing of WebVTT was made more forgiving. Newline handling was made more predictable.

Yours truly wrote a WebVTT parser and a Live WebVTT Validator in JavaScript so you can validate your captioning files.

Other changes

There were many other changes of significance:

And even more than those, which you can look up for yourself by going through the HTML5 tracker or by following us on twitter: @WHATWG.

4 Responses to “WHATWG Weekly: Now it’s <time> for <data>”

  1. Was there a bug in W3C bugzilla leading to the change with respect to <time> and <data>?