Mathias Bauer wrote:
> But perhaps it's too early to discuss this. We should have a look on a
> potential API without discussing wether we will use RPC or a stream
based communication.
>
> Bruce, can you help us getting a *short* description of the necessary
> APIs? Which "language" does Zotero "talk" with Word?
OK, I found it already. :-)
I had a look on the Zotero Word Integration Alpha and its VBA code. It
seems that they use SOAP to let Word talk to themselves and then use the
Word API to insert and update the fields based on what they received.
Using the same SOAP interfaces in OOo doesn't look like a problem to me.
We have developed a generic SOAP client that can integrate SOAP services
into OOo Basic in a way that they can be used in the same way as UNO
services. The WSDL of the service is used to create an object dynamical
at runtime. So integrating SOAP calls into OOo Basic is a piece of cake.
In OOo we still need the extended citation and bibliography support we
already talked about. ATM we can only insert the simple "Bibliography"
text field that is currently available. But I think that you know that,
Bruce. ;-)
I assume that e.g. KOffice can use the same SOAP calls as "the API", of
course the internal API to KWord will be different to what we find in
OOo and Word and so it doesn't matter if they used a different
technology to "talk" to their application.
So my current understanding is that we should go on with meditating
about the SOAP API of Zotero: is this API suitable for our applications,
and is it a good API for other sources - however they will implement it:
if we think about other sources for bibliographic content that are
locally installed I assume that using SOAP is not the preferred way of
integration.
In OOo I would factor out the data retrieval and make it an installable
"driver" that is integrated via a service provider API. On top of that
we have a UNO service implementing the same API as the SOAP service.
This will enable our extension to work with all sources in the same way.
source1 -----> file, RPC "drivers" ----> UNOService(1)
source2 -----> SOAP ----> SOAP Client -> Service(2)
(1),(2) have the same "interface" in Basic and be used there
interchangeable:
bibl API Text API
UNO service / SOAP service ----------> data --------> Writer
Ciao,
Mathias
--
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to "[EMAIL PROTECTED]".
I use it for the OOo lists and only rarely read other mails sent to it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
