Hey Dragos, It is ironic that you post this question, as it was just brought up at the OSLC Core meeting today. There is was recommended that we update the wording in the specification to indicate that a 400 Bad Request (with an appropriate message) be returned if a query includes any un-supported or invalid parameters in the where clause (or presumably in any of the arguments to the query).
The wording is to specifically address any concern that a query can be executed where the server independently discards information, without any indication of such to the client. <jim/> jim conallen CAM Lead Architect [email protected] Rational Software, IBM Software Group From: Dragos Cojocari <[email protected]> To: [email protected] Date: 10/20/2010 02:34 PM Subject: [oslc-core] Query capabilities Sent by: [email protected] Hi all, I went through the OSLC Core Specification v2 Query Syntax One aspect that is not clear is how can be determined which query arguments are supported and what happens if an unsupported argument is used in the query. Will the service indicate in any way (HTTP response) if an unsupported parameter is found in the query string or will it ignore that argument? If the service silently ignores unsupported arguments the consumer will get incorrect data. 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
