- From: Ivan Herman <ivan@w3.org>
- Date: Tue, 12 Mar 2019 11:02:28 +0100
- To: Ruben Taelman <ruben.taelman@ugent.be>
- Cc: W3C JSON-LD Working Group <public-json-ld-wg@w3.org>
- Message-Id: <CA9CA140-5925-4A96-8E10-ADF16D976668@w3.org>
Hi Ruben, > On 12 Mar 2019, at 10:43, Ruben Taelman <ruben.taelman@ugent.be <mailto:ruben.taelman@ugent.be>> wrote: > > Dear all, > > I had the pleasure of meeting some of the JSON-LD WG members > at the W3C graph data workshop in Berlin last week. > Since I have been working on a couple of JSON-LD related things, > Gregg suggested me to join the group, which I just did. > And you are very welcome! > I may be able to help out in the following ways: > > 1. I recently implemented a streaming JSON-LD parser in JavaScript, > for which I sent a mail to this list last month [1]. > Because of this, I can offer some insights on a potential streaming profile for JSON-LD [2]. > I understand that it was decided to not give this issue a high priority, > but it may be useful to include it as a side-note somewhere. > > 2. I can assist with the creation of the new JSON-LD 1.1 test suite, > since I used the JSON-LD 1.0 test suite quite extensively while implementing the streaming parser. > I also implemented a tool for running RDF test suites [3], > which may be useful for automating this execution. > > 3. I developed GraphQL-LD [4], as a way to lift JSON-like GraphQL queries > to the RDF domain using JSON-LD contexts. > This offers a nice use case for applying JSON-LD contexts to non-JSON things. > Following a discussion with Pierre-Antoine, this can motivate the need for > an extension mechanism for custom context keywords. > > I’m looking forward to help out wherever I can! > > Side-question: At what time is the weekly telco in CEST? To be very precise: the timing of the call is set in Boston, Cambridge MA time (after all, the center of the universe is at MIT, right?). In Cambridge the call is at noon. This means, usually, 6pm for you or I, but while the US is already in DST and Europe is not, it is indeed at 5pm for us. This will reverse back to 6pm in April. My side question: what is your preferred nickname on IRC? I need to administer that to get our minutes all right[1]. Thanks! Ivan [1] https://www.w3.org/2018/json-ld-wg/Meetings/#meeting-minutes <https://www.w3.org/2018/json-ld-wg/Meetings/#meeting-minutes> > According to the wiki [5], this should be 18:00, > but this conflicts with the information on a mail from last year [6] mentioning 17:00. > > [1] https://lists.w3.org/Archives/Public/public-json-ld-wg/2019Feb/0010.html <https://lists.w3.org/Archives/Public/public-json-ld-wg/2019Feb/0010.html> > [2] https://github.com/w3c/json-ld-api/issues/5 <https://github.com/w3c/json-ld-api/issues/5> > [3] https://github.com/rubensworks/rdf-test-suite.js <https://github.com/rubensworks/rdf-test-suite.js> > [4] https://comunica.github.io/Article-ISWC2018-Demo-GraphQlLD/ <https://comunica.github.io/Article-ISWC2018-Demo-GraphQlLD/> > [5] https://www.w3.org/2018/json-ld-wg/Meetings/ <https://www.w3.org/2018/json-ld-wg/Meetings/> > [6] https://lists.w3.org/Archives/Public/public-json-ld-wg/2018Oct/0015.html <https://lists.w3.org/Archives/Public/public-json-ld-wg/2018Oct/0015.html> > > Kind regards, > Ruben Taelman ---- Ivan Herman, W3C Publishing@W3C Technical Lead Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/> mobile: +31-641044153 ORCID ID: https://orcid.org/0000-0003-0782-2704 <https://orcid.org/0000-0003-0782-2704>
Received on Tuesday, 12 March 2019 10:02:33 UTC