This information is also part of ODMA 2.0 Library Files edition 2.0-1. For later editions and current status, consult the ODMA 2.0 Library Files description page.
This response addresses questions about the appropriate version of ODMA to use in developing applications, in providing DMS integrations, and in configuring ODMA Connection Managers.
There is information on achieving maximum interoperability in the way that ODMA versions are supported and ODMA software is configured.
Tell them the answer.
ODMA 1.0 is the most flexible for development of ODMA-aware applications and other desktop tools. ODMA 1.0 is the level of API that is the most likely to work with any ODMA-compliant DMS and ODMA Connection Manager.
Applications that rely on capabilities of ODMA 1.5 should be designed to operate with ODMA 1.5 features as optionally available. [Also say what the consequences of requiring ODMA 1.5 are.]
Applications that require direct use of advanced document-management concepts, or that want to operate silently with a comparable DMS will require ODMA 2.0 support. It is also desirable to have ODMA 2.0 functions used as options. Say what the consequences of requiring ODMA 2.0 are. Point out that an ODMA 2.0-compliant DMS can report that many ODMA-2.0-specific operations are not supported in a given configuration.
ODMA 2.0 is the level of support that is most likely to work with any ODMA-aware application, Connection Manager, or tool. ODMA 2.0-compliant components must be designed to work properly when delivered requests from ODMA 1.0 and ODMA 1.5 aware applications and when initiated by any version of ODMA Connection Manager.
Because it is not known what features of ODMA 2.0 will be required by an ODMA 2.0-aware application, it is preferable to provide ODMA 2.0 support, with limited implementations, than refuse to supply ODMA 2.0 interfaces.
The support for the additional ODMA 1.5 interface is always optional.
Using the latest available Connection Manager is critical to maximizing interoperability in all ODMA configurations.
For an application, if the Connection Manager version is lower than the version required by the application, the Connection Manager can refuse the
ODMRegisterApprequest. This is regardless of the availability of DMS integrations that satisfy the version requirements of the registering application.
For an application, if the Connection Manager version is lower than the version whose
.libfile was used in compiling the application, the application may fail to load. We recommend defensive development practices that avoid this for applications, but the risk is real for legacy application implementations. (See the interoperability confirmation FAQtip.)
For a DMS, if the Connection Manager version is lower than the version supported by the DMS integration, the Connection Manager will operate correctly with the DMS, but the additional supported ODMA functions will not be utilized. (These functions may still be accessed via
ODMQueryInterface, but this is a peculiar and difficult case.)
- Dennis Hamilton
- initiated this FAQtip in support of ODMATech discussions on which ODMA versions to develop for.
- version 0.10: Is a place-holder and outline for a note to be reviewed and developed further.
created 2000-12-11-13:49 -0800 (pst) by orcmid
$$Author: Orcmid $
$$Date: 01-01-11 8:31 $
$$Revision: 5 $