Re: query language from László Lajos Jánszky on 2014-09-10 (public-hydra@w3.org from September 2014)

From: László Lajos Jánszky <laszlo.janszky@gmail.com>
Date: Wed, 10 Sep 2014 19:46:49 +0200
To: Erik Wilde <dret@berkeley.edu>
Cc: Ryan McDonough <ryan@damnhandy.com>, Ruben Verborgh <ruben.verborgh@ugent.be>, "public-hydra@w3.org" <public-hydra@w3.org>
Message-ID: <CA+=RcCoRCY--xfQdvDHsmsKmM_4VRi1sfZtz6JmO4BhZ+2WTPw@mail.gmail.com>

> yes it does, if it is not sufficient to GET the representation of some resource to understand how to construct such a query.

Yes ofc. because it would couple the client to the REST API. But if we
had a standard way to describe such queries then I don't think it
would violate any REST constraint.

Actually I am not so sure that we need a new query language for this.
I mean it could be any existing query language, for example SPARQL in
an URL serialized form. But we have to describe the parameters
somehow... Not an easy task...

Received on Wednesday, 10 September 2014 17:47:18 UTC