tools for document interoperability
This is the web diary for nfoWorks and realization of the Harmony Principles. Pursuing Harmony tracks nfoWorks research, analysis, specification, and implementation of tools for document interoperability. There is commentary on related activities that address conformance, interoperability, and harmonization of document formats.
The nfoCentrale Blog Conclave
nfoCentrale Associated Sites
Technorati Tags: Cover Pages, W3C, multimodal architecture, MMI, multimodal interfaces, document behavior, document content, interoperability
[update 2008-11-06 I don’t know how I failed to see that the very first sentence didn’t carry the sense I intended for it.]
A current weakness in the open-document standards arena is the poorly-specified and tacit coupling of format provisions to behavior in various document processing contexts (creation, viewing, editing/manipulation, and various “final-form” renderings and, these days, interactive performance governed by the document, whether slide-show or something more elaborate).
We’ll get to that some day, and the ways that such aspects are layered into specifications and their allowance for application innovation and conformance novelty remain to be discovered.
This Cover Pages Daily Newslink item from 2008-10-21 leads to an account of the W3C Technical Report on Multimodal Architecture and Interfaces Fifth Working Draft.
I’m putting down an nfoWorks marker because of these intriguing passages in the Newslink:
I am hesitant about the following:
There are some wise words about keeping straight the different design-time and run-time considerations.
I suspect that this is not going to bear directly on realization of the Harmony Principles, but it might provide useful conceptual underpinnings for an account of the behavioral aspects that are at least as important in document-mediated interoperability as the standard document format.
From the Cover Pages: XML Daily Newslink for 2008-10-14, there is announcement that the OASIS Darwin Information Typing Architecture (DITA) Technical Committee has formed a new subcommittee. The DITA for Technical Standards Subcommittee has the ambitious purpose of furthering and promoting DITA use for the creation, maintenance, and support of technical standards specifications. The idea is to have a “common standard for the creation and publication of … technical standards specifications:”
I’m not sure that this has any near-term benefit, but it does arouse my interest in another way. I am finding it very difficult to wrap my head around the current and in-progress OpenDocument Format (ODF) and Office Open XML (OOXML) specifications. I need some way to wrestle out my understanding in a way that allows me to surface a conceptualization of the functions of either in a way that their reconciliation at the Harmony Principles level can be grasped and described in some useful way.
DITA surfaces on my radar from time to time. It is something I think I should know more about. I don’t know how to apply it in the context of standard document formats, nor am I clear how it is applicable to the conceptualization and expression of document-format standards. It does strike me that some help is needed, based on my early efforts in the analysis of ODF specifications. (At this point, concept-mapping software might be even more useful, and I will look into that as well.)
It is time to dig deeper into DITA to see how it can support a harmonization effort with regard to office document formats and their harmonizable specification.
created 2008-08-13-18:06 -0700 (pdt)