Thanks Steve, I think one of the supporting cases, that I tried to hint at in the examples, are queries that involve internal or derived information that is not available in the public OSLC form. For example Design Management 4.0 supports a lot of versioning features, none of which appear in the OSLC. A pre-defined query could leverage this information in a way, that could never be exposed in the official OSLC representation.
Also we have noted in our experience with DM, that queries are expensive. Especially ones that have complicated joins. Sometimes it is far more efficient to just perform GETs on resources and do a little be of old fashion programming logic to compute the desired result. Pre-defined queries provide a means to make some common expensive queries far more efficient. Thanks, jim conallen Rational Design Management (DM) Integration Architect, OSLC AM Lead [email protected] Rational Software, IBM Software Group From: Steve K Speicher/Raleigh/IBM@IBMUS To: [email protected], Date: 08/29/2012 04:26 PM Subject: [oslc-ArchMgmt] Predefined query supporting integration use cases Sent by: [email protected] I was looking through [1] and was trying to locate some supporting integration use cases for this. I can imagine how it would be useful for end-user usage and some integration cases, though I can also think where the query syntax could solve some of those same cases. Just wanted to queue this up for tomorrow's call or perhaps it is a quick answer. [1] - http://open-services.net/bin/view/Main/AmPredefinedQuery Thanks, Steve Speicher IBM Rational Software OSLC - Lifecycle integration inspired by the web -> http://open-services.net _______________________________________________ Oslc-Am mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-am_open-services.net
