obvious extension of o-xml to all forms of programming, and need for import facility from existing code

o-xml is obviously transformable (xslt or special sax program) to bytecode, 
sourcecode in c/java etc or even direct to assembly language as an output 
medium.

Of course, there is a large requirement for importing existing code to o-xml.

Perhaps a diagram somewhere showing:

C++                                                                                 
Java 
C -->  import utility -->  o-xml --->xslt etc -> Java src /x86 code etc 

for those who are new to the concepts and need to be sold o-xml would be a 
good thing on the website.

One of the great things I think you can do with code in XML format is enforce 
rules such that a functional spec for a function (for extreme programming 
this would be called 'the story') is written first, followed by unit test 
cases (perhaps even parameterised ... like    20e4>x>4). Xlinks to test 
results could also be stored in the same document  (assume a versioned XML 
storage system here).
Similarily, code auditing can be enforced.

The advantages to having a functional spec (with audit points in it) would be 
that you could transform the program and obtain the functional spec as a PDF.
As well as enforcing the functional spec is updated by the same guy who is 
changing the code, at the same time as he's coding.

Commercially, I think a tie up with Rational Rose (now owned by Borland) would 
be worth contemplating. Dancing to close to Microsoft might be a good way to 
get ripped off according to the horror stories I've heard (although they 
might not be true, I simply don't know for a fact).

Jeff Davies