- From: László Lajos Jánszky <laszlo.janszky@gmail.com>
- Date: Wed, 10 Sep 2014 20:57:56 +0200
- To: Erik Wilde <dret@berkeley.edu>
- Cc: "public-hydra@w3.org" <public-hydra@w3.org>
Yes Erik, that's the conclusion.
Btw. we don't necessary need a new query language, just a vocab to
describe what parameters and operators (possibly structures) are
allowed and the type of the query language... So the current hydra
vocab does not interfere with this feature.
> yup, that's the hacky tunneling way of doing it. you'd end up with this:
>
> {
> "@context": "http://www.w3.org/ns/hydra/context.jsonld",
> "@type": "IriTemplate",
> "template": "http://api.example.com/issues{?q}",
> "mapping": [
> {
> "@type": "IriTemplateMapping",
> "variable": "q",
> "property": "http://laszlo.com/myquerylanguage",
> }
> ]
> }
>
> and then clients would need to understand your query language or just
> understand that there is some "q" that takes some value that has a type that
> they don't understand.
Thanks for the help! :-)
Received on Wednesday, 10 September 2014 18:58:26 UTC