I think there are some generally "semantic" things that are just good practice, like using logical classnames, keeping markup and styles separate, using the right list type for the task, etc. but I completely agree with the article.

It's all about readability and, call it crazy, but I think markup and code are like poetry. Imagine trying to have universal semantics for poetry...it seems dumb, right? But general practices make sense and general types of structure are good for different things.

Code and markup should be looked at the same way. This article, to me, did a great job reminding us of that.