[oslc-core] Behavior of oslc.where and oslc.sort if resources are not managed by the service provider

[Dragos Cojocari]

Hey everyone,

and a Happy new year.

I'd like to understand what is the defined behaviour if a query specifies 
in its where/orderBy clause and the collection of resources contains 
resources not managed by the service provider and the serviceprovider 
cannot filter/sort them. What should the provider do:
- reject the response with an error
- include only the resources for which the filter/sort can be calculated
- undefined

Example data:




So for the data above what is the expected result for the following query: 
 
http://<server>:<post>/defects?oslc.select=*&oslc.where=oslc:shortTitle="Some 
defect"

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20110112/bc756546/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 10549 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20110112/bc756546/attachment.gif>