17:03:18 <RRSAgent> RRSAgent has joined #json-ld
17:03:22 <RRSAgent> logging to https://www.w3.org/2026/02/18-json-ld-irc
17:03:22 <Zakim> RRSAgent, make logs Public
17:03:23 <Zakim> please title this meeting ("meeting: ..."), bigbluehat
17:03:30 <bigbluehat> meeting: JSON-LD WG
17:03:30 <bigbluehat> chair: bigbluehat
17:03:30 <bigbluehat> present+
17:03:45 <anatoly-scherbakov> present+
17:03:46 <VictorLu> VictorLu has joined #json-ld
17:03:47 <bigbluehat> agenda: https://www.w3.org/events/meetings/de31b974-ca9c-4325-bcea-60b91a1b78d9/20260218T120000/
17:03:50 <agendabot> clear agenda
17:03:50 <agendabot> agenda+ Announcements and Introductions
17:03:50 <agendabot> agenda+ YAML-LD Issue curation (20 minutes)
17:03:50 <agendabot> agenda+ CBOR-LD Issue curation (20 minutes)
17:03:50 <agendabot> agenda+ JSON-LD Issue Discussion and Organization
17:03:51 <agendabot> agenda+ Open Discussion
17:03:56 <niklasl> present+
17:04:03 <bigbluehat> Zakim, next item
17:04:04 <Zakim> agendum 1 -- Announcements and Introductions -- taken up [from agendabot]
17:05:54 <anatoly-scherbakov> scribe+
17:06:00 <TallTed> bigbluehat -- For next time, you can `agendabot, find agenda`.  See https://w3c.github.io/AgendaBot/manual.html for more tricks.
17:06:42 <anatoly-scherbakov> bigbluehat: Netflix are using RDF and CBOR-LD
17:07:04 <anatoly-scherbakov> bigbluehat: would like to invite them to talk
17:07:18 <anatoly-scherbakov> +1
17:07:51 <anatoly-scherbakov> bigbluehat: will schedule them
17:08:06 <bigbluehat> Zakim, next item
17:08:06 <Zakim> agendum 2 -- YAML-LD Issue curation (20 minutes) -- taken up [from agendabot]
17:08:12 <bigbluehat> https://github.com/w3c/yaml-ld/pulls
17:08:20 <anatoly-scherbakov> bigbluehat: looking at YAML-LD PRs
17:08:36 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/pull/166
17:08:37 <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:09:20 <TallTed> TallTed has changed the topic to: JSON-LD WG & CG -- WG 2026-02-18 agenda: https://www.w3.org/events/meetings/de31b974-ca9c-4325-bcea-60b91a1b78d9/20260218T120000/
17:09:23 <anatoly-scherbakov> bigbluehat: affiliations were added
17:09:41 <dlehn> present+
17:10:01 <anatoly-scherbakov> bigbluehat: merging
17:10:51 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/pull/168
17:10:51 <gb> s|https://github.com/w3c/yaml-ld/pull/168|-> Pull Request 168 #20 Reference exact test suite versions (by anatoly-scherbakov) https://github.com/w3c/yaml-ld/pull/168
17:12:05 <anatoly-scherbakov> bigbluehat: merging
17:12:24 <ivan> q+ to meta issue
17:12:35 <anatoly-scherbakov> bigbluehat: editorial PRs can be merged directly without discussion
17:12:38 <bigbluehat> ack ivan
17:12:38 <Zakim> ivan, you wanted to meta issue
17:13:04 <anatoly-scherbakov> ivan: we should not work on CG document anymore
17:13:22 <anatoly-scherbakov> ivan: respec header must be changed to WG document
17:13:46 <anatoly-scherbakov> ivan: CG-DRAFT to ED-DRAFT
17:14:31 <anatoly-scherbakov> bigbluehat: can handle this in my PR
17:14:39 <TallTed> "editorial PRs can be merged directly without discussion" but should exist for at least a few days before they get merged, to allow for me and others to catch errors of whatever flavor.
17:14:39 <TallTed> It's a much lower lift to suggest changes to a PR than to create another PR.
17:14:39 <TallTed> Near-immediate merges obviate most of the point of working through PRs instead of direct commits.
17:15:05 <anatoly-scherbakov> Makes sense TallTed
17:15:27 <anatoly-scherbakov> s/ED-DRAFT/ED/
17:15:44 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/issues/163
17:15:44 <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:16:03 <dlehn> q+
17:16:26 <anatoly-scherbakov> bigbluehat: this is done, can resurface if more IP
17:16:38 <anatoly-scherbakov> bigbluehat: ...IPR commitments needed
17:16:39 <bigbluehat> ack dlehn
17:17:25 <anatoly-scherbakov> dlehn: what's about rack dependencies?
17:17:39 <anatoly-scherbakov> bigbluehat: after Gregg passing, Ruby code is decaying
17:18:07 <anatoly-scherbakov> bigbluehat: we need support for Ruby or  a rewrite
17:18:11 <pchampin> present+
17:19:11 <TallTed> present+
17:19:16 <anatoly-scherbakov> dlehn: so should we just upgrade these minor versions?
17:19:22 <anatoly-scherbakov> bigbluehat: we can, and see what happens
17:20:30 <anatoly-scherbakov> +1
17:21:39 <anatoly-scherbakov> bigbluehat: ultimately, when a spec has an editor then maintenance of Ruby code will be their responsibility
17:22:58 <anatoly-scherbakov> bigbluehat: there is probably no risk, so this is not a high priority
17:23:57 <anatoly-scherbakov> q+
17:24:05 <bigbluehat> scribe+
17:24:14 <bigbluehat> anatoly-scherbakov: I haven't looked into these issues in a bit
17:24:21 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22test%3Aneeds%20tests%22
17:24:31 <bigbluehat> anatoly-scherbakov: the plan was to write tests for each of these
17:24:44 <bigbluehat> ... to confirm that YAML-LD implementations could do these
17:24:56 <bigbluehat> ... especially when contexts and frames are in YAML-LD
17:25:01 <bigbluehat> ... the need is still there
17:25:06 <bigbluehat> ... I can look into it
17:25:33 <bigbluehat> ... I wanted to mention that I've created milestones
17:25:51 <bigbluehat> ... the idea is to free us from looking at the issues that cannot or are not addressable
17:26:10 <bigbluehat> ... for example, the triples as subjects one is related to RDF1.2
17:26:23 <bigbluehat> ... and the extended profile idea was from Gregg for using more of YAML
17:27:23 <anatoly-scherbakov> bigbluehat: YAML-LD could use future-work label
17:27:48 <anatoly-scherbakov> bigbluehat: adding it
17:28:23 <anatoly-scherbakov> s/future-work/defer-future-version/
17:28:53 <anatoly-scherbakov> bigbluehat: we'll do calls with editors to do such stuff
17:29:39 <anatoly-scherbakov> bigbluehat: moving json literal support to future work
17:30:09 <anatoly-scherbakov> bigbluehat: -00 milestone is unclear
17:30:55 <anatoly-scherbakov> bigbluehat: now, we can filter issues excluding future versions
17:31:12 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/issues/143
17:31:12 <gb> s|https://github.com/w3c/yaml-ld/issues/143|-> Issue 143 Should output type of `expand()` be `dict` or `str`? (by anatoly-scherbakov) https://github.com/w3c/yaml-ld/issues/143
17:31:18 <bigbluehat> anatoly-scherbakov: I wrote this one as a question
17:31:29 <bigbluehat> ... mostly about the proper typing of the expand function
17:31:52 <bigbluehat> ... I would likely re-request this in JSON-LD API spec
17:32:47 <anatoly-scherbakov> bigbluehat: keeping this for now
17:32:57 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/issues/118
17:32:57 <gb> s|https://github.com/w3c/yaml-ld/issues/118|-> Issue 118 Write test manifests in YAML-LD instead of JSON-LD (by anatoly-scherbakov) [test:needs implementation] https://github.com/w3c/yaml-ld/issues/118
17:33:43 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/issues/103
17:33:44 <gb> s|https://github.com/w3c/yaml-ld/issues/103|-> https://github.com/w3c/yaml-ld/issues/103 "Issue 103 Test: anchor names do not convey semantic information (by anatoly-scherbakov) [test:missing-coverage] [test:needs implementation]"
17:34:35 <bigbluehat> anatoly-scherbakov: in a YAML document you can create an anchor to assign a name to a piece of the document
17:34:58 <bigbluehat> ... and then refer to it from within the document essentially duplicating it into the place where the anchor is referenced
17:35:13 <bigbluehat> ... and in YAML-LD the anchors are being resolved via YAML parsing
17:35:26 <bigbluehat> ... and when you look at it in Linked Data the anchors are gone
17:35:35 <bigbluehat> ... so there is not semantic meaning
17:35:46 <bigbluehat> ... and this issue is about writing a test for this
17:36:07 <pchampin> q+
17:36:26 <bigbluehat> ... it could be possible to maintain the anchors, but it would be for future work
17:37:00 <bigbluehat> bigbluehat: so this issues is just for writing a test
17:37:46 <bigbluehat> ... does this need a test? because the anchors are gone after YAML.parse() aren't they?
17:38:03 <bigbluehat> anatoly-scherbakov: yes, but there were ideas for the future to possibly give the anchors semantic meaning
17:38:28 <bigbluehat> ... and theoretically one could keep those around, but it would reduce compatibility with JSON-LD and others
17:38:45 <niklasl> I'd probably be a -1 on that (as it sounds like it reduces interoperability?)
17:39:09 <anatoly-scherbakov> bigbluehat: this issue might be beyond scope
17:39:15 <bigbluehat> ack anatoly-scherbakov
17:39:19 <bigbluehat> ack pchampin
17:39:26 <bigbluehat> pchampin: I'm +1 on writing this kind of test
17:39:36 <anatoly-scherbakov> pchampin: agree with adding such a test even if being non-compliant requires lots of work
17:39:44 <anatoly-scherbakov> pchampin: because the idea existed
17:39:57 <anatoly-scherbakov> pchampin: YAML has several data model levels
17:40:05 <anatoly-scherbakov> pchampin: one of these keeps comments
17:40:20 <anatoly-scherbakov> pchampin: some parsers give you the choice of the level
17:40:24 <bigbluehat> q?
17:40:34 <anatoly-scherbakov> pchampin: I guess some parsers give you access to anchors if you want
17:41:09 <anatoly-scherbakov> pchampin: also important to distinguish anchors in context vs data
17:41:17 <anatoly-scherbakov> pchampin: anchors in context might be very useful
17:41:28 <anatoly-scherbakov> pchampin: for instance, for the same scope context in different places
17:42:02 <pchampin> https://w3c.github.io/yaml-ld/spec/#example-with-anchors
17:43:13 <anatoly-scherbakov> bigbluehat: making the test makes sense, spec has an anchors example, maybe we could explain a bit further how to use anchors in context
17:44:34 <anatoly-scherbakov> anatoly-scherbakov: we can close this
17:46:00 <anatoly-scherbakov> bigbluehat: what is FHIR?
17:46:53 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/issues/98
17:46:54 <gb> s|https://github.com/w3c/yaml-ld/issues/98|-> Issue 98 investigate FHIR Shorthand (FSH) (by VladimirAlexiev) [out-of-scope] https://github.com/w3c/yaml-ld/issues/98
17:47:04 <anatoly-scherbakov> bigbluehat: might be up for discussion elsewhere, marking as out of scope
17:48:45 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/issues/84
17:48:46 <gb> s|https://github.com/w3c/yaml-ld/issues/84|-> Issue 84 Downgrading from Extended Internal Representation should use value objects (by gkellogg) [enhancement] [spec] https://github.com/w3c/yaml-ld/issues/84
17:49:50 <anatoly-scherbakov> bigbluehat: deferring to future version
17:50:58 <bigbluehat> subtopic: https://github.com/w3c/yaml-ld/issues/83
17:50:58 <gb> s|https://github.com/w3c/yaml-ld/issues/83|-> Issue 83 use regular expressions to resolve literals; URIs, CURIEs (by VladimirAlexiev) [UCR] https://github.com/w3c/yaml-ld/issues/83
17:51:22 <anatoly-scherbakov> bigbluehat: let's come back to this one later
17:52:13 <anatoly-scherbakov> +1
17:52:18 <anatoly-scherbakov> bigbluehat: let's close the Work Plan issue
17:52:59 <anatoly-scherbakov> bigbluehat: let's do further cleanup
17:53:33 <anatoly-scherbakov> bigbluehat: we'll probably do CBOR-LD next week and we are looking to meet Netflix
17:53:54 <RRSAgent> I have made the request to generate https://www.w3.org/2026/02/18-json-ld-minutes.html TallTed
17:54:15 <TallTed> previous meeting: https://www.w3.org/2026/02/11-json-ld-minutes.html
17:54:28 <TallTed> next meeting: https://www.w3.org/2026/02/25-json-ld-minutes.html
17:54:35 <m2gbot> m2gbot has joined #json-ld
17:55:04 <bigbluehat> Zakim, bye
17:55:04 <Zakim> leaving.  As of this point the attendees have been bigbluehat, anatoly-scherbakov, niklasl, dlehn, pchampin, TallTed
17:55:04 <Zakim> Zakim has left #json-ld
17:55:21 <bigbluehat> we also need to talk about bringing the other minutes site/space back up to snuff
17:55:23 <pchampin> RRSAgent, make minutes
17:55:24 <RRSAgent> I have made the request to generate https://www.w3.org/2026/02/18-json-ld-minutes.html pchampin
18:43:55 <gb> gb has joined #json-ld