16:11:14 RRSAgent has joined #rdf-star 16:11:19 logging to https://www.w3.org/2023/12/14-rdf-star-irc 16:30:53 gkellogg has joined #rdf-star 16:46:40 AndyS has joined #rdf-star 16:48:44 gkellogg has joined #rdf-star 16:49:48 Anyone know where the scribes list is kept? https://github.com/w3c/rdf-star-wg/blob/main/docs/scribes.md is 7 months old. 16:56:32 AndyS: I rotate them in my head 16:56:57 enrico has joined #rdf-star 16:57:01 present+ 16:58:02 AndyS: I do go through the one you posted I think https://github.com/w3c/rdf-star-wg/blob/main/docs/scribes.md 16:59:47 eBremer has joined #rdf-star 16:59:47 Agenda: https://www.w3.org/events/meetings/0a6aa6e3-635c-42c2-baba-938c76b6ef01/20231214T120000/ 16:59:51 clear agenda 16:59:51 agenda+ Approval of minutes from the last two metings: [1] 16:59:51 agenda+ Proposal for next week's discussion 16:59:51 agenda+ Review of open actions, available at [2] 16:59:51 agenda+ Review of pull requests, available at [3] 16:59:52 agenda+ Issue Triage, available at [4] 16:59:55 agenda+ Any Other Business (AOB), time permitting 16:59:59 present+ 16:59:59 meeting: RDF-star WG biweekly meeting 16:59:59 rrsagent, draft minutes 17:00:01 I have made the request to generate https://www.w3.org/2023/12/14-rdf-star-minutes.html TallTed 17:00:03 rrsagent, make logs public 17:00:09 zakim, start meeting 17:00:09 RRSAgent, make logs Public 17:00:11 please title this meeting ("meeting: ..."), pchampin 17:00:17 ora has joined #rdf-star 17:00:40 scribe+ 17:00:42 present+ 17:00:58 Chair: Ora 17:01:07 meeting: RDF-star WG biweekly short meeting 17:01:17 gkellogg has joined #rdf-star 17:01:22 present+ 17:01:25 present+ 17:01:26 present+ 17:01:39 niklasl has joined #rdf-star 17:01:39 s/scribe+/scribe: ktk 17:01:50 tl has joined #rdf-star 17:01:50 RRSAgent, draft minutes 17:01:51 I have made the request to generate https://www.w3.org/2023/12/14-rdf-star-minutes.html TallTed 17:01:57 AZ has joined #rdf-star 17:02:00 meeting: RDF-star Working Group Weekly Meeting 17:02:02 present+ 17:02:11 present+ 17:02:23 present+ 17:02:34 present+ 17:03:03 Zakim, next item 17:03:03 agendum 1 -- Approval of minutes from the last two metings: -- taken up [from 1] 17:03:34 present+ 17:03:47 doerthe has joined #rdf-star 17:03:47 https://www.w3.org/2023/11/30-rdf-star-minutes.html 17:03:48 s/metings/meetings/ 17:03:50 present+ 17:04:05 pfps has joined #rdf-star 17:04:07 q? 17:04:20 PROPOSAL: Approve minutes 2023-11-30 17:04:25 +1 17:04:26 +1 17:04:26 +1 17:04:28 it needs a s/metings/meetings/g :-) 17:04:28 +1 17:04:31 +1 17:04:35 +1 17:04:38 +1 17:04:57 +0 (I was not there) 17:05:00 +1 17:05:01 present+ 17:05:01 +1 17:05:03 +1 17:05:10 RESOLUTION: Approve minutes 2023-11-30 17:05:20 present+ 17:05:29 https://www.w3.org/2023/12/07-rdf-star-minutes.html 17:05:59 PROPOSAL: Approve minutes 2023-12-07 17:06:07 q? 17:06:17 +1 17:06:19 +1 17:06:22 +1 17:06:22 +1 17:06:22 +1 17:06:23 +1 17:06:27 +1 17:06:29 +1 17:06:53 +1 17:06:57 +0 (I wasn't there) 17:07:03 +1 17:07:09 can pierre-antoine but a topic into these minutes? 17:07:28 s/but/put/ 17:07:47 ... topic suggestion to follow 17:07:54 olaf has joined #rdf-star 17:07:59 RRSAgent, draft minutes 17:08:00 I have made the request to generate https://www.w3.org/2023/12/14-rdf-star-minutes.html TallTed 17:08:06 RESOLUTION: Approve minutes 2023-12-07 17:08:24 Zakim, next item 17:08:24 agendum 2 -- Proposal for next week's discussion -- taken up [from agendabot] 17:08:35 s/AndyS: I rotate them in my head/ AndyS, I rotate them in my head 17:08:45 Souri has joined #rdf-star 17:08:49 present+ 17:09:09 present+ 17:09:14 q+ 17:09:17 ... probably something like "discussion on how to proceed" 17:09:26 Ora: We did not converge on anything. There are a lot of interesting proposals on the table. As the chair, I wouldn't want to kill them off but the reality is we need to come to an agreement about the direction of our work. Lately there was more about Souris proposal. I'm not done with my analysis. 17:09:33 ... It looks interesting. 17:09:37 RRSAgent, draft minutes 17:09:38 I have made the request to generate https://www.w3.org/2023/12/14-rdf-star-minutes.html TallTed 17:09:44 q+ 17:09:44 ... I understand the goals of it. 17:09:54 ... I guess regarding that my question is about the existing RDF 1.1 semantics. 17:09:54 ack AndyS 17:10:10 AndyS: Are we having a meeting next week? It's close to Xmas. And the next few weeks. 17:10:19 q+ 17:10:48 pchampin - I've messed up the pre-item-1 section beyond `s` fixing. please clean that after meeting ends 17:11:23 ack Souri 17:11:24 q- 17:12:31 q+ 17:12:35 Souri: Please look at my slides I posted today at 4AM, not at the ones before. 17:13:30 I can attend next week, but I may not be available on 4 Jan 17:13:36 +1 next week okay for me 17:13:41 ora: Proposal is we keep the meetings on 21.12.23 and 4.1.24 17:13:45 I wouldn't be available for any of the two meetings (neither next Thursday nor the Thursday after) 17:13:47 I can attend next week 17:13:56 ... and only the one in between is cancelled 17:13:59 I also can't attend both meetings 17:15:03 21 is fine by me 17:15:51 Ora: We cancel the one on 28.12. 17:16:00 Ora: So what are we gonna talk about. 17:16:05 ack tl 17:16:40 q+ 17:16:47 tl: To understand the timeline. The WG is scheduled until August. At what time would we have to publish something. What is the timeline for a decision? 17:16:49 ack pchampin 17:17:44 q+ 17:17:57 pchampin: The steps for getting a recommendation is a proposed recommendation, which needs to be approved by the members. Before that we need a candidate recommendation. And we at least need 28 days for that. So in total at least 2 months, which is a very optimistic, non realistic scenario. 17:18:00 https://www.w3.org/2022/08/rdf-star-wg-charter/#timeline 17:18:38 ... We are late based on our planing. Realisticly we will need a charter extension. 17:18:56 ack gkellogg 17:20:11 gkellogg: A new charter needs to reflect the reality. But most important it needs to reflect what we want to do. 17:20:23 fwiw -- Souri's latest (4am) RDFn slides -- https://lists.w3.org/Archives/Public/public-rdf-star-wg/2023Dec/att-0045/RDFn_Slides_Dec_14_2023.pdf 17:20:50 ora: I would like to understand Souris proposal, with the RDF 1.1 semantics compatibility. 17:20:51 q+ 17:20:53 q+ 17:20:53 q+ 17:20:59 q+ 17:21:04 q+ 17:21:08 ack niklasl 17:21:49 +1 to considering use cases 17:21:49 q- 17:21:49 niklasl: Use cases. Not opposed to Souris proposal, pfps analyzed them and we need to keep them in mind. For this proposal and possibly some others. 17:22:08 ... Also the proposals regarding the doubts of named graphs. They should be kept in mind in the background. 17:22:08 ack pchampin 17:22:31 pchampin: +1 on use cases, I would like to see how it impacts the abstract syntax as well. 17:23:05 ack ktk 17:23:16 ... I know Souri said it's not implementation focussed, but it still has very much an implementation taste for me. So I'm interested what changes it applies to the abstract syntax. 17:23:18 scribe+ 17:23:49 ktk: we has a discussion with Ora about the impact of the different proposals, 17:24:02 +1 for meaning for abstract syntax (e.g. what "multiple asserted" within the same graph means) 17:24:08 ... we are taking about a 1.x version, we are not supposed to break things. 17:24:28 +1 semantic-style versioning. 1.2 should not break 1.1, 1.0. 2.0 branding will be needed for breaking changes. 17:24:33 q+ 17:24:34 ack AndyS 17:24:51 ... I would like to look at each proposal in that perspective. 17:25:22 https://lists.w3.org/Archives/Public/public-rdf-star-wg/2023Dec/0033.html 17:25:23 scribe- 17:25:56 AndyS: I tried to summarize my take of the discussions and put them on the list. 17:26:09 ack tl 17:26:10 ... I would like to talk about that. 17:26:43 tl: RDF Star introduces a new term, this doesn't break RDF 1.x but it is a fundamental change. 17:27:19 ora: if we say it doesn't break it means the existing RDF 1.1 continues to work as it has. 17:27:37 q+ 17:27:39 ... can the next week's discussion be use to discuss Andys summary proposal and Souris work 17:27:46 ack enrico 17:28:09 enrico: I was thinking about Andys proposal. This merits some discussions, it's a simple and clear proposal. 17:28:28 +1 discuss AndyS's post [1] and Souri's slides [2]. [1] https://lists.w3.org/Archives/Public/public-rdf-star-wg/2023Dec/0033.html [2] https://lists.w3.org/Archives/Public/public-rdf-star-wg/2023Dec/att-0045/RDFn_Slides_Dec_14_2023.pdf 17:28:44 ... The minimal thing is to do what was proposed in the CG. Or we can go further like Andys proposal. 17:28:54 ... We can discuss this further in the semantics TF tomorrow. 17:29:32 Ora: What TallTed put in IRC is a very good description of the topics. 17:29:41 Zakim, next item 17:29:41 agendum 3 -- Review of open actions, available at -- taken up [from 2] 17:29:53 https://github.com/orgs/w3c/projects/20/views/3 17:31:21 pchampin: Shortnames now point to the latest REC, not the very latest. 17:31:37 ... Some missmatches are made consistent as well. 17:31:42 q+ to claim victory on 4/ 17:31:49 q+ what about https://www.w3.org/TR/n-triples/? 17:32:00 q+ to ask what about https://www.w3.org/TR/n-triples/? 17:33:12 gkellogg: n-triples does not seem to point to the right one yet. 17:33:31 pchampin: Superseeding is still a mistery to me. I keep investigating. 17:33:44 q? 17:33:52 ack me 17:33:52 gkellogg, you wanted to ask what about https://www.w3.org/TR/n-triples/? 17:34:15 ack pfps 17:34:15 pfps, you wanted to claim victory on 4/ 17:34:25 +1 for "no less than CR" 17:34:37 pfps: I'm claiming victory on mine. I looked at all use cases from the summary page. 17:34:58 TallTed has joined #rdf-star 17:35:10 AndyS: I claim victory on mine. 17:35:44 Zakim, next item 17:35:44 agendum 4 -- Review of pull requests, available at -- taken up [from 3] 17:35:55 https://github.com/orgs/w3c/projects/20/views/4 17:36:24 q? 17:37:08 s/Superseeding/Superseding 17:37:22 RRSAgent, draft minutes 17:37:23 I have made the request to generate https://www.w3.org/2023/12/14-rdf-star-minutes.html TallTed 17:37:42 q+ to talk about PR on scribes.md not listed here 17:39:36 s/21.12.23 and 4.1.24/2023-12-21 and 2024-01-04 17:39:50 s/on 28.12/on 2023-12-28 17:40:53 ack AZ 17:40:53 AZ, you wanted to talk about PR on scribes.md not listed here 17:41:35 q+ 17:41:56 ack pchampin 17:42:01 https://github.com/w3c/rdf-star-wg/pull/97 17:42:23 AZ: I have a pull-request on scribes but it does not show up 17:42:28 ktk: I will take care of it, thanks. 17:42:44 action: pchampin to add the rdf-star-wg repo to the dashboard 17:42:51 Created -> action #100 https://github.com/w3c/rdf-star-wg/issues/100 17:42:51 pchampin: I will add the RDF-Star WG repo to the dashboard 17:43:45 there are a few more languishing PRs on rdf-star-wg -- https://github.com/w3c/rdf-star-wg/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-asc 17:43:54 q+ 17:44:15 ora: The JSON one is still open. 17:44:22 q- 17:44:28 gkellogg: We reached an impasse 17:44:44 pfps: someone will need to nail down the lexical space. 17:44:45 +1 for until more bandwith 17:45:04 s/bandwith/bandwidth/ 17:45:14 gkellogg: I suggest we defer this issue until we come to conclusion of the more fundamential issues. 17:45:37 ora: agreed. 17:45:42 Zakim, next item 17:45:42 agendum 5 -- Issue Triage, available at -- taken up [from 4] 17:45:50 https://github.com/orgs/w3c/projects/20/views/5 17:46:10 q+ 17:46:24 ack gkellogg 17:46:43 gkellogg: we better discuss https://github.com/orgs/w3c/projects/20/views/6 17:46:49 q+ 17:47:17 ... regarding that, once we finished case normalization & concepts, that brings back what do we do when normalizing n-quads and n-triples. 17:48:10 ack AndyS 17:48:56 AndyS: yes, I thought we agreed on that and not mentioning particular case concepts in RDF concepts. Because it goes into canonicalization 17:49:15 gkellogg: I will do a pull-request based upon that direction. 17:50:20 q? 17:51:49 https://xkcd.com/2867/ 17:53:13 AndyS: implicit timezones. For SPARQL or the web, implicit timezones are less useful. Proposal to make this explicit. 17:53:51 q+ 17:53:51 q? 17:54:01 ack pchampin 17:55:22 pchampin: I sympathise with Andys reasoning. But setting it to Z makes it more likely to betray the authors intention. 17:55:38 AndyS: that's the problem with deciding, someone is unhappy. 17:55:44 In the face of ambiguity, refuse the temptation to guess. https://peps.python.org/pep-0020/ 17:56:06 s/is unhappy/will be unhappy/ 17:56:15 Zakim, draft minutes 17:56:15 I don't understand 'draft minutes', ktk 17:56:20 I don't *want* to refuse to guess, but I think that is the more careful (perhaps even more responsible) way 17:56:25 RRSAgent, draft minutes 17:56:26 I have made the request to generate https://www.w3.org/2023/12/14-rdf-star-minutes.html ktk 17:57:04 w3c has a mastodon server 17:57:11 w3c.social 17:57:50 ora: W3C annouced to leave Twitter/X. 17:58:03 https://w3c.social/explore 17:58:03 ... maybe we should have an account for our group at some point. 17:58:52 pfps has left #rdf-star 17:59:23 regrets+ fsasaki 17:59:59 RRSAgent, draft minutes 18:00:01 I have made the request to generate https://www.w3.org/2023/12/14-rdf-star-minutes.html ktk 18:05:13 niklas - when sorting a mixture of with and without timezone, it's a choice point (undef comparisons go in a different place in the ordering) 18:06:44 I've linked the discussion here and removed "needs discussion" label for now. previous meeting: https://www.w3.org/2023/12/07-rdf-star-minutes.html next meeting: https://www.w3.org/2023/12/21-rdf-star-minutes.html s/AndyS: I do go through/ I do go through