Deep PDF
Background
A serious issue for innovation is how to deal with legacy document formats. In the case of development of new word processors the current document intermediary format is Microsoft Word's .DOC format and Adobe's .PDF (Portable Digital Format). PDF documents are prevalent in the academic world and it is very useful that the PDF document can act as a wrapper for other data, which is what makes this new approach possible:
Proposal
The word processor produces a clean PDF which any PDF reader can access but also embeds the complete original document (in our case a .liquid document for Author) and an open XML version of the document inside the PDF.
Benefit
This way anyone can open the PDF and have basic interactions but if they use a ‘Deep PDF’ aware application they get access to richer interactions, since all the original meta is included.
Creation
On export from a ‘Deep PDF’-enabled application the following document will be generated:
This document will also contain these two versions of the document, compressed (.zip):
Opening / Reading
Opening / Reading
If the user who received the document and has a Deep PDF reader chooses to edit, the app will ask if the original document should be compressed and archived inside the new document. The way this would be handled would be up to the individual application developers. This is a publication format, not a working/saving format.
Blog posts on this, using the earlier name of 'rich pdf' : wordpress.liquid.info/category/rich-pdf