Point one has been raised in a previous thread (Standalone Code Tag), where it got a somewhat mixed reception... it has merits in terms of not constituting an override of the existing <code> tag in HTML, which is good, but unless we want to go retrofit all the old nodes with them, that doesn't buy us anything (the translation would have to be left in for backward compatability). Though that retrofit woulndn't be all that hard... I'm just not sure it's worth the trouble, honestly.

Item two, however, sounds like a great idea--and if E2 has something similar already implemented, then it probably wouldn't be too much of a pain for vroom to implement, which I suspect would be something of a deal-breaker (he being elsewhere employed and all).