16:59:21 RRSAgent has joined #rdf-star 16:59:25 logging to https://www.w3.org/2025/02/20-rdf-star-irc 16:59:25 olaf has joined #rdf-star 16:59:25 RRSAgent, make logs Public 16:59:26 please title this meeting ("meeting: ..."), pchampin 16:59:46 present+ 16:59:46 AndyS has joined #rdf-star 16:59:47 meeting: RDF-Star WG biweekly meeting 16:59:52 Dominik_T has joined #rdf-star 16:59:52 scribe: fsasaki 16:59:56 AZ has joined #rdf-star 17:00:08 niklasl has joined #rdf-star 17:00:11 present+ 17:00:20 present+ 17:00:20 present+ 17:00:20 present+ 17:00:35 present+ 17:00:39 eBremer has joined #rdf-star 17:00:41 present+ 17:01:00 I have made the request to generate https://www.w3.org/2025/02/20-rdf-star-minutes.html TallTed 17:01:07 Agenda: https://www.w3.org/events/meetings/f1d5533f-ff2b-4d70-941c-db47b0b5918d/20250220T120000/ 17:01:07 clear agenda 17:01:07 agenda+ Approval of minutes from the last two meetings: -> 1 https://www.w3.org/2025/02/06-rdf-star-minutes.html , -> 2 https://www.w3.org/2025/02/13-rdf-star-minutes.html 17:01:07 agenda+ Publish RDF Primer as a draft note 17:01:07 agenda+ Closing stale issues 17:01:07 agenda+ Prioritization of next week's topics -> 3 https://github.com/orgs/w3c/projects/20/views/6 17:01:07 agenda+ Review of open actions, available at -> 4 https://github.com/orgs/w3c/projects/20/views/3 17:01:07 ora has joined #rdf-star 17:01:07 present+ 17:01:10 agenda+ Review of pull requests, available at -> 5 https://github.com/orgs/w3c/projects/20/views/4 17:01:11 present+ 17:01:11 agenda+ Issue Triage, available at -> 6 https://github.com/orgs/w3c/projects/20/views/5 17:01:12 present+ 17:01:12 present+ 17:01:14 agenda+ Any Other Business (AOB), time permitting 17:01:15 chair+ 17:02:02 previous meeting: https://www.w3.org/2025/02/14-rdf-star-minutes.html 17:02:02 next meeting: https://www.w3.org/2025/02/21-rdf-star-minutes.html 17:02:07 present+ 17:02:18 doerthe has joined #rdf-star 17:02:27 present+ 17:02:35 present+ 17:02:42 present+ 17:02:52 agenda? 17:02:57 james has joined #rdf-star 17:03:03 zakim, open item 1 17:03:03 agendum 1 -- Approval of minutes from the last two meetings: -> 1 https://www.w3.org/2025/02/06-rdf-star-minutes.html , -> 2 https://www.w3.org/2025/02/13-rdf-star-minutes.html -- 17:03:06 ... taken up [from agendabot] 17:03:18 look fine to me :-) 17:03:21 ora: minutes approval OK? 17:03:24 +1 17:03:32 +1 17:03:45 PROPOSAL: Approve last two meetings' minutes 17:03:48 +1 17:03:52 +0 17:03:53 +1 17:03:54 +1 17:03:55 +1 17:03:55 +1 17:03:56 +1 17:03:56 +1 17:03:57 +1 17:04:00 +1 17:04:03 +0 17:04:12 RESOLUTION: minutes from last two meetings approved 17:04:27 Looks fine (I also got my wording three(?) weeks ago updated by pchampin as asked for by james on 6 feb). 17:04:27 +1 17:04:32 +1 17:04:36 +1 17:04:37 +1 17:04:41 RESOLVED: Approve last two meetings' minutes 17:04:55 Zakim, next item 17:04:55 agendum 2 -- Publish RDF Primer as a draft note -- taken up [from agendabot] 17:04:58 s/RESOLUTION: minutes from last two meetings approved// 17:04:59 s/RESOLUTION: minutes from last two meetings approved// 17:05:14 ora: RDF primer will be a note 17:05:23 q? 17:05:25 ... we have not published a draft version yet 17:05:28 q+ 17:05:29 q+ 17:05:35 ack pchampin 17:05:36 Souri has joined #rdf-star 17:05:40 q+ 17:05:41 q+ 17:05:42 present+ 17:05:47 pa: we need a group decision to publish a first draft 17:05:54 ... could be bundled in one resolution 17:05:56 q- 17:06:16 ... need a resolution to use echidna 17:06:23 ... using echidna would be a good thing 17:06:38 ora: so every time we merge a pull request it publishes automatically? 17:06:40 pa: yes 17:06:51 ora: so we decide on publishing and then on echidna 17:07:11 https://www.w3.org/TR/rdf-primer/ 17:07:24 pa: this URI points to version 1.0 of primer 17:07:37 ... version 1.1 is at RDF 17:07:46 ... we want a version less short name 17:08:36 ack tl 17:09:05 tl: would like to wait a week, but would not block publishing now 17:09:18 ack niklasl 17:09:31 niklas: agree 17:10:01 .... and good to have echidna on place 17:10:01 q+ 17:10:02 james0 has joined #rdf-star 17:10:09 present+ 17:10:09 ack gkellogg 17:10:23 greg: support of dark mode work and style changes, should be propagated to other specs 17:10:27 niklas: agree 17:10:43 ... would like to discuss some details on this, after this call or tomorrow 17:10:46 PROPOSAL: Publish RDF Primer as a Draft Note 17:10:49 ora: I can stay after the call 17:10:57 +1 17:10:58 +1 17:10:59 +1 17:10:59 +1 17:11:00 +1 17:11:03 +1 17:11:04 +1 17:11:05 +1 17:11:05 +1 17:11:07 +0 17:11:11 +1 17:11:12 +1 17:11:15 +1 17:11:15 +1 17:11:20 +1 17:11:29 +1 17:11:31 +1 17:11:58 RESOLVED: Publish RDF Primer as a Draft Note 17:12:21 q? 17:12:41 ora: now about echidna 17:13:36 PROPOSAL: Adopt echidna for the RDF Primer 17:13:40 +1 17:13:40 +1 17:13:41 +1 17:13:41 +1 17:13:42 +1 17:13:44 +1 17:13:44 +1 17:13:45 +1 17:13:45 +1 17:13:46 +1 17:13:46 +1 17:13:46 +1 17:13:47 +1 17:13:48 +1 17:13:53 +1 17:14:02 +0 17:14:09 +1 17:14:22 RESOLVED: Adopt echidna for the RDF Primer 17:14:44 Zakim, next item 17:14:44 agendum 3 -- Closing stale issues -- taken up [from agendabot] 17:14:49 pa: will make this happen 17:15:14 s/happen/happen, the echidna setup and primer publication/ 17:15:41 pa: started to review stale issues systematically 17:16:09 I have made the request to generate https://www.w3.org/2025/02/20-rdf-star-minutes.html TallTed 17:16:16 ... proposal to have the chairs and I to review the old actions and add comment if we think issues can be closed to assure that person receive notifications 17:16:41 ... after two weeks if there is no notification we will close the issue 17:16:55 q+ 17:17:02 ack AndyS 17:17:08 ... any objection to this approach? 17:17:19 andyS: is this for all repos? 17:17:29 ... started with rdf-star, but plan to do that with all repos 17:17:40 andyS: some issues are out of scope 17:17:57 ... we can save us some time on these 17:18:03 https://github.com/w3c/rdf-turtle/issues/87 17:18:04 https://github.com/w3c/rdf-turtle/issues/87 -> Issue 87 forbid redefining the same PREFIX; consider forbidding relative BASE (by VladimirAlexiev) 17:18:13 q+ 17:18:19 ack pchampin 17:18:29 pa: priority is to focus on issues that are outdated 17:18:33 ... there are many like these 17:18:47 ... this should help to manage other issues more efficiently 17:19:46 ora: pa will not close the issues but mark them as candidates to be closed after two weeks 17:19:57 ... so there is time to engage on them 17:20:10 PROPOSAL: Close stale/outdated/superseded issues as per pchampin's proposal 17:20:15 +1 17:20:16 +1 17:20:17 +1 17:20:17 +1 17:20:17 +1 17:20:19 +1 17:20:19 +1 17:20:20 +1 17:20:21 +1 17:20:21 +1 17:20:21 +1 17:20:22 +1 17:20:22 +1 17:20:25 +1 17:20:26 +1 17:20:27 +1 17:20:33 +1 17:20:35 +1 17:20:36 q+ 17:20:47 ack ktk 17:20:57 RESOLVED: Close stale/outdated/superseded issues as per pchampin's proposal 17:21:22 pa: we were reaching limits of number of items in the project 17:22:14 ora: what does it mean to remove them? 17:22:21 pa: they are not visible via the project 17:22:43 ... the issues are present but are no longer associated with the project 17:22:51 ... we still keep the history 17:22:57 Zakim, next item 17:22:57 agendum 4 -- Prioritization of next week's topics -> 3 https://github.com/orgs/w3c/projects/20/views/6 -- taken up [from agendabot] 17:23:07 q+ 17:23:42 ora: everybody saw the poll on the triple terms I assume 17:23:50 ... the poll closes before the meeting 17:23:57 ack tl 17:24:01 https://github.com/w3c/rdf-star-wg/issues/131 17:24:01 https://github.com/w3c/rdf-star-wg/issues/131 -> Issue 131 Streamline Turtle-star syntactic sugar and future-proof it for graphs (by rat10) [needs discussion] 17:24:19 q+ 17:24:21 tl: syntax issue we could discuss, no. 131 17:24:26 ack AndyS 17:24:32 q+ 17:24:54 andyS: can we cover the other turtle syntax issue first, 132 on rdf star WG list 17:24:55 https://github.com/w3c/rdf-star-wg/issues/132 17:24:55 https://github.com/w3c/rdf-star-wg/issues/132 -> Issue 132 Turtle Grammar: Collections and blank node property lists in triple terms (by doerthe) [needs discussion] 17:25:04 ack pfps 17:25:18 q+ 17:25:29 pfps: propose to discuss if we will address sparql errata 17:25:59 adrian: propose 132 first, then 131 17:26:07 ack pchampin 17:26:07 (no objections) 17:26:30 pa: about the poll and triple terms in subject position 17:26:37 ... we want to see if we will have consensus 17:26:57 ... if we do not have consensus, the chairs will move forward and say: there was dissent. 17:27:14 q+ 17:27:28 pa: think we then do not need to add this to agenda 17:28:02 ack fsasaki 17:28:14 scribe+ 17:28:47 fsasaki: so far, we have a lot of I don't care options; is another poll planned with only two options before a decision is made? 17:28:58 felix: the poll has three options: agree, disagree, I do not care. if there is no clear picture, will you do a vote with 2 options? 17:29:15 ora: if there is no clear picture we may vote again, if one or the other is clear, we can decide 17:29:15 scribe- 17:29:50 ora: we want to see if there is large for or against this 17:30:30 ora: we will have a chairs meeting and then see if there is need for another poll in two weeks 17:30:54 ora: peter, are you ok with the current order of topics? 17:30:57 pfps: yes 17:31:00 s/large for /large support for 17:31:09 q+ 17:31:10 q+ 17:31:14 ora: if we time box topics we may do 3 topics next week 17:31:15 ack gkellogg 17:31:22 q+ 17:31:30 I have made the request to generate https://www.w3.org/2025/02/20-rdf-star-minutes.html TallTed 17:31:36 gregg: named graphs in rdf xml, is that in scope? 17:31:49 ... and then named graphs RDFa ... 17:32:16 ora: I would say: out of scope 17:32:20 ... but we can discuss this 17:32:36 gregg: it is among the topics we can take up after REC publication 17:32:37 ack pfps 17:32:56 pfps: issue on xyz literal 17:33:00 ... should this go away? 17:33:07 adrian: issue 84 17:33:19 ... propose to put this to the list of topics 17:33:23 ack AndyS 17:33:40 andyS: issue about versioning could be advanced 17:33:51 +1 to continue the discussion on versioning 17:33:52 q+ 17:34:04 andyS: number 141 on rdf-star WG 17:34:21 w3c/rdf-star-wg#141 17:34:22 https://github.com/w3c/rdf-star-wg/issues/141 -> Issue 141 Which parties carry what costs of text/turtle changes, and do those outweigh which benefits for whom? (by RubenVerborgh) [needs discussion] 17:34:25 ora: we need PAs experiment results for that. 17:34:39 pa: will summarize next week 17:34:58 q+ 17:35:15 ora: two turtle issues, then versioning, then plain literal issue for next week 17:35:20 adrian: agree 17:35:45 ... is rdf/xml and named graphs for later, do we agree on that? 17:35:54 ora: could go after REC publication 17:36:01 ack james 17:36:27 q+ 17:36:37 james: wondering about why some topics are more important than 84 17:37:09 discussion on how the topics are being set for next week 17:37:29 ack pchampin 17:37:34 q? 17:37:53 s/about why /if not 17:38:03 pa: 84 is "plain literal", this is a low hanging fruit 17:38:04 q+ 17:38:09 ... can be earlier in the agenda 17:38:17 ack niklasl 17:38:27 https://github.com/w3c/rdf-semantics/issues/84 17:38:28 https://github.com/w3c/rdf-semantics/issues/84 -> Issue 84 remove rdf:plainLiteral from Semantics? (by pfps) [needs discussion] [spec:substantive] 17:38:30 I think https://github.com/w3c/rdf-primer/issues/14 can be closed now. 17:38:30 https://github.com/w3c/rdf-primer/issues/14 -> Issue 14 Quoted triples not mentioned in primer (by kvistgaard) [needs discussion] [propose closing] 17:38:52 niklas: issue 14 can be closed now, see above 17:39:13 ... what are triple terms is now in primer 17:39:15 ack ktk 17:39:19 ora: agree 17:40:14 adrian: current topic list is a combination of both types of topics 17:40:25 ora: enough material for next week, suggest to move on 17:40:39 Zakim, next item 17:40:39 agendum 5 -- Review of open actions, available at -> 4 https://github.com/orgs/w3c/projects/20/views/3 -- taken up [from agendabot] 17:40:39 ... let us get 84 more up (on top) 17:41:04 q+ 17:41:30 pa: will work on rdf primer and echidna 17:41:36 ... 145 can be closed 17:41:48 I have made the request to generate https://www.w3.org/2025/02/20-rdf-star-minutes.html TallTed 17:41:54 ... pending PR on RDF concepts about unification of terminology, can be closed 17:41:54 ... have merged PR 17:42:01 https://github.com/w3c/rdf-concepts/pull/158 17:42:02 https://github.com/w3c/rdf-concepts/pull/158 -> Pull Request 158 unify terminology for triples (by pchampin) [needs discussion] [spec:enhancement] 17:43:15 pa: we define one concept "rdf triple", then distinguish asserted triple and triple term 17:43:18 q+ 17:43:27 ack pchampin 17:43:28 q+ 17:43:28 ... it removes some redundancy in the text 17:43:32 ... suggest to merge PR 17:43:36 ack tl 17:43:43 q+ 17:43:50 tl: is the term "statement" in? 17:44:07 pa: have not touched occurrences of this term yet 17:44:14 ... some said that triple terms are statements 17:44:42 ... "statement" is used in the introduction 17:44:52 ack gkellogg 17:44:58 q+ 17:45:00 ack pfps 17:45:03 ... there has not been further changes to this term besides the ones mentioned 17:45:06 q+ 17:45:37 q+ 17:45:46 q- 17:45:47 q+ 17:45:53 pfps: suggest that editors can reject certain changes 17:46:02 ack gkellogg 17:46:14 gregg: ambiguity in notion of asserted triples 17:46:26 ... was not clear from the text 17:46:39 andyS: suggest to merge the PR 17:46:49 ... pa said that other things need work 17:46:53 gregg: fine by me 17:46:54 ack TallTed 17:47:13 TallTed: open items after the merge should become issues 17:47:59 ... I think these should not be only editor's disgression 17:48:09 q+ 17:48:17 q- 17:48:17 q+ 17:48:17 q+ 17:48:28 ack gkellogg 17:48:43 gregg: editors should control what goes into the doc 17:48:59 ack AndyS 17:48:59 ... the editors are bound by the decision of the WG 17:49:09 andyS: clarity is important 17:49:16 q+ 17:49:16 ... many decisions come down to value judgment 17:49:21 ... they are not factual matters 17:49:51 ora: want to see some of the items not go up to the WG 17:50:11 ... if there are some discussions between two people, they should try to resolve it 17:50:18 andyS: it is too easy to reject 17:50:28 ... there is no compromise at the moment 17:50:35 ... people say the same thing again and again 17:50:42 q? 17:50:45 ora: I would like to see editos to be able to exercise judgment 17:50:47 q+ 17:51:20 ... but do not disagree with andy 17:51:23 ack niklasl 17:51:52 niklas: there are activities making sure that spec text says certain propositions 17:52:03 ... did not make a PR for that but work on wording 17:52:19 ack TallTed 17:52:23 ... but agree with what andy says, hard if we have to resolve all value judgment in complete consensus for every wording 17:52:53 TallTed: I feel that this is addressed at me 17:53:01 ... my suggestions are for new readers outside of our group 17:53:27 q+ 17:53:28 ... please clarify what does not work with my suggestions 17:53:48 ... interjection etc. matters 17:53:58 ora: agree, my comments were not targeted on you 17:54:23 TallTed: transferring things into an issue will not create a WG discussion automatically 17:54:36 ... it just starts a discussion about (dis)agreement 17:54:45 https://www.goodreads.com/quotes/494930-i-have-spent-most-of-the-day-putting-in-a 17:54:52 ... if editor feels strongly about it, it may be something for the WG 17:55:36 ack pchampin 17:56:16 pa: what ora said 17:57:10 .... I am in favor of discussing issues async if possible 17:57:21 .... do you expect the editors to create the issues? 17:57:27 TallTed: yes 17:57:51 q+ 17:57:56 q- 17:58:14 pa: think merging PRs is a reasonable course of action 17:58:31 q? 17:58:50 ack pfps 17:59:02 IMO, the person form whom this issue is important should raise the issue 17:59:23 pfps: disagree with pa, editors need to respond to WG comments 17:59:39 ... should be able to say: my judgment is not best way to say this 17:59:51 q+ 18:00:05 ... person who brought this up can go along, if they care enough they should address the issuue? 18:00:23 ack TallTed 18:01:44 RRSAgent, make minutes 18:01:46 I have made the request to generate https://www.w3.org/2025/02/20-rdf-star-minutes.html pchampin 18:01:53 I have made the request to generate https://www.w3.org/2025/02/20-rdf-star-minutes.html fsasaki 18:02:39 https://github.com/w3c/rdf-concepts/pull/115 -> Pull Request 115 add section about 'unstar' mapping (by pchampin) [spec:enhancement] 18:14:24 olaf has left #rdf-star 18:38:07 gkellogg has joined #rdf-star 18:57:16 gkellogg has joined #rdf-star 19:11:53 gkellogg has joined #rdf-star 19:37:11 gkellogg has joined #rdf-star 21:56:20 gkellogg has joined #rdf-star 21:56:43 gkellogg has joined #rdf-star 22:16:56 gkellogg has joined #rdf-star 22:29:27 gkellogg has joined #rdf-star 23:24:32 gkellogg has joined #rdf-star 23:26:08 gkellogg has joined #rdf-star