openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: [DISCUSSION] ODF Plugfest, September 2015 - Interop Testing
Date Sat, 01 Aug 2015 17:49:05 GMT

Comment below,
-----Original Message-----
From: Andrea Pescetti [] 
Sent: Saturday, August 1, 2015 07:29
Subject: Re: [DISCUSSION] ODF Plugfest, September 2015 (was RE: [NOMINATION] Dennis Hamilton
... )

On 01/08/2015 Dennis E. Hamilton wrote:
> I think if we create a portfolio of tests and a few slides on the
> status of AOO by mid-September, anyone could be present as an AOO
> participant.

So in terms of tests we would need, for example, ODF documents exported 
by Google Docs (or IBM Docs, or whatever claims to produce ODF) that do 
not render as expected in OpenOffice? I assume this "interoperability" 
(seeing the type of event) is meant exclusively in ODF format, right? 
I.e., nothing related to OOXML for example.

[ ... ]
   Yes, the event is strictly about ODF documents.

   Demonstrable issues among Google Docs, any of the listed products in the Market Place,
and ODF support in Microsoft Office Web Apps (not just desktop) are worthwhile.

   In general, I think thematic tests around specific features are best.  

   For example, there are differences in the implementation of ODF Digital Signatures between
Microsoft Office and Apache OpenOffice.  LibreOffice may have differences from each.  It is
important to nail this down for those in civil administration who depend on such arrangements
and for whom the Plugfest is very important.  I had started some tests in this area.  I could
probably dust them off for submission.

   Another area that has been a keen issue has to do with interchange of documents having
tracked changes.  I have a lot to say about that, but a simple test profile might be very
useful.  In this case, there is probably only interoperability among AOO and LibreOffice,
although LibreOffice 5 is reported to have changes in this area.  I don't know if those extend
to what appears in the format.  

As far as I know, the ODF TC Advanced Collaboration subcommittee is working on a complete
replacement of what is done now with ODF.  There is nothing to test for that at the moment.

   In all cases, it is not necessary to attend in order to submit tests.  It is obviously
better if there is someone there and a time block is available for performing the test and
also providing some sort of perspective on the results.  If there is to be any feedback and
follow-up, that seems necessary.  Generally, only the attendees know anything about results
and there tends not to be any after-testing report.

   It is understandable that these tests are performed discretely.  However, an "after-action"
report that reveals the state of affairs without pointing at implementations would be very

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message