|
|
0.02 2008-04-23 21:12 -0700 |
Work on the ODMJNI Java-ODMA Integration reveals a great deal about the appeal of ODMA in its particular niche. There is still no comparable integration arrangement that solves the problem that ODMA was introduced to address in 1994. At that time Windows 3.11 occupied the desktop and Windows NT was not yet established as the platform it would become.
The ODMJNI 1.0 work also exposes those significant limitations that hamper ODMA usage on contemporary systems:
- absence of end-to-end Unicode support
- weak integration into the GUI of desktop applications
- no integration in the Java, .NET, and ActiveX/COM worlds
- inadequate provisions for troubleshooting, integration confirmation, and configuration management on the desktop
These and other limitations are attributable to the common reliance of the 16-bit and 32-bit APIs and ODMA Connection Managers on what are now mainly-obsolete technologies. The fundamental constraints were perpetuated as ODMA 1.0 evolved to the 1997 establishment of ODMA 2.0 and then remained at that level.
The current transition of Windows and desktop applications to 64-bit processors and x64 implementations imposes a natural end-of-life for ODMA 2.0 and the ODMA32 implementation. ODMA32 will fade away along with the 32-bit processors (and 64-bit compatibility arrangements) on which it is hosted.
This major transition also represents an opportunity for an ODMA64 (and an unleashed ODMA 3.0) that is unhampered by ODMA32 and ODMA 2.0 limitations. Assuming that the specialized appeal of ODMA lingers on, perpetuation in an ODMA64 implementation can provide a practical migration of the ODMA "sweet spot" to the arriving generation of managed-document applications.
This on-line folio is the place for capturing initial efforts at envisioning an ODMA64. The technical tension is around
preserving the value that ODMA uniquely provides for managed-document integration on the desktop
overcoming the limitations of ODMA32 and the ODMA 2.0 specification
avoiding the second-system syndrome and reaching farther than necessary for the preservation of ODMA's primary benefits
ensuring that the ODMA64 integration layer is unquestionably the most-dependable software of the managed-document "stack" from office productivity software to document management systems and back
Whether there is adequate demand and investment for taking ODMA this far is a different matter. This envisioning is intended to be informative and useful either way.
It is not expected that meaningful availability of an ODMA64 with these qualities could occur before 2010. That's partly because of the low level of activity around ODMA development. It's mainly because of the preparations that must occur around ODMA32 to set the stage. Interest in such a venture may simply not last that long.
- see also:
- d080101: ODMA Roadmap
d080102: ODMA Effectiveness- d071003: ODMA32 2.5 Integration
d071004: ODMA32 Core- ODMA q070701: ODMJNI Java-ODMA Integration Kit
NuovoDoc Analysis: ODMA -- Where's It Going?
Professor von Clueless: How About That ODMA64? (weblog post, 2007-11-10)
- Hamilton, Dennis E.
- ODMA64 3.0 Interoperability. AIIM ODMA Interoperability Exchange, ODMdev Development Note d071002 0.02, February 15, 2008. Available at <http://ODMA.info/dev/devNotes/2007/10/d071002.htm>.
|
|
created 2007-10-25-19:20 -0700 (pdt) by
orcmid |
