o-XML link. James Carlyle introduced me to o-XML today. It looks very interesting; one of the closest things to Jelly I've seen so far. It'd actually be pretty easy to implement the o-XML spec using Jelly. [James Strachan's Radio Weblog]
Booo. XML is designed for representing data. Programming languages are designed for representing behavior. Have a look at the examples of oXML and try writing them out again in a dynamic OO language like Python or Ruby. The XML versions are massively overcomplicated and very hard to read (XML has a noisy syntax). Remember, machines have no problems reading code, it's humans you need to think about.
XPlusPlus is another offender.
You've got a point Joe. I think for traditional programming tasks like may of o-XML's examples a real programming language is much more applicable.
However for simple declarative XML and SOAP processing, like Cocoon, BPEL4WS. workflow, building, XSLT and the like, using XML so that literal XML can be embedded and new simple declarative languages can be made is cool. Its a fine line between the two. e.g. you could say that a build system like Ant or Maven should really just be a python script. Though I think most Java developers would disagree.