text: Another option is to use an intermediate API that is based on the ODWEK Java API for the 
  Content Manager OnDemand access portion. Content Management Interoperability Services 
  (CMIS) or other web services can be used as the intermediate API. The web service 
  application uses ODWEK to access Content Manager OnDemand and relays this access 
  through its own web services to any other application. In this case, the Windows application 
  only needs to talk to the web service. For more information about CMIS and its limitations, 
  see 8.3.2, “Content Management Interoperability Services” on page 204. 
  
  The use of an intermediate API increases complexity and potentially decreases performance, 
  but it decouples a Windows application and Content Manager OnDemand in terms of API 
  versioning and requiring a Content Manager OnDemand installation. 
  
  **8.1.3 Client compatibility**
  
  During the development history of Content Manager OnDemand, features were added and 
  internal API schemes were changed. Therefore, not every client level can work with every 
  server level. When you choose a client infrastructure for your Content Manager OnDemand 
  environment, you must consider version dependencies. 
  
  **Client compatibility matrix**
  At the API level, all user clients share a common API core that is based on the Windows client 
  and ODWEK. Almost all other client and API implementations are based on these common 
  APIs. An up-to-date overview of the compatibility matrix that shows the client and ODWEK 
  level that can work with each server level is available at the following website: 
  
  http://www.ibm.com/support/docview.wss?uid=swg21392275 