Hierarchical File System - sgml/signature GitHub Wiki

CMIS‑Native Products With High Spec Compliance and Low Mapping Complexity

Which commercial or non‑commercial products besides Alfresco have a native CMIS implementation with high spec compliance and low mapping complexity?

Nuxeo Platform

Nuxeo provides a fully native CMIS implementation. CMIS is treated as a first‑class API, and the internal content model—documents, facets, and schemas—maps cleanly to CMIS types and secondary types. The schema‑driven architecture aligns naturally with CMIS, resulting in high compliance and low mapping complexity.

OpenText Content Server (formerly Livelink)

OpenText Content Server includes a native CMIS interface built directly on top of its modern REST architecture. Its node‑based metadata model maps well to CMIS objects, and its CMIS support is more straightforward than older ECM systems. This gives it high CMIS compliance and relatively low mapping complexity.

KnowledgeTree (legacy, open source)

KnowledgeTree, although discontinued, offered one of the earliest native CMIS implementations. Its internal content model was intentionally aligned with CMIS during its final development cycles, resulting in high compliance for its era and low mapping complexity.

OpenKM (commercial + open source)

OpenKM includes a native CMIS interface integrated directly into the repository. Its simple node‑based model maps naturally to CMIS objects, and it supports core CMIS features with high compliance and low mapping complexity. It remains one of the more straightforward CMIS‑native systems still maintained.

What CMIS‑readiness questions should you ask any vendor?

  • Does the platform fully support CMIS 1.1, including browser binding, JSON responses, and secondary types?
  • How closely does the internal content model map to CMIS object types, properties, and relationships?
  • Are CMIS queries (CMIS‑QL) optimized for large repositories, and does the vendor publish performance benchmarks?
  • Does the CMIS layer expose all versioning operations, including check‑in, check‑out, and version labels?
  • How does the platform handle CMIS ACLs, and how do they map to the vendor's native permission model?
  • Are renditions consistently exposed through CMIS for all document types?
  • Does the platform support CMIS change logs, and how are they implemented internally?
  • Is the CMIS implementation used internally by the vendor's own components, or only exposed externally?
  • Does the vendor provide automated compliance testing using the CMIS TCK (Technology Compatibility Kit)?
  • What is the vendor's roadmap for CMIS support, maintenance, and long‑term compatibility?

Virtual File Systems

CMIS

Recursion

Streams to File Redirection

Sequential Execution