Two ODF Toolkit releases in a row!

ODF is the Open Document Format, the native format used by LibreOffice (and supported by many other apps too). Then there’s the ODF Toolkit, a set of Java modules that allow programmatic creation, scanning and manipulation of ODF files. Svante Schubert writes with some updates:

We are happy to announce that there have been recently two ODF Toolkit releases in a row. These were our first releases at The Document Foundation (TDF), after the migration of the project to TDF in 2019:

  • With the 0.9.0 release, we have our last JDK 8 release (due to a switch of the Java Doc Taglet API we are using). After this release, we dropped the so-called “Simple API” (which was once forked from our ODFDOM doc Java Package by IBM, but not merged back, leaving lots of duplicated code that was unable to embrace our new change API). And the XSLT Runner Ant plugin will be removed in a future release, as we are no longer using Ant but Maven (to avoid maintenance of untested functionality).
  • With the 0.10.0 release, we support the next JDK 11 LTS version and our new change API that was implemented by myself for Open-XChange’s web office OX Documents – thanks to them, especially Malte Timmermann and Rafael Laguna for keeping the Apache License 2. Unfortunately, OX forked before I started there and it took me several months – and some sponsorship from a PrototypeFund project – to merge manually every file and enable all tests again (which some OX colleagues had disabled as they took too long…). (Please check out the PrototypeFund: Any German taxpayer may apply with an open-source project/idea!).

I would like to thank also all those numerous folks assisting us to make this work – especially recently in pushing this forward!

Especially, I would like to congratulate Michael Stahl for officially becoming the co-maintainer of this project. Michael has been my long term colleague (from StarOffice Hamburg times) and helps me constantly drop procrastination and/or fix issues I am no longer capable to realize as I looked too long at them. In addition, Michael and I also serve as editors of the OASIS ODF TC. There at the ODF TC, we envision having a faster turn-around of ODF spec deliveries and making their information set more readable for downstream software as we are. Thanks to allotropia software GmbH, Michael’s employer, for providing him with the time for working on these tasks!

So what’s next? Obviously, it’s more than time to release an ODF Toolkit 1.0.0.

Personally, I would like to get the code generation right, but keep as much compatibility to prior releases as possible. Michael and my aim is to work from the end of January on this release (any helping hand is most welcome) 😊

There is also ODF 1.3, to be embraced by a release in the near future.

In February, I will likely have an online talk at FOSDEM, at the LibreOffice dev room about our project and what I intend to do next year.

In a nutshell, I was able to receive some NGI Search funding for this project to enable search in ODF documents.

Aside from the obvious search API – focusing on one higher-level based on user semantic and likely having also one lower-level based on XML, I would like to refactor my “spaghetti feature code” in the SAX parser that made the implementation of the changes hard to maintain. Sorry for that, not my first and likely not my last mistake – but I am learning! 🙂

We’re going to work out a more elaborate picture for the FOSDEM presentation.

Until then, have fun with the ODF Toolkit!

Open Letter to Members of EU Parliament

Today, the Coalition for Competitive Digital Markets (https://competitivedigitalmarkets.eu/), a group of more than 50 technology companies from 16 different European countries, sent an open letter to members of the European Parliament to raise awareness about interoperability and to impose stricter rules on big companies – the so-called ‘big tech’ companies – that act as gatekeepers and prevent transparency and openness in digital markets.

Open Letter 6 December

LibreOffice Technology DevRoom Call for Papers

FOSDEM 2022 will be a virtual event, taking place online on Saturday, February 5, and Sunday, February 6. The LibreOffice DevRoom is scheduled for Sunday, February 6, from 9AM to 7PM (times to be confirmed). If we will get more interesting talk proposals than the maximum number we can fit in one day, we will have the opportunity to extend the DevRoom to Saturday, February 5, in the afternoon.

NEW RULES FOR 2022

  • The reference time will be Brussels local time (CET).
  • Talks will be pre-recorded in advance, and streamed during the event
  • Q/A session will be live
  • A facility will be provided for people watching to chat between themselves
  • A facility will be provided for people watching to submit questions

IMPORTANT DATES TO REMEMBER

  • December 26: Submission deadline
  • December 28: Announcement of selected talks
  • December 31: Publication of DevRoom final schedule
  • January 16: Availability of pre-recordings for review
  • January 23: Deadline for upload of presentations

CALL FOR PAPERS

We are inviting proposals for talks about LibreOffice Technology, including ODF standard document format, on topics such as code, localization, QA, UX, documentation, tools, extensions, migrations and general advocacy. Please keep in mind that product pitches are not allowed at FOSDEM.

The length of talks is limited to a maximum of 25 minutes, as we would like to have some minutes for questions after each presentation, and to fit as many presenters as possible in the schedule. Exceptions must be explicitly requested and justified. You may be assigned LESS time than you have requested.

IMPORTANT INFORMATIONS

  • Presentations have to be pre-recorded and tested for streaming before the event.
  • Once your talk is pre-recorded, and approved by a reviewer in term of quality for streaming, it will have to be uploaded by January 23, to be prepared and ready for broadcast (the deadline cannot be moved further).
  • During the stream of talks, speakers must be available online for the Q/A session.

TALK SUBMISSIONS

All talk submissions have to be made in the Pentabarf event planning tool: https://penta.fosdem.org/submission/FOSDEM22.

While filing the proposal, please provide the title of your talk, a short abstract (one or two paragraphs), some information about yourself (name, bio and photo, but please do remember that your profile might be already stored in Pentabarf). To submit your talk, click on “Create Event” and select the “LibreOffice Technology” DevRoom as the “Track”. Otherwise, your talk will not be even considered for any devroom at all.

If you already have a Pentabarf account from a previous year, even if your talk was not accepted, please reuse it. Create an account if, and only if, you don’t have one from a previous year. If you have any issues with Pentabarf, please get in touch with the DevRoom manager.

DEVROOM MANAGER

Italo Vignoli: italo@libreoffice.org

EU coalition urges EU to push back against gate keeping by Microsoft, files official complaint

Brussels, November 26 – A coalition of EU software and cloud businesses joined Nextcloud GmbH in respect of their formal complaint to the European Commission about Microsoft’s anti-competitive behavior in respect of its OneDrive (cloud) offering. In a repeat from earlier monopolistic actions, Microsoft is bundling its OneDrive, Teams and other services with Windows and aggressively pushing consumers to sign up and hand over their data to Microsoft. This limits consumer choice and creates a barrier for other companies offering competing services.

Over the last few years have grown their market share to 66% of the EU market, while local providers lost out from 26 to 16%. By heavily favoring their own products and services (so-called “self-preferencing”) or outright blocking other vendors they leverage their position as gate keepers to extend their reach in more and more neighbouring markets and push users deeper into their ecosystems. Local, more specialised vendors are unable to compete “on the merits” as the key to success is not a good product but the ability to distort competition and block market access.

“This is quite similar to what Microsoft did when it killed competition in the browser market, stopping nearly all browser innovation for over a decade. Copy an innovators’ product, bundle it with your own dominant product and kill their business, then stop innovating. This kind of behavior is bad for the consumer, for the market and, of course, for local businesses in the EU. Together with the other members of the coalition, we are asking the antitrust authorities in Europe to enforce a level playing field, giving customers a free choice and to give competition a fair chance,” said Frank Karlitschek, CEO and founder of Nextcloud GmbH

The European Commission’s Directorate-General for Competition exists precisely for the purpose of preventing this kind of abusive behavior and keeping the market competitive and fair for all players. Nextcloud GmbH has filed an official complaint with the European Commission’s Directorate-General for Competition about the abusive practices of Microsoft related to OneDrive. Nextcloud GmbH has also filed a request with the German anti-trust authorities (the “Bundeskartellamt”) for an investigation against Microsoft and is discussing a complaint in France with its coalition members.

Dozens of European SMEs organisations support these efforts to push back against Big Tech and create a level playing field, supporting innovation and local (European) businesses.

A full list of these companies as well as non-profits and industry consortia can be found on https://antitrust.nextcloud.com. On the same page, there is also a list of the media coverage.

About Nextcloud GmbH

Nextcloud Hub is the industry-leading, fully open-source, on-premises team productivity platform and Germany’s number one collaboration solution. It combines the easy user interface of consumer-grade cloud solutions with the security and compliance measures enterprises need. Nextcloud Hub brings together universal access to data through mobile, desktop and web interfaces with next-generation, on-premise secure communication and collaboration features like real-time document editing, chat and video calls, putting them under the direct control of IT and integrated with existing infrastructure. Nextcloud’s easy and quick deployment, open, modular architecture and emphasis on security and advanced federation capabilities enable modern enterprises to leverage their existing file storage assets within and across the borders of their organization. For more information, visit nextcloud.com or follow @Nextclouders on Twitter.

ODF 1.3 is an OASIS Standard

The Document Foundation is pleased to announce that LibreOffice’s native document format – the OpenDocument Format for Office Applications (ODF) 1.3 – has been approved as OASIS Standard with 14 affirmative consents and no objections. ODF is a free, open XML-based document file format for office applications, to be used for documents containing text, spreadsheets, charts and graphical elements. ODF 1.3 is an update to the international standard Version 1.2, which was approved by the International Organization for Standardization (ISO) as ISO/IEC 26300 (2015).

The OpenDocument Format specifies the characteristics of an open XML-based application-independent and platform-independent digital document file format, as well as the characteristics of software applications which read, write and process such documents. It is applicable to document authoring, editing, viewing, exchange and archiving, including text documents, spreadsheets, presentation graphics, drawings, charts and similar documents commonly used by personal productivity software applications.

The most important new features of ODF 1.3 are digital signatures for documents and OpenPGP-based encryption of XML documents, with improvements in areas such as change tracking and document security, additional details in the description of elements in first pages, text, numbers and charts, and other timely improvements. The development of ODF 1.3 features has been funded by donations to The Document Foundation.

ODF Technical Committee has received 3 Statements of Use from The Document Foundation, CIBlabs GmbH, and Collabora Productivity.

ODF 1.3 Specification can be downloaded from OASIS website.

Part 1: Introduction
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part1-introduction/OpenDocument-v1.3-os-part1-introduction.odt (Authoritative)
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part1-introduction/OpenDocument-v1.3-os-part1-introduction.html
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part1-introduction/OpenDocument-v1.3-os-part1-introduction.pdf

Part 2: Packages
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part2-packages/OpenDocument-v1.3-os-part2-packages.odt (Authoritative)
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part2-packages/OpenDocument-v1.3-os-part2-packages.html
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part2-packages/OpenDocument-v1.3-os-part2-packages.pdf

Part 3: OpenDocument Schema
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.odt (Authoritative)
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.pdf

Part 4: Recalculated Formula (OpenFormula) Format
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part4-formula/OpenDocument-v1.3-os-part4-formula.odt (Authoritative)
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part4-formula/OpenDocument-v1.3-os-part4-formula.html
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part4-formula/OpenDocument-v1.3-os-part4-formula.pdf

XML/RNG schemas and OWL ontologies: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/schemas/

OASIS provides a complete package of the specification and any related files in a single ZIP: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/OpenDocument-v1.3-os.zip

ODF is the only document format which protects the rights of users as digital citizens, and allows transparent sharing of content without disruption, today and in the future.

Update from the ODF Technical Committee

While waiting for the official publication of ODF (OpenDocument) 1.3 as an OASIS Standard, after the approval of the ODF Technical Committee Draft at the end of April 2021, there are a few news updates from the ODF TC which are worth some publicity.

Since 2020, the ODF TC has two co-chairs – Patrick Durusau and Svante Schubert – and four co-editors: Francis Cave, Patrick Durusau, Svante Schubert and Michael Stahl. In the past, there were only two editors, and having doubled the number provides more bandwidth and flexibility.

The ODF TC has recently updated the project charter after more than a decade. The updated document is available on this page. The most important news is the commitment to deliver a Committee Specification Draft at least every year in December, consisting of RelaxNG schemas and written specifications, to avoid a long delay between two consecutive versions of the standard as in the recent past.

The ODF TC also aims to provide a fast-track for new ODF features of implementers, and publish the basic description (OASIS Committee Specification) more frequently, so features can be quickly  reviewed and embraced into an ODF Specification without the need to use the intermediate LibreOffice External namespaces (lo-ext), with all the associated delays and costs.

In addition, Michael Stahl and Svante Schubert have collected all the technical tooling required for the publishing of the ODF specification and the specification artefacts into an OASIS Github repository: https://github.com/oasis-tcs/odf-tc. The aim is to be able to deliver all specification deliverables by automation from command line, to become more agile, and improve transparency and quality by adopting modern toolings.

Last, but not least, the ODF TC is considering an ODF Plugfest in 2022.

Learn more about the OpenDocument Format here.