15:07:57 <RRSAgent> RRSAgent has joined #json-ld
15:07:57 <RRSAgent> logging to https://www.w3.org/2020/03/20-json-ld-irc
15:08:00 <Zakim> RRSAgent, make logs Public
15:08:01 <Zakim> please title this meeting ("meeting: ..."), ivan
15:08:08 <ivan> ivan has changed the topic to: Meeting Agenda 2020-03-20: https://lists.w3.org/Archives/Public/public-json-ld-wg/2020Mar/0011.html
15:08:09 <ivan> Date: 2020-03-20
15:08:09 <ivan> Agenda: https://lists.w3.org/Archives/Public/public-json-ld-wg/2020Mar/0011.html
15:08:09 <ivan> Chair: azaroth
15:08:09 <ivan> Meeting: JSON-LD Working Group Telco
15:12:38 <ajs6f> ajs6f has joined #json-ld
15:51:27 <gkellogg> gkellogg has joined #json-ld
15:52:54 <rubensworks> rubensworks has joined #json-ld
15:57:04 <pchampin> pchampin has joined #json-ld
15:59:30 <gkellogg> present+
15:59:34 <azaroth> azaroth has joined #json-ld
15:59:38 <azaroth> present+
16:00:16 <rubensworks> present+
16:01:20 <ajs6f> present+
16:01:23 <pchampin> present+
16:01:24 <bigbluehat> present+
16:02:34 <timCole> timCole has joined #json-ld
16:02:52 <ivan> present+
16:03:00 <timCole> present+
16:03:03 <pchampin> scribe: pchampin
16:03:08 <azaroth> TOPIC: Announcements
16:03:45 <pchampin> azaroth: any update on editorial changes?
16:04:02 <pchampin> gkellogg: some non-normative changes
16:04:18 <pchampin> ... `@prefix=false` may need some precision in the syntax document
16:04:43 <pchampin> ... requires some examples
16:05:24 <pchampin> ... Most other pull-requests are about tests.
16:06:13 <pchampin> One more: clarification in the "inverse context creation" algo;
16:06:19 <pchampin> ... One more: clarification in the "inverse context creation" algo;
16:06:28 <azaroth> SUBTOPIC: no-response API editorial changes
16:06:31 <pchampin> ... some steps were reordered, and an "otherwise" was missing.
16:07:09 <pchampin> azaroth: we resolved to close a number of issues if we did'nt hear about them until today,
16:07:12 <pchampin> ... and we didn't.
16:07:56 <hsolbrig> hsolbrig has joined #json-ld
16:07:57 <hsolbrig> present+
16:08:32 <pchampin> ... Greg (kasei) did some changes related to the issues he submitted
16:08:38 <pchampin> ... which fixed some tests, but broke others.
16:08:45 <pchampin> ... He was happy with those issues being closed.
16:09:44 <pchampin> azaroth: XXX was worried that nobody implemented Framing from scratch.
16:09:52 <dlehn> present+
16:09:53 <pchampin> gkellogg: Framing has changed quite a lot since 1.0.
16:09:54 <azaroth> s/XXX/Greg W/
16:10:13 <azaroth> SUBTOPIC:  Other announcements / reminders?
16:10:53 <pchampin> gkellogg: there are signs of life of various repositories.
16:10:55 <ivan> q+
16:11:23 <pchampin> hsolbrig: Some work is happening on RDFlib.
16:11:32 <azaroth> ack ivan
16:12:02 <pchampin> ivan: I recently hit some issue with RDFlib,
16:12:08 <pchampin> q+
16:12:20 <pchampin> ... it seemed that nobody was touching the core of the lib.
16:12:38 <pchampin> ... It does not work with recent versions of Python 3.
16:12:56 <pchampin> hsolbrig: yes, there has been much activity recently.
16:13:01 <azaroth> ack pchampin
16:13:07 <azaroth> scribe+
16:13:28 <azaroth> pchampin: One of my old PRs for rdflib was accepted :)
16:13:34 <azaroth> q?
16:14:07 <azaroth> q?
16:14:24 <pchampin> azaroth: any other implementation?
16:14:39 <pchampin> gkellogg: I switched from jsonld-js to pyld,
16:14:43 <pchampin> ... solved a few issues there.
16:15:23 <pchampin> azaroth: another issue we ran into.
16:15:36 <pchampin> ... we have a pipeline generating many JSON-LD files,
16:15:51 <pchampin> ... converting them to RDF and storing them in a triple store.
16:16:15 <pchampin> s/may/millions of/
16:16:18 <gkellogg> q+
16:16:27 <pchampin> ... Context processing is taking a lot of time.
16:16:33 <azaroth> ack gkellogg
16:16:37 <pchampin> ... Some caching would be beneficial.
16:16:55 <pchampin> gkellogg: we have that guidance stating that implementations should cache contexts,
16:17:21 <pchampin> ... something that was asked in particular by danbri about the schema.org context.
16:17:30 <pchampin> ... Standard HTTP caching can be used,
16:17:54 <pchampin> ... but my implementation also has an ad-hoc cache, storing contexts in their internal representations.
16:19:00 <hsolbrig> q+
16:19:04 <pchampin> ... We might recommend a set of techniques for doing that.
16:19:43 <azaroth> ack hsolbrig
16:20:28 <pchampin> hsolbrig: we find ourselves modularizing contexts a lot,
16:20:34 <azaroth> q?
16:20:42 <pchampin> ... rather than having one big context covering everything.
16:20:46 <pchampin> ... So we rely on caching a lot.
16:20:47 <dlehn> q+
16:20:56 <azaroth> ack dlehn
16:21:12 <pchampin> azaroth: gkellogg, Greg W and I will have a call about this next week.
16:21:16 <pchampin> ... If anyone wants to join...
16:21:34 <dlehn> jsonld.js has some support for caching too
16:22:32 <pchampin> gkellogg: in jsonld.js and pyld, the internal representation of contexts is basically a dictionnary.
16:23:06 <pchampin> ... caching the result of "context processing" is quite easy.
16:23:29 <azaroth> q?
16:23:29 <azaroth> q?
16:24:21 <pchampin> gkellogg: last week, I said I wanted to merge the expand and toRdf test suites.
16:24:39 <pchampin> ... there has been a big PR unifying the naming, which should make this easier.
16:24:46 <azaroth> TOPIC: Technical Issues
16:25:09 <pchampin> azaroth: I don't think we have any tech issue?
16:25:20 <pchampin> hsolbrig: I found one yesterday, actually...
16:25:32 <azaroth> https://github.com/w3c/json-ld-syntax/issues/339
16:26:57 <pchampin> ... the term IRI ends with a gendelim, so it looks like a valid prefix
16:27:02 <gkellogg> q+
16:27:17 <azaroth> ack gkellogg
16:27:25 <pchampin> ... RDFlib uses it as a prefix, even when `@prefix=false` is set.
16:27:56 <pchampin> gkellogg: it is an internal representation issue, it has nothing to do with JSON-LD
16:28:03 <hsolbrig> q+
16:29:27 <pchampin> ... the API document is clear, `@prefix=false` prevents the term to be used as a prefix
16:29:32 <azaroth> ack hsolbrig
16:29:33 <pchampin> ... in expansion or compaction.
16:29:43 <pchampin> ... But the syntax documents needs some clarification.
16:30:00 <azaroth> Playground: http://tinyurl.com/rpddoss
16:30:16 <pchampin> hsolbrig: I don't go to the API doc for this kind of issue.
16:30:30 <pchampin> ... Fixing the syntax document is good for me.
16:31:37 <pchampin> azaroth: this kind of example can be useful for having human-readable types
16:32:00 <pchampin> ... Is it worth puting an editorial note about spaces?
16:32:35 <hsolbrig> q+
16:32:40 <pchampin> gkellogg: we made a provision for the empty string, and terms ending with a colon,
16:32:47 <pchampin> ... but where would we stop? What about tabs?
16:33:01 <azaroth> acj hsolbrig
16:33:04 <azaroth> ack hsolbrig
16:33:24 <pchampin> hsolbrig: this kind of example will creep up more and more.
16:33:49 <pchampin> ... When importing data from spreadsheets, spaces (in headers) may be common.
16:34:26 <pchampin> gkellogg: we could put some restrictions on terms used as prefix...
16:34:29 <azaroth> q?
16:35:33 <pchampin> ... In CSVW we addressed this kind of issues, using URI patterns.
16:35:33 <azaroth> TOPIC:  Notes
16:35:55 <pchampin> azaroth: rubensworks, any progress on the Streaming note?
16:35:58 <azaroth> SUBTOPIC: Streaming Note
16:36:20 <pchampin> rubensworks: I opened a new PR this morning. Not sure it needs to be reviewed.
16:36:38 <pchampin> ... Once merged, I will ask people to go to through the whole doc.
16:36:48 <rubensworks> https://github.com/w3c/json-ld-streaming/pull/4
16:36:52 <rubensworks> https://w3c.github.io/json-ld-streaming/
16:37:15 <pchampin> ... Everything I want to have in that note is present now.
16:37:34 <pchampin> .. Feel free to open an issue if you think something is missing.
16:37:51 <pchampin> gkellogg: have you considered having a kind of test suite for streaming?
16:38:20 <pchampin> rubensworks: we could add a few tests (`@context` and `@type` not in the correct order)
16:38:36 <pchampin> ... Let me add it to my list.
16:39:03 <pchampin> ... That suite would be quite small. There are only a few restrictions.
16:39:38 <azaroth> q?
16:39:38 <azaroth> SUBTOPIC: CBOR
16:40:47 <azaroth> SUBTOPIC: Best Practices?
16:40:53 <azaroth> [crickets]
16:40:58 <pchampin> pchampin: no activity there, France is stuck in confinement right now
16:41:07 <pchampin> s/there/on CBOR/
16:41:59 <pchampin> hsolbrig: we would be interested in getting access to the original order in JSON lists,
16:42:07 <pchampin> ... in order to apply our own sorting algorithms.
16:42:20 <pchampin> ... But I understand this goes beyond the scope.
16:42:42 <bigbluehat> https://www.w3.org/TR/csv2json/
16:42:45 <gkellogg> https://www.w3.org/TR/tabular-metadata/
16:42:57 <pchampin> gkellogg: you should look as CSVW, it might help address your use case
16:43:02 <azaroth> q?
16:43:11 <azaroth> TOPIC: AoB?
16:43:13 <rubensworks> q+
16:43:29 <rubensworks> https://www.rubensworks.net/blog/2019/03/13/streaming-rdf-parsers/
16:43:45 <pchampin> rubensworks: a while ago, I wrote this blog post.
16:43:57 <pchampin> ... Would it be valuable to link to that within the note. Is it appropriate?
16:44:41 <pchampin> ivan: It is a note, so I don't think this would be a problem.
16:45:02 <pchampin> rubensworks: I will include it then.
16:45:26 <azaroth> ack rubensworks
16:45:26 <azaroth> SUBTOPIC: Streaming, redux
16:45:43 <pchampin> ... Any specific process for finalizing the note?
16:46:14 <pchampin> ivan: we have to have a formal resolution, then go through the webmaster.
16:46:40 <pchampin> ... This is easy, mostly administrative (getting an ID).
16:46:56 <pchampin> azaroth: any preferred short name for it?
16:46:57 <gkellogg> json-ld11-streaming?
16:47:13 <azaroth> +1
16:47:17 <ivan> +1
16:47:37 <rubensworks> +1
16:47:40 <azaroth> PROPOSAL: Short name for streaming note should be json-ld11-streaming
16:47:41 <gkellogg> +1
16:47:41 <azaroth> +1
16:47:44 <ajs6f> +1
16:47:44 <dlehn> +1
16:47:46 <timCole> +1
16:47:47 <pchampin> +1
16:47:47 <rubensworks> +1
16:47:55 <hsolbrig> +1
16:47:57 <bigbluehat> +1
16:48:01 <azaroth> RESOLVED: Short name for streaming note should be json-ld11-streaming
16:48:16 <pchampin> azaroth: anything else?
16:48:16 <bigbluehat> q+
16:48:17 <dlehn> here's some JSON-LD helps save the world news: http://blog.schema.org/2020/03/schema-for-coronavirus-special.html
16:48:20 <azaroth> ack bigbluehat
16:48:59 <bigbluehat> https://schema.org/CovidTestingFacility - maybe build stuff with this to help folks :)
16:48:59 <pchampin> bigbluehat: shows how JSON-LD and CSVW can be useful.
16:49:58 <azaroth> q?
16:50:02 <bigbluehat> twitters about it https://twitter.com/westurner/status/1239938629310410752
16:50:46 <azaroth> TOPIC: Adjourn
16:51:03 <ivan> zakim, end meeting
16:51:03 <Zakim> As of this point the attendees have been gkellogg, azaroth, rubensworks, ajs6f, pchampin, bigbluehat, ivan, timCole, hsolbrig, dlehn
16:51:05 <Zakim> RRSAgent, please draft minutes
16:51:05 <RRSAgent> I have made the request to generate https://www.w3.org/2020/03/20-json-ld-minutes.html Zakim
16:51:08 <Zakim> I am happy to have been of service, ivan; please remember to excuse RRSAgent.  Goodbye
16:51:12 <Zakim> Zakim has left #json-ld
16:51:44 <ivan> rrsagent, bye
16:51:44 <RRSAgent> I see no action items