Setting up ooa with a database as back-end...

The Application Programming Interface and the OASIS Open Document Format

Setting up ooa with a database as back-end...

Postby jweinberg » Mon Oct 08, 2018 9:54 pm

The Open Document format specification: ... cification ... part1.html
is essentially based on a zipped xml file with some well-defined internal directories.

I do corpora research, so the constant zipping and unzipping in order to run queries which then blindly run in a linear, textual way, would be prohibitively expensive. Text (free language usage kind) you can not express through a DAG, but xml-ish data you certainly can. So, I was thinking of an interface that would still maintain the functional illusion of saving ODF files onto a file system, but internally that fs path would just be a pointer to a table in a database and once the data is updated the database processing takes it from there.

Does the java UNO API provide a hook into the File -> Save ... , File -> Open, ... IO operations facilitating the encapsulation of such functionality?

I don’t think that implementing such a functionality (letting users define the interface to whatever back-end they choose as part of the setup) is a big deal. This idea could be worked up into a RFE for the spec itself.
OpenOffice 2.4 on Debian
Posts: 1
Joined: Mon Oct 08, 2018 9:06 pm

Return to UNO API and ODF

Who is online

Users browsing this forum: No registered users and 3 guests