16:04:08 <RRSAgent> RRSAgent has joined #json-ld
16:04:12 <RRSAgent> logging to https://www.w3.org/2026/04/15-json-ld-irc
16:04:12 <Zakim> RRSAgent, make logs Public
16:04:13 <Zakim> please title this meeting ("meeting: ..."), bigbluehat
16:04:19 <bigbluehat> meeting: JSON-LD WG
16:04:19 <bigbluehat> chair: bigbluehat
16:04:19 <bigbluehat> present+
16:04:21 <anatoly-scherbakov> present+
16:04:34 <bigbluehat> agenda: https://www.w3.org/events/meetings/de31b974-ca9c-4325-bcea-60b91a1b78d9/20260415T120000/
16:04:35 <agendabot> clear agenda
16:04:35 <agendabot> agenda+ Announcements and Introductions
16:04:35 <agendabot> agenda+ Presentation from Slava Tykhonov of CODATA
16:04:35 <agendabot> agenda+ YAML-LD check-in
16:04:35 <agendabot> agenda+ CBOR-LD PRs & Issues
16:04:37 <wes-smith> wes-smith has joined #json-ld
16:04:42 <agendabot> agenda+ Open Discussion
16:04:44 <wes-smith> present+
16:04:52 <TallTed> meeting: JSON-LD WG Meeting
16:04:52 <TallTed> present+
16:05:18 <bigbluehat> Zakim, next item
16:05:18 <Zakim> agendum 1 -- Announcements and Introductions -- taken up [from agendabot]
16:05:33 <bigbluehat> scribe+
16:05:34 <pchampin> sribe+
16:05:43 <ivan> present+
16:05:55 <pchampin> slava:  Slava Tykhonov, head of dynamic intelligence at CODATA
16:05:56 <TallTed> scribe+ pchampin
16:06:06 <TallTed> s/sribe+//
16:06:17 <pchampin> ... I'm going to talk about Croissant mostly
16:07:03 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/15-json-ld-minutes.html TallTed
16:07:26 <bigbluehat> Zakim, next item
16:07:26 <Zakim> agendum 2 -- Presentation from Slava Tykhonov of CODATA -- taken up [from agendabot]
16:07:29 <pchampin> bigbluehat: should we change our schedule due to AC meeting?
16:07:33 <pchampin> pchampin: I'm not going
16:07:36 <TallTed> previous meeting: https://www.w3.org/2026/04/08-json-ld-minutes.html
16:07:36 <pchampin> ivan: me neither
16:07:38 <TallTed> next meeting: https://www.w3.org/2026/04/22-json-ld-minutes.html
16:07:48 <pchampin> bigbluehat: ok, let's keep our usual schedule
16:07:49 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/15-json-ld-minutes.html TallTed
16:09:31 <pchampin> slides: https://docs.google.com/presentation/d/1dTCuiGHEeNqGThwbgUqK8oL5rzk8YVXP/edit?slide=id.g3c447b49fa9_0_527#slide=id.g3c447b49fa9_0_527
16:11:12 <pchampin> slava: (presenting slides) CDIF is not really a new standard, more a compilation of existing standards
16:12:55 <pchampin> ... Croissant ls widely supported by AI platform
16:12:55 <pchampin> ... (presenting more slides)
16:13:00 <dlehn> present+
16:37:21 <pchampin> bigbluehat: we need to move on, but I'm amazed how much ground you are covering.
16:37:43 <pchampin> ... I have a JSON-LD related question
16:37:58 <pchampin> ... In your Croissant examples, the context is always embedded. Is it by design?
16:38:19 <pchampin> slava: this is by design, pushed by Google. We (CODATA) have a different opinion.
16:38:35 <pchampin> ... We would prefer to have contexts by reference, managed with ODRL policies.
16:39:28 <pchampin> ... But Google do not like that access to some data can be removed at any time.
16:40:02 <pchampin> ... We want more granularity and access control -- e.g. for use-cases such as medical data.
16:40:16 <pchampin> q+
16:40:25 <bigbluehat> ack pchampin
16:40:37 <bigbluehat> pchampin: it's great to see all these technologies brought together
16:40:53 <bigbluehat> ... Slava may be aware, but the Dataset Exchange WG is being rechartered
16:41:07 <bigbluehat> ... we're adding DDI related things
16:41:18 <bigbluehat> ... and at some point, I suppose this will become part of CDIF
16:41:49 <bigbluehat> slava: it's great that these are becoming official standards
16:42:33 <bigbluehat> Zakim, next item
16:42:33 <Zakim> agendum 3 -- YAML-LD check-in -- taken up [from agendabot]
16:42:37 <bigbluehat> bigbluehat: let's skip this one
16:42:39 <bigbluehat> Zakim, next item
16:42:39 <Zakim> agendum 3 was just opened, bigbluehat
16:42:45 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/15-json-ld-minutes.html TallTed
16:43:08 <TallTed> Zakim, close item 3
16:43:08 <Zakim> agendum 3, YAML-LD check-in, closed
16:43:08 <Zakim> I see 2 items remaining on the agenda; the next one is
16:43:08 <Zakim> 4. CBOR-LD PRs & Issues [from agendabot]
16:43:08 <TallTed> Zakim, next item
16:43:08 <Zakim> agendum 4 -- CBOR-LD PRs & Issues -- taken up [from agendabot]
16:43:29 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/15-json-ld-minutes.html TallTed
16:43:54 <pchampin> bigbluehat: we have a handful of PRs, all approved and editorial
16:44:09 <bigbluehat> subtopic: https://github.com/w3c/cbor-ld/pull/73
16:44:09 <gb> s|https://github.com/w3c/cbor-ld/pull/73|-> https://github.com/w3c/cbor-ld/issues/73 "https://github.com/w3c/cbor-ld/pull/73"
16:44:19 <pchampin> wes-smith: I didn't want to merge cbor-ld#73 before mentioning it here
16:44:20 <gb> https://github.com/w3c/cbor-ld/pull/73 -> Pull Request 73 Apply writing and grammar fixes, remove constraints on registry dictionary format. (by wes-smith)
16:44:29 <pchampin> ... anyone objecting? it is editorial
16:44:51 <pchampin> [crickets]
16:44:53 <bigbluehat> subtopic: https://github.com/w3c/cbor-ld/pull/76
16:44:54 <gb> s|https://github.com/w3c/cbor-ld/pull/76|-> Pull Request 76 Prepare First Public Working Draft (by pchampin) https://github.com/w3c/cbor-ld/pull/76
16:45:25 <pchampin> wes-smith: pchampin's PR to add a FPWD snapshot
16:45:42 <pchampin> pchampin: please let's merge it, so that I can move forward with the transition to actuallly publish it
16:46:10 <bigbluehat> subtopic: https://github.com/w3c/cbor-ld/pull/75
16:46:11 <gb> s|https://github.com/w3c/cbor-ld/pull/75|-> Pull Request 75 add json ld links (by BigBlueHat) https://github.com/w3c/cbor-ld/pull/75
16:46:19 <bigbluehat> bigbluehat: I'll try to have this done by next week.
16:46:54 <bigbluehat> subtopic: https://github.com/w3c/cbor-ld/issues/46
16:46:56 <gb> s|https://github.com/w3c/cbor-ld/issues/46|-> Issue 46 Define registration process (by dlongley) [needs discussion] https://github.com/w3c/cbor-ld/issues/46
16:47:52 <pchampin> wes-smith: my view is that registration will look like w3id registration
16:48:01 <pchampin> ... people would propose PR
16:48:14 <pchampin> ... the requirements for registration would depend on what you would request
16:48:43 <pchampin> ... small values are precious, so the requirements on those would be higher (complete specification, proof of implementation)
16:48:58 <pchampin> ... bigger values would be first-come first-served
16:49:29 <pchampin> ... the current editors of the CBOR-LD spec at the time of the request would be the reviewers
16:49:30 <pchampin> q+
16:49:37 <bigbluehat> ack pchampin
16:49:57 <bigbluehat> pchampin: there may be a situation where there is no current editor of the CBOR-LD specification
16:50:03 <bigbluehat> ... so we'd need a backup plan
16:50:31 <pchampin> bigbluehat: if it leans on editors for now, that's fine; we can move forward from there
16:51:14 <pchampin> ... once the WG closes, we don't want wes-smith to be stuck with this for eternity
16:51:22 <pchampin> ... we need a transition within the lifetime of the WG
16:52:06 <pchampin> ... there are several questions? is it going to be a W3C registry? a simple github repo?
16:52:29 <pchampin> ... what wes-smith described seems subjective
16:52:42 <pchampin> ... (smaller values vs. bigger values)
16:53:00 <pchampin> wes-smith: yes, we could try to make it less subjective
16:53:09 <pchampin> ... e.g. require a specification from an official SDO
16:53:16 <dlehn> q+
16:54:06 <pchampin> bigbluehat: unlike the DID registry, it is not open season
16:54:23 <pchampin> ... what if there are conflicting use of the same value?
16:54:32 <pchampin> ... unlike DNS, there is no programmatic enforcement
16:55:06 <pchampin> wes-smith: if someone chose to use CBOR-LD payloads with an entry number that do not comply with that entry, noone will be able to consume it
16:55:18 <bigbluehat> ack dlehn
16:55:54 <pchampin> dlehn: this looks similar to the way CBOR tags registration works
16:56:12 <pchampin> wes-smith: yes, that's the inspiration, and that's where the subjectivity comes
16:56:35 <bigbluehat> q+
16:56:42 <pchampin> ... part of it is specified, part of it is subjective
16:57:20 <bigbluehat> ack bigbluehat
16:57:24 <pchampin> dlehn: there are technical reasons for doing that, but also resource problems
16:57:58 <pchampin> bigbluehat: what would be the break point between small and big value?
16:58:23 <pchampin> wes-smith: that would be a byte size, as defined by the CBOR format
16:58:52 <pchampin> ... I'll turn that into a drafty PR
16:59:37 <pchampin> bigbluehat: we don't have time for anything else
16:59:58 <pchampin> ... thanks for giving time to Slava to present; loads of W3C specifications involved, with JSON-LD all the way
17:00:04 <pchampin> ... interesting use-cases
17:00:15 <pchampin> RRSAgent, make minutes
17:00:16 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/15-json-ld-minutes.html pchampin
17:00:58 <bigbluehat> Zakim, end meeting
17:00:58 <Zakim> As of this point the attendees have been bigbluehat, anatoly-scherbakov, wes-smith, TallTed, ivan, dlehn
17:01:00 <Zakim> RRSAgent, please draft minutes
17:01:02 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/15-json-ld-minutes.html Zakim
17:01:26 <Zakim> I am happy to have been of service, bigbluehat; please remember to excuse RRSAgent.  Goodbye
17:01:26 <Zakim> Zakim has left #json-ld
17:01:26 <bigbluehat> RRSAgent, bye
17:01:26 <RRSAgent> I see no action items