This is a far from foregone conclusion. Sure, it could be encoded in
XML, and the underlying data structure more easily discerned, but
then again, reverse-engineering the Word file format is a doable
task, too. So the XML encoding makes the job easier, but you
*still* need to have an application that understands the built-in
structuring rules enough to make sense of the data.
MS Office XML file formats are helpful only insofar as they are
well-documented and parseable from an application point of view.
Without that, I can generate a nice tree from JUMBO, but
what else can I do? Not a lot...
My point in all this is to point out that *only* well-supported,
public DTDs (and maybe even sample code to parse example instances
of the data) are going to make the big changes happen. When you
and I agree on what XML spreadsheet data *looks like*, then we're
onto something.
-- Michael J. Suzio Interconnect of Ann Arbor msuzio@anecdote.com / 1-734-665-5342