There are things in WebDAV that aren't available in CMIS (locking, redirects, advanced versioning, namespace operations like MOVE). There are certainly other things only available in CMIS. Both could be extended to become a better match (and therefore it may have been a bad idea to start from scratch instead of just adding to/profiling WebDAV).
The main real difference is that the collection model in WebDAV is more specific (in that it exposes a real hierarchy with MOVE/COPY operations), while in CMIS (as per AtomPub) the client has less control. Depending on the requirements, that can be an advantage or a disadvantage.
WebDAV is an older standard and is based entirely on the HTTP specification. In fact, HTTP was extended to move it from read-only to read-write. Before WebDAV the HTTP specification was not able to handle back-and-forth file transfers so it was extended for that purpose. WebDAV is very rudimentary and only lets authors manage in a file-browse mode. The first WebDAV spec that came out did not include versioning capabilities. It was later on in the "Delta V" release of the spec where complete versioning was spec'ed out. While WebDAV is extraordinarily prevalent (Microsoft desktops, some Adobe products, etc) most vendors have only implemented the earlier WebDAV spec. (i.e. not DeltaV)
CMIS on the other hand is a much more complete and rich specification. CMIS is basically a web-service based common API. CMIS includes support for extending metadata, searching, advanced permissions, versioning capabilities, etc and really further advances the notion of a common-plumbing layer for an organizations' various repositories. It is really a common denominator API amongst the various ECM vendors such as Microsoft IBM, OpenText, ECM and so on.
Volumes could be written on CMIS at this point but those are some big differences. One note is that of this writing CMIS is still not a 1.0 spec (almost there) whereas WebDAV had been around for over a decade. There are likely to be considerable changes coming as CMIS evolves.
发布评论
评论（2）
没有简单的答案。
WebDAV 中的某些功能在 CMIS 中不可用（锁定、重定向、高级版本控制、MOVE 等命名空间操作）。当然还有一些其他东西只能在 CMIS 中使用。两者都可以扩展以成为更好的匹配（因此从头开始而不是仅仅添加到/分析 WebDAV 可能是一个坏主意）。
主要的真正区别在于，WebDAV 中的集合模型更加具体（因为它通过 MOVE/COPY 操作公开真实的层次结构），而在 CMIS 中（根据 AtomPub），客户端的控制权较少。根据要求，这可能是优点，也可能是缺点。
There's no simple answer.
There are things in WebDAV that aren't available in CMIS (locking, redirects, advanced versioning, namespace operations like MOVE). There are certainly other things only available in CMIS. Both could be extended to become a better match (and therefore it may have been a bad idea to start from scratch instead of just adding to/profiling WebDAV).
The main real difference is that the collection model in WebDAV is more specific (in that it exposes a real hierarchy with MOVE/COPY operations), while in CMIS (as per AtomPub) the client has less control. Depending on the requirements, that can be an advantage or a disadvantage.
WebDAV 是一个较旧的标准，完全基于 HTTP 规范。事实上，HTTP 经过扩展，从只读变为读写。在 WebDAV 之前，HTTP 规范无法处理来回文件传输，因此对其进行了扩展。 WebDAV 非常初级，仅允许作者以文件浏览模式进行管理。发布的第一个 WebDAV 规范不包括版本控制功能。后来在该规范的“Delta V”版本中，完整的版本控制被规范出来。虽然 WebDAV 非常流行（Microsoft 桌面、某些 Adobe 产品等），但大多数供应商仅实现了早期的 WebDAV 规范。 （即不是 DeltaV）
另一方面，CMIS 是一个更加完整和丰富的规范。 CMIS 基本上是一个基于 Web 服务的通用 API。 CMIS 包括对扩展元数据、搜索、高级权限、版本控制功能等的支持，并真正进一步推进了组织各种存储库的公共管道层的概念。它实际上是各种 ECM 供应商（例如 Microsoft IBM、OpenText、ECM 等）之间的共同点 API。
此时可以在 CMIS 上编写卷，但这些是一些很大的差异。需要注意的是，在撰写本文时，CMIS 仍然不是 1.0 规范（几乎已经存在），而 WebDAV 已经存在了十多年。随着 CMIS 的发展，可能会发生相当大的变化。
WebDAV is an older standard and is based entirely on the HTTP specification. In fact, HTTP was extended to move it from read-only to read-write. Before WebDAV the HTTP specification was not able to handle back-and-forth file transfers so it was extended for that purpose. WebDAV is very rudimentary and only lets authors manage in a file-browse mode. The first WebDAV spec that came out did not include versioning capabilities. It was later on in the "Delta V" release of the spec where complete versioning was spec'ed out. While WebDAV is extraordinarily prevalent (Microsoft desktops, some Adobe products, etc) most vendors have only implemented the earlier WebDAV spec. (i.e. not DeltaV)
CMIS on the other hand is a much more complete and rich specification. CMIS is basically a web-service based common API. CMIS includes support for extending metadata, searching, advanced permissions, versioning capabilities, etc and really further advances the notion of a common-plumbing layer for an organizations' various repositories. It is really a common denominator API amongst the various ECM vendors such as Microsoft IBM, OpenText, ECM and so on.
Volumes could be written on CMIS at this point but those are some big differences. One note is that of this writing CMIS is still not a 1.0 spec (almost there) whereas WebDAV had been around for over a decade. There are likely to be considerable changes coming as CMIS evolves.