Quoting Bob Jamison <rwjj@...127...>:
Just so that people have an idea what we are talking about, here is a little content.xml I made from making a little drawing with a couple of images in it, and saving as a .odg. You can see the mix of namespaces, with svg providing most of information with svg:something tags, while the main OO.o drawing objects remain as <draw:something > tags.
True, svg: is provided with their own schema, but it is -so- similar. The majority of mapping should be trivial, and the things where we fail, we can just document.
Oh, that's interesting. But like Jon says, it's not much good as a clipboard format unless 100% of whatever SVG revision we currently support can be encapsulated in it. Does it allow e.g. svg:svg ?
-mental