15:58:52 RRSAgent has joined #rdf-star 15:58:56 logging to https://www.w3.org/2025/07/03-rdf-star-irc 15:58:57 meeting: RDF-Star WG biweekly meeting 15:59:17 Agenda: https://www.w3.org/events/meetings/40c79d60-8147-4da7-8185-c39434216daf/20250703T120000/ 15:59:17 clear agenda 15:59:17 agenda+ Approval of minutes from the last two meetings: -> 1 https://www.w3.org/2025/06/19-rdf-star-minutes.html , -> 2 https://www.w3.org/2025/06/26-rdf-star-minutes.html 15:59:17 agenda+ Proposal for next week's discussion 15:59:18 agenda+ Review of open actions, available at -> 3 https://github.com/orgs/w3c/projects/20/views/3 15:59:19 agenda+ Review of pull requests, available at -> 4 https://github.com/orgs/w3c/projects/20/views/4 15:59:22 agenda+ Issue Triage, available at -> 5 https://github.com/orgs/w3c/projects/20/views/5 15:59:25 agenda+ Any Other Business (AOB), time permitting 15:59:37 present+ 15:59:55 present+ 16:00:18 present+ 16:00:27 present+ 16:01:41 s/RDF-Star WG/RDF & SPARQL WG/ 16:01:55 scribe: fsasaki 16:02:15 niklasl has joined #rdf-star 16:02:19 ora has joined #rdf-star 16:02:29 I have made the request to generate https://www.w3.org/2025/07/03-rdf-star-minutes.html TallTed 16:02:32 present+ 16:02:35 present+ 16:02:40 olaf has joined #rdf-star 16:02:52 present+ 16:03:02 present+ 16:03:07 present+ 16:03:09 chair+ 16:03:21 pfps has joined #rdf-star 16:03:41 present+ 16:03:50 Zakim, open issue 1 16:03:50 I don't understand 'open issue 1', ktk 16:03:51 previous meeting: https://www.w3.org/2025/06/27-rdf-star-minutes.html 16:03:51 next meeting: https://www.w3.org/2025/07/10-rdf-star-minutes.html 16:03:53 present+ 16:04:00 Zakim, next item 16:04:01 agendum 1 -- Approval of minutes from the last two meetings: -> 1 https://www.w3.org/2025/06/19-rdf-star-minutes.html , -> 2 https://www.w3.org/2025/06/26-rdf-star-minutes.html -- 16:04:03 ... taken up [from agendabot] 16:04:29 ora: asking for minutes approval 16:04:32 minutes look acceptable to me 16:04:58 PROPOSAL: Approve minutes from 2025-06-19 and 2025-06-26 16:05:03 +1 16:05:06 +1 16:05:06 +1 16:05:08 +1 16:05:11 +1 16:05:11 +1 16:05:14 +1 16:05:14 +1 16:05:14 +1 16:05:16 +1 16:05:20 Souri has joined #rdf-star 16:05:24 +1 16:05:24 +1 16:05:43 present+ 16:05:46 RESOLVED: Approve minutes from 2025-06-19 and 2025-06-26 16:06:01 Zakim, next item 16:06:01 agendum 2 -- Proposal for next week's discussion -- taken up [from agendabot] 16:06:56 ora: broad review by horizontal groups could be a topic, or should chairs handle this? 16:07:47 pchampin: could discuss in group. We should cover groups listed in charter 16:07:59 q+ 16:08:10 ... might be good to check who can cover what group. 16:08:13 ack gkellogg 16:08:14 ora: agree 16:08:31 gregg: we worked with i18n by tagging issues, that shows up for them 16:08:52 ... so we can just do the tagging with i18n as label and then follow up with an email to chairs 16:09:17 q+ 16:09:20 ora: is it up to us to ask groups what to look at? 16:09:31 ... e.g. bidi as a topic for i18n? 16:09:42 q+ to ask if we need formal "its OK" responses from any coords or is silence enough? 16:09:48 ack pchampin 16:09:49 gregg: yes, it is worth pointing things out 16:10:11 ... but review groups should look into what they want to focus 16:10:29 ack AndyS 16:10:29 AndyS, you wanted to ask if we need formal "its OK" responses from any coords or is silence enough? 16:10:29 pchampin: we need to cover also liaison groups, i.e. outside W3C 16:10:55 andy: do we need formal responses from groups or is time out of response ok? 16:11:02 pchampin: there is no formal time out in the process 16:11:17 ... the team decides on the time out 16:11:40 ... there is an informal possibility of a time out of groups are not responsive enough 16:11:52 ... it just has to be reasonable 16:12:12 andy: is there is a responsibility of groups to send a reply? 16:12:27 pchampin: yes, we need acks even if there is no issue 16:12:41 q+ 16:12:45 ora: so we discuss this next weeks and then see who contacts what group 16:12:47 q+ 16:12:50 ack tl 16:12:59 tl: discuss issue-169 16:13:13 q+ 16:13:16 https://github.com/w3c/rdf-star-wg/issues/169 16:13:17 https://github.com/w3c/rdf-star-wg/issues/169 -> Issue 169 definition of reifiers is non-normative and seems vague (by rat10) [needs discussion] 16:13:23 ... i.e. "reifiers should have a better definition" issue 16:13:24 ack gkellogg 16:13:43 gregg: we still have to discuss the "resolve IRIs" topic 16:14:01 ... i.e. do all IRI go through IRI resolution algorithm 16:14:12 .... there are tests that make some assumptions 16:14:16 ack pfps 16:14:42 ... they need to take the discussion into account 16:14:56 RRSAgent, draft minutes 16:14:58 I have made the request to generate https://www.w3.org/2025/07/03-rdf-star-minutes.html ktk 16:15:02 q+ 16:15:11 ack pchampin 16:15:23 RRSAgent, make log public 16:15:44 pfps: want to discuss a certain issue with given time 16:15:52 ora: 15 to 20 minutes suggested 16:16:00 q+ 16:16:12 q+ 16:16:15 andy: asked in the issue for feedback if WG members want to discuss 16:16:24 ack pfps 16:16:35 pfps: agree with andy about that approach 16:17:01 ack tl 16:17:11 s/pfps: want to discuss/pchampin: want to discuss 16:17:35 tl: I raised the issue last time and got some support, not fighting for labels 16:18:35 ora: if you want to discuss things tl let us timebox for 15 min and then discuss 16:19:09 q+ 16:19:15 ack pchampin 16:19:29 pchampin: I participated in the discussion of the issue 16:19:52 ... there is an issue if langstring without a language tag should be introduced by parsers 16:20:03 https://github.com/w3c/rdf-turtle/issues/37 16:20:04 https://github.com/w3c/rdf-turtle/issues/37 -> Issue 37 language strings missing a language tag (by pchampin) [propose closing] [test:needs tests] 16:20:27 gregg: needs discussion. This will also hit concrete syntaxes. 16:20:39 ora: objections on discussing this? will also be time boxed. 16:20:52 pchampin: will prepare summary of the issue 16:21:20 ... will send a mail to the group before the call 16:21:44 ora: at this point, the WG will just check of things of the list 16:21:58 q+ 16:22:07 ... so we could spend the rest next week in that way 16:22:07 ack AndyS 16:22:16 andy: can we put issue-169 on the agenda? 16:22:50 q+ 16:22:59 ack niklasl 16:23:20 niklas: thinking about editorial topics, e.g. rdf commons repository 16:23:54 q+ 16:23:59 ora: do we have a point in which the alternating meetings do not make sense? 16:24:10 ack pfps 16:24:13 q+ 16:24:16 ... should we dedicate the meetings to checking things of the list? 16:24:48 ack ktk 16:24:54 pfps: semantics doc has parts that depend on definitions, unproductive to change those if first parts change 16:25:22 adrian: in the last weeks we get more admin stuff than real remaining work, I feel 16:25:36 q+ 16:25:43 ... if that is true, how can we go through the remaining topics? 16:25:53 ack AndyS 16:26:06 ora: this is about nailing things down 16:26:13 pfps: yes, and we took a step back on this 16:26:20 q+ 16:26:24 andy: semantics should be earlier on our path 16:26:35 pfps: others should talk on that 16:26:43 ... doerte and enrico should talk on that 16:26:59 ack niklasl 16:27:10 niklas: dominik is doing the schema doc, I can do primer things, that is not related to the semantics doc 16:27:47 ... dominik needs to look into the reification topic in relation to semantics then schema doc 16:28:02 ... we need to have work meetings editing and merging branches 16:28:21 q+ 16:28:24 ora: editors should get together on these docs 16:28:27 ack gkellogg 16:28:47 gregg: prio should be on first round of CR 16:29:06 ... we should focus on open items, pfps mentioned items in schema and primer 16:29:20 gregg: we should now focus on what it takes to work on those 16:29:26 q+ 16:29:32 ack ktk 16:29:33 ... and do then the work in git, focus our time in the meetings right 16:30:14 adrian: should we still need the larger group, try to close in the call also to close pull requests? 16:30:18 ora: agree 16:30:28 gregg: not each topic is mature enough 16:30:33 adrian: agree 16:30:53 gregg: PRs related to certain docs. Concepts has a number open, requires some focus. 16:31:13 ora: let us put some time on the agenda about this 16:31:30 ... this is a good development! We wanted to get here 16:31:47 gregg: looking for gaps in test coverage is important 16:32:06 ... many times we do not have a normative statement but still tests are necessary 16:32:20 Zakim, next item 16:32:20 agendum 3 -- Review of open actions, available at -> 3 https://github.com/orgs/w3c/projects/20/views/3 -- taken up [from agendabot] 16:32:33 q+ 16:33:11 ora: my action not done yet 16:33:37 q+ 16:33:38 niklas: work in progress on the owlification issue 16:33:46 ora: will then take a look 16:34:07 ack pchampin 16:34:26 pchampin: 165 is done, 168 is pending 16:34:55 ack gkellogg 16:34:58 niklasl i'd be interested to have a look at your owl-ification work 16:35:21 gregg: on 168, great idea from niklas to use build process to have to avoid copying files and use referencing instead 16:35:28 .... will do that after we got CR drafts out 16:36:04 niklas: trying out that pattern in my fork 16:36:11 Zakim, next item 16:36:11 agendum 4 -- Review of pull requests, available at -> 4 https://github.com/orgs/w3c/projects/20/views/4 -- taken up [from agendabot] 16:36:27 q+ 16:36:39 ora: anything we can merge? 16:36:46 ack gkellogg 16:36:53 gregg: n-quads and n-triples PRs are close being done 16:37:13 ... people request changes, please review ones these are done and comment or approve PR 16:37:21 ora: agree 16:38:10 q+ 16:38:17 gregg: sometimes there have been requests for changes, discussion, implementations. If you are asked to look at these, please give it a prio to review and approve if possible. 16:38:18 ora: agree 16:38:41 ... how about the minor changes to turtle? 16:38:54 gregg: there have been great suggestions from ted on these 16:39:11 ... once we have closure on the docs we move on 16:39:17 ... we are close on this 16:39:37 ack pfps 16:39:42 q+ 16:39:51 ack AndyS 16:40:03 sorry, on mute 16:40:06 q+ 16:40:23 andy: on rdf concepts, does pchampin need input from me? 16:40:31 pchampin: just more time, will give it high prio 16:40:47 ack pfps 16:40:50 andy: if you need anything let me know 16:41:04 pfps: I have a PR for tests, who should be doing these 16:41:09 ... is there an editor for tests 16:41:33 gregg: if you are an editor of a doc, please make a merge of related tests 16:41:45 pfps: works for me 16:41:47 +1 16:41:50 +1 16:41:53 andy: is this about 200? 16:41:55 pfps: 201 16:42:04 ... just merged 16:42:12 ... will look at 200 16:42:30 ... waiting for doerte to get back to me 16:43:03 ora: others that are not tagged, what to do about them? 16:43:14 gregg: 79 is created by me 16:43:30 ... nothing is in manifest that drove the expected behaviour 16:44:00 ... depended on running a script that gregg wiliams managed 16:44:18 ... not relating to work that needs to be done soon, we should consider if that is the approach we want to do 16:44:44 ora: would be ok to check if people want to merge 16:44:52 andy: agree, worth it for moving things forward 16:45:08 adrian: 193 and 198 seem to be ok, on concepts doc 16:45:42 pchampin: will take care about this by end of week 16:46:28 ora: what about n-quads, no 78 16:46:56 gregg: once ted is ok, we are good to go 16:47:17 ... then need to change n-triples, turtle, trig to check if related changes are required 16:47:48 ... we need to have people review the doc for such related changes, we are ahead of the process for that 16:47:59 Zakim, next item 16:47:59 agendum 5 -- Issue Triage, available at -> 5 https://github.com/orgs/w3c/projects/20/views/5 -- taken up [from agendabot] 16:48:41 going through proposed closing list 16:48:51 ora: language strings missing topic, already discussed 16:49:02 ... will discuss next week 16:49:08 gregg: we can close 161 16:49:27 +1 16:49:37 ora: ok, let us close 16:50:17 ora: rdfs 14 entailment topic, how about that? 16:50:37 andy: the document is saying different than what is intended 16:50:47 ora: can it be closed? 16:51:52 ora: not sure what proposed closing means if we do not close issues 16:52:11 pfps: suggesting to close this 16:52:15 ... andy seems to agree 16:52:22 ora: ok, let us close that 16:52:45 ... 83 is editoral 16:53:13 ... does this depend on bidi topic? 16:53:19 pfps: no. it is teds issue 16:54:00 ora: we discussed that editors should do good judgment and do things 16:54:08 https://github.com/w3c/rdf-semantics/issues/83 -> Issue 83 wording defining "RDF Literals" needs clarification (by TallTed) [propose closing] [spec:editorial] 16:54:49 ted: would like to see input besides me and the editors 16:55:05 ora: will provide some input 16:55:13 ted: please others look at this as well 16:55:40 ora: anything else? 16:56:23 ... like us to get to a point, if something is proposed to close, whose who disagree should speak up 16:56:41 adrian: same for PRs, close after 2 weeks without response 16:56:45 ora: agree 16:57:19 ... tomorrow US has public holiday 16:57:32 andy: will cancel sparql task force meeting tomorrow 16:57:48 ... want to have editors for next discussion 16:57:52 RRSAgent, draft minutes 16:57:54 I have made the request to generate https://www.w3.org/2025/07/03-rdf-star-minutes.html ktk 16:59:03 olaf has left #rdf-star 16:59:53 s/editoral/editorial/ 17:00:09 s/check of/check off/ 17:00:13 i|79 is created by me|subtopic: w3c/rdf-tests#79 17:00:40 i|what about n-quads, no 78|w3c/rdf-n-quads#78 17:01:17 s|w3c/rdf-n-quads#78|subtopic: w3c/rdf-n-quads#78 17:01:21 RRSAgent, make minutes 17:01:22 I have made the request to generate https://www.w3.org/2025/07/03-rdf-star-minutes.html pchampin 17:02:41 i|rdfs 14 entailment topic|subtopic: w3c/rdf-semantics#126 17:03:12 s| … 83 is editorial|ora: 83 is editorial 17:03:48 i|83 is editorial|subtopic: w3c/rdf-semantics#83 17:04:51 i|anything else?|topic: AOB 17:04:54 RRSAgent, make minutes 17:04:55 I have made the request to generate https://www.w3.org/2025/07/03-rdf-star-minutes.html pchampin 18:08:25 gkellogg has joined #rdf-star 18:27:16 gkellogg has joined #rdf-star 18:47:25 pfps has left #rdf-star 19:20:43 gkellogg has joined #rdf-star 21:23:49 gkellogg has joined #rdf-star 21:51:06 gkellogg has joined #rdf-star 23:05:44 gkellogg has joined #rdf-star