15:56:43 RRSAgent has joined #rdf-star 15:56:47 logging to https://www.w3.org/2026/06/04-rdf-star-irc 15:56:47 zakim, start meeting 15:56:47 RRSAgent, make logs Public 15:56:48 please title this meeting ("meeting: ..."), AndyS 15:56:59 meeting: RDF and SPARQL Working Group 15:57:11 https://www.w3.org/events/meetings/e5234c80-4c06-4c6b-af43-c78a1dbd390a/20260604T120000/#agenda 15:57:20 agenda: https://www.w3.org/events/meetings/e5234c80-4c06-4c6b-af43-c78a1dbd390a/20260604T120000/#agenda 15:57:20 clear agenda 15:57:20 agenda+ Approval of minutes from the last two meetings: -> 1 https://www.w3.org/2026/05/21-rdf-star-minutes.html -> 2 https://www.w3.org/2026/05/28-rdf-star-minutes.html 15:57:20 agenda+ Feedback from Threat Modeling Plenary session 15:57:21 agenda+ Review of open actions, available at -> 3 https://github.com/orgs/w3c/projects/20/views/3 15:57:22 agenda+ Review of open PRs, available at -> 4 https://github.com/orgs/w3c/projects/20/views/4 15:57:25 agenda+ Identifying issues to solve before CR -> 5 https://github.com/orgs/w3c/projects/20/views/5 15:57:28 agenda+ Any Other Business (AOB), time permitting 15:57:41 previous meeting: https://www.w3.org/2026/05/28-rdf-star-minutes.html 15:57:41 next meeting: https://www.w3.org/2026/06/11-rdf-star-minutes.html 15:57:48 present+ 15:57:58 present+ 15:58:09 rrsagent, make logs public 15:58:10 rrsagent, please draft minutes 15:58:11 I have made the request to generate https://www.w3.org/2026/06/04-rdf-star-minutes.html AndyS 15:58:18 agenda? 15:58:23 TallTed has joined #rdf-star 15:58:40 lisp has joined #rdf-star 15:58:43 present+ 15:58:45 olaf has joined #rdf-star 15:59:52 present+ 16:00:02 present+ 16:00:12 present+ 16:00:36 present+ 16:00:44 doerthe has joined #rdf-star 16:00:53 present+ 16:01:03 present+ 16:01:07 regrets+ AZ, Dominik_T 16:01:35 present+ 16:02:10 niklasl has joined #rdf-star 16:02:21 william-vw has joined #rdf-star 16:02:24 present+ 16:02:30 I have made the request to generate https://www.w3.org/2026/06/04-rdf-star-minutes.html TallTed 16:02:37 scribe+ 16:02:46 ora has joined #rdf-star 16:03:01 present+ 16:03:01 chair+ 16:03:20 present+ 16:03:25 s|https://www.w3.org/events/meetings/e5234c80-4c06-4c6b-af43-c78a1dbd390a/20260604T120000/#agenda|| 16:03:27 Zakim, open item 1 16:03:28 agendum 1 -- Approval of minutes from the last two meetings: -> 1 https://www.w3.org/2026/05/21-rdf-star-minutes.html -> 2 https://www.w3.org/2026/05/28-rdf-star-minutes.html -- 16:03:31 ... taken up [from agendabot] 16:03:47 Souri has joined #rdf-star 16:03:53 present+ 16:03:54 present+ 16:03:54 minutes are acceptable (but last week's is not great) 16:03:59 present+ 16:04:40 I have made the request to generate https://www.w3.org/2026/06/04-rdf-star-minutes.html TallTed 16:04:52 I can fix that 16:04:56 tl has joined #rdf-star 16:05:23 PROPOSAL: Approve minutes from 2026-05-21 and 2026-05-28 16:05:25 +0.5 (+1 with fix) 16:05:26 +1 16:05:27 +1 16:05:30 +1 16:05:30 +1 16:05:31 +1 16:05:32 +1 16:05:33 +1 16:05:43 +1 16:05:43 +1 16:05:43 present+ 16:05:43 +1 16:05:43 s|https://www.w3.org/events/meetings/e5234c80-4c06-4c6b-af43-c78a1dbd390a/20260604T120000/#agenda|| 16:05:43 s|agenda:|agenda: https://www.w3.org/events/meetings/e5234c80-4c06-4c6b-af43-c78a1dbd390a/20260604T120000/#agenda| 16:05:50 +1 16:05:55 I have made the request to generate https://www.w3.org/2026/06/04-rdf-star-minutes.html TallTed 16:06:01 +0 (didn't attend) 16:06:07 +1 16:06:10 +1 16:06:19 +1 for 5/28, +0 for 5/21 16:06:30 RESOLVED: Approve minutes from 2026-05-21 and 2026-05-28 16:06:30 Zakim, next item 16:06:30 agendum 2 -- Feedback from Threat Modeling Plenary session -- taken up [from agendabot] 16:08:26 ktk: the meeting was a two hour discussion, quite academic at the beginning, explanation where we fit in, a lot of details 16:09:12 .. in my opinion: it is as complicated as we make it, we should not try to make a thread model for the RDF as a whole 16:09:28 s|thread|threat 16:09:31 .. so we should do it separated 16:09:33 q+ 16:09:47 ack pchampin 16:10:29 pchampin: I agree with ktk, I had some more discussions afterwards within W3C, we should make it simple 16:10:45 .. we should make diagrams much more focussed 16:11:33 q+ 16:11:37 .. goal should be to refrain what we already have into this new framework. I think that we could do a single document where we could all point to 16:11:38 ack AndyS 16:12:33 q+ 16:12:55 AndyS: pchampin helped to keep the focus, there were 10 experts on the topic who were very interested in the details, we should still keep it simple 16:13:21 ack pchampin 16:14:33 pchampin: the json-ld working group is also active, they will take care of json-ld. We will not have to tackle it. JSON-ld depends on external date 16:14:53 s|external date|external data 16:14:56 good to know, thanks :) 16:15:00 q+ 16:15:06 ack TallTed 16:15:20 AndyS: the JSON-LD issue even comes up in automatic scans 16:16:15 TallTed: There is a push to align JSON-LD 1.2 with RDF and SPARQL 1.2. Version numbers do not line up 16:16:56 .. maybe we could have a JSON 1.12 or similar and then later on align with RDF 1.2 16:17:33 q+ 16:18:01 .. it was discussed in an issue 16:18:06 ack pchampin 16:19:10 pchampin: I am aware of the issue. It was a choice of the JSON-LD working group to not align yet 16:19:45 Souri has joined #rdf-star 16:19:49 .. it is not ideal, but it is not easy to align all version numbers, whihc is why they opted against it 16:19:57 present+ 16:20:01 s|whihc|which 16:20:15 ora: they have to state that there is no meaningful connection between version numbers 16:20:22 .. next step? 16:20:38 q+ 16:20:44 ack pchampin 16:21:13 pchampin: I will try to make more focussed diagrams, help welcome 16:21:35 .. I plan to do that in the coming weeks 16:21:43 ktk: I can review 16:22:27 q? 16:22:31 Zakim, next item 16:22:31 agendum 3 -- Review of open actions, available at -> 3 https://github.com/orgs/w3c/projects/20/views/3 -- taken up [from agendabot] 16:22:48 q+ 16:22:51 i|I am aware of the issue|https://github.com/w3c/json-ld-syntax/issues/488 16:22:59 ack TallTed 16:23:31 TallTed: github has new views, maybe we can use that 16:23:44 q+ 16:24:15 ack pchampin 16:24:55 pchampin: I added the comments, TallTad moved them to a visible place, we can use it 16:29:03 ora: I asked the ISWC (190) organizers but got no response so far 16:29:17 .. I will ping them 16:29:38 reviews were due today, so yes, maybe ping them in a week or so :) 16:30:21 AndyS: I did 3 PRs (#190) 16:30:21 https://github.com/w3c/rdf-star-wg/issues/190 -> Action 190 email the ISWC organizers (on rdfguy) due 2026-05-21 16:30:24 Zakim, next item 16:30:24 agendum 4 -- Review of open PRs, available at -> 4 https://github.com/orgs/w3c/projects/20/views/4 -- taken up [from agendabot] 16:41:38 ora: let's talk about https://github.com/w3c/rdf-new/pull/20, did we already talk about it 16:41:39 https://github.com/w3c/rdf-new/pull/20 -> Pull Request 20 the version published on GH pages must not be formatted as a DNOTE (by pchampin) 16:41:59 pchampin: pretty straight forward, I think we can merge 16:42:17 ora: https://github.com/w3c/rdf-tests/pull/260 ? 16:42:18 https://github.com/w3c/rdf-tests/pull/260 -> Pull Request 260 Beginning of manifest validations using SHACL (by Tpt) 16:42:57 ThomasTanon: I still need to finish it 16:43:24 ora: https://github.com/w3c/rdf-tests/pull/296 ? 16:43:25 https://github.com/w3c/rdf-tests/pull/296 -> Pull Request 296 More testing of triple terms in RDF/XML (by afs) 16:44:08 AndyS: we need a new policy for RDF-XML, here we need a decision 16:44:35 .. same for https://github.com/w3c/rdf-tests/pull/301 16:44:35 https://github.com/w3c/rdf-tests/pull/301 -> Pull Request 301 RDF/XML: add a test to make sure the parser fails on unknown rdf:parseType value (by Tpt) 16:45:34 ora: what does the spec say at the moment? 16:46:05 AndyS: unknown terms are parsed as literals 16:46:11 niklasl has joined #rdf-star 16:46:35 .. we need to discuss with jerven, to better know what to do 16:46:41 s/as literals/as RDF XMLliterals/ 16:47:09 ora: https://github.com/w3c/sparql-query/pull/327 ? 16:47:09 https://github.com/w3c/sparql-query/pull/327 -> Pull Request 327 Clarify that unaggregated variables in SELECT raise an error (by Tpt) [spec:bug] 16:47:57 .. what is preventing this from being merged? 16:48:16 AndyS: it is not clear what the spec says 16:48:43 .. these are long-term issues we have to sort out, but maybe they do not have priority 16:49:23 ora: https://github.com/w3c/rdf-concepts/pull/275 ? 16:49:23 https://github.com/w3c/rdf-concepts/pull/275 -> Pull Request 275 add note about sets of quads vs. dataset (by pchampin) 16:50:12 pchampin: I updated it and it has less details now to avoid confusion 16:51:37 q? 16:52:25 lisp has joined #rdf-star 16:55:53 AndyS: can I get approvals for https://github.com/w3c/sparql-query/pull/383 ? 16:55:53 https://github.com/w3c/sparql-query/pull/383 -> Pull Request 383 GH-382: Move numeric escape sequences into the grammar (by afs) 16:58:49 RRSAgent, make minutes 16:58:51 I have made the request to generate https://www.w3.org/2026/06/04-rdf-star-minutes.html pchampin 17:00:09 s/focussed/focused/ 17:00:28 s/TallTad/TallTed/ 17:00:39 s/straight forward/straightforward/ 17:00:48 s/RDF XMLliterals/RDF XML literals/ 17:00:54 s/json-ld/JSON-LD/g 17:01:02 s/JSON-ld/JSON-LD/g 17:01:14 RRSAgent, make minutes 17:01:16 I have made the request to generate https://www.w3.org/2026/06/04-rdf-star-minutes.html ktk 17:01:52 s/focussed/focused/g 17:02:51 s/refrain/reframe/ 17:02:54 RRSAgent, make minutes 17:02:55 I have made the request to generate https://www.w3.org/2026/06/04-rdf-star-minutes.html ktk 17:03:56 RRSAgent, leave 17:03:56 I see no action items