Another almost-reinventing-Lisp in Introducing RDFa, just messier.

You could represent HTML as a simple Lisp expressions - for example:

<a href="http://some/where" onclick="foo()">some content</a>

maps simply to the equivalent:

(a ((href "http://some/where") (onclick (foo))) "some content")

You can then view the web browser as a sort of specialized interpreter with built-in default behaviors for ‘a’ and ‘href’ nodes. CSS lets you redefine some of those default behaviors, kinda (the semantics are less than complete). You can attach addition behaviors using Javascript, kinda (again, the semantics are incomplete).

If you were well acquainted with Lisp, the programming model increasing exposed by new uses of HTML, CSS, and Javascript (as offered in RDFa) - is rather old and familiar. As a markup format for documents, arguably HTML is better suited than Lisp notation. As an underlying data model, combined usage seems to be stumbling steadily closer to Lisp.

Don’t know what to do about this, but it is amusing, kinda.