W3C home > Mailing lists > Public > public-linked-json@w3.org > October 2016

Re: Reactivating the CG to work on updated versions of the specs

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Mon, 10 Oct 2016 15:50:52 -0700
Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, Linked JSON <public-linked-json@w3.org>
Message-Id: <DC5A6F53-6CE4-4D10-BCE6-541CD99DAA57@greggkellogg.net>
To: George Svarovsky <gsvarovsky@idbs.com>
> On Oct 10, 2016, at 2:32 AM, George Svarovsky <gsvarovsky@idbs.com> wrote:
> 
> Hi Markus & Gregg & everyone

Hi George, glad to have you! Please consider joining the Community Group [1], which simplifies IP issues.

> I've worked with JSON-LD since 2013, for IDBS internal POC work, including prototype APIs and indexing in elasticsearch. I'd like to make it the lingua franca of our foundational APIs going forward. So although I'm not currently a 'heavy user', I'd like to become one! and I'd be very happy to be involved in the new wave of progress.
> 
> I have a particular interest in framing, and I concur with Markus that what I actually want is (some degree of) graph query. I have some thoughts, which I'll write out in a new thread.

I think there are several ways we could go:

1) Improve framing based on the existing algorithms which provide some degree of manipulating and limiting the framed data based on existing relationships.
2) Consider a way to include a variable syntax, and how this might be used for both matching and constructing data
3) Consider the implications of using SPARQL via de-serialization from JSON-LD to the RDF data model, performing a SPARQL query operation, and re-serializing back to JSON-LD and framing using some variation of the existing algorithms.

I’m certainly interested in hearing suggestions on other approaches, along with some use cases/examples.

> Otherwise do let me know the best way I can help…

Excellent.

> George
> 
> George Svarovsky | Technical Director | IDBS
> gsvarovsky@idbs.com | www.idbs.com | @gsvarovsky

Gregg

[1] https://www.w3.org/community/json-ld/participants

> -----Original Message-----
> From: Markus Lanthaler [mailto:markus.lanthaler@gmx.net]
> Sent: 10 October 2016 09:55
> To: 'Linked JSON' <public-linked-json@w3.org>
> Subject: RE: Reactivating the CG to work on updated versions of the specs
> 
> It is great to see you taking the initiative on this Gregg!
> 
> On 30 Sep 2016 at 11:31, Gregg Kellogg wrote:
>> JSON-LD 1.0 and JSON-LD API 1.0 have been out and successful for many years now.
>> JSON-LD has succeeded beyond the wildest dreams of the CG, thanks to broad adoption.
> 
> Indeed!
> 
> 
>> Additionally, the Framing algorithm [2] has proven to be important,
>> but work on the specification was never complete, and implementations
>> have moved beyond what was documented in any case.
> 
> It is certainly handy but I'm not sure there's agreement on what exactly it should be. Initially it was just (or at least mostly) about re-framing an existing graph... I think what a lot of people (myself included) actually want and need is to query a graph and control the serialization of the result. Maybe we should start with a discussion on the role of framing!?
> 
> 
>> I think it’s time to get back to these documents to create a future
>> 1.1 Community Group release of the specifications;
> 
> 1.1 sounds like minor tweaks to the existing official W3C specifications but some of the discussions and proposals I just saw go way beyond that. What do you consider to be in scope for 1.1?
> 
> 
>> At this point, I’d be happy to see active engagement on the mailing
>> list to move these issues forward; I’m prepared to do the heavy
>> lifting on the specification documents, and to maintain tests and my
>> own Ruby implementation to match. Hopefully, other implementors and
>> heavy users can actively engage in making this happen (perhaps an hour
>> a week). It may be that we’ll want to start up the bi-weekly calls we used to discuss and resolve on these issues prior to moving into the RDF WG.
> 
> I'd definitely like to help with this but unfortunately my spare cycles are quite limited.
> 
> 
> Cheers,
> Markus
> 
> 
> --
> Markus Lanthaler
> @markuslanthaler
> 
> 
> The content of this e-mail, including any attachments, is confidential and may be commercially sensitive. If you are not, or believe you may not be, the intended recipient, please advise the sender immediately by return e-mail, delete this e-mail and destroy any copies.
Received on Monday, 10 October 2016 22:51:22 UTC

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