RESTful services use standard HTTP requests. You can use any number of query parameters to filter your results. For example, to fetch all products (in XML) with a price greater than 50 you'd send a GET request to the following URL:
http://my.web.service.com/v1/products.xml?price_gt=50
Since you have full control over the web service, it is you who has to decide what kind of filtering should be available, and via which parameters. You could, for example, also add an offset and limit parameter to fetch a specific amount of records.
For a browser-based client, you'd need an HTML representation of your resources/records. Most web applications have a filtering form with the available filtering parameters. In my previous example, I could add a simple text field for full-text search in the products' title/description and a couple of text fields or select menus to allow the user to fetch products within their preferred price range.
The way I see it, there is no standard way to define a filtering language and web interface, as it all depends on what data and filtering capabilities you want to provide to your users. It also depends on the language the web service is written in and whether you need a simple HTML UI or an AJAX-driven UI on the client side.