IOML

I/O Markup Language is intended as a language for specifying any kind of interface, more or less. There are probably other languages which purport to serve the same purpose (e.g. XUL, but it remains to be seen whether these work the way I see IOML working, or can be adapted to do so.

Until I have time to look carefully at XUL and/or begin more detailed specifications for IOML, I'm collecting reasons why HTML Is Broken.

Notes

The description for hsc ("HTML Sucks Completely") sounds like it might be similar to IOML on some levels, and especially like the markup language I actually implemented for generating data-driven static pages on vbz.net: "It can be used on any HTML file and creates a new HTML file as output. In the input file, you may use an extended syntax based on HTML, which allows for things like macros, conditionals, variables, expressions etc." Vbz's language was specifically designed for pulling data from a relational database; I don't know if hsc can do this or not.