Interop demo ideas

It looks like we have 5 implementations to work with for the demo.:

1) OpenOffice
2) KOffice
3) Symphony
4) lpOD (Python API)
5) ODFDOM (Java API)

So what can we show?

One way to look at interop is how ODF documents, based on the standards
they support internally, are interoperable with other systems.  For
example, the MathML in an ODF document can interop with other MathML
tools.  The RDF in ODF can interop with other tools.  We could show that
with KOffice, for example.  And the XForms support in ODF allows us to
"post" form data in a user-defined or industry-defined XML format.

And then there is the interop of the document as a whole, between
applications, like OpenOffice and KOffice.  I think this is what we most
commonly think about.  But by itself it is a bit boring.

Finally we have tooling scenarios.  Is this interop?  It is if you then
load the document in an editor, or if you start in an editor and then
operate on the document via a toolkit.

Here's a strawman for how a 90-minute interop demo might look:

1) Introduction to ODF the standard.  What it is, why it is important,
etc. (15 minutes)

2) Quick presentation/demo for each implementation.  (6 minutes per
implementation * 5 = 30 minutes)

3) ODF-RDF interop demo (5 minutes)

4) ODF-XForms interop demo (5 minutes)

5) ODF-MathML inteorp demo (5 minutes)

6) Two-app interop scenario #1 (maybe OpenOffice/KOffice) (10 minutes)

7) Two-app interop scenario #2 (maybe Symphony/ODFDOM) (10 minutes)

8) Three-app interop scenario (?????) (10 minutes)

General idea is to build up from simple scenarios to more complicated
ones.

But one problem I see is that we have no mobile or web editors.  So the
diversity of application types is rather low.  We have 3 desktop editors
and 2 toolkits.

-Rob