RE: [cmis] CMIS stored query?

Another use case for this would the wide range systems that don’t have a full blown query engine, but allow some form of specialized query. Systems like Picasa, flickr, Twitter that might allow querying just by hash tag or keyword for example. Another good example of such a system is the REST API on Google Docs: http://code.google.com/apis/documents/docs/3.0/reference.html#Parameters

This allows you to do certain queries (like by title, by last modified date, by author, …) but does not offer a general query language.

Templated or stored queries are probably much more suitable for those broad range of systems than implementing a query language with a very small subset. It is also much easier to implement on server side and for a client it is easier to build a UI that matches the query capabilities of the server.

It would be worth spending a few more thoughts on this.

Jens

From: Churchland, David [mailto:david.churchland@hp.com]
Sent: Dienstag, 29. März 2011 23:10
To: cmis@lists.oasis-open.org
Subject: [cmis] CMIS stored query?

Here is a paragraph in the REST binding documentation that hints at a nascent stored query capability in CMIS:

This is a collection for processing queries. If the implementation supports GET on this collection, then the implementation SHOULD at least return a feed consisting of zero or more atom entries. These atom entries should represent persisted objects related to query such as persisted queries, long running queries or search templates.

Does anyone else have an interest in incorporating this (as an optional capability) into the domain model, e.g.:

· getQuery,

· createQuery,

· deleteQuery

· updateQuery

· query object supported in query

My interest in this is mostly about having shared navigational shortcuts, for example a stored query of my favorite documents which I can access both from my Desktop client and my mobile device client.

cmis message