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

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?

0 votes

1 answers

2186 views

ANSWER



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.

0 votes



rg1
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.
08/29/2013

FYI the OASIS TC answer is: https://lists.oasis-open.org/archives/cmis/201308/msg00028.html . You can follow the thread if needed. I can pass on more comments.
08/29/2013

rg1
Yes, it would seem useful to include a query constraint such as WHERE ANY cmis:changeToken NOT IN ('val1','val2','vale3'…). val[1..n] presumably would have been captured in a previous query.
09/04/2013