16:59:20 <RRSAgent> RRSAgent has joined #json-ld
16:59:24 <RRSAgent> logging to https://www.w3.org/2023/02/01-json-ld-irc
16:59:24 <Zakim> RRSAgent, make logs Public
16:59:55 <Zakim> please title this meeting ("meeting: ..."), gkellogg
16:59:56 <gkellogg> meeting: JSON-LD WG
17:00:09 <gkellogg> rrsagent, make logs public
17:00:40 <juuso-aut> juuso-aut has joined #json-ld
17:01:02 <anatoly-scherbakov> anatoly-scherbakov has joined #json-ld
17:01:08 <anatoly-scherbakov> present+
17:01:36 <pchampin> present+
17:01:38 <gkellogg> present+
17:02:47 <gkellogg> chair: bigbluehat
17:03:04 <TallTed> present+
17:03:09 <bigbluehat> present+
17:03:41 <gkellogg> https://www.w3.org/events/meetings/cc5608da-eddd-4857-b849-293bcd25e8ad/20230201T120000
17:04:23 <TallTed> TallTed has changed the topic to: JSON-LD WG -- 2023-02-01 Agenda: https://www.w3.org/events/meetings/cc5608da-eddd-4857-b849-293bcd25e8ad/20230201T120000
17:05:24 <pchampin> scribe+
17:05:44 <pchampin> topic: WG rechartered
17:06:02 <pchampin> bigbluehat: first WG meeting in a while
17:06:11 <dlehn> present+
17:06:24 <pchampin> ... we have been rachartered
17:06:25 <pchampin> https://www.w3.org/2023/01/json-ld-wg-charter.html
17:06:30 <pchampin> ... until Jan 2025
17:06:35 <juuso-aut> present+
17:06:50 <pchampin> ... We were supposed to have meeting quatertly, which we didn't.
17:06:59 <pchampin> ... Instead, the CG did meet on a regular basis.
17:07:12 <pchampin> ... We need to improve the working model between both groups.
17:07:18 <pchampin> ... The quarterly WG calls must happen.
17:07:31 <pchampin> ... The CG calls can be on a per-need basis.
17:07:49 <gkellogg> q+
17:08:07 <pchampin> ... WG members must manually re-join the WG (participants to this call have already).
17:08:23 <pchampin> ... If you know any, remind them that they must rejoin.
17:08:25 <bigbluehat> Participants: https://www.w3.org/groups/wg/json-ld/participants
17:08:40 <pchampin> gkellogg: if you look at the participants list (when logged in)
17:09:04 <pchampin> ... there is an icon on the members having not re-joined yet
17:09:13 <pchampin> ... which includes some participants of this call
17:09:53 <pchampin> subtopic: future of the WG
17:10:14 <pchampin> bigbluehat: has anyone any idea before we go through other agenda items?
17:10:35 <pchampin> gkellogg: there are a number of errata, some of them normative.
17:10:56 <pchampin> ... There is also work in the RDF-star WG that might impact JSON-LD.
17:11:16 <pchampin> ... Some work in the CG about JSON-LD-star might become part of a future JSON-LD 1.2..
17:11:24 <pchampin> https://github.com/json-ld/json-ld-star
17:11:41 <pchampin> gkellogg: also a lot of activity since last summer in the CG around YAML-LD
17:11:52 <pchampin> ... we are considering publishing a final report
17:12:40 <pchampin> ... The charter mentions YAML-LD; the WG may chose to bring that on REC track.
17:13:07 <pchampin> bigbluehat: is the vision to let the CG tell us when they think this is ready?
17:13:24 <pchampin> gkellogg: yes, but the problem is finding time
17:14:13 <pchampin> ... But my feeling is that the CG work on YAML-LD could probably be put forward as a final report in its current state.
17:14:30 <pchampin> bigbluehat: we need to discuss this in the CG.
17:14:49 <pchampin> ... a CG final report does not need the same level of maturity as a REC.
17:14:59 <pchampin> dlehn: is anyone using YAML-LD?
17:15:05 <pchampin> anatoly-scherbakov: I am trying to.
17:15:19 <pchampin> juuso-aut: me as well.
17:15:44 <pchampin> anatoly-scherbakov: using YAML-LD for visualization purposes (converting YAML-LD to HTML)
17:15:54 <pchampin> ... I'm preparing an open-source tool.
17:16:24 <pchampin> ... I'm enthusiats about YAML-LD, I find it practical.
17:16:43 <pchampin> ... But I have not contributed much to the specification -- waiting more practical feedback.
17:16:44 <gkellogg> https://json-ld.github.io/yaml-ld-primer/
17:17:01 <pchampin> s/waiting more/waiting for more/
17:17:19 <pchampin> ... Devoting more time to it recently.
17:17:47 <pchampin> bigbluehat: could you take more editorial responsibility on the document?
17:17:53 <pchampin> anatoly-scherbakov: what would that entail?
17:18:32 <gkellogg> YAML-LD issues: https://github.com/json-ld/yaml-ld/issues
17:18:34 <gkellogg> q+
17:18:44 <pchampin> bigbluehat: identifying what is missing in the CG document to be elligible to REC track
17:18:56 <pchampin> ... CG documents don't need tests; WG documents do
17:19:09 <pchampin> anatoly-scherbakov: could do with a naive translation of JSON-LD tests
17:19:16 <TallTed> MUST test MUSTs; SHOULD test SHOULDs and MAYs, as these results can be differentiators when choosing which implementation(s) to deploy
17:19:34 <pchampin> ... But advanced features of YAML in YAML-LD need specific signs, but I am not using them.
17:19:58 <bigbluehat> ack gkellogg
17:20:08 <pchampin> ... I am doing the simplest possible thing (converting `@-keywords` into `$-keywords` with the context)
17:20:18 <juuso-aut> q+
17:20:36 <pchampin> gkellogg: I did work on tests, working on the extended internal representation
17:20:46 <pchampin> ... but we should keep this discussion for  a CG meeting.
17:20:58 <pchampin> ... I put a link above on the open issues.
17:21:09 <bigbluehat> ack juuso-aut
17:21:47 <pchampin> juuso-aut: We got  1,5 year project where we are planning to use YAML-LD.
17:22:06 <pchampin> ... But can't say how much time I can devote to standardization (it is a commercial project).
17:22:15 <pchampin> ... But at least I will continue to attend the calls.
17:22:41 <pchampin> bigbluehat: any other future documents?
17:22:56 <pchampin> ... At least we should address the errata more formally.
17:23:10 <pchampin> ... I don't think they affect any test.
17:23:32 <pchampin> gkellogg: for the errata considered editorial, the ED has already been updated.
17:24:05 <pchampin> ... I don't think there are any barrier to publishing this new version.
17:24:53 <pchampin> ... Normative errata do impact the tests,
17:25:08 <pchampin> ... but maybe we want to keep them until some JSON-LD 1.2 version,
17:25:26 <pchampin> ... which would also take into account the work in the RDF-star WG.
17:25:34 <pchampin> Topic: Next call
17:25:46 <pchampin> bigbluehat: I suggest we stick to the quarterly schedule for the WG
17:25:47 <anatoly-scherbakov> q
17:25:49 <anatoly-scherbakov> q+
17:25:58 <pchampin> ... and make CG calls in the meantime.
17:26:00 <gkellogg> ack anatoly-scherbakov
17:26:11 <pchampin> anatoly-scherbakov: I would be interested by CG meetings.
17:26:45 <pchampin> ... The homework consists in reading the current YAML-LD specification, and open issues, right?
17:26:53 <pchampin> bigbluehat: correct
17:27:14 <pchampin> gkellogg: The next CG meeting would be on Feb 15, this time.
17:27:58 <pchampin> bigbluehat: I should update the homepage, to clarify the relation between the WG and the CG.
17:28:08 <pchampin> TallTed: I don't think we should work as you suggest.
17:28:20 <pchampin> ... The WG and CG have very different patent policies.
17:28:48 <pchampin> bigbluehat: the YAML-LD needs to progress in the CG, where it started.
17:29:23 <pchampin> ... But we must be clear about which group is meeting, because of the patent policy differences.
17:29:45 <pchampin> TallTed: it should be really clear which documents belong to which group.
17:29:57 <pchampin> ... And encourage people in the CG to move work to the WG it it matters to them.
17:30:23 <pchampin> gkellogg: a blog post would be a good idea;
17:30:39 <pchampin> ... there is some fatigue after doing a lot of work;
17:30:46 <pchampin> ... we must encourage people to re-join.
17:31:44 <pchampin> ... We have refrained from reflecting any normative update in the ED, focusing on editorial ones.
17:31:48 <pchampin> TallTed: sounds good
17:32:36 <pchampin> bigbluehat: defining the responsibilities of WG vs CG will encourage people to join the WG
17:33:19 <pchampin> TallTed: most people don't keep up with the blog; they focus on the mailing list
17:33:45 <pchampin> bigbluehat: AOB?
17:34:09 <pchampin> gkellogg: for the next CG meeting, please send which issues you want to discuss
17:34:38 <gkellogg> zakim, end meeting
17:34:38 <Zakim> As of this point the attendees have been anatoly-scherbakov, pchampin, gkellogg, TallTed, bigbluehat, dlehn, juuso-aut
17:34:40 <Zakim> RRSAgent, please draft minutes
17:34:42 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-json-ld-minutes.html Zakim
17:34:49 <Zakim> I am happy to have been of service, gkellogg; please remember to excuse RRSAgent.  Goodbye
17:34:49 <Zakim> Zakim has left #json-ld
17:34:52 <gkellogg> rrsagent, publish minutes
17:34:54 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-json-ld-minutes.html gkellogg
18:11:02 <gkellogg> gkellogg has joined #json-ld
18:12:32 <gkellogg> gkellogg has joined #json-ld
18:21:18 <gkellogg> gkellogg has joined #json-ld
18:26:14 <gkellogg> gkellogg has joined #json-ld
18:42:59 <gkellogg> gkellogg has joined #json-ld
19:01:23 <gkellogg> gkellogg has joined #json-ld
19:09:09 <dlongley> dlongley has joined #json-ld
19:19:36 <gkellogg> gkellogg has joined #json-ld
19:26:28 <gkellogg> gkellogg has joined #json-ld