15:50:54 RRSAgent has joined #rdf-star 15:50:58 logging to https://www.w3.org/2026/06/25-rdf-star-irc 15:50:58 zakim, start meeting 15:50:58 meeting: RDF and SPARQL Working Group 15:50:58 RRSAgent, make logs Public 15:50:59 please title this meeting ("meeting: ..."), AndyS 15:51:10 meeting: RDF and SPARQL Working Group 15:51:28 previous meeting: https://www.w3.org/2026/06/18-rdf-star-minutes.html 15:51:28 next meeting: https://www.w3.org/2026/07/02-rdf-star-minutes.html 15:51:28 rrsagent, make logs public 15:52:02 agenda: https://www.w3.org/events/meetings/11e4d020-9c58-4fff-83c5-37c9e2502295/20260625T120000/#agenda 15:52:02 clear agenda 15:52:02 agenda+ RDF & SPARQL 1.2 "What is new" stable URL 15:52:02 agenda+ Vote about OWLification document -> 1 https://github.com/w3c/rdf-star-wg/issues/150 15:52:02 agenda+ SPARQL Issue Triage -> 2 https://github.com/orgs/w3c/projects/20/views/5 15:52:03 agenda+ Any Other Business (AOB), time permitting 15:52:15 rrsagent, please draft minutes 15:52:17 I have made the request to generate https://www.w3.org/2026/06/25-rdf-star-minutes.html AndyS 15:52:33 rubensworks has joined #rdf-star 15:52:48 present+ 15:54:37 present+ 15:55:05 tl has joined #rdf-star 15:55:11 regrets+ ora, fsasaki, j22, william-vw 15:57:40 draggett has joined #rdf-star 15:59:11 lisp has joined #rdf-star 15:59:14 niklasl has joined #rdf-star 15:59:31 present+ 16:00:13 present+ 16:00:20 pfps has joined #rdf-star 16:00:26 present+ 16:00:35 present+ 16:00:56 present+ 16:00:57 present+ 16:01:20 present+ 16:01:35 present+ 16:01:54 scribe: draggett: 16:01:56 scribe: draggett 16:02:16 Zakim, open item 1 16:02:16 agendum 1 -- RDF & SPARQL 1.2 "What is new" stable URL -- taken up [from agendabot] 16:02:18 present+ 16:02:29 chair: ktk 16:02:29 olaf has joined #rdf-star 16:02:31 present+ 16:02:37 present+ 16:03:25 pchampin: we've been asked to provide a stable URL for our draft 16:03:44 q? 16:03:50 Topic: RDF & SPARQL 1.2 "What is new" stable URL 16:03:51 +1 16:04:01 seems reasonable 16:04:09 q? 16:04:10 +1 16:04:20 [no objections] 16:04:21 +1 16:04:41 pchampin: we probably need a WG decision 16:05:09 PROPOSAL: publish rdf12-new as a WG Note Draft 16:05:11 TallTed: we don't need +1 16:05:22 ... for this 16:05:32 RESOLUTION: publish rdf12-new as a WG Note Draft 16:05:33 Adian asks pchampin to draft a resolution 16:05:41 q+ 16:06:01 https://w3c.github.io/rdf-new/spec/ 16:06:19 Souri has joined #rdf-star 16:06:23 present+ 16:06:45 Adrian: does this require one or two documents? 16:07:08 q+ 16:07:24 ack tl 16:07:25 pchampin: good question. The SPARQL document is at a very early stage, bare bones right now. 16:07:44 s/Adian/ktk/ 16:07:48 Consensus requires more than no objectsions 16:08:03 s/Adrian:/ktk:/ 16:08:08 doerthe has joined #rdf-star 16:08:15 present+ 16:08:29 TallTed: if we were arguing about the content of the document that would matter, but for now we just need documents we can point to 16:09:10 ack me 16:09:13 AndyS: we could argue that there is only one document to point to 16:09:21 q+ 16:09:30 ack pchampin 16:09:53 +1 to only one document 16:09:55 pchampin: I don't have a strong opinion right now. We could decide that all new SPARQL features belong in RDF-new 16:10:16 Adrian: we can defer that decision 16:10:28 q+ 16:10:46 AndyS: we need to decide right now in respect to what URLs to provide 16:11:29 ack TallTed 16:11:49 note that there is currently no sparql-new spec, so we do not break any expectation in that respect 16:11:58 (on TR I mean) 16:11:58 TallTed: we have a good number of documents .... I doubt that anyone will only implement SPARQL. We just need to make decision and I would prefer one for SPARQL and one for RDF 16:12:16 i retract my "+1 to only one document" and agree with ted 16:12:32 Makes sense to me (two). 16:12:35 Adrian: any objections to having two URLs? 16:12:42 [no] 16:13:13 ... asks pchampin to draft a resolution 16:13:22 PROPOSED: publish sparql12-new as a WG Note Draft https://w3c.github.io/sparql-new/spec/ 16:13:43 q? 16:13:50 +1 16:13:51 +1 16:13:52 +1 16:13:52 datestamped will be needed for stable *content* ... so there is small question whether they want stable *content* or stable *evolving* 16:13:52 +1 16:13:53 +1 16:13:53 +1 16:13:54 +1 16:13:55 +1 16:13:56 +1 16:13:57 +1 16:13:57 +1 16:13:59 + 16:14:04 +1 16:14:07 +1 16:14:21 RESOLUTION: publish sparql12-new as a WG Note Draft 16:14:54 s|RESOLUTION: publish sparql12-new as a WG Note Draft|RESOLUTION: publish sparql12-new as a WG Note Draft https://w3c.github.io/sparql-new/spec/ 16:14:55 pchampin agrees to publish the draft accordingly 16:15:01 Zakim, next item 16:15:01 agendum 2 -- Vote about OWLification document -> 1 https://github.com/w3c/rdf-star-wg/issues/150 -- taken up [from agendabot] 16:15:11 q+ 16:16:34 niklasl: this was a NOTE I created based upon discussions quite some time ago around expressing triple terms in respect to RDFS 16:17:10 .... explains further details 16:17:25 This could become a WG Note 16:17:44 Adrian: this stays as a separate document, right? 16:17:47 niklasl: yes 16:18:20 tl: I am unhappy about the way it talks about literals 16:18:24 ack tl 16:18:31 q+ 16:19:12 q+ 16:19:19 ... it becomes like text, but triple terms are not text 16:19:34 ... I can't subscribe to this 16:19:59 q- 16:20:20 q+ 16:20:43 Adrian: for now we shouldn't talk about the content, rather creating a WG Note 16:20:57 tl: okay, I am not against creating a Note 16:21:40 q? 16:21:40 Is the doc in a repo? or other collaborative editing space? 16:21:41 ack niklasl 16:21:50 q+ 16:21:51 niklasl: there is no place in the document that says that propositions are literals. I can improve the clarity of the account though 16:22:16 what document is this? 16:22:20 tl points to the wording he finds problematic 16:22:23 q+ to ask that the doc go into a repo or other collaborative editing space for further refinement? 16:22:40 https://niklasl.github.io/rdf-struct-patterns/spec/ 16:22:59 ack tl 16:23:14 given that we're now producing a WG NOTE, can that migrate to a WG repo? 16:23:18 niklasl: we can discuss the wording in github issues 16:23:31 https://niklasl.github.io/rdf-struct-patterns/spec/#properties-of-formal-structures 16:23:40 pfps: what document and what paragraph are we talking about? 16:23:58 niklasl: paragraph 3 in section 3 16:24:03 ack pfps 16:24:39 ack TallTed 16:24:39 TallTed, you wanted to ask that the doc go into a repo or other collaborative editing space for further refinement? 16:24:54 q+ 16:24:55 TallTed: given we've agreed that this becomes a WG Note, it should be moved to the WG repo 16:25:11 I still don't see what the issue is. 16:25:48 pchampin: [staff contact hat on] we already have several WG Notes, and worry that we don't dilute our efforts 16:25:50 Thomas was referring to the sentence "This is not necessary for propositions and literal values, since their meaning is completely encoded by their corresponding terms—ground triple terms and literals—in the abstract syntax.", for the exact problem you need to ask him 16:25:57 q? 16:26:04 ack pchampin 16:26:07 q+ 16:26:14 ack niklasl 16:26:29 niklasl: I sympathise with pchampin's concern 16:26:32 s/should be moved to the WG repo/should be moved to a WG repo/ 16:27:09 ... and working first on high priority documents 16:27:10 I'm still completely confused about the argument, which appears to be "X and Y are stated to share some characteristics therefore X and Y are the same". 16:27:16 q+ 16:27:26 ack tl 16:27:52 tl: the name shouldn't be too abstract 16:28:03 I have made the request to generate https://www.w3.org/2026/06/25-rdf-star-minutes.html TallTed 16:28:09 niklasl: we can change it later as we see fit 16:28:18 Create a note on "RDF 1.2 Properties of Formal Structures" (working title) 16:29:05 pchampin: the name isn't critical, what is important is to bring the document to a WG repo 16:29:19 PROPOSED: the WG adopts https://github.com/niklasl/rdf-struct-patterns/ for future publication as a WG Note 16:29:27 rubensworks has joined #rdf-star 16:29:35 +1 16:29:36 +1 16:29:37 +1 16:29:38 +0 16:29:38 +1 16:29:39 +0.5 16:29:39 +1 16:29:41 +1 16:29:41 +1 16:29:44 +1 16:29:45 +1 16:29:50 +1 16:30:03 RESOLUTION: Tthe WG adopts https://github.com/niklasl/rdf-struct-patterns/ for future publication as a WG Note 16:30:07 +0.7 (sounds like a good idea in absolute but I have not read it) 16:30:20 s/Tthe/The/ 16:30:45 Zakim, next item 16:30:45 agendum 3 -- SPARQL Issue Triage -> 2 https://github.com/orgs/w3c/projects/20/views/5 -- taken up [from agendabot] 16:31:19 q? 16:31:20 Just sort the display by Repository 16:31:37 Adrian: I tried to find a summary but failed. Let's open the discussion. 16:32:15 It is unrealistic to go through all the SPARQL issues in the time we have. 16:32:48 It is very likely that SPARQL will become a living spec. What is needed in the short term? 16:32:51 q+ 16:32:54 q+ 16:32:56 ack AndyS 16:33:39 AndyS: these are personal ideas: there are a few critical issues we should address (talks us through them) 16:33:56 These are all in the main spec 16:34:02 ack Tpt 16:34:20 q+ 16:34:51 https://github.com/w3c/sparql-query/issues/326 16:34:52 https://github.com/w3c/sparql-query/issues/326 -> Issue 326 Remaining erratas and errata-like issues (by Tpt) 16:34:55 ThomasT: I agree with AndyS that are a few big issues to fix and some others we would like to deal with 16:35:06 ack TallTed 16:35:19 https://github.com/w3c/sparql-query/pull/355 16:35:20 https://github.com/w3c/sparql-query/pull/355 -> Pull Request 355 Syntax scope requirements for (NOT)EXISTS (by afs) 16:35:20 TallTed asks AndyS to share the links to the critical issues 16:35:28 https://github.com/w3c/sparql-query/pull/355 16:36:29 https://github.com/w3c/sparql-query/pull/327 16:36:30 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:36:48 q? 16:38:18 gtw: I agree with AndyS 16:38:33 q+ 16:38:38 ack olaf 16:39:11 olaf: I also started working on a PR relating to property terms 16:39:34 s/Topic: RDF & SPARQL 1.2 "What is new" stable URL// 16:40:08 https://github.com/w3c/sparql-query/pull/396 16:40:10 I have made the request to generate https://www.w3.org/2026/06/25-rdf-star-minutes.html TallTed 16:40:16 https://github.com/w3c/sparql-query/pull/396 -> Pull Request 396 Evaluation of property path patterns that contain triple patterns (by hartig) 16:40:27 Adrian: please make a comment 16:40:48 q+ 16:40:53 AndyS: anybody with write access can edit the document 16:41:00 https://github.com/w3c/sparql-query/issues/53 16:41:01 https://github.com/w3c/sparql-query/issues/53 -> Issue 53 Incorporate RDF-star CG report (by rubensworks) [spec:substantive] 16:41:01 ack rubensworks 16:41:34 rubensworks: most of this was discussed some time ago, we can review that 16:42:01 Adrian: any implementor's feedback? 16:42:20 I have nothing to flag at this point 16:43:00 q? 16:43:07 james: nothing I would object to (earlier than the last 2 weeks which I haven't looked at) 16:43:07 q+ 16:43:29 Adrian: let's use Thomas's issue as the main one to work on 16:43:31 Will { ?x :p1/:p2 ?y } ever have any match if the only triple with :p1 as predicate has a triple term as object? EXAMPLE=> :bob :thinks <<( :alice :likes :bob )>> . 16:44:01 ack Tpt 16:44:21 Adrian: we should give everyone a chance to look at this 16:45:02 q? 16:45:24 Zakim, next item 16:45:24 agendum 4 -- Any Other Business (AOB), time permitting -- taken up [from agendabot] 16:45:34 q+ 16:45:38 ack pchampin 16:46:33 pchampin: I wanted to inform the WG that I heard back from the TAG in respect to MIME types, they have been looking at the PR and I will chat with the staff contact for the TAG 16:47:26 Adrian: i've heard from the ISWC re the joint session which looks good 16:47:58 is that question any different than a question about literals? 16:48:47 Adrian wrap the meeting up ... 16:49:00 rrsagent, make minutes 16:49:02 I have made the request to generate https://www.w3.org/2026/06/25-rdf-star-minutes.html draggett 16:50:09 olaf has left #rdf-star 16:52:11 rubenswo_ has joined #rdf-star