15:58:22 RRSAgent has joined #rdf-star 15:58:26 logging to https://www.w3.org/2023/11/30-rdf-star-irc 15:58:30 meeting: RDF-star Working Group Weekly Meeting 15:59:17 Agenda: https://www.w3.org/events/meetings/0a6aa6e3-635c-42c2-baba-938c76b6ef01/20231130T120000/ 15:59:18 clear agenda 15:59:18 agenda+ Approval of minutes from the last two metings: [1] 15:59:18 agenda+ Proposal for next week's discussion 15:59:18 agenda+ Review of open actions, available at [2] 15:59:18 agenda+ Review of pull requests, available at [3] 15:59:21 agenda+ Issue Triage, available at [4] 15:59:24 agenda+ Any Other Business (AOB), time permitting 16:16:00 gkellogg has joined #rdf-star 16:50:18 gkellogg has joined #rdf-star 16:56:58 AndyS has joined #rdf-star 16:57:16 gkellogg has joined #rdf-star 16:57:36 eBremer has joined #rdf-star 16:57:59 tl has joined #rdf-star 16:58:13 rubensworks has joined #rdf-star 16:58:31 olaf has joined #rdf-star 16:58:56 niklasl has joined #rdf-star 16:59:30 fsasaki has joined #rdf-star 17:00:05 Regrets: AZ, Dominik_T 17:00:07 present+ 17:00:11 present+ 17:00:13 present+ 17:00:14 ora has joined #rdf-star 17:00:19 present+ 17:00:24 present+ 17:00:29 TallTed has joined #rdf-star 17:00:30 present+ 17:00:34 present+ 17:00:48 doerthe has joined #rdf-star 17:01:29 present+ 17:01:31 RRSAgent, draft minutes 17:01:32 I have made the request to generate https://www.w3.org/2023/11/30-rdf-star-minutes.html ktk 17:01:38 RRSAgent, make log public 17:01:55 Chair: ora: 17:02:00 present+ 17:02:08 present+ 17:02:17 chair: ora 17:02:26 Scribe: doerthe: 17:02:33 enrico has joined #rdf-star 17:02:36 present+ 17:02:40 present+ 17:03:00 regrets for today meeting 17:03:13 present+ 17:03:41 present+ 17:03:42 Regrets+ Tpt 17:03:43 s/Scribe: doerthe:/Scribe: doerthe/ 17:03:45 RRSAgent, draft minutes 17:03:46 I have made the request to generate https://www.w3.org/2023/11/30-rdf-star-minutes.html TallTed 17:03:52 regrets+ tpt 17:03:52 present+ 17:04:15 s/regrets for today meeting// 17:04:17 s/Chair: ora:/Chair: ora/ 17:04:37 https://www.w3.org/2023/11/02-rdf-star-minutes.html 17:04:45 agenda: https://www.w3.org/events/meetings/0a6aa6e3-635c-42c2-baba-938c76b6ef01/20231130T120000/ 17:04:45 clear agenda 17:04:45 agenda+ Approval of minutes from the last two metings: [1] 17:04:45 agenda+ Proposal for next week's discussion 17:04:45 agenda+ Review of open actions, available at [2] 17:04:45 agenda+ Review of pull requests, available at [3] 17:04:48 agenda+ Issue Triage, available at [4] 17:04:51 agenda+ Any Other Business (AOB), time permitting 17:05:00 q? 17:05:01 TallTed has changed the topic to: RDF-star — 2023-11-30 Agenda: https://www.w3.org/events/meetings/0a6aa6e3-635c-42c2-baba-938c76b6ef01/20231130T120000/ 17:05:23 Zakim, open item 1 17:05:23 agendum 1 -- Approval of minutes from the last two metings: -- taken up [from 1 via agendabot] 17:05:29 Souri has joined #rdf-star 17:05:41 present+ 17:05:43 PROPOSAL: Approve minutes 2023-11-02 17:05:47 im not listed as present last time 17:05:58 +1 17:06:13 +1 17:06:15 +1 17:06:15 +1 17:06:16 +1 17:06:19 +1 17:06:20 +1 17:06:21 +0 (was not present) 17:06:23 +1 17:06:26 +1 17:06:27 +1 17:06:46 +1 17:07:03 RESOLUTION: Approve minutes 2023-11-02 17:07:16 https://www.w3.org/2023/11/16-rdf-star-minutes.html 17:08:02 draggett has joined #rdf-star 17:08:09 PROPOSAL: Approve minutes 2023-11-16 17:08:13 +1 17:08:15 +1 17:08:16 +1 17:08:16 +1 17:08:17 +0.5 (present only during the first half) 17:08:18 +1 17:08:20 +1 17:08:20 +1 17:08:22 +1 17:08:24 +0 (not present) 17:08:25 +1 17:08:32 +1 17:08:37 +1 17:08:41 RESOLUTION: Approve minutes 2023-11-16 17:09:02 Zakim, next item 17:09:02 agendum 2 -- Proposal for next week's discussion -- taken up [from agendabot] 17:10:16 ora: I was lost after the last discussion. Not sure what to do next. I discussed with Adrian. We strongly suggest that we select a course that leads to completion of the work in the expected time 17:10:27 RRSAgent, draft minutes 17:10:28 I have made the request to generate https://www.w3.org/2023/11/30-rdf-star-minutes.html TallTed 17:10:34 ora: but without closing door 17:11:56 ktk: Regarding Thomas' mail, I propose that we try to get into a clear direction. I do not want to open more doors. We should have something ready in summer next year 17:12:10 ktk: we can extend on that afterwards 17:12:25 ktk: that is ora's and my proposal 17:12:43 q? 17:13:02 ora: we do not want to dictate a solution, but we want to finish the charter 17:13:39 s|https://www.w3.org/2023/11/02-rdf-star-minutes.html|| 17:13:39 s|Approve minutes 2023-11-02|Approve minutes 2023-11-02, https://www.w3.org/2023/11/02-rdf-star-minutes.html| 17:13:39 s|https://www.w3.org/2023/11/16-rdf-star-minutes.html|| 17:13:39 s|Approve minutes 2023-11-16|Approve minutes 2023-11-16, https://www.w3.org/2023/11/16-rdf-star-minutes.html| 17:14:00 q+ 17:14:04 q+ 17:14:11 ack fsasaki 17:14:27 ktk: I was asked whether graphs are not allowed as a solution. The charter is on triple terms and we should discuss these first 17:14:42 q+ 17:14:54 ack TallTed 17:15:00 fsasaki: I'd like to second that. I think a fast solution is important 17:15:56 TallTed: Even though the charter talks about triple terms, but it is possible for the working group to widen the scope. The charter is not binding in that way 17:16:01 ack tl 17:16:11 pfps has joined #rdf-star 17:16:16 s/is important/is important also to assure that RDF keeps competitive to other graph related approaches/ 17:16:27 q+ 17:16:39 q+ 17:16:51 present+ 17:17:17 tl: I can reduce nested graphs to nested triples. I would like to discuss the possible problems about graph terms. I am not convinced that they are that big. I would like to do that in seperate meeting 17:17:27 ack TallTed 17:17:45 I am totally unconvinced that using nested graphs is "for free". Where is the complete proposal for this? 17:17:59 tl: My plan was not to go hijack the group to solve the named graph issues, but I think that graphs and triples are related 17:18:16 ack ora 17:18:52 TallTed: even though graphs and triples are similar froma philosophical point of view, they technically differ 17:19:32 ora: I would like people to think about which compromises they would accept to prepare for next week 17:19:43 +1 "can I live with this?" is a key question for each proposal 17:20:28 q+ 17:20:39 ora: do we all agree on that we want to talk about graph terms vs. triple terms and possible compromises next week? 17:20:52 q+ 17:20:54 ack AndyS 17:20:56 ora: I really hope to reach a decision next week 17:21:25 +1 to AndyS 17:21:30 AndaS: could we make sure that all material is available long before the meeting (24h?) 17:21:54 gKellog: I second that, especially having the time difference in mind 17:22:01 s/AndaS/AndyS/ 17:22:02 s/AndaS:/AndyS:/ 17:22:37 gkellog: we should also think about how we deal with the Christmas break and how we do planning 17:22:50 s/gKellog:/gkellogg:/ 17:22:51 s/24/48/ 17:22:54 q? 17:23:02 q+ 17:23:04 ack gkellogg 17:23:09 ack tl 17:23:09 s/gkellog:/gkellogg:/ 17:23:15 RRSAgent, draft minutes 17:23:16 I have made the request to generate https://www.w3.org/2023/11/30-rdf-star-minutes.html TallTed 17:23:22 s/gKellogg:/gkellogg:/ 17:23:30 tl: so we won't have the discussion about named graphs next week? 17:23:52 tl: I would like to have the discussion without pressure 17:24:37 ora: we could discuss through the mailing list and in the meeting 17:25:02 ora: I really want to reach a decision 17:25:10 q? 17:25:14 pfps` has joined #rdf-star 17:25:22 ora: that includes that we take a decision as a group at some point 17:25:34 Zakim, next item 17:25:34 agendum 3 -- Review of open actions, available at -- taken up [from 2] 17:25:44 https://github.com/orgs/w3c/projects/20/views/3 17:25:52 q+ 17:26:11 https://github.com/w3c/rdf-star-wg/issues/84 17:26:11 https://github.com/w3c/rdf-star-wg/issues/84 -> Action 84 1.1 specs should reference 1.2 versions (on pchampin) 17:27:26 q+ to talk about my aciton 17:27:26 pchampin: I investigated on https://github.com/w3c/rdf-star-wg/issues/84 which was about links to latest versions 17:27:38 s/aciton/action/ 17:27:50 pchampin: the links will be changed 17:28:51 pfps: I worked on updating the use cases. I worked on it and will continue today 17:29:42 q? 17:29:47 q- 17:29:55 ack pfps` 17:29:55 pfps`, you wanted to talk about my aciton 17:30:00 Zakim, next item 17:30:00 agendum 4 -- Review of pull requests, available at -- taken up [from 3] 17:30:09 q+ 17:30:09 https://github.com/orgs/w3c/projects/20/views/4 17:30:18 ack olaf 17:30:49 olaf: There is an open request 1032, will you have a look at it Andy? 17:30:57 AndyS: yes 17:31:13 s|1032|w3c/sparql-query#132 17:31:14 https://github.com/w3c/sparql-query/issues/132 -> Pull Request 132 More accurate definition of the Group operator (by hartig) [spec:editorial] 17:31:55 Apologies for my tardiness on query#132 17:31:56 https://github.com/w3c/query/issues/132 -> Issue 132 [not found] 17:31:57 q+ 17:32:02 gkellogg: there is a test for quads I added, if there is no objection, I will merge 17:32:44 s/a test for quads/tests for text-direction in n-quads, turtle and trig 17:33:29 olaf: What do we do for SPARQL 1.2 tests? how do we proceed? 17:33:50 AndyS: are these tests for the repository? 17:34:22 q? 17:34:32 ack olaf 17:34:37 q? 17:34:44 AndyS: there is a directory for it which is empty, we can start to fill it. We can follow the structure of the old tests 17:35:12 olaf: do we add the old tests there as well? 17:35:24 AndyS: Only the new ones 17:36:08 gkellogg: what do we do with the tests from [please help] 17:36:57 AndyS: these are premature, we should not add them now 17:37:51 AndyS: all tests need to be manually checked 17:38:04 ora: can we deprecate tests if needed? 17:38:35 s/[please help]/RDF-star Community Group/ 17:39:17 gkellogg: I would add some tags, but from experience, that can cause confusion 17:39:37 q+ 17:39:46 ack niklasl 17:40:21 niklasl: we should for sure add tests for the things we change 17:40:59 Zakim, next item 17:40:59 agendum 5 -- Issue Triage, available at -- taken up [from 4] 17:41:02 https://github.com/orgs/w3c/projects/20/views/5 17:41:47 ora: how do we do the triage? 17:42:40 gkellogg: we wanted to focus on the tasks with "needs discussion" tags 17:44:00 q? 17:44:16 subtopic: https://github.com/w3c/sparql-results-csv-tsv/issues/10 17:44:17 https://github.com/w3c/sparql-results-csv-tsv/issues/10 -> Issue 10 TSV: state how to handle special characters in strings (by Tpt) [needs discussion] 17:45:02 discovering this issue right now, but I tend to agree with AndyS 17:46:19 Action: AndyS to follow-up on on issue TSV#10 17:46:26 I created -> issue #10 https://github.com/w3c/rdf-common/issues/10 17:46:26 but I could not add the "action" label. 17:46:26 That probably means I don't have push permission on w3c/rdf-common. 17:46:26 I created -> issue #11 https://github.com/w3c/rdf-common/issues/11 17:46:26 but I could not add the "action" label. 17:46:26 That probably means I don't have push permission on w3c/rdf-common. 17:47:07 AndyS: I will have a look at the issue 17:47:08 Now in https://github.com/w3c/rdf-star-wg/issues/98 17:47:08 https://github.com/w3c/rdf-star-wg/issues/98 -> Action 98 follow-up on on issue TSV#10 (on ) due 2023-12-07 17:47:33 q+ 17:47:39 subtopic: https://github.com/w3c/rdf-concepts/issues/55 17:47:39 https://github.com/w3c/rdf-concepts/issues/55 -> Issue 55 Compare language tags after normalizing to lower case. (by gkellogg) [needs discussion] [spec:enhancement] 17:48:06 q- 17:48:25 gkellogg: the issue is that language tags can be done differently by different implementations 17:48:38 In Oracle, we lowercase it. 17:48:52 ora: do we know what the major implementations do with the issue 17:50:37 gkellogg: we do not need to fix that in the abstract syntax 17:50:57 q+ 17:51:15 AndyS: does that not break canonicalization? 17:51:26 gkellogg: yes it would 17:51:55 q+ 17:51:56 Ontotext GraphDB uses RFC formatting. 17:53:11 gkellogg: we could leave it open for serialisations and fix it in the abstract syntax 17:53:42 ora: Are the issues about comparisons or storage? 17:54:00 gkellogg: comparison is case-insensitve 17:54:45 AndyS: we could say within a concrete system the representation should be consistent 17:55:06 ack pchampin 17:56:03 q- 17:56:53 pchampin: I wanted to suggest the same as Andy just did. We should only say that two literals only differing in lower vs. upper case letters in their language tags should be the same without dictating what this needs to be 17:57:15 ack niklasl 17:57:25 q+ 17:57:29 pchampin: we can add that there can be a canonical case 17:57:41 ack tl 17:57:49 tl: I would like to have a semantic task force 17:58:57 tomorrow currently shows as cancelled. but I will join if it happens. https://www.w3.org/events/meetings/6d0cd306-0be8-4267-865a-6272cc8d9da4/20231201T100000/ 17:59:00 enrico: If you want, we can have a meeting. I wanted to write a very concise proposal as well covering the minimal requirements 17:59:21 RRSAgent, draft minutes 17:59:22 I have made the request to generate https://www.w3.org/2023/11/30-rdf-star-minutes.html ktk 18:00:09 enrico: I want to propose two possibilities, we could discuss 18:00:47 enrico: I can de-cancel tomorrow's meeting 18:00:56 olaf has left #rdf-star 18:01:42 scribe- 18:01:49 not sure, I can join tomorrow 18:10:12 RRSAgent, leave 18:10:12 I see 1 open action item saved in https://www.w3.org/2023/11/30-rdf-star-actions.rdf : 18:10:12 ACTION: AndyS to follow-up on on issue TSV#10 [1] 18:10:12 recorded in https://www.w3.org/2023/11/30-rdf-star-irc#T17-46-19 18:10:15 Created -> action #99 https://github.com/w3c/rdf-star-wg/issues/99 s/metings/meetings/g previous meeting: https://www.w3.org/2023/11/16-rdf-star-minutes.html next meeting: https://www.w3.org/2023/12/07-rdf-star-minutes.html