15:30:37 RRSAgent has joined #json-ld 15:30:37 logging to https://www.w3.org/2018/06/22-json-ld-irc 15:30:41 rrsagent, set log public 15:30:41 Meeting: JSON-LD Working Group Telco 15:30:41 Chair: azaroth 15:30:41 Date: 2018-06-22 15:30:41 Regrets+ tcole, leonardr 15:30:41 Agenda: https://lists.w3.org/Archives/Public/public-json-ld-wg/2018Jun/0002.html 15:30:42 ivan has changed the topic to: Meeting Agenda 2018-06-22: https://lists.w3.org/Archives/Public/public-json-ld-wg/2018Jun/0002.html 15:32:50 azaroth has joined #json-ld 15:34:05 Morning! 15:49:40 zakim, what is this? 15:49:40 I don't understand your question, azaroth. 15:49:59 simonstey has joined #json-ld 15:50:16 zakim, this is json-ld 15:50:16 got it, azaroth 15:51:16 present+ Rob_Sanderson 15:52:23 present+ Ivan_Herman 15:52:36 ajs6f has joined #json-ld 15:56:46 present+ Benjamin_Young 15:56:52 present+ Adam Soroka 15:57:02 present+ simonstey 15:58:16 present+ dlehn 15:58:45 regrets+ Dave_Longley 15:59:03 regrets+ Jeff_Mixter 15:59:55 present+ Gregg_Kellogg 16:00:14 regrets+ Axel_Polleres 16:02:47 ivan: That is scriptjs? 16:03:05 ivan: ty! 16:04:11 scribe: simonstey 16:04:40 uh oh! 16:04:47 s/uh oh!// 16:05:31 topic: Welcome & Introduction 16:05:33 bigbluehat: Yes, ty-- I got myself updated there. 16:05:51 azaroth: we'll make a short introduction round and will go over the charter 16:06:03 s/bigbluehat: Yes, ty-- I got myself updated there.// 16:06:16 ... giving an overview about the wg's working mode 16:06:39 ... TPAC is in october, we'll have a meeting there and registration is already open 16:07:40 hsolbrig has joined #json-ld 16:08:05 azaroth: semantic architect for gettys trust, I'm one of the chairs of the group 16:08:18 ... have also been the chair of the annotation WG 16:08:58 ... we use json-ld @ getty, also in a profile of a complicated museum ontology 16:09:39 ... bridge the gap between pure semantic web folks and web developers that don't care so much about semantic stuff but want to get stuff done 16:10:02 ivan: I'm the staff contact for this group, I'm used to be the activity lead for SW 16:10:25 ... I have a long relationship with json-ld, done a lot in publishing WGs 16:10:45 ... I'm now drawn back in a SW WG again 16:11:35 ... we are active in the web application WG, the manifest will be based on json-ld & schema.org 16:11:47 ... so another use(r) of json-ld 16:12:09 ... I'll take care of cleaning up minutes 16:12:40 ajs6f: from the apache foundation 16:13:41 ... we have a prime interest in being able to bring together information from various domains 16:13:50 ... RDF and json-ld are the way to go there 16:14:14 ... the apache side is very eager to contribute and see what kind of implementations are being realized 16:14:52 bigbluehat: worked with ivan in the annotation WG 16:15:08 ... co-chairing this WG 16:15:34 ... I'm with Wiley 16:16:40 hsolbrig: I'm with the Mayo Clinic 16:17:29 ... some communities we work with realized that they need readability/accessability of JSON 16:17:33 Hi, I'm David Lehn with Digital Bazaar. We've been involved with JSON-LD since the early days and continue to use and promote it for many uses. I've been involved in part in the specs, website, and js and python implementations. 16:18:38 ... my interest is primarily based on keeping ShEx aligned with JSON-LD 16:18:56 gkellogg: I'm one of the 3 editors of JSON-LD 1.0 recs 16:19:27 https://www.w3.org/community/json-ld/ 16:19:53 https://json-ld.org/presentations/JSON-LD-Update-TPAC-2017 16:19:53 ... I resurrected the JSON-LD CD and we worked together on serialization/syntax/API and framing 16:20:25 ... this document highlights the things the group wanted to work on 16:20:44 scribe: azaroth42 16:21:12 simonstey: I'm with Vienna university, together with Axel Polleres. Also research scientist at Siemens. Mostly have university hat on for W3C 16:21:41 ... joined as because craving some standardization activities. Was in SHACL group, and ??? with Ivan. 16:21:50 s/???/ODRL/ 16:22:21 ... Both have finished. Content wise, interested in JSON-LD 1.1 through work at siemens by reading through framing. Describes the /shape/ of the document, so see connection to ShEx / SHACL 16:22:45 ... from Axel, he says I should say that he is interested to see how nested lists in RDF can be included 16:23:07 scribenick: simonstey 16:23:33 topic: overview of the charter 16:23:42 Topic: overview of the charter 16:23:51 charter: https://www.w3.org/2018/03/jsonld-wg-charter.html 16:24:53 ivan: the interest W3C has in this WG is the potential bridge JSON-LD provides 16:25:06 ... bringing together SW and non-SW folks 16:25:25 ... the charter starts with 3 documents 16:25:58 ... we have the possibility to split a document into two recs if we feel that it gets too long 16:26:24 ... especially things regarding HTTP 16:27:10 ... we may want to have a separate note on how things would look like in YAML 16:27:41 ... or other things we might consider being worthwhile 16:28:04 ... there are things we deliberately left out, like ??? 16:28:34 s/???/RDF Normalisation and Linked Data Signatures/ 16:29:17 ... we try to be more normalized with RDF terms than 1.0 was 16:29:34 ... other things are related to privacy issues 16:30:03 ... i.e. downloading the same context file multiple times could allow others to trace your activities 16:30:49 ... we should also look at optimization/efficiency issues in more detail 16:31:22 ... timeline-wise, we hoped to have a WG with a lifespan of 1 1/2 years 16:31:47 ... but due to mentioned privacy issues, we decided to make it 2 years 16:32:10 ... FPWD is planned to be published in september (earlier is ofc possible) 16:32:59 gkellogg: we did have a chat with Web of Things, so they might join our calls at some point 16:33:37 ... we might need a way to be able to reference a context file without having the need to download it 16:34:10 ... we have to look for ways of addressing the complexity of our specs 16:34:27 ... esp. wrt. illegal values 16:35:00 azaroth: we were urged by google and others to not break existing JSON-LD documents 16:35:43 profile might mean form (expanded, compacted, …) use of specific context or frame. 16:35:49 ... other things of interest include verifying whether a document conforms to a certain profile 16:36:02 Topic: Working Mode 16:36:25 https://www.w3.org/2018/json-ld-wg/WorkMode/ 16:36:43 ivan: this document was reviewed by the chairs 16:36:59 ... if something is missing, please just make a pull request 16:37:10 ... we are heavily github based 16:37:22 ... all 3 documents we have are on separate github repos 16:37:55 ... we like to have all minor and major issues resolved via github issues 16:38:19 ... we've added a lot of labels, so please make use of them 16:38:35 ... ask questions! 16:38:49 ... mailing lists will mostly be used for admin stuff 16:39:17 ... very generic discussions might also be done there, but for the most things please use github 16:40:19 ... we have a call each week, 9h difference between some members of the WG 16:41:09 ... I hope this timing works for most members, we'll look at it again in 2-3 months 16:42:26 ... think about non-english natives and talk slower if possible 16:42:46 hsolbrig 16:42:56 (my github id) 16:43:21 ... each WG has a wiki, you can be assigned to review issues/be referenced in issues etc. 16:43:29 s/hsolbrig// 16:43:33 s/(my github id)// 16:44:25 azaroth: please do speak up if you are not familiar with certain jargon/words/phrases 16:45:45 workergnome has joined #json-ld 16:45:49 ... we as chairs/staff contact will make sure to highlight whether we have our participantor chair hat on 16:46:29 ... we certainly also have our opinions, but sometimes have to make certain decisions to keep things going 16:46:40 q+ 16:46:59 ack ivan 16:47:00 ack ivan 16:47:08 ... we might decide to shift discussions to github/mail etc. 16:47:47 ivan: you can queue up with q+, don't just talk over everyone else 16:48:04 ... you can remove yourself from the queue with q- 16:48:08 persent+ David_Newbury 16:48:15 present+ David_Newbury 16:48:27 ... we try to encourage a distributed way of making decisions 16:49:12 ... so any decision we make on a call, becomes "official" after a week (i.e. the next call) 16:49:59 workergnome: David Newbury, I'm working with rob on linked data stuff 16:50:19 ... figuring out how to do all the implementation stuff related to json-ld 16:50:37 ... that's my goal for this wg 16:50:38 Sure--my GitHub handle is @workergnome 16:50:50 s/Sure--my GitHub handle is @workergnome// 16:51:06 q+ 16:51:16 ack gkellogg 16:51:25 bigbluehat: please use /me for things you dont want to have in the minutes 16:51:46 gkellogg: we currently have 4 different repos, all of which have issue lists 16:51:49 Our repos list: https://github.com/search?q=topic%3Ajson-ld-wg+org%3Aw3c&type=Repositories 16:52:06 ... how we want to manage those cross-over issues? 16:52:24 q+ 16:52:25 azaroth: we'll move over issues from the community group 16:52:30 ack ajs6f 16:53:06 ajs6f: github does have the ability to have "projects" which may or may not be a way to manage the issue gkellogg mentioned 16:53:15 q+ 16:53:19 ack bigbluehat 16:53:23 ivan: it's up to the WG to use projects 16:53:50 bigbluehat: we won't be able to use projects on the organization level (that being W3C) 16:53:59 q+ 16:54:05 ack ivan 16:54:08 ack ivan 16:54:08 ... but we could make it ??? 16:54:52 q? 16:54:57 ivan: W3C has a process of regularly backing up its github content 16:55:15 topic: TPAC 16:55:26 ... so I don't think it would be beneficial to move it outside the w3c scope 16:55:42 azaroth: end of october in france 16:55:58 ... we'll have a 2 day F2F meeting 16:56:11 https://www.w3.org/2018/10/TPAC/ 16:56:13 https://www.w3.org/2018/10/TPAC/ 16:56:21 ... the more people we are the better 16:56:27 q+ 16:56:52 q+ to mention our WG is on Thursday & Friday 16:56:58 ... the registration for tpac is already open, the prices have been gone up (again) 16:57:11 q- 16:57:35 ... the early bird rate ends at the end of july 16:58:11 ack bigbluehat 16:58:11 bigbluehat, you wanted to mention our WG is on Thursday & Friday 16:58:25 ... [some issues regarding hotel rates mentioned] 16:58:28 https://www.w3.org/2018/10/TPAC/schedule.html#Thursday 16:58:36 bigbluehat: WG is meeting on thursday/friday 16:58:55 q+ 16:59:00 ... if you can make it for the whole week, I can highly recommend it 16:59:04 ack ivan 16:59:36 ivan: this WG exists, because of a ad-hoc meeting @ last year's tpac 17:00:20 azaroth: there will likely be other F2F meetings outside of tpac 17:00:40 ... if people are interested in hosting them, let us chairs know 17:01:18 ... also if couple of members are going to the same conference this could also be a good opportunity to meet 17:01:33 ... next friday same time, we'll meet again 17:01:43 rrsagent, draft minutes 17:01:43 I have made the request to generate https://www.w3.org/2018/06/22-json-ld-minutes.html ivan