topic Re: Why does CMIS 1.1 specify Queryable:FALSE for cmis:changeToken? in Nuxeo Forum

Why does CMIS 1.1 specify Queryable:FALSE for cmis:changeToken?

rg1_ — Thu, 29 Aug 2013 14:37:58 GMT

The CMIS 1.0 Specification does not specify whether the cmis:changeToken property should be Queryable. The CMIS 1.1 Specification now states cmis:changeToken is explicitly NOT Queryable. Why is this the case? I would like to return the cmis:changeToken as part of a query resultSet to avoid extraneous getObject invocations. Thoughts?

Re: Why does CMIS 1.1 specify Queryable:FALSE for cmis:changeToken?

Florent_Guillau — Thu, 29 Aug 2013 18:25:34 GMT

You'd have to ask the OASIS CMIS Technical Committee (of which I'm a member), but I'd say that it's because change token are potentially computed or retrieved differently than other properties, and thus most CMIS servers cannot efficiently return them with the rest of the data.

I'll ask the question in the OASIS TC list to check if this change from 1.0 to 1.1 is not an oversight, because some CMIS servers may want to support it nonetheless.

Re: Why does CMIS 1.1 specify Queryable:FALSE for cmis:changeToken?

rg1_ — Thu, 29 Aug 2013 18:31:48 GMT

Much thanks! I hope this turns out to be an oversight. This would seem easy and useful for Nuxeo to support, for example, given the way it generates change tokens.

Re: Why does CMIS 1.1 specify Queryable:FALSE for cmis:changeToken?

Florent_Guillau — Thu, 29 Aug 2013 19:15:58 GMT

FYI the OASIS TC answer is

Re: Why does CMIS 1.1 specify Queryable:FALSE for cmis:changeToken?

rg1_ — Wed, 04 Sep 2013 15:10:25 GMT

Yes, it would seem useful to include a query constraint such as WHERE ANY cmis