Elda silently ignores URI based filters on List Endpoints that use an api:select selector.

[GoogleCodeExporter]

The api:select selector lets an api developer provide a whole SPARQL select 
query. Elda will manage the LIMIT and OFFSET paging - but it does not/cannot 
inject URI based filter elements into the query.

Currently elda (1.2.8) seems to silently ignore URI based filters at endpoints 
implemented using api:select selectors.

This will be counter inuitive to an api user expecting a filter to have an 
effect. Elda should probably 404 and respond with a message that says that the 
corresponding URI parameters are not supported on the given endpoint.

Original issue reported on code.google.com by skwli...@gmail.com on 14 Mar 2012 at 7:34

[GoogleCodeExporter]

400 

Original comment by ehog.he...@googlemail.com on 23 Mar 2012 at 1:55

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by ehog.he...@googlemail.com on 23 Mar 2012 at 1:56

[GoogleCodeExporter]

"but it does not/cannot inject URI based filter elements into the query."

Not true: if ?X appears in the query, then the value of the variable X (if 
there is
one) is appropriately injected in ?X's place.

(other query parameters are still iffy, mind.)

Original comment by ehog.he...@googlemail.com on 28 May 2012 at 11:21

• Changed title: Elda silently ignores URI based filters on List Endpoints that use an api:select selector.

[GoogleCodeExporter]

So... is this "Not a problem"  or "Needs attention"?

Original comment by skwli...@gmail.com on 10 Jun 2013 at 12:46