Re: [cmis] CMIS stored query?

[Scott Malabarba <scott.malabarba@us.ibm.com>]

I'm interested.  It'd be a useful
feature and would provide better support for taxonomy-driven systems.
I think supporting search templates
/ parameterized queries would be pretty important.

Any interest in allowing POST to a stored
query?  Say, for example, if the atom entry returned for a given stored
query has the <cmis:allowsPost>true</cmis:allowsPost> 
property, then the client can post an
object to the query's entry URL.  The server will create an object
with metadata that matches the query.
The use case I have in mind is virtual
folders:  I want the virtual folder backed by my stored query to act
like a real folder and let me drag-and-drop content into it.





From:      
 "Churchland, David"
<david.churchland@hp.com>
To:      
 "cmis@lists.oasis-open.org"
<cmis@lists.oasis-open.org>
Date:      
 03/29/2011 02:14 PM
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.