16:56:06 RRSAgent has joined #rdf-star 16:56:11 logging to https://www.w3.org/2025/12/18-rdf-star-irc 16:56:11 meeting: RDF-star WG meeting 16:56:37 Agenda: https://www.w3.org/events/meetings/e5234c80-4c06-4c6b-af43-c78a1dbd390a/20251218T120000/ 16:56:37 clear agenda 16:56:37 agenda+ Approval of last week’s minutes: -> 1 https://www.w3.org/2025/12/11-rdf-star-minutes.html 16:56:37 agenda+ Review of open actions, available at -> 2 https://github.com/orgs/w3c/projects/20/views/3 16:56:37 agenda+ Identifying issues to solve before CR -> 3 https://github.com/orgs/w3c/projects/20/views/8 16:56:39 agenda+ Any Other Business (AOB), time permitting 16:57:28 regrets+ tl, AZ 16:57:35 RRSAgent, draft minutes 16:57:36 I have made the request to generate https://www.w3.org/2025/12/18-rdf-star-minutes.html ktk 16:57:43 RRSAgent, make log public 16:59:16 AndyS has joined #rdf-star 16:59:21 lisp has joined #rdf-star 16:59:33 pfps has joined #rdf-star 16:59:38 olaf has joined #rdf-star 17:00:05 niklasl has joined #rdf-star 17:00:30 Dominik_T has joined #rdf-star 17:00:30 present+ 17:00:37 fsasaki has joined #rdf-star 17:00:42 present+ 17:00:42 present+ 17:00:46 present+ 17:00:49 present+ 17:00:58 present+ 17:01:01 I have made the request to generate https://www.w3.org/2025/12/18-rdf-star-minutes.html AndyS 17:01:16 ora has joined #rdf-star 17:01:39 Present+ 17:01:49 present+ 17:02:09 present+ 17:02:23 present+ 17:02:50 scribe+ 17:02:58 present+ 17:03:01 chair+ 17:03:26 Zakim, open item 1 17:03:26 agendum 1 -- Approval of last week’s minutes: -> 1 https://www.w3.org/2025/12/11-rdf-star-minutes.html -- taken up [from agendabot] 17:03:49 ora: comments about last week's minutes? 17:03:54 PROPOSAL: Approve last week's minutes 17:04:07 +1 17:04:07 +0 17:04:10 +1 17:04:11 +1 17:04:12 +1 17:04:14 +1 17:04:15 +1 17:04:18 +1 17:04:18 +1 17:04:22 +1 17:04:25 +0 17:04:27 +1 17:04:34 +1 17:04:56 RESOLVED: Approve last week's minutes 17:05:01 Zakim, next item 17:05:01 agendum 2 -- Review of open actions, available at -> 2 https://github.com/orgs/w3c/projects/20/views/3 -- taken up [from agendabot] 17:05:19 ora: I haven't completed my actions 17:05:27 q+ 17:05:38 ... but promise that I will work on them over the (upcoming) holidays 17:06:14 ack pchampin 17:06:17 pchampin: RDF-INTEROP is published 17:06:25 ... Echidna is set up for it 17:06:50 ora: Can we close this action? 17:07:25 pchampin: Let's keep it open until we know that Echidna runs correctly once we merge a PR 17:08:02 TallTed has joined #rdf-star 17:08:15 niklasl: I have updated the text to use the term for INTEROP 17:09:05 Zakim, next item 17:09:05 agendum 3 -- Identifying issues to solve before CR -> 3 https://github.com/orgs/w3c/projects/20/views/8 -- taken up [from agendabot] 17:09:06 ora: okay, let people comment on the action 17:09:35 ora: What did we hear from the TAG? 17:09:59 pchampin: I got a message from Sarven a minute before this call. 17:10:11 ... there are responses on the horizontal review issues 17:10:12 https://github.com/w3ctag/design-reviews/issues/1161#issuecomment-3671223503 17:10:13 https://github.com/w3ctag/design-reviews/issues/1161 -> Issue 1161 WG New Spec: RDF 1.2 N-Triples (by pchampin) [Review type: horizontal review] [Resolution: ambivalent] 17:10:31 ... I haven't looked at the issues in detail yet 17:10:46 ... but I know that the TAG is concerned with the version announcement 17:10:59 ... they don't intent to block anything 17:11:07 https://github.com/w3ctag/design-reviews/issues/1159#issuecomment-3671161845 17:11:08 https://github.com/w3ctag/design-reviews/issues/1159 -> Issue 1159 WG New Spec: RDF 1.2 Concepts and Abstract Data Model (by pchampin) [Review type: horizontal review] [Resolution: satisfied with concerns] 17:11:24 ... Sarven's message contains some advice on what the TAG thinks we should do. 17:11:42 ... The expectation is that we clarify how the version announcement should be used. 17:12:02 ... because it has the potential to break some uses of RDF 17:12:03 q+ 17:12:26 ora: Should we add some language to the spec or just let this go? 17:12:43 pchampin: Additional language won't hurt? 17:12:48 ora: Will it help? 17:12:54 N-Triples could never be "just concatenated". :\ 17:13:00 pchampin: It will help the TAG ;-) 17:13:07 ack AndyS 17:13:37 AndyS: Where is the comment about the media type not changing? 17:14:03 pchampin: I had some conversations with Sarven and (?) 17:14:13 ... they see hat we consider both options 17:14:19 s/hat/that 17:14:33 AndyS: You can ask them about CSS versioning. 17:15:04 ... Regarding declaring version, we could note in Concepts that, at the moment, 17:15:23 ... things are stacked. You should choose the highest version. 17:15:32 ora: Good idea. 17:15:33 q+ 17:15:38 ack ktk 17:15:52 ktk: The bnode argument should be used. 17:16:43 ora: Regarding the bnode issue, I have many people made the case that you can just split and concatenate. They don't think about the bnodes! 17:16:56 ora: Volunteers to add some language to Concepts? 17:17:12 AndyS: Yes, me. It should be only one sentence. 17:17:48 ora: What about implementation reports? 17:17:52 pchampin: We had two calls on this topic, minutes: 1) https://github.com/w3ctag/meetings/blob/gh-pages/2025/telcons/12-08-minutes.md#design-reviews1159-wg-new-spec-rdf-12-concepts-and-abstract-data-model-github---csarven-1 . 2) will go up sometime this week (placed in the same directory) 17:18:18 ^ Some background on other formats.. and why they are not exactly comparable to this situation. 17:18:23 q+ 17:18:30 (Sorry to drive-by share text.. can't join.. :) 17:18:35 ora: What's the rule? We need two implementations, right? 17:18:45 ack pchampin 17:18:53 pchampin: We need two independent implementations for every feature. 17:19:19 ... So, in theory, we may have only incomplete implementation. 17:19:28 ora: For each *new* feature? 17:20:02 pchampin: The way it is measured is that the tests pass. 17:20:15 ktk: What does "feature" mean? 17:20:46 TallTed: The purpose is to show that every feature, as defined in the spec, can indeed be implemented. 17:21:27 pchampin: In terms of tests, we can reuse from the RDF-star CG 17:21:46 ... We also discussed the EARL reports. 17:22:00 doerthe has joined #rdf-star 17:22:06 present+ 17:22:23 AndyS: Do we know two people who can cover the semantics tests? 17:22:37 ... They seem to have been broken since 6 months. 17:22:49 ... Apparently, none is running them. 17:23:02 ... Who has implementations for semantics tests? 17:23:18 q+ 17:23:35 ora: Are you saying these are not serious things? 17:24:00 ack doerthe 17:24:01 AndyS: The fix is trivial. It just shows that none is running the tests. 17:24:15 q+ 17:24:26 ack pchampin 17:24:38 doerthe: I could try to implement something (in January) to be able to run these test. 17:25:01 pchampin: Corese implements the specs and they are currently considering the tests. 17:25:21 ... They may not have come to the semantics test, but we can count on them to get to it. 17:25:33 q+ 17:25:41 ora: Anything else to discuss regarding getting to CR? 17:25:49 https://github.com/ad-freiburg/sparql-conformance 17:25:50 ack ktk 17:26:22 ktk: QLever team build this. It is not specific to QLever. 17:26:38 ... It is a test *suite* to run the tests. 17:26:47 AndyS: Good to see that. 17:26:53 I also have one for Sophia, but I need to publish the code, though 17:27:10 ... We (with Thomas and Ruben) are working on the SPARQL tests. 17:27:39 ora: Other business then? 17:27:48 AndyS: Back to TAG response 17:28:10 ... (reading comment from the GitHub issue) 17:28:23 ... "accidentally" 17:28:44 pchampin: Looks like a misunderstanding. 17:29:20 ora: Any "RDF-star" feature would mean new details in the synatx, which would break old stuff. 17:29:26 AndyS: Text direction as well. 17:29:42 pchampin: Arguably, text direction could be ambiguous. 17:29:55 ... Turtle grammar allows for something. 17:30:44 Turtle 1.1: [144s] LANGTAG ::= '@' [a-zA-Z]+ ('-' [a-zA-Z0-9]+)* 17:30:45 ... RDF 1.1 Turtle parser can be expected to still parse it and assume it is a language tag. The grammar allows that. 17:30:57 AndyS: That's not true. 17:31:21 ... We are save. 17:31:31 pchampin: Right, I was wrong. 17:31:47 ora: Should we tell TAG this? 17:31:53 ... I think we should. 17:32:17 ... In addition, should we have some language in the spec, because it may not be obvious to the readers. 17:32:33 AndyS: There is a sentence hat kinda covers that. 17:32:37 q+ 17:32:38 s/hat/that 17:32:58 ack pchampin 17:33:10 pchampin: Two things: 17:33:45 ... 1) the abstract syntax extends the 1.1 syntax and 2) every concrete syntax extends its 1.1 version 17:33:54 q+ 17:34:09 ... We can prep some boilerplate that we can use in all syntax-related specs. 17:34:28 ... Maybe we should add something in the Changes section. 17:34:33 ack AndyS 17:34:42 ... I can prepare something. 17:35:02 AndyS: That's an argument for Trig, Turtle, etc, but RDF/XML is different. 17:35:26 ... I am not sure what the spec says. 17:35:41 ... The processing algorithm might not catch it. 17:35:56 ora: We should check. 17:36:23 ... And put some additional language about it in the RDF/XML spec. 17:36:25 I can open an issue on the rdf/xml to make sure that this is ok 17:36:33 ... We didn't change the syntax of XML. 17:36:47 ... yes, j22, please open an issue 17:36:59 ora: Anyhting else? 17:37:08 zakim, next item 17:37:08 agendum 4 -- Any Other Business (AOB), time permitting -- taken up [from agendabot] 17:39:00 q+ 17:40:22 ack AndyS 17:40:50 I opened https://github.com/w3c/rdf-xml/issues/77 17:40:51 https://github.com/w3c/rdf-xml/issues/77 -> Issue 77 Ensure that the attributes and elements do not cause issues for rdf/xml 1.0/1.1 (by JervenBolleman) 17:41:11 q+ 17:45:29 q+ 17:46:34 ack ktk 17:50:11 ack j 17:51:47 if you want to trust a good bunchmark have a validated LDBC one 17:53:44 Want to note that due to high compliance to standards in rdf/sparql world that it is easy to actually benchmark your own workload on many endpoints. 17:56:22 RRSAgent, make minutes 17:56:24 I have made the request to generate https://www.w3.org/2025/12/18-rdf-star-minutes.html pchampin 17:58:34 olaf has left #rdf-star present+ TallTed previous meeting: https://www.w3.org/2025/12/11-rdf-star-minutes.html next meeting: https://www.w3.org/2026/01/08-rdf-star-minutes.html