Death of The Document - CIO Central - CIO Network - Forbes - 0 views
blogs.forbes.com/...death-of-the-document
forbes visual-documents visually-immersive static-documents compound-documents
shared by Gary Edwards on 29 Apr 11
- No Cached
-
Gary Edwards on 29 Apr 11Well, not quite. More IBM happy talk about interoperability and easy document interchange. While i agree with the static versus interactive - collaborative document perspective, it's far more complicated. Today we have a world of "native" docs and "visual" docs. Native docs are bound to their authoring productivity environment, and are stubbornly NOT interchangeable. Even for ODF and OOXML formats. Visual documents are spun from natives, and they are highly interchangeable, but interactively limited. They lack the direct interaction of native authoring environments. The Visual document phenomenon starts with PDF and the virtual print driver. Any authoring application(s) in a productivity environment can print a PDF using the magic of the virtual print driver. In 2008, when ISO stamped PDF with "accessibility tags", a new, highly interactive version of PDF was offically recognized. We know this as "Tagged PDF". And it has led the sweeping revolution of wide implementation of the paperless transaction process. The Visual Document phenomenon doesn't stop there. The highly mobile WebKit revolution ushered in by the 2008 iPhone phenomenon led to wide acceptance of highly interactive and collaborative, but richly visual versions of SVG and HTML5-CSS3-JSON-JavaScript documents. Today we have SVG-HTML+ type visually immersive documents spun out of Server side publication presses such as FlipBoard, Cognito cComics, QWiki, Needle, Sports Illustrated, Push Pop Press, and TreeSaver to name but a few. Clearly the visually immersive category of documents is exploding, but not for business - productivity documents. Adobe has proposed a "CSS Regions" standard for richly immersive layout that might change that. But mostly i think the problem for business documents, reports and forms is that they are "compound documents" bound to desktop productivity environments and workgroups. The great transition from desktop/workgroup productivity environme