In response to Jim's proposal for pre-defined queries, Ian Green wrote:
>>how about delegated UI that allow new predefined queries to be created? There are two different capabilities related to "pre-defined queries"....Jim's proposal I believe was to include some specific queries in the spec. Then a client would use that URL for that purpose with all OSLC providers. A second notion is that in general, the tools that are providing these services allow a customer to define queries that customer finds useful and save them by name. The spec can also have an attribute/service that lists these queries...the attribute would be the same for all providers, the data in the list would be unique to each customer. A client uses that through configuration: If the client needs a query for a specific purpose, the customer must create an appropriate query in whatever tool they use as provider, then supply the name of the query through some configuration of the client tool. This is the typical way clients of integrations get specialized data. Then the code the client writes is portable to any OSLC provider, since the query the customer names will show up in the list for the attribute/service. Ian's idea of a delegated UI then makes a lot of sense: When a client tool needs a specialized query to be configured, they can ask the customer to do it through that delegated UI, returning back the URL, and the provider then exposes the parameter formats through the service attribute. I don't see anything "AM" specific about this. I think Ian already pointed to the idea of "filter queries" in some of the Rational products as being the same type of thing. Should this move to OSLC Core? Andy Berner
