- From: Thomas Hoppe <thomas.hoppe@n-fuse.de>
- Date: Sun, 20 Dec 2015 18:43:58 +0100
- To: public-hydra@w3.org
On 12/20/2015 04:49 PM, Markus Lanthaler wrote: >>> >> - assuming we need "transformations" or also just simply the equivalent > of >>> >>the SELECT part of a SQL/SPARQL query how do we possibly model that >> > >> >Not issues for Hydra Core I think. >> >(But in any case, it's not a showstopper for the hydra:filter property.) > Not sure I agree about that.. at least being able to select which fields to > return has been requested quite a few times by now. > > I agree that this is a very common use case for APIs but I see it as a general thing, not only in the case of filtering. So I think we should come up with a solution that can be layered on top of a normal GET call _and_ a case where a hydra:filter is involved. Very common in current rest API is a query param like "fields=created,modified,...". Something like this should be easy to model with IRI templates. Alternatively or additionally it might make sense to let the client specify a shape.
Received on Sunday, 20 December 2015 17:44:43 UTC