16:42:54 RRSAgent has joined #rdf-star 16:42:58 logging to https://www.w3.org/2024/01/25-rdf-star-irc 16:44:34 meeting: RDF-Star WG biweekly meeting 16:44:39 RRSAgent, draft minutes 16:44:40 I have made the request to generate https://www.w3.org/2024/01/25-rdf-star-minutes.html TallTed 16:44:44 RRSAgent, make logs public 16:55:31 TallTed: tnx for preparing 16:56:04 Regrets: Ora, az, olaf, gkellog 16:56:19 Chair: ktk 16:57:32 tl has joined #rdf-star 16:58:49 p+ 16:58:58 previous meeting: https://www.w3.org/2024/01/18-rdf-star-minutes.html 16:59:13 next meeting: https://www.w3.org/2024/02/01-rdf-star-minutes.html 16:59:23 AndyS has joined #rdf-star 16:59:52 I wonder if we shouldn't include/inject the TF meetings into the previous/next meeting statements? 17:00:18 present+ 17:00:21 TallTed, good point 17:00:32 present+ 17:00:54 present+ 17:01:02 pfps has joined #rdf-star 17:01:02 eBremer has joined #rdf-star 17:01:15 present+ 17:02:13 present+ 17:02:51 present+ 17:03:02 present+ 17:03:09 scribe: gtw 17:03:27 present+ 17:03:35 RRSAgent, draft minutes 17:03:37 I have made the request to generate https://www.w3.org/2024/01/25-rdf-star-minutes.html TallTed 17:03:59 zakim, open agendum 1 17:03:59 I see nothing on the agenda 17:04:14 agenda: https://www.w3.org/events/meetings/0a6aa6e3-635c-42c2-baba-938c76b6ef01/20240125T120000/ 17:04:14 clear agenda 17:04:14 agenda+ Approval of minutes from the last two metings: [1] 17:04:14 agenda+ Proposal for next week's discussion [2] 17:04:14 agenda+ Review of open actions, available at [3] 17:04:15 agenda+ Review of pull requests, available at [4] 17:04:17 agenda+ Issue Triage, available at [5] 17:04:20 agenda+ Any Other Business (AOB), time permitting 17:04:29 Zakim, open item 1 17:04:29 agendum 1 -- Approval of minutes from the last two metings: -- taken up [from 1 via agendabot] 17:04:29 zakim, open agendum 1 17:04:31 agendum 1 -- Approval of minutes from the last two metings: -- taken up [from 1 via agendabot] 17:04:43 https://www.w3.org/2024/01/11-rdf-star-minutes.html 17:04:44 ktk: two meeting minutes to approve. 17:04:46 minutes look fine 17:04:57 eBremer_ has joined #rdf-star 17:05:05 PROPOSAL: Approve minutes 2024-01-11 17:05:13 +1 17:05:15 +1 17:05:15 +1 17:05:18 +1 17:05:18 +1 17:05:22 s|https://www.w3.org/2024/01/11-rdf-star-minutes.html|subtopic:https://www.w3.org/2024/01/11-rdf-star-minutes.html| 17:05:23 +1 17:05:34 +1 17:05:49 +1 17:05:49 PROPOSAL: Approve minutes 2024-01-11 17:05:51 fsasaki has joined #rdf-star 17:05:55 present+ 17:05:56 present+ 17:05:56 RESOLUTION: Approve minutes 2024-01-11 17:06:08 https://www.w3.org/2024/01/18-rdf-star-minutes.html 17:06:23 ktk: gkellogg sent regrets. PA can you add that? 17:06:26 these minutes look fine also 17:06:26 ... otherwise looks fine. 17:06:31 s|https://www.w3.org/2024/01/18-rdf-star-minutes.html|subtopic: https://www.w3.org/2024/01/18-rdf-star-minutes.html| 17:06:39 RRSAgent, draft minutes 17:06:40 I have made the request to generate https://www.w3.org/2024/01/25-rdf-star-minutes.html TallTed 17:06:46 PROPOSAL: Approve minutes 2024-01-18 17:06:46 doerthe has joined #rdf-star 17:06:47 +1 17:06:50 present+ 17:06:51 +1 17:06:51 +1 17:06:52 +1 17:06:53 +1 17:06:54 +1 17:07:17 +1 17:07:18 +1 17:07:24 s/agendum 1 -- Approval of minutes from the last two metings: -- taken up [from 1 via agendabot]// 17:07:25 +1 17:07:25 +1 17:07:32 RRSAgent, draft minutes 17:07:33 I have made the request to generate https://www.w3.org/2024/01/25-rdf-star-minutes.html TallTed 17:07:39 RESOLUTION: Approve minutes 2024-01-18 17:07:52 Zakim, next item 17:07:52 agendum 2 -- Proposal for next week's discussion -- taken up [from 2] 17:08:14 ktk: another long meeting next week. impression from the list - most discussed topics are the syntactic sugar proposal. 17:08:26 ... big part of discussion is well-formed or not-well-formed. 17:08:30 ... any comments? 17:08:30 q+ 17:09:02 AndyS: two weeks ago we had proposal about what subject was. some thigns weren't carrieid forward from meeting. need to be clearer. 17:09:25 ... if it's just which is the largest volume on the mailing list, i can see how you came to conclusion. 17:09:34 ... as pchampin's summary makeks clear, there are other things in-flight. 17:09:46 ... suggest how we work across proposals. 17:09:57 ... defining which issues we wish to address. 17:10:09 ... presuming which issues the WG is seeing as will-address or not. 17:10:18 pchampin, chairs -- please correct `meting` to `meeting` in agendas, going forward 17:10:21 ktk: can you point to the one from pchampin ? 17:10:35 https://lists.w3.org/Archives/Public/public-rdf-star/2024Jan/0001.html 17:10:50 AndyS: titled "Summary of the Options" 17:11:00 pchampin: I probably sent to the CG mailing list. 17:11:11 ktk: could you post to the main list again? 17:11:16 pchampin: yes 17:11:20 https://lists.w3.org/Archives/Public/public-rdf-star/2024Jan/0001.html 17:11:37 AndyS: I've done the same thing with mine. 17:11:50 q= 17:11:51 ... (atomic reification write-up.) 17:11:52 q? 17:11:57 ack AndyS 17:12:12 ktk: any feedback to AndyS? 17:12:25 AndyS: two of proposals are not involving well-formed directly. 17:12:40 ktk: your proposal is to go through this and try to see how much concensus we can find? 17:13:00 AndyS: I think we have to do it. Otherwise only talking about one area. Implicitly would be saying other areas are not of interest. 17:13:20 q+ 17:13:20 s/thigns/things 17:13:22 ktk: ok. good proposal. any other comments? 17:13:27 ack pchampin 17:13:53 pchampin: apologies for confusion. goal of this email was to try and have a sensitive view on how approaches differ. 17:14:32 "Atomic reification" https://lists.w3.org/Archives/Public/public-rdf-star/2024Jan/0000.html 17:14:42 ... last friday there was confusion about what we were meant to discuss. 17:14:57 ... goal is to provide something concrete. 17:15:05 ... tried my best to collate different sources with links. 17:15:14 ... also to have everythign in once place. easy to compare. 17:15:22 q? 17:15:53 TallTed: AndyS you sent yours to the list, too? 17:15:56 AndyS: I'm about to. 17:16:48 ktk: let's take this as base for discussion. 17:16:50 s/the list/the WG list/ 17:16:57 Zakim, next item 17:16:57 agendum 3 -- Review of open actions, available at -- taken up [from 3] 17:17:13 q+ 17:17:14 ktk: we have open actions 17:17:56 pchampin: I checked that every issue and PR ends up in the dashboard. 17:18:01 ... this is proven complete. 17:18:13 zakim, next item 17:18:13 I see a speaker queue remaining and respectfully decline to close this agendum, ktk 17:18:17 q? 17:18:21 ack pchampin 17:18:23 zakim, next item 17:18:23 agendum 4 -- Review of pull requests, available at -- taken up [from 4] 17:18:33 q+ 17:18:58 ktk: olaf is not here. 17:19:08 ... no update on JSON PR. 17:19:16 ... what is "minicore" AndyS? 17:19:23 ... #102 17:19:24 https://github.com/w3c/rdf-star-wg/issues/102 -> Pull Request 102 Create miniCore.md (by rat10) 17:19:41 pfps: he should be able to create the document. not sure why this is still sitting there. 17:19:58 q? 17:19:59 pchampin: we're just editors. only editors have the merge privilige. 17:20:05 AndyS: is that related to the wiki as well? 17:20:17 q+ 17:20:17 pchampin: wiki permissions are different. 17:20:30 ... I can change permissions. Give merge permissions to all participants. 17:20:40 ... given use we have for docs folder, probably would make sense. 17:20:43 ktk: only for this repo? 17:20:44 pchampin: yes. 17:20:51 ktk: no problem with that. 17:20:57 pchampin: in the mean time, I can merge PRs. 17:21:03 q? 17:21:15 ack tl 17:21:15 tl: I don't know if approach makes sense. it was 2 weeks ago. 17:21:25 ... we should try to organize discussion around repo. 17:21:37 ... I got a lot of editoral comments. 17:21:56 ... I think I'm going to start writing mails again. Didn't have feeling that this worked out. 17:22:06 ... I don't care if this gets merged into docs folder. It's already outdated. 17:22:23 tl: you can merge it or leave it. 17:22:36 pfps: #45 or 3 on the list out of 5. that's a technical change to semantics. 17:22:37 https://github.com/w3c/rdf-star-wg/issues/45 -> CLOSED Pull Request 45 put em-dashes where they belong in rdf-terminology.md (by TallTed) [documentation] 17:22:49 ... could go in except that when I look at it, TallTed has requested changes. I can't see what the changes are. 17:23:08 ack pfps 17:23:12 s|#45|w3c/rdf-semantics#45 17:23:12 https://github.com/w3c/rdf-semantics/issues/45 -> Pull Request 45 add entailment rule for datatypes (by pfps) [spec:bug] [test:needs tests] 17:23:25 pfps: try to do it sometime and take yourself off. I can merge even without that, but would prefer to wait for you. 17:23:35 TallTed: it's waiting for approval after changes. 17:23:47 q? 17:23:51 Zakim, next item 17:23:51 agendum 5 -- Issue Triage, available at -- taken up [from 5] 17:24:15 ktk: last time we said we wanted to add one flag. not sure much happened. 17:24:27 ... any comments on any issues? 17:24:45 q+ 17:25:02 ack AndyS 17:25:14 AndyS: I think it's difficult to have discussion until we decide what it's based upon. 17:25:23 pfps: ok taking off need for discussion for now. 17:25:35 ... I'll remove the label. 17:26:04 pfps: one thing related to triage. I did the #45 PR. it has an associated issue. 17:26:04 https://github.com/w3c/rdf-star-wg/issues/45 -> CLOSED Pull Request 45 put em-dashes where they belong in rdf-terminology.md (by TallTed) [documentation] 17:26:11 s|#45|w3c/rdf-semantics#45 17:26:12 https://github.com/w3c/rdf-semantics/issues/45 -> Pull Request 45 add entailment rule for datatypes (by pfps) [spec:bug] [test:needs tests] 17:26:13 ... how are we going to do tests? 17:26:22 ... I put a needstest label on the issue which will stay open. 17:26:32 q+ 17:26:49 ack pchampin 17:26:55 pchampin: That's probably on me. I don't think this label exists at the moment. 17:27:07 pfps: it's test:needstest. 17:27:47 Zakim, next item 17:27:47 agendum 6 -- Any Other Business (AOB), time permitting -- taken up [from agendabot] 17:28:01 q+ 17:28:07 ack pchampin 17:28:29 pchampin: we talked about changing the permissions on the rdf WG repo. 17:28:42 ... do we need a fuller decision? or do I just add an action? 17:28:54 ... how do we make a decision on that? 17:29:00 ktk: we can do a proposal. 17:29:05 AndyS: or chair's discretion. 17:29:12 pfps: chair's discretion sounds good. 17:30:03 pchampin: realized we are roughly at 75% of our chartered time. need to start thinking about rechartering. 17:30:16 ... another item in our discussion at some point. not too controversial. 17:30:23 ... will discuss with charis and come back to the group. 17:30:36 ktk: when is the official end? 17:30:39 ... august? 17:30:42 pchampin: something like that. 17:30:53 q? 17:30:59 q+ 17:31:02 s/charis/chairs/ 17:31:15 https://hackmd.io/@niklasl/HJ3IudCdp 17:31:20 niklasl: motivating examples (pchampin suggested a couple of weeks ago) 17:31:33 ... I could add them to the wiki. Not sure if they are relevant anymore. 17:31:43 ... A lot of use-cases. Perhaps that's good enough. 17:31:49 ack niklasl 17:32:13 ktk: details for TPAC are set this year. might make sense to meet again. 17:32:20 ... in the US. 17:32:35 ... Anaheim, CA. Sept 23–27, 2024. 17:32:39 https://www.w3.org/events/tpac/2024/tpac-2024-hybrid-meeting/ 17:32:54 ... probably a different combination than last year being more US-focused. 17:33:03 ... I might consider it. 17:33:10 pchampin: I will probably go. 17:33:47 pfps: I expect meeting will be across a very big parking lot from disneyland. 17:34:08 TallTed: meeting should be on teacups. 17:34:14 q? 17:34:29 TallTed: good if people can review open issues. 17:34:34 ... that are unlabeled. 17:34:41 ... add some labeling. we can do triage next time. 17:34:52 pfps: I was looking at those. Some are from outside the WG. Not sure what to do about them. 17:35:01 q+ to suggest we should assign them to WG participants 17:35:01 TallTed: reply to them in some way. 17:35:10 ack pchampin 17:35:10 pchampin, you wanted to suggest we should assign them to WG participants 17:35:27 pchampin: good point. issues from people outside WG. one thing we could do is assign to group participants. 17:35:52 ... look at your issues. might be something we want to consider having asignees for. 17:36:19 pchampin: of course, it's probably no quick way to filter issues by who they are from. 17:36:27 pfps: only 102. not a long time to go through them. 17:36:51 ktk: long meeting next week. 17:37:15 RRSAgent, make minutes 17:37:16 I have made the request to generate https://www.w3.org/2024/01/25-rdf-star-minutes.html pchampin 17:37:23 s/reply to them in some way/we have to reply to them in some way (addressed this way, not going to address, etc.)/ 17:37:23 RRSAgent, draft minutes 17:37:24 I have made the request to generate https://www.w3.org/2024/01/25-rdf-star-minutes.html TallTed 17:37:32 eBremer_ has left #rdf-star 17:41:58 RRSAgent, bye 17:41:58 I see no action items s|https://github.com/w3c/rdf-star-wg/issues/45 -> CLOSED Pull Request 45 put em-dashes where they belong in rdf-terminology.md (by TallTed) [documentation]||g regrets+ enrico