Hi Vincent,
The aim of CMIS is to be repository vendor independent and most
applications don't need to know which server they are talking to. The
CMIS specification covers most standard content related use cases.
You should avoid all additional functionalities a repository provides,
if you can. If you discover that you heavily rely on non-standard
functionality, check if CMIS is the right interface for you. It might,
but it is a good indicator to verify your decision.
If you really have to, you can check which repository you are connected
to. The repository info provides the vendor and the product name.
Cheers,
Florian
Hello !
It seems Cmis implementation depends on the software.
For example :
http://wiki.alfresco.com/wiki/CMIS_Query_Language#Differences_between_cmis-strict_and_cmis-alfresco
I'm not a cmis specialist to properly evaluate if the differences are
significant but if they are, wouldn't the libs need some kind of
doctype (I'm more of web developper ... ) to know which rules may
apply ?
Have a nice day !
Vincent
