The answer is twofold.

ODF 1.2 is not a new format; it's mostly a superset of the ODF 1.1 specifications. In the past, the transition from ODF 1.0 to ODF 1.1 went almost unnoticed for the users. ODF 1.2 brings more new features, but not deep structural changes. As a consequence, the present version OpenOffice::OODoc API should be compatible with OOo 3.0 files; it simply ignores the ODF 1.2 specific features, that is not a matter for most applications. Of course, some of these new features will probably be supported in the near future, and the new format will probably raise new issues that will have to be fixed.

On the other hand, OODoc provides a low level layer, mainly available through getElement(), insertElement(), getNodeByXPath(), and so on. This layer relies on a DOM/XPath engine that is ODF-agnostic, and it allows the user to create custom accessors for any kind of object. So one can easily (with some knowledge of the OASIS spec) extend the toolbox in order to process specific ODF 1.2 objects without waiting for a future release of OODoc.

Anyway, this forum is a good place to advertise the needs and discuss the priorities in this area.