14:07:20 RRSAgent has joined #rdf-star 14:07:24 logging to https://www.w3.org/2023/05/11-rdf-star-irc 14:07:24 RRSAgent, make logs Public 14:07:25 please title this meeting ("meeting: ..."), pchampin 14:07:31 meeting: RDF-star WG weekly meeting 14:07:59 agenda: https://www.w3.org/events/meetings/f2add3af-6743-4f52-8fcc-4f62c6cdd8af/20230511T120000/#agenda 14:07:59 clear agenda 14:07:59 agenda+ Scribe: Hartig, Olaf (alternate: Williams, Gregory) 14:07:59 agenda+ Approval of last week's minutes: -> 1 https://www.w3.org/2023/05/04-rdf-star-minutes.html 14:07:59 agenda+ Status of "First Public Working Draft" (FPWD) 14:08:00 agenda+ Use Case Proposals 14:08:02 agenda+ Review of open actions, available at -> 2 https://github.com/orgs/w3c/projects/20/views/3 14:08:05 agenda+ Review of pull requests, available at -> 3 https://github.com/orgs/w3c/projects/20/views/4 14:08:08 agenda+ Any Other Business (AOB), time permitting 14:08:44 previous meeting: https://www.w3.org/2023/05/04-rdf-star-minutes.html 14:08:54 next meeting: https://www.w3.org/2023/05/25-rdf-star-minutes.html 14:14:19 gkellogg has joined #rdf-star 14:15:22 gkellogg_ has joined #rdf-star 14:19:29 gkellogg has joined #rdf-star 14:21:13 gkellogg_ has joined #rdf-star 14:23:18 gkellogg has joined #rdf-star 14:40:43 gkellogg has joined #rdf-star 14:49:11 gkellogg has joined #rdf-star 14:56:33 gkellogg has joined #rdf-star 14:59:13 gkellogg_ has joined #rdf-star 15:02:20 gkellogg has joined #rdf-star 15:06:06 gkellogg_ has joined #rdf-star 15:51:23 FYI I will be travelling next week and so unable to scribe. I tried looking at the scribe list to know who would be next in line, but it seems not to have been updated in a few weeks. Maybe Ruben? 15:51:37 ok tnx will check it out 15:51:40 ah 15:51:46 next week is public holiday in many parts anyway 15:51:50 I think we will skip that 15:54:31 pfps has joined #rdf-star 15:58:26 olaf has joined #rdf-star 15:59:00 zakim, who's here? 15:59:00 Present: (no one) 15:59:02 On IRC I see olaf, pfps, gkellogg_, RRSAgent, Zakim, ghurlbot, driib, agendabot, csarven, VladimirAlexiev, Timothe, Tpt, ktk, rhiaro, gtw, pchampin 15:59:06 present+ 15:59:41 present+ 15:59:57 present+ 16:00:23 present+ 16:00:30 present+ 16:00:55 Zakim, show agenda 16:00:55 I see 7 items remaining on the agenda: 16:00:55 1. Scribe: Hartig, Olaf (alternate: Williams, Gregory) [from agendabot] 16:00:55 2. Approval of last week's minutes: -> 1 https://www.w3.org/2023/05/04-rdf-star-minutes.html [from agendabot] 16:00:55 3. Status of "First Public Working Draft" (FPWD) [from agendabot] 16:00:55 4. Use Case Proposals [from agendabot] 16:00:55 5. Review of open actions, available at -> 2 https://github.com/orgs/w3c/projects/20/views/3 [from agendabot] 16:00:55 6. Review of pull requests, available at -> 3 https://github.com/orgs/w3c/projects/20/views/4 [from agendabot] 16:00:55 7. Any Other Business (AOB), time permitting [from agendabot] 16:01:04 Zakim, open item 1 16:01:04 agendum 1 -- Scribe: Hartig, Olaf (alternate: Williams, Gregory) -- taken up [from agendabot] 16:01:17 Scribe: olaf: 16:01:19 Scribe: olaf 16:01:25 TallTed has joined #rdf-star 16:01:30 Zakim, close item 1 16:01:30 agendum 1, Scribe: Hartig, Olaf (alternate: Williams, Gregory), closed 16:01:31 I see 6 items remaining on the agenda; the next one is 16:01:31 2. Approval of last week's minutes: -> 1 https://www.w3.org/2023/05/04-rdf-star-minutes.html [from agendabot] 16:01:36 Dominik_T has joined #rdf-star 16:02:14 present+ 16:02:24 present+ 16:02:48 AZ has joined #rdf-star 16:02:54 AndyS has joined #rdf-star 16:03:05 present+ 16:03:59 Regrets: Ora 16:04:16 present+ 16:04:40 Tpt: I don't see you on zoom 16:04:47 present+ 16:05:05 Sorry I am not in the zoom yet, I should be able to connect in a few minutes 16:05:11 ktk: review of last week's agenda. Any comments? 16:05:13 present+ 16:05:14 PROPOSAL: Approve last week's minutes 16:06:11 ktk: confusion in the discussion board 16:06:20 ... because there are two numbers 16:06:32 ... the issue number itself and some other number 16:07:23 minutes look fine to me 16:09:13 +1 approve minutes 16:09:20 ktk: when closing issues in IRC, use the complete URL from the discussion board 16:09:21 +1 16:09:23 +1 16:09:25 +1 16:09:27 +1 16:09:27 +1 16:09:30 +1 16:09:31 +1 to accepting minute 16:09:37 s/minute/minutes/ 16:09:48 RESOLUTION: Approve last week's minutes 16:09:55 Zakim, close item 16:09:55 I don't understand 'close item', ktk 16:10:01 Zakim, close item 2 16:10:01 agendum 2, Approval of last week's minutes: -> 1 https://www.w3.org/2023/05/04-rdf-star-minutes.html, closed 16:10:03 I see 5 items remaining on the agenda; the next one is 16:10:03 3. Status of "First Public Working Draft" (FPWD) [from agendabot] 16:10:12 zakim, open item 3 16:10:12 agendum 3 -- Status of "First Public Working Draft" (FPWD) -- taken up [from agendabot] 16:10:43 ktk: any updates on the FPWDs? 16:11:04 AndyS: docs are ready to go, waiting for pchampin 16:11:20 gkellogg_: yes 16:11:32 ... but be prepared for last-minute changes 16:11:55 https://github.com/w3c/respec/discussions/4445 16:11:55 ktk: I asked on the discussion board of respec 16:12:12 ... whether one can ping specific versions of respec 16:12:12 q+ 16:12:29 gkellogg_: yes, we need to be aware of that 16:12:55 ... there are important changes in these versions 16:13:03 ack gkellogg_ 16:13:22 Zakim, next item 16:13:22 agendum 4 -- Use Case Proposals -- taken up [from agendabot] 16:13:24 RRSAgent, draft minutes 16:13:25 I have made the request to generate https://www.w3.org/2023/05/11-rdf-star-minutes.html TallTed 16:13:43 RRSAgent, make logs public 16:14:09 ktk: proposal was to pfps a chance to talk about the progress on the use cases 16:14:15 scribe- olaf: 16:14:25 pfps: not much progress 16:14:30 chair: ktk 16:14:39 q+ 16:14:52 ... releven group has a use case that they want to work out 16:14:56 RRSAgent, draft minutes 16:14:57 I have made the request to generate https://www.w3.org/2023/05/11-rdf-star-minutes.html TallTed 16:15:14 ... hopefully ready within the next couple of days 16:15:31 ktk: which repo? 16:15:42 https://github.com/w3c/rdf-ucr 16:15:50 (was it announced?) 16:15:52 pfps: I added a PR to the main repo to remove the issue about the use case 16:16:03 q- 16:16:16 s/Scribe: olaf:// 16:16:26 RRSAgent, draft minutes 16:16:28 I have made the request to generate https://www.w3.org/2023/05/11-rdf-star-minutes.html TallTed 16:16:34 ... want to have a first well-developed use case in that repo before announcing the repo 16:17:05 ... would keep the item on the agenda for next week 16:17:14 q? 16:17:17 ... in case there are noteworthy changes 16:17:27 q+ 16:17:37 s/last week's agenda. Any comments/last week's minutes. Any comments/ 16:17:38 Zakim, next item 16:17:38 I see a speaker queue remaining and respectfully decline to close this agendum, ktk 16:17:53 AndyS: we have agenda items for outstanding actions and PRs, but none for issues 16:17:55 ack AndyS 16:18:07 ... we should cover them in the next agenda item 16:18:14 Zakim, next item 16:18:14 agendum 5 -- Review of open actions, available at -> 2 https://github.com/orgs/w3c/projects/20/views/3 -- taken up [from agendabot] 16:19:00 ktk: question to pchampin about TPAC but he is not here 16:19:22 AZ: no remark on my issue 16:20:25 ... option: we define partial conformance to RDF 1.2 16:20:34 ... option 1: ?? 16:20:45 ... Didn't get feedback on the options. 16:21:01 ... partial would be explicitly defined. 16:21:07 q+ 16:21:24 ... I would like to get more feedback, on the list or in the issue 16:21:44 AndyS: I would find it easier if there was a draft to provide comments on. 16:22:05 ack me 16:22:12 AZ: problem is that there are two issues that are tightly related 16:22:35 ... two actions not issues 16:23:08 ... issue 19 and issue 23 16:23:22 ktk: talk to Ora and decide on which one to close 16:23:42 gkellogg_: they can be assigned to both of you 16:24:13 s/gkellogg_/TallTed/ 16:24:23 Zakim, next item 16:24:23 agendum 6 -- Review of pull requests, available at -> 3 https://github.com/orgs/w3c/projects/20/views/4 -- taken up [from agendabot] 16:24:29 https://github.com/w3c/rdf-concepts/issues/9 and https://github.com/w3c/rdf-star-wg/wiki/Text-Direction-Proposal (draft - for now, consider it an "existence proof" of solution) 16:25:06 AndyS: I took up the discussion up to a certain point and drafted it in a wiki page 16:25:15 ... to have somethign concrete 16:26:03 ... in order to give everyone a sense of what the issue/effort is when taking up the issue 16:26:13 ... of putting text direction support in RDF 16:26:26 q+ 16:26:35 ... We need a formal resolution to take up that work 16:26:56 ... We may at least do a strawpoll 16:26:56 q+ to note it is a worthwhile thing, but a substantial effort touching (almost?) every doc in our queue 16:27:12 q+ to ask what the resolution is 16:27:28 gkellogg_: Some people have noted that this hits every implementation, every serialization format, etc. 16:27:38 ... So, it is a quite consequential change 16:28:10 q+ 16:28:10 ... It opens up RDF to a large part of the world 16:28:13 Chair: ktk 16:28:28 ... unfortunate that unicode does not provide that 16:28:48 ack gkellogg_ 16:28:53 ... we came up with an informative mechanism in ... group 16:29:17 ack TallTed 16:29:17 TallTed, you wanted to note it is a worthwhile thing, but a substantial effort touching (almost?) every doc in our queue 16:29:30 TallTed: Concerned about the amount of work involved in this 16:29:44 ... fear that this opens a big can of worms 16:30:07 ack pfps 16:30:07 pfps, you wanted to ask what the resolution is 16:30:19 ... not standing in the way but people who want to pick this up will have a lot of work to do 16:30:29 pfps: agree 16:30:32 q- 16:30:43 AndyS: Respect the concerns 16:30:58 ... we work in the context of the wider W3C context 16:31:00 q+ 16:31:07 ack AndyS 16:31:13 my worry is that this is significant work for implementers so it may end up splitting RDF 1.2 classis 16:31:28 ... if we don't pick it up, we have to defend why not 16:31:49 ... there are complicated cases, languages with multiple scripts 16:31:59 q+ 16:32:28 ack gkellogg_ 16:32:34 https://github.com/w3c/rdf-star-wg/blob/main/docs/text-direction.md#the-i18n-namespace 16:32:35 ... in the wiki page I tried to outline the impacts on the different specs (e.g., SPARQL, Turtle) 16:32:59 gkellogg_: there are a couple of examples 16:33:09 afer spending a lot of time on this issue I'm still confused as to what exactly has to be done by RDF 16:33:15 ... possibility to leverage datatype 16:33:25 q+ 16:33:36 ... in SPARQL 16:33:45 ... wouldn't change surface syntax 16:34:13 ... contained to fewer areas of our specs 16:34:18 s/RDF 1.2 classis/RDF 1.2 classic/ 16:34:20 ktk: I am also much confused 16:34:25 ack ktk 16:34:36 ... we should understand what is specific to RDF in this work 16:35:03 AndyS: point at the moment is not to discuss possible solutions but to decide whether we take it up 16:35:30 ... in W3C to get to REC we need horizontal review, ITC is one of them 16:35:44 ... they have offered to help 16:36:06 s/ITC/I18n/ 16:36:36 ktk: proposal or strawpoll? 16:36:47 Standardize text direction for RDF 1.2 (and related specs) 16:37:31 s/Standardize/draft proposal: Standardize/ 16:38:03 rdf-concepts#9 16:38:03 https://github.com/w3c/rdf-concepts/issues/9 -> Issue 9 text direction (gkellogg) i18n-tracker, needs discussion, spec:substantive 16:38:16 Accept RDF-Concepts issue #9: text direction 16:38:16 https://github.com/w3c/rdf-star-wg/issues/9 -> Issue 9 ambiguity of canonical N-Triples (pchampin) complete 16:39:46 PROPOSAL: Accept RDF-Concepts issue "text direction" https://github.com/w3c/rdf-concepts/issues/9 16:40:00 +1 16:40:01 +1 16:40:03 +1 16:40:07 +1 16:40:07 +1 16:40:10 +1 16:40:11 +0.5 16:40:16 +0 16:40:27 -0 as this still appears to commit the wg to produce something 16:40:28 +0 16:40:36 +1 16:41:07 ktk: Do wee need majority? 16:41:22 RESOLUTION: Accept RDF-Concepts issue "text direction" https://github.com/w3c/rdf-concepts/issues/9 16:41:30 TallTed: If there is no -1 and a substantial number of +1 then it is accepted 16:41:38 s/wee/we/ 16:42:00 Andys: I would find it easier to have an online discussion about it. 16:42:32 ktk: let's look at the PRs now 16:42:46 q+ 16:43:27 Dominik_T: I would like to change the HTML to be better visible in mobile phones and small devices 16:43:28 ack me 16:43:45 ... I will change the CSS a bit 16:43:56 ... in the PR 16:44:03 ... will do that tomorrow 16:44:27 pfps: changes to CSS can do a lot of things 16:44:41 q+ 16:44:50 q+ 16:44:51 ... thse PRs causes a lot of discussion / waste of time 16:45:07 ack pfps 16:45:12 ... would have been better as an issue for the group to discuss rather than lots of PRs 16:45:18 ack TallTed 16:45:37 TallTed: I agree, should better be an issue first and then tested as a PR on one repo 16:46:05 ... instead of PRs in all repos at the same time 16:46:51 pfps: I don't know the syntax of CSS to understand whether the change is substantial 16:46:56 ack gkellogg_ 16:47:18 gkellogg_: regarding the markup problem, I was looking at the results of the build which had issues 16:48:19 ... regarding making many PRs about CSS for lots of repos, it is a problem that the discussion is all over the place now and that tables are used in different ways in the different specs 16:48:50 ... generally, this is about accessibility, which we may have to look at 16:48:53 q+ 16:48:58 ack AndyS 16:49:11 ... accessibility issues are often uncovered during the wider reviewer 16:49:35 AndyS: this PR (for SPARQL) I would like to be merged 16:49:53 ... because long-standing PRs are difficult to work on 16:49:56 q+ to mention that the last version I saw made things worse in my opinion 16:50:04 ... but I request to avoid breaks within words 16:50:07 ack me 16:50:31 pfps: I don't want this PR merged in the smenatics doc 16:50:37 q+ 16:50:40 ... because it breaks within words 16:51:03 ack pfps 16:51:04 pfps, you wanted to mention that the last version I saw made things worse in my opinion 16:51:08 ack TallTed 16:51:25 TallTed: There is a requested change in this PR for the semantics doc 16:51:41 ... 'break-word' has been deprecated 16:53:19 ... If you apply my change request, pfps' issue about the breaking of words will be resolved 16:53:19 ktk: can you apply that? 16:53:19 Dominik_T: yes 16:53:19 ktk: only apply it to the semantics doc first 16:53:50 pfps: changes to common things like CSS need to be done very carefully 16:53:52 The most demanding SPARQL effect is the grammar in query. We can treat it specially. 16:54:06 +1 fix rdf-semantics#30, and upon approval, replicate to the other CSS PRs 16:54:07 https://github.com/w3c/rdf-semantics/issues/30 -> Pull Request 30 improve display on mobile phones (domel) needs discussion 16:54:09 ktk: propose to apply it only to the semantics doc first 16:54:40 ... Thursday next week is a public holiday in Europe 16:54:55 AndyS: May 18? 16:54:58 ktk: yes 16:55:01 18th of May is holiday in France 16:55:12 AndyS: not a public holiday in the UK 16:55:29 TallTed: yes on the 18th, not 25th 16:55:38 I will be travelling on the 18th 16:55:44 gtw: not here next week 16:55:53 I'm here on the 18th, not on the 25th 16:56:01 Timothe: I will be here 16:56:08 AZ: not here 16:56:23 Dominik_T: on holiday next week 16:56:38 q+ to quickly observe conflict tomorrow, between RDF-star Semantics TF and RDF C14n Special Topic call 16:56:56 ktk: propose to skip next week 16:57:09 regrets for me 2023-05-25 16:57:30 ... and those who won't be here on the 25th, please log your regrets in the IRC 16:57:53 RRSAgent, draft minutes 16:57:54 I have made the request to generate https://www.w3.org/2023/05/11-rdf-star-minutes.html TallTed 17:00:03 i/Thursday next week/topic: next meeting/ 17:01:17 i|let's look at the PRs now|topic: Open PRs https://github.com/orgs/w3c/projects/20/views/4/ 17:01:24 RRSAgent, draft minutes 17:01:26 I have made the request to generate https://www.w3.org/2023/05/11-rdf-star-minutes.html TallTed 17:02:28 zakim, end meeting 17:02:28 As of this point the attendees have been gkellogg_, olaf, ktk, gtw, Timothe, Dominik_T, Tpt, AZ, TallTed, AndyS, pfps 17:02:30 RRSAgent, please draft minutes 17:02:31 I have made the request to generate https://www.w3.org/2023/05/11-rdf-star-minutes.html Zakim 17:03:06 I am happy to have been of service, TallTed; please remember to excuse RRSAgent. Goodbye 17:03:06 Zakim has left #rdf-star 17:03:06 RRSAgent, bye 17:03:06 I see no action items