Disclaimer: You are free to reuse it “as-is”, on your own responsibility and without any guarantee whatsoever. No rights can be derived from, successfully or unsuccessfully, completing the steps outlined below.

This is a simple scenario introduced at the Granada ODF Plugfest that may result in a number of different documents per application. It concerns not commonalities but unique features of the respective application or their auxiliary products that other products should still be able to represent in some way - while remaining fully editable and usable in the application itself. This concerns for example visual objects like integrated flow charts/adaptive graphics (SmartArt, SmartDraw), music notation and globe shape.

The point is to check on the basic principle that ODF provides a number of fallback mechanisms so that applications can have advanced features that outpace the standardisation, while being able to use ODF as the main format for all use cases and while remaining visually interoperable with others.

Procedural steps (to be repeated for all unique features of the application)

Create a new document and insert the unique feature object of the application.

Save the document as unique-[identifyingfeaturename-[application]-original.odt. (Note that “[application]” should be replaced by the name of the application being used.)

Create a PDF in your own application capturing the visual appearance

Exit the application.

Reopen the document and make some edits to the unique feature object. E.g. add some music notes, change the SmartArt/SmartDraw model, etc.

Create a PDF in your own application capturing the visual appearance

Save the document as unique-[identifyingfeaturename-[application]-edited.odt. (Note that “[application]” should be replaced by the name of the application being used.)

Please follow the file name convention outlined in the faq. Note that the PDF files can be included as a previewing aid, but uploading the ODF files is much more important.