1.The CMIS specification is a well-written and easy-to-read document, but some things are still left open to interpretation.
CMIS规范是一个编写良好、容易阅读的文档，但有些内容仍然需要解释。
2.Folders in a CMIS repository form a strict hierarchy, in which a folder can be contained only within a single parent folder.
在CMIS知识库里的文件夹会形成一个严格的层次结构，在这个层次体系中一个文件夹只能包含在单一的父文件夹中。
3.Please always test with at least two compliant repositories to make sure that you are Oasis CMIS specification compliant.
请总是使用至少两个兼容存储库进行测试，以确保遵循OasisCMIS规范。
4.It's possible (as a CMIS repository option) to allow documents to be contained in multiple folders or even in no folders at all.
（作为一个CMIS知识库选项）文档可以被放在多个文件夹中，或者不在任意文件夹中。
5.Being restful, all of its services are accessed through URL, but the CMIS specification leaves the specific URLs up to each vendor.
由于是restful，所以它所有的服务都通过URL访问，但是CMIS规范将特定的URL留给每个供应商。
6.In the case of CMIS, the containers are called repositories, which is what you see listed in the service document.
在CMIS中，这些容器又被称为知识库，就是在服务文档中列出的您能看到的部分。
7.The CMIS specification also defines a set of a few dozen content services to access this content (see figure 5).
CMIS规范也定义了一系列的内容服务来访问这一内容（见图5）。
8.The canDrop function in cmisconnector. js is called when a dragged object passes over a node in the CMIS repository tree.
当一个被拖拽的对象通过CMIS知识库树形中的节点时，就会调用cmisconnector.js中的canDrop函数。
9.In the case of a folder entry, the entry contains the object type property with the value of cmis: folder.
如果是文件夹，则条目包括值为cmis：folder的对象类型属性。
10.So however you set up the property definitions in your target CMIS repository, this code will try to make it work.
因此，不管您在目标CMIS存储库中如何设置属性定义，这个代码将尝试使其有效。