d071004: ODMA Core

Important Note: There is no longer any development or support for the original 16-bit ODMA software. Although the source code, Visual Studio projects, binaries, and ODMA SDKs for 16-bit ODMA are included in the ODMA Core preservation activity, there will be no further maintenance or development for 16-bit ODMA.

1. Preservation

The existing materials for 16-bit ODMA and ODMA32 are organized for preservation and public archiving:

The materials are preserved as downloads on the ODMA Interoperability Exchange site.
A CD-ROM of the materials is prepared as a historical archive for AIIM International and anyone else who finds value in the historical materials.
The ODMA core materials are preserved in the ActiveODMA SourceForge project file releases.
The ODMA32 core materials are also added to the ActiveODMA source-code version-control system.

2. Identification and Repackaging

The ODMA32 2.0 portions of the ODMA Core are updated to provide

version identification
copyright notices
license information
descriptive manifests of the material

The repackaged ODMA 2.0 material is made available as the base distribution for the ODMA32 Core. (The libraries and compiled binaries are not touched.)

The repackaged forms are made available as downloads on the ODMA Interoperability Exchange site, as ActiveODMA file releases, and as source code in the ActiveODMA source-code version control system. These become the basis for future work.

3. Stabilization and Modernization

The current ODMA32 Core header files are not satisfactory for development of professional-quality ODMA-based software. The samples contain defects and require obsolete tools to rebuild. These files will be revised and upgraded.

The header files will be reorganized and extended for appropriate use in software development using currently-supported tools (such as Visual C++ 2005/2008). The revisions will have distinct names so that there is no conflict with applications that have been built with the original ODMA 2.0 and earlier versions.
As part of the development of additional samples and ODMA32 2.5 supplementary libraries, the existing samples will be rebuilt or replaced with corrected ones that can be maintained using free tools such as the Visual Studio Express Editions and the Java SDK.
There will be additional documentation and demonstration of trouble-shooting using components of the ODMA32 Core.

Under no conditions will the ODMA 2.0 Connection Manager, or any earlier Connection Manager version, be rebuilt, replaced, or revised as part of this activity. It is crucial that none of these activities risk destabilization of the ODMA Connection Manager.

4. Enhancement and Retirement

As part of developing the set of supplemental components identified as ODMA 2.5,

Simple improvements found desirable in the ODMA32 Core will be released. Completion of ODMA 2.5 will determine the freezing of the stable ODMA32 Core.
At some point, the ODMA 2.0 Connection Manager will be reviewed, updated, and rebuilt with current development tools. This version will be verified and stabilized using the test fixtures and regression tests that are accumulated as part of ODMA 2.5 work.
If the refined and rebuilt ODMA 2.0 Connection Manager is released for independent distribution, it will be as a maintenance release (i.e., 2.0.1). There should be no noticeable functional difference when the maintenance release is introduced into a production setting. The maintenance release may perform better and there may be better defense against errors in ODMA-aware client software and ODMA-compliant DMS integrations. There will be improved logging for trouble-shooting. There may be adjustments to the installation and troubleshooting procedures. The released Connection Manager will be digitally signed.
The refined ODMA 2.0 Connection Manager, with all maintenance changes, will provide the baseline for development of modifications for ODMA 2.5 functions. These functions will not interfere with ODMA 2.0 and earlier applications and there will be no change to the ODMA 2.0 and earlier APIs. The only reason for making an ODMA 2.5 Connection Manager is to provide more-efficient connection between application and DMS when both are implemented using managed code. If that can be achieved with only the maintenance release of the ODMA 2.0 Connection Manager, the maintenance release will be pushed out with the ODMA 2.5 supplements.

The ODMA 2.5 effort brings ODMA32 to a level where it can be used as a springboard for transition to ODMA64, the potential ODMA 3.0 version of ODMA. Any ODMA64 Core will be developed and released independently. ODMA32 will never transition to the incompatible ODMA 3.0.

5. Available Materials

Attribution:

Hamilton, Dennis E.

ODMA Core. AIIM ODMA Interoperability Exchange, ODMdev Development Note d071004 0.01, February 15, 2008. Available at <http://ODMA.info/dev/devNotes/2007/10/d071004.htm>.

Revision History:

0.01 2008-02-15-18:50 Elaborate the Core Progression

The four stages of the Core Progression are sketched.

0.00 2007-10-28-16:46 Create placeholder to morph into the necessary material

Incorporate job jar and use it to drive the completion of essential items here, providing an initial skeleton for more content. The first objective is provision of a target for cross references that also serves as a placeholder for further details, developer notes, and work items. There is some sketchy material on what is meant by the core and what is to be done with it.

You are navigating ODMdev.
This work is licensed under a
Creative Commons Attribution 2.5 License.

created 2007-10-25-19:20 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 08-04-23 21:12 $
$$Revision: 59 $