17:02:25 <RRSAgent> RRSAgent has joined #json-ld
17:02:29 <RRSAgent> logging to https://www.w3.org/2026/02/11-json-ld-irc
17:02:29 <Zakim> RRSAgent, make logs Public
17:02:30 <Zakim> please title this meeting ("meeting: ..."), bigbluehat
17:02:37 <bigbluehat> meeting: JSON-LD WG
17:02:37 <bigbluehat> chair: bigbluehat, VictorLu
17:02:37 <bigbluehat> present+
17:02:52 <TallTed> present+
17:03:00 <bigbluehat> agenda: https://www.w3.org/events/meetings/de31b974-ca9c-4325-bcea-60b91a1b78d9/20260211T120000/
17:03:00 <agendabot> clear agenda
17:03:00 <agendabot> agenda+ Announcements and Introductions
17:03:00 <agendabot> agenda+ JSON-LD Issue Discussion and Organization
17:03:00 <agendabot> agenda+ Open Discussion
17:03:08 <RRSAgent> I have made the request to generate https://www.w3.org/2026/02/11-json-ld-minutes.html TallTed
17:03:23 <niklasl> present+
17:03:54 <TallTed> previous meeting: https://www.w3.org/2026/02/04-json-ld-minutes.html
17:03:54 <TallTed> next meeting: https://www.w3.org/2026/02/18-json-ld-minutes.html
17:04:08 <anatoly-scherbakov> present+
17:04:46 <RRSAgent> I have made the request to generate https://www.w3.org/2026/02/11-json-ld-minutes.html TallTed
17:06:17 <dlehn> present+
17:06:38 <TallTed> q+
17:06:53 <bigbluehat> topic: Discussing auto-scribing
17:07:28 <ivan> present+
17:13:43 <ivan> q+
17:13:49 <bigbluehat> ack TallTed
17:13:52 <TallTed> q-
17:13:52 <bigbluehat> ack ivan
17:15:03 <bigbluehat> topic: other respec tooling
17:16:08 <niklasl> https://datatracker.ietf.org/doc/html/rfc8610 ?
17:16:23 <dlehn> q+
17:17:13 <bigbluehat> ack dlehn
17:17:16 <bigbluehat> scribe+
17:17:22 <bigbluehat> ivan: do we use CDDL?
17:18:42 <RRSAgent> I have made the request to generate https://www.w3.org/2026/02/11-json-ld-minutes.html TallTed
17:18:52 <bigbluehat> Wes: no. we don't
17:19:30 <niklasl> scribe+
17:19:58 <ajs6f> ajs6f has joined #json-ld
17:20:25 <niklasl> bigbluehat: Let's look at open PRs for yaml-ld and cbor-ld and relate issues to them Timebox 20 min each.
17:20:28 <bigbluehat> topic: YAML-LD PRs and/or Issues
17:20:31 <bigbluehat> https://github.com/w3c/yaml-ld/pulls
17:20:42 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/pull/166
17:20:42 <gb> s|https://github.com/w3c/yaml-ld/pull/166|-> Pull Request 166 Specify editors, authors, and contributors (by anatoly-scherbakov) https://github.com/w3c/yaml-ld/pull/166
17:20:59 <niklasl> https://github.com/w3c/yaml-ld/pull/166 is missing reviews
17:21:31 <ivan> q+
17:21:47 <bigbluehat> ack ivan
17:22:40 <niklasl> ivan: We need to add the affiliations of the persons; either real for membr orgs., or "invited expert"
17:22:44 <anatoly-scherbakov> q+
17:22:54 <TallTed> q+
17:23:03 <bigbluehat> ack anatoly-scherbakov
17:23:05 <niklasl> ... Did we agree to keep Gregg or how do we otherwise acknowledge him?
17:24:22 <niklasl> anatoly-scherbakov: I'll add affiliations. My understanding of editors and former editors is that if they've contributed to this version, they're (current) editors, otherwise (prev. spec) as "former". Therefore Gregg is editor for this one (1.0).
17:24:25 <bigbluehat> q?
17:25:15 <bigbluehat> ack TallTed
17:25:21 <niklasl> ivan: To formal rule for this; my take is that editor is for contacting the person to talk about this document. We can have a former editors section and/or keep the authors, but I think keeping as editor won't work.
17:25:42 <ajs6f> ajs6f has joined #json-ld
17:25:57 <niklasl> TallTed: I think we need to get a more common agreement on this. I agree with the logic of Ivan though.
17:26:11 <ajs6f> present+
17:26:58 <bigbluehat> q?
17:27:06 <niklasl> ... There are other former editors, and there is a lot of different plain text approaches of this; the team should bring some formal guidelines for all editors.
17:27:30 <niklasl> ivan: But formal guidance will take a long time.
17:27:42 <niklasl> ... We need to make a decision here.
17:27:51 <niklasl> q+
17:27:56 <bigbluehat> ack niklasl
17:28:11 <bigbluehat> niklasl: I'm trying to recall what we did for RDF 1.2
17:28:23 <bigbluehat> ... TallTed do you recall? I think we used `formerEditors` was used
17:28:31 <bigbluehat> TallTed: yeah. Just not sure what else.
17:28:34 <ivan> q+
17:28:56 <niklasl> See https://w3c.github.io/rdf-concepts/spec/ (plain text approach in "current editors")
17:29:03 <bigbluehat> ack ivan
17:29:47 <bigbluehat> ivan: I think we should copy RDF 1.2's approach
17:29:50 <niklasl> "Gregg Kellogg (until 2025-09-06), in memoriam"
17:31:07 <niklasl> ivan: Do like in RDF 1.2. Concepts - keep in Editors, with added in memoriam
17:31:25 <niklasl> +1
17:31:31 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/pull/165
17:31:32 <gb> s|https://github.com/w3c/yaml-ld/pull/165|-> Pull Request 165 fix links in README.md to point to the w3c org (by pchampin) https://github.com/w3c/yaml-ld/pull/165
17:32:01 <niklasl> bigbluehat: this (#165) should be straightforward.
17:32:02 <gb> https://github.com/w3c/json-ld-syntax/issues/165 -> CLOSED Issue 165 Missing @type in expanded form when an id map is used in conjunction with @type in a term definition (by 2bigO) [out of scope: transformation]
17:32:14 <niklasl> ivan: No formal decision needed for this.
17:32:31 <niklasl> bigbluehat: feel free to merge once reviewed.
17:32:42 <niklasl> TallTed: leave for some days for the missing commas.
17:32:58 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/pull/37
17:32:58 <gb> s|https://github.com/w3c/yaml-ld/pull/37|-> Pull Request 37 Add remaining Use Case Issues. (by gkellogg) [UCR] https://github.com/w3c/yaml-ld/pull/37
17:33:51 <niklasl> bigbluehat: this is a draft PR; close or merge-close? Let editors decide?
17:35:00 <niklasl> bigbluehat: half of those issues aren't closed yet. We can ignore this PR for now and see if it works to address those.
17:35:31 <niklasl> anatoly-scherbakov: agreed
17:35:40 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/issues/163
17:35:40 <gb> s|https://github.com/w3c/yaml-ld/issues/163|-> Issue 163 IPR Commitments (by BigBlueHat) https://github.com/w3c/yaml-ld/issues/163
17:35:55 <niklasl> bigbluehat: The IPR issues should be cleared up, but we need to be sure.
17:36:09 <bigbluehat> https://www.w3.org/community/json-ld/spec/236/commitments
17:37:30 <niklasl> bigbluehat: We can ping Pierre-Antoine suggesting to close this.
17:38:09 <bigbluehat> topic: CBOR-LD PRs and/or Issues
17:38:36 <bigbluehat> https://github.com/w3c/cbor-ld/pulls
17:39:43 <wes-smith> wes-smith has joined #json-ld
17:39:54 <bigbluehat> subtopic: https://github.com/w3c/cbor-ld/pull/22
17:39:55 <gb> s|https://github.com/w3c/cbor-ld/pull/22|-> Pull Request 22 Add OpenBadges v3.0.0 context URL to registry. (by BigBlueHat) https://github.com/w3c/cbor-ld/pull/22
17:40:23 <niklasl> wes-smith: I advice to close that; it's been overtaken.
17:40:54 <niklasl> present+ wes-smith
17:41:01 <bigbluehat> subtopic: https://github.com/w3c/cbor-ld/pull/53
17:41:02 <gb> s|https://github.com/w3c/cbor-ld/pull/53|-> Pull Request 53 Remove inline registry table, point to external repository/document. (by wes-smith) https://github.com/w3c/cbor-ld/pull/53
17:41:39 <niklasl> wes-smith: A simple PR, the old registry was inline; this removes it and points to the new separate registry.
17:42:05 <RRSAgent> I have made the request to generate https://www.w3.org/2026/02/11-json-ld-minutes.html TallTed
17:42:12 <niklasl> bigbluehat: Any issues with the registry location?
17:42:20 <niklasl> ... See no reason not to point to it.
17:42:24 <dlehn> q+
17:42:40 <ivan> q+
17:42:41 <niklasl> wes-smith: there is a corresponding open issue
17:42:50 <bigbluehat> ack dlehn
17:43:04 <niklasl> dlehn: why remove the dash from the repo name?
17:43:35 <niklasl> wes-smith: it's currently there, if that needs to change we can do that
17:43:54 <niklasl> dlehn: not a big issue
17:44:22 <wes-smith> wes-smith has joined #json-ld
17:44:27 <bigbluehat> ack ivan
17:44:50 <niklasl> ivan: Is the registry repository maintained by the json-ld community?
17:45:03 <niklasl> wes-smith: that is the understanding
17:45:30 <niklasl> ivan: the CG is then responsible for the name.
17:46:03 <niklasl> ... It should be mentioned that the CG owns/maintains that repository
17:46:16 <niklasl> wes-smith: I will add some text to that effect
17:46:20 <bigbluehat> q?
17:48:48 <niklasl> bigbluehat: We need to look at some of the repository permissions.
17:48:55 <wes-smith> wes-smith has joined #json-ld
17:49:06 <niklasl> ... Pierre-Antoine may be able to sort those out.
17:49:30 <niklasl> ivan: Transferring repositories needs some follow-up permission work.
17:50:21 <niklasl> The group reviewed and the PR is merged.
17:51:05 <niklasl> bigbluehat: We also close issue 52 with that.
17:51:30 <bigbluehat> subtopic: https://github.com/w3c/cbor-ld/pull/54
17:51:30 <gb> s|https://github.com/w3c/cbor-ld/pull/54|-> Pull Request 54 Remove tag registration issue, cleanup wording around CBOR tag. (by wes-smith) https://github.com/w3c/cbor-ld/pull/54
17:52:17 <niklasl> wes-smith: Removing some outdated text regarding IANA tag, and warnings about provisional state, and related cleanup.
17:52:47 <wes-smith> wes-smith has joined #json-ld
17:53:16 <niklasl> ivan: Is the idea to publish first as CG FPWD and then move to WG?
17:53:43 <dlehn> q+
17:53:50 <bigbluehat> ack dlehn
17:54:10 <dlehn> https://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml
17:54:13 <niklasl> bigbluehat: this seems like a race condition; the intent was to do that; might we skip that now?
17:54:20 <dlehn> that needs to be fixed
17:54:40 <ivan> q+
17:54:56 <bigbluehat> ack ivan
17:55:17 <niklasl> ivan: The problem is that the source still this is a CG draft. ReSpec does its job.
17:55:42 <niklasl> The respec json structure needs to be updated; for CBOR-LD and YAML-LD
17:56:12 <niklasl> a/The respec/... The respec/
17:56:18 <niklasl> s/The respec/... The respec/
17:56:44 <niklasl> bigbluehat: Any objections to merge 54?
17:57:31 <wes-smith> wes-smith has joined #json-ld
17:57:34 <niklasl> dlehn: The link in the iana page for CBOR-LD is broken
17:58:23 <ivan> q+
17:58:28 <niklasl> bigbluehat: I will set up a redirect for that. But we need to fix that in the registry if possible.
17:58:34 <bigbluehat> ack ivan
17:59:06 <niklasl> ivan: There is no reference to the JSON-LD specification in this spec. There needs to be formal references in the spec.
17:59:17 <niklasl> bigbluehat: I'll raise an issue for thst.
17:59:23 <niklasl> s/thst/that/
17:59:41 <niklasl> ivan: you may still merge this
18:00:02 <bigbluehat> bye, Zakim
18:00:08 <bigbluehat> Zakim, end meeting
18:00:08 <Zakim> As of this point the attendees have been bigbluehat, TallTed, niklasl, anatoly-scherbakov, dlehn, ivan, ajs6f, wes-smith
18:00:10 <Zakim> RRSAgent, please draft minutes
18:00:11 <RRSAgent> I have made the request to generate https://www.w3.org/2026/02/11-json-ld-minutes.html Zakim
18:00:17 <Zakim> I am happy to have been of service, bigbluehat; please remember to excuse RRSAgent.  Goodbye
18:00:18 <Zakim> Zakim has left #json-ld
18:10:29 <TallTed> RRSAgent, bye
18:10:29 <RRSAgent> I see no action items