16:55:30 RRSAgent has joined #json-ld 16:55:34 logging to https://www.w3.org/2025/02/12-json-ld-irc 16:55:34 RRSAgent, make logs Public 16:55:35 please title this meeting ("meeting: ..."), bigbluehat 16:55:42 meeting: JSON-LD CG 16:56:09 url: https://www.w3.org/events/meetings/635aef15-a607-499c-b32a-926d3cb3a580/20250212T120000/#agenda 16:56:13 bigbluehat has changed the topic to: https://www.w3.org/events/meetings/635aef15-a607-499c-b32a-926d3cb3a580/20250212T120000/#agenda 16:56:28 agenda: https://www.w3.org/events/meetings/635aef15-a607-499c-b32a-926d3cb3a580/20250212T120000/#agenda 16:56:29 clear agenda 16:56:29 agenda+ Announcements and Introductions 16:56:29 agenda+ JSON-LD Issue Discussion 16:56:29 agenda+ Open Discussion 16:56:29 agenda+ Next call 16:56:46 chair: bigbluehat 16:57:27 anatoly-scherbakov has joined #json-ld 16:59:46 niklasl has joined #json-ld 16:59:51 present+ 16:59:51 present+ 17:00:30 present+ 17:00:40 present+ 17:01:53 Zakim, next item 17:01:53 agendum 1 -- Announcements and Introductions -- taken up [from agendabot] 17:02:33 pchampin: work on our charter has been made to the AC 17:02:46 ... so others can have a chance to chime in 17:02:50 scribe+ 17:02:54 scribe+ 17:03:13 s/been made/been announced 17:03:51 https://github.com/json-ld/json-ld-wg-charter 17:04:16 pchampin: the announcement pointed the members to the public repo (link above) 17:04:48 Zakim, next item 17:04:48 agendum 2 -- JSON-LD Issue Discussion -- taken up [from agendabot] 17:04:59 present+ 17:05:03 https://github.com/orgs/w3c/projects/84/views/1 17:05:40 bigbluehat: I don't think the project has been re-sorted. Let's look at pending PRs. 17:06:04 https://github.com/w3c/json-ld-api/pull/625 17:06:05 https://github.com/w3c/json-ld-api/pull/625 -> Pull Request 625 (closes #555) Fall back to default logic in `useNativeTypes` mode for RDF numbers which are not JSON numbers (by anatoly-scherbakov) [class-3] 17:06:32 q+ 17:06:34 s|https://github.com/w3c/json-ld-api/pull/625|subtopic: https://github.com/w3c/json-ld-api/pull/625 17:06:42 bigbluehat: this one was heavily approved 17:06:59 anatoly-scherbakov: I've recently applied suggestions from TallTed and pchampin 17:07:31 bigbluehat: the people involved in the review are all here. Any objection to merge it now? 17:07:35 pchampin: none from me 17:08:08 bigbluehat: hearing none, let's merge this PR 17:08:43 subtopic: https://github.com/w3c/json-ld-api/pull/559 17:08:43 https://github.com/w3c/json-ld-api/pull/559 -> Pull Request 559 Add JSON literal tests. (by davidlehn) [spec:substantive] [test:missing-coverage] 17:09:29 subtopic: https://github.com/w3c/json-ld-api/pull/585 17:09:29 https://github.com/w3c/json-ld-api/pull/585 -> Pull Request 585 Add graph container array tests. (by davidlehn) [test:missing-coverage] 17:10:39 bigbluehat: for this one (and the previous one), we don't have the commenters here. Hard to discuss them here. 17:10:49 subtopic: https://github.com/w3c/json-ld-api/issues/627 17:10:49 https://github.com/w3c/json-ld-api/issues/627 -> Issue 627 Recommend a way for dependent specs to call into this one, that's not WebIDL (by jyasskin) [ms:future-work] [needs discussion] 17:11:51 bigbluehat: we discussed this last call. I asked Jeffrey for more examples, which he provided. 17:12:05 ... ivan, you pointed out that DID-Resolution uses INFRA instead of WebIDL. 17:12:20 ... The main remaining issue is the amount of editorial work. 17:12:22 q+ 17:12:31 ack anatoly-scherbakov 17:12:34 ack pchampin 17:13:24 pchampin: we could maybe automate the WebIDL to INFRA conversion? 17:13:32 bigbluehat: or have an AI do that... 17:14:05 subtopic: https://github.com/w3c/json-ld-api/issues/558 17:14:06 https://github.com/w3c/json-ld-api/issues/558 -> Issue 558 Compaction cannot round-trip terms using `@container: @list` and `@type: @vocab` (by niklasl) [spec:enhancement] [spec:substantive] [ErratumRaised] [class-3] 17:14:45 bigbluehat: niklasl, this one is yours. No activity in the past 2 years (almost exactly). 17:15:21 https://github.com/niklasl/trld/commit/1190a251514e7cb7bc8d596ba6b6bf4da3632bab 17:15:29 niklasl: I have a proposal about what to do. I have refactored my implementation accordingly. 17:15:35 ... (link above) 17:16:37 ... AFAICT this fixes the issue. 17:17:27 bigbluehat: niklasl, would you be willing to write a PR for that? 17:17:33 niklasl: yes, I can try 17:18:16 ... I also need to check whether there are any side effects. 17:18:59 bigbluehat: this needs to be wrapped in / tags, like the other PRs we have. 17:19:05 subtopic: https://github.com/w3c/json-ld-syntax/issues/436 17:19:06 https://github.com/w3c/json-ld-syntax/issues/436 -> Issue 436 URI in Profile triggers CORS Unsafe Request Header Byte rule (by azaroth42) [spec:w3c] [needs discussion] [tag-needs-resolution] 17:19:58 q+ 17:20:09 present+ 17:20:15 ack pchampin 17:23:09 pchampin: I discussed this with Yves Lafon, staff contact of the TAG. 17:23:37 q+ 17:23:44 ... This restriction of fetch is considered as an important security feature, this is unlikely to go away. 17:23:51 ack niklasl 17:24:12 ... To mitigate this issue, should we (JSON-LD WG) set up a registry for short-names for profiles of application/ld+json ? 17:24:28 niklasl: I don't think that a registry would solve the problem. 17:24:54 ... We need to distinguish data shapes from the semantics of data. 17:25:30 ... Activity Streams went for a specific media-type, others may have to do that. 17:25:32 q+ 17:25:52 ... This issue seems specific to an RDF mindset. 17:26:04 ... E.g. I want RDF, and I only understand SKOS. 17:26:51 ack pchampin 17:26:55 ... I have not seen the same kind of issue in other contexts, where structure and semantics are the same. 17:28:01 q+ 17:28:05 ack bigbluehat 17:28:09 ... does the web need "compound media type negotiation" ... 🤔 17:28:19 pchampin: actually, video formats also suffer from the coarseness of media-types 17:29:53 bigbluehat: CORS breaks a lot of things. I don't think Ruben's proposal will fly. 17:29:54 q+ 17:30:27 (Or in the video format context, I guess "Accepts-Codex", ... And in the RDF context, maybe what I really want is "Accepts-Vocabulary" ... but try to realize that through "Accepts-Profile", for better or worse...) 17:30:29 ack pchampin 17:30:40 ... We have been discussing recently with the people working on profile-based conneg. 17:31:24 q+ 17:32:44 q+ 17:33:21 ack bigbluehat 17:33:49 pchampin: activity on the dx-connegp has been on and off for a while. We may want to provide some help. 17:35:23 bigbluehat: JSON-LD mostly needs to help downstream specifications know what to choose among the media type vs. profile negotiation vs. something else 17:35:39 ... we can and should point to the profile negotiation doc when it's available 17:35:45 niklasl: we at the National Libarry of Sweden, would really like to see a form of profile-based conneg. I think I could spend some time on this. 17:36:02 ... Part of it is orthogonal to JSON-LD. 17:36:17 bigbluehat: agreed, it is not a core issue for us. 17:37:33 ack niklasl 17:39:01 subtopic: dlehn PRs 17:41:27 dlehn: what should I do about those, until we have a solid decision about the desired behaviour. 17:41:49 bigbluehat: if you would post a comment spelling out the decision that we need to make, this would be helpful. 17:42:47 dlehn: this mostly came out from somebody reporting a bug. 17:44:50 TallTed: a possible resolution is "this is an edge case, we won't solve it now" 17:45:46 subtopic: https://github.com/json-ld/cbor-ld-spec/pull/22 17:45:47 https://github.com/json-ld/cbor-ld-spec/pull/22 -> Pull Request 22 Add OpenBadges v3.0.0 context URL to registry. (by BigBlueHat) 17:47:03 bigbluehat: this PR adds a context URL in the CBOR-LD registry 17:47:04 q+ 17:47:13 ack dlehn 17:47:22 ... Dmitri suggested to change from the version-less URL to the versionned one. 17:47:42 dlehn: aren't we moving away from the registry, for CBOR-LD? 17:47:52 ... People may continue to use the old stuff, though... 17:48:44 ... We need to refine how it is supposed to work. 17:49:25 bigbluehat: I'll ask Wes dans Dave Longley (who are most active on CBOR-LD these days) what they think of it. 17:49:52 ... This should be a more general discussion. 17:50:07 q+ 17:50:16 ack pchampin 17:52:07 pchampin: I'm uncorfortable with CBOR numbers pointing to URL with changing content. 17:52:17 ... But we need to discuss this with Wes and Dave Longley. 17:53:05 RRSAgent, make minutes 17:53:06 I have made the request to generate https://www.w3.org/2025/02/12-json-ld-minutes.html pchampin 17:53:18 present+ 17:53:26 I have made the request to generate https://www.w3.org/2025/02/12-json-ld-minutes.html TallTed 17:53:35 zakim, close this agendum 17:53:35 agendum 2 closed 17:53:35 zakim, end meeting 17:53:35 rrsagent, bye 17:53:35 I see no action items present+ bigbluehat