Dragos, oslc.searchTerms is not a complete replacement for oslc.where with "like" or "contains". It was intended to work with paging so that you could just look at the first page of results and get the best matches. You wouldn't have to get the complete set of resources. For example, to get the top 10 matches, specify oslc.pageSize=10, get the first page and ignore the rest.
Regards, ___________________________________________________________________________ Arthur Ryman DE, PPM Chief Architect IBM Software, Rational Toronto Lab | +1-905-413-3077 Twitter | Facebook | YouTube From: Dragos Cojocari <[email protected]> To: Arthur Ryman/Toronto/IBM@IBMCA Cc: [email protected], [email protected] Date: 05/30/2011 08:11 AM Subject: Re: [oslc-core] Enhancing OSLC Query filtering Thanks Arthur. I've seen the oslcTerms but I don't think it can behave as a replacement of oslc.where with additional predicates. There are 2 reasons that make me say this: - it seems it's possible for results that do not match the search terms to be returned ( with oslc.score = 0) meaning that a larger set of data than needed will be returned. Is my interpretation correct? - the searchTerms performs sorting on the result set and it is defined to override the oslc.sort parameter which might be not desirable in all cases. Regards, Dragos Arthur Ryman <[email protected]> 05/30/2011 03:00 PM To Dragos Cojocari/Romania/IBM@IBMRO cc [email protected], [email protected] Subject Re: [oslc-core] Enhancing OSLC Query filtering Dragos, There is a full text search mechanism. oslc.searchTerms [1] The query syntax was intended to be simple and relatively easy to implement. For complex queries, we should use a standard query language, e.g. SPARQL. So rather than enhance the simple query syntax, we should be promoting query based on SPARQL, e.g. from an index. [1] http://open-services.net/bin/view/Main/OSLCCoreSpecQuery?sortcol=table;up=#oslc_searchTerms Regards, ___________________________________________________________________________ Arthur Ryman DE, PPM Chief Architect IBM Software, Rational Toronto Lab | +1-905-413-3077 Twitter | Facebook | YouTube From: Dragos Cojocari <[email protected]> To: [email protected] Date: 05/30/2011 06:17 AM Subject: [oslc-core] Enhancing OSLC Query filtering Sent by: [email protected] Hey all, the oslc.where parameter of OSLC queries allow filtering data using basic operators. In some cases this is not sufficient as expressing conditions using basic operators is either not possible or very cumbersome. Can the OSLC Query be enhanced with some common used predicates such as "like", "contains" etc? An example is searching for all the resources that contain a specific word in their dc:title property. Regards, Dragos Exceptand situatiile in care partile au convenit in alt mod: / Unless stated otherwise above: IBM România S.R.L. Bucharest Business Park, Corp A2, Şos. Bucureşti-Ploieşti Nr. 1A, 013681 Bucureşti 1, ROMANIA CIF RO378660, RC J/40/5106/1991 Cap.Soc. 41.670 Lei_______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net Exceptand situatiile in care partile au convenit in alt mod: / Unless stated otherwise above: IBM România S.R.L. Bucharest Business Park, Corp A2, Şos. Bucureşti-Ploieşti Nr. 1A, 013681 Bucureşti 1, ROMANIA CIF RO378660, RC J/40/5106/1991 Cap.Soc. 41.670 Lei
