W3C home > Mailing lists > Public > public-linked-json@w3.org > May 2013

Re: Query languages LDPath / JSON-LD Framing

From: Andreas Kuckartz <A.Kuckartz@ping.de>
Date: 7 May 2013 23:03:38 +0200
Message-ID: <51896C2A.5050303@ping.de>
To: "Markus Lanthaler" <markus.lanthaler@gmx.net>
Cc: public-linked-json@w3.org
Markus Lanthaler:
>> Remote data: this is for the oparl.de standard.
>
> I knew it :-)

Surprise ;-)

> I'm working on an approach called Hydra [1] (as you know). It allows
> you to define URI templates and bind the variables to properties
> (predicates). So it's similar to a form and should provide the
> functionality you are looking for. Unfortunately I haven't found the
> time yet to document it properly. You could use it as follows in your
> APIs home document (using prefixes):
>
> {
>   "@context": {
>     "@vocab": "http://purl.org/hydra/core#",
>     "oparl": "http://oparl.de/vocab#",
>   }
>   ... other data ...
>   "oparl:search": {
>     "template": "http://example.com/search{?user,state}",
>     "mappings": [
>       { "variable": "user", "property": "oparl:user" },
>       { "variable": "state", "property": "oparl:state" }
>     ]
>   }
> }
>
> The advantage is that a client doesn't need to know anything
> beforehand. It can discover the interface at runtime which brings you
> quite a lot of flexibility.

That sounds interesting.

> Do you know what queries you need to support? Or do you need to query
> the data by arbitrary criterions?

Arbitrary criteria probably do not need to be supported (if that were
the case I probably would suggest SPARQL). Details will be discussed
"officially" using the issue tracker on and after June 20 (in German,
but I guess that English comments would also be welcome ;-):
https://github.com/OParl/specs/issues/30

Cheers,
Andreas
Received on Tuesday, 7 May 2013 21:20:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:37 UTC