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

RE: LevelGraph and JSONLD

From: Markus Lanthaler <markus.lanthaler@gmx.net>
Date: Thu, 18 Jul 2013 08:50:37 +0200
To: <public-linked-json@w3.org>
Message-ID: <000701ce8383$1e330e60$5a992b20$@lanthaler@gmx.net>
On Wednesday, July 17, 2013 5:27 PM, Matteo Collina wrote:
> 2013/7/17 Markus Lanthaler <markus.lanthaler@gmx.net>
>> I'm wondering whether this is a simple key-value store where the value is
>> the JSON-LD document as-is or whether you process the document before
>> storing it.
>
> I convert the document into triples, actually I call toRDF

Makes sense.. You should probably clarify that in the readme though as I
believe a lot of people would otherwise assume that they get the same
document back in a get.

>> It would probably make sense to somehow integrate framing [1] so that you
>> can query for data and return in a specific form to simplify its
processing.
>
> That will be super, but I am not sure how to implement.
> Albeit powerful, the whole framing business is somewhat to me (and the doc
> does not help).
> Could you please make an example?

The idea is that you can "query" the data and return it in a specific shape.
For example, I could write a frame like (omitting the context for
simplicity):

{
  "@type": "foaf:Person",
  "foaf:made": {
    "@type": "foaf:Document"
  }
}

That would return all Persons that made one or more documents.

While the (outdated) spec filters only based on @type my implementation
allows you to filter on any property. The more interesting part though is
that you won't get a flattened result but a result in a user-specified tree
structure.

Does that clarify it a bit?


--
Markus Lanthaler
@markuslanthaler
Received on Thursday, 18 July 2013 06:51:11 UTC

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