11:53:40 RRSAgent has joined #data-shapes 11:53:44 logging to https://www.w3.org/2025/08/25-data-shapes-irc 11:53:44 Zakim has joined #data-shapes 11:53:44 meeting: Data Shapes WG 11:53:48 agenda: https://github.com/w3c/data-shapes/blob/agenda/admin/agenda-2025-08-25.md 11:53:48 bah. slow bots! 11:53:50 clear agenda 11:53:50 agenda+ Discussion 11:53:50 agenda+ Process 11:54:19 meeting: Data Shapes WG 11:54:19 agenda: https://github.com/w3c/data-shapes/blob/agenda/admin/agenda-2025-08-25.md 11:54:20 clear agenda 11:54:20 agenda+ Discussion 11:54:20 agenda+ Process 11:54:32 clear agenda 11:54:33 agenda+ Phase 2 subgroup reports 11:54:35 agenda+ stadardised document elements 11:54:37 agenda+ Overview's What's New 11:54:39 agenda+ SHACL-C v. SHACL-CS? 11:56:36 I have made the request to generate https://www.w3.org/2025/08/25-data-shapes-minutes.html TallTed 11:56:45 TallTed has changed the topic to: Data Shapes WG -- 2025-08-25 agenda: https://github.com/w3c/data-shapes/blob/agenda/admin/agenda-2025-08-25.md 11:57:20 HolgerK has joined #data-shapes 11:57:29 previous meeting: https://www.w3.org/2025/08/18-data-shapes-minutes.html 11:57:29 next meeting: https://www.w3.org/2025/09/01-data-shapes-minutes.html 11:57:40 s/bah. slow bots!// 11:58:11 present+ 11:58:46 chair: elianaP 12:00:24 Agenda request - publishing editors working drafts of phase 2 docs 12:00:40 elianaP has joined #data-shapes 12:01:29 simonstey has joined #data-shapes 12:01:40 agenda? 12:02:08 present+ 12:02:14 ajnelson-nist has joined #data-shapes 12:02:22 present+ 12:02:25 I have made the request to generate https://www.w3.org/2025/08/25-data-shapes-minutes.html TallTed 12:02:31 present+ 12:02:31 edmond has joined #data-shapes 12:02:40 YoucTagh has joined #data-shapes 12:02:56 mgberg has joined #data-shapes 12:03:15 present+ 12:03:27 present+ 12:03:39 present+ 12:03:40 DavidHabgood has joined #data-shapes 12:04:31 scribe: ajnelson-nist 12:04:39 Robert has joined #data-shapes 12:05:21 SimonW has joined #data-shapes 12:05:22 present+ 12:05:26 nicholascar has joined #data-shapes 12:05:29 One additional point added to agenda from AndyS. 12:05:32 present+ 12:05:33 topic: Subgroup reports 12:05:48 subtopic: Profiling subgroup 12:05:51 present+ 12:05:58 nicholascar: Nothing added to profiles in the last week. 12:06:11 subtopic: SHACL UI 12:06:34 edmond: Had first meeting. Went over features in specs that we want to align with in SHACL UI. 12:06:45 ... Topics have been written up in GitHub issue, will go over in tomorrow's meeting. 12:06:53 ... Task force creatd, meeting now in W3C calendar. 12:07:00 s/creatd/created/ 12:07:18 elianaP: Does Profiling group have meeting this week? 12:07:32 nicholascar: Yes, same Zoom link as regular meeting, but at Thursday, this time. 12:07:39 subtopic: SHACL Rules 12:07:47 AndyS: First meeting tomorrow. 12:07:56 ... Task force established per W3C process. 12:08:04 present+ Carine 12:08:09 ... Meeting agenda should be on everyone's calendar. 12:08:31 subtopic: SHACL Compact Syntax 12:08:49 elianaP: no Vladimir or Jesse today 12:08:49 fsasaki has joined #data-shapes 12:08:57 ... Unsure if there's a meeting for that this week. 12:09:05 present+ 12:09:08 topic: Standardized document elements 12:09:37 present+ 12:09:46 present+ 12:09:57 nicholascar: I said I'd get the document listings so there'd be a consistent include mechanism. Written statically at the moment. PR noted in agenda. 12:10:13 ... We can look for other standardized pieces of documents. 12:10:27 ... Review needed, from elianaP or ajnelson-nist. 12:10:27 q+ 12:10:31 Topic: What's new section 12:10:46 nicholascar: Required for horizontal review process. 12:10:58 ... Written up Holger's LinkedIn post. 12:11:14 ... The What's New WILL shift a bit as the documents evolve. 12:11:25 ... Editors need to keep an eye on this What's New text so it evolves in line. 12:11:34 ... This will probably be the most summarized form of our deliverables. 12:11:44 ... PR is ready for everyone to look at. 12:12:20 ... Request - we should get this out of Review and into an an initial draft so editors can incrementally revise. 12:12:34 elianaP: Requirements for Explainer should be checked. 12:13:00 nicholascar: This seems close already to the Explainer requirements. 12:13:09 AndyS, elianaP, caribou -- some more work will be needed on the TF subgrounds (such has how to join). note there are 2 here -- https://www.w3.org/groups/tf/?search=shacl -- but there's also https://www.w3.org/events/meetings/be6795a3-ddea-4b65-97e4-e58efa13f0c4/ 12:13:18 AndyS: Stepping back to task forces, 12:13:24 ack AndyS 12:13:38 ... updates on Compact Syntax? 12:13:56 q+ 12:13:57 nicholascar: There are two editors at the moment. 12:14:05 AndyS: But they're not editors yet until there's a document. 12:14:35 elianaP: Will send an ask to them to confirm their timelines. 12:14:55 q? 12:15:02 ack me 12:15:02 s/But they're not editors yet/No additional contributors until/ 12:15:04 ack TallTed 12:15:17 topic: SHACL-C vs. SHACL-CS 12:15:26 elianaP: Assuming this is about the abbreviation of SHACL Compact Syntax. 12:15:55 nicholascar: Eliana, can you also ask the editors their opinion? 12:16:06 q+ 12:16:39 more re TF -- `SHACL Rules` and `SHACL UI` are in my calendar 12:16:52 ajnelson-nist: Suggestion for looking to prefixes for if we'd want cs vs. c. 12:17:12 TallTed: There was some use in issues pre-existing the group that went either way. 12:17:12 q+ 12:17:46 ( elianaP, TallTed, nicholascar, ajnelson-nist seem to lean towards "cs") 12:17:49 ack me 12:17:53 The file extensions are ".shc" and ".shaclc" 12:18:01 I have made the request to generate https://www.w3.org/2025/08/25-data-shapes-minutes.html TallTed 12:19:04 Topic: Call for consensus 12:19:31 caribou : Will look into resolving Call for Consensus on documents' early publishing. 12:19:39 agenda? 12:19:44 Topic: Blocking PRs on editorial issues 12:19:49 https://github.com/w3c/data-shapes/pull/509#discussion_r2289027948 12:20:02 HolgerK: There was some controversy on some issues about editorial issues holding PRs. 12:20:13 SimonW has joined #data-shapes 12:20:33 ... Should these editorial changes be treated as blocking? 12:20:34 q+ 12:20:47 ... If there are strong feelings about layout of source code, they should be done in a later pass. 12:21:05 ... This is a blocker on some personal workflows. 12:21:41 ack me 12:22:09 TallTed: When I'm reviewing a PR, I put in suggested changes, some purely editorial, some not. 12:22:24 ... I shoot for better comprehensibility, for consumers outside of this group. 12:22:42 ... It is perfectly reasonable and acceptable to make new issues about requested changes. 12:23:17 q+ 12:23:25 ack me 12:23:49 HolgerK: In the case where it's about sentences, I've just accepted them. 12:24:09 q+ 12:24:22 ... Once properties get added with different word-length, lines outside of that one line need to shift in order to remain aligning. 12:24:48 ... But this blocks a PR. 12:25:51 TallTed: In any Suggestion, there is a 3-dot menu at the upper right of every Suggestion, which can export the change to a new Issue. 12:25:51 q+ 12:26:01 ... 12:26:02 q+ 12:26:24 ack TallTed 12:26:27 HolgerK: When others make suggestions, they are not blocking. 12:26:43 TallTed: But comments disappear into GitHub. 12:26:57 HolgerK: I do handle both the same way. 12:26:57 ... 12:27:21 ... Request - please make comments before requesting changes. 12:27:27 q- 12:27:40 q- 12:28:03 TallTed: Comments are less-accountable than Requested Changes. 12:28:34 q+ 12:29:04 ... Someone who files a Comment neds to go back to see how each individual Comment was handled. 12:29:22 caribou: When an Issue is made, that's just editorial, the editors are trusted to handle it well. 12:29:43 q+ 12:29:51 ... The theory is stronger-consideration issues would go to the discussion group. 12:30:42 elianaP: Are there other options for this? Such as filing Issues proactively? 12:31:18 TallTed: Editorial often means "Does not change normativity." 12:31:45 ... The job of the Editor is not to serve as a magazine editor. It is to serve as the implementor of the working-group's discussions on how things should be done. 12:32:16 ... Timing of deployment of these decisions is left to the editor. Time crunch at the end is an option. 12:33:21 ... Turtle does not have as much prettifying support in scripting for these documents. So, we're at manual implementation for these style matters. 12:34:10 q+ 12:34:31 ack me 12:35:46 nicholascar: I think I agree much with TallTed's workflow here. Most of TallTed's comments on a recent PR were actionable, I resolved them. Some weren't, but in at least one case, I postponed one to an Issue, and marked the comment Resolved, delegated to separate Issue. 12:35:49 (and things that take a bit of time now should not be problematic now when we have flexible timing, vs things that take a bit of time at the end of process when we're under the gun) 12:35:54 q+ 12:36:19 HolgerK: Ok, I can try working like this. Will make a separate ticket for tabbing property values. 12:36:50 q- 12:39:58 I have made the request to generate https://www.w3.org/2025/08/25-data-shapes-minutes.html TallTed 12:59:35 Zakim, end meeting 12:59:35 As of this point the attendees have been TallTed, HolgerK, elianaP, AndyS, ajnelson-nist, simonstey, edmond, mgberg, YoucTagh, SimonW, Carine, DavidHabgood, fsasaki, Robert 12:59:38 RRSAgent, please draft minutes 12:59:40 I have made the request to generate https://www.w3.org/2025/08/25-data-shapes-minutes.html Zakim 12:59:45 I am happy to have been of service, elianaP; please remember to excuse RRSAgent. Goodbye 12:59:45 Zakim has left #data-shapes 12:59:52 RRSAgent, excuse us 12:59:52 I see no action items