15:06:41 RRSAgent has joined #lws 15:06:46 logging to https://www.w3.org/2024/11/04-lws-irc 15:06:55 Zakim has joined #lws 15:07:03 zakim, start meeting 15:07:03 RRSAgent, make logs Public 15:07:05 please title this meeting ("meeting: ..."), acoburn 15:07:11 meeting: Linked Web Storage 15:07:15 present+ 15:07:16 present+ 15:07:16 present+ 15:07:21 present+ 15:07:22 present + 15:07:25 present+ 15:07:26 present+ 15:07:27 present+ 15:07:30 present+ 15:07:37 present+ 15:07:58 present+ 15:08:00 jeswr has joined #lws 15:08:03 agenda+ meeting cadence 15:08:05 present+ 15:08:14 agenda+ Use Cases template 15:08:47 AZ has joined #lws 15:08:51 present+ 15:08:55 q+ 15:09:00 q+ 15:09:04 topic: Introductions 15:09:06 ack kaefer3000 15:09:06 TallTed has joined #lws 15:09:30 q+ 15:09:32 present+ 15:09:40 ryey has joined #lws 15:09:51 present+ 15:09:55 kaefer3000: I'm Tobias, I'm at Karsleruhe 15:10:17 scribe+ 15:10:20 ... i'm part of the SoLid symposium steering committe 15:10:21 ack uvdsl 15:10:47 s/Karsleruhe/Karlsruhe/ 15:11:04 uvdsl: I'm Christoph 15:11:24 ... I'm a student of Tobias 15:11:49 RRSAgent, draft minutes 15:11:50 I have made the request to generate https://www.w3.org/2024/11/04-lws-minutes.html acoburn 15:12:22 q? 15:12:32 ack kaefer 15:12:42 present+ 15:12:44 TallTed has changed the topic to: Linked Web Storage WG -- 2024-11-04 agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20241104T100000/ 15:12:48 ack timbl 15:13:11 timbl: I'm Tim Berners-Lee 15:13:22 ... working on making the Web R/W 15:13:51 ... day job is with Inrupt but spend lots of time in open source world, e.g. SoLid OS 15:13:56 chair: acoburn 15:14:06 topic: Meeting cadence 15:14:08 Zakim, next agendu 15:14:08 I don't understand 'next agendu', ericP 15:14:46 Zakim, next agenda? 15:14:46 I don't understand your question, timbl. 15:14:58 acoburn: last week we talked about the meeting cadence. 15:15:08 ... The charter says "every 2 weeks", but we have a lot to do in 2 years. 15:15:29 Proposed: The lws working group will meet weekly rather than every other week. 15:15:44 ... We have an initial vote on the proposal above last week, but didn't conclude that vote. 15:15:50 q+ 15:15:59 ack csarven 15:16:29 Yes i think that is good idea to meet everyweek 15:16:41 q+ 15:16:50 ack pchampin 15:17:51 pchampin: reading last minutes, i saw the possibility of changing the time to aid folks in other timezones 15:18:24 ... perhaps we can have an Asia-Pacific-friendly meetring every now and then 15:18:34 csarven: +1 to pchampin's suggestion, that address my concerns. 15:18:48 ... +1 also to a weekly meeting. 15:19:24 ... Processwise, it would be good to make an announcement to the participants to ask if they want another time. 15:19:47 q+ 15:19:48 ... If only the people in the meeting are making the decisions, this may not be representative. 15:19:55 ack jacoscaz 15:20:25 jacoscaz: +1 to what csarven said. 15:20:38 ... In my case, I should be able to join most meeting, but I can't guarantee that I can attend them all. 15:20:52 ... It would be good to give people who can't attend an additional week to comment on decisions. 15:21:03 cpn has joined #lws 15:21:06 present- Have to run now =) Thanks. 15:21:37 acoburn: as a matter of principle, when big decisions are taken, there need to be a provision for async participants as well. 15:21:53 ... We need to strike a balance between being reactive and giving time for sufficient feedback. 15:22:29 Proposed: The lws working group will meet weekly rather than every other week, with one meeting per month to accommodate different timezones 15:22:39 ... I think there are 2 parts to the proposal, let me revise it. 15:23:18 ... the proposal is to meet weekly, with a monthly slot, TBD, to accomodate other timezones 15:23:20 +1 15:23:23 +1 15:23:30 +1 15:23:33 +1 15:23:38 +1 15:23:39 +1 15:23:39 +1 15:23:40 +1 15:23:41 +1 15:23:43 +1 15:23:44 +1 15:24:33 acoburn: could someone send a message to the group to ask for input on an alternative timezone? 15:24:39 ... meetings would still be on monday. 15:25:14 jacoscaz: hesitating because this is my 1st WG, but I'm happy to do it. 15:25:30 RESOLVED: The lws working group will meet weekly rather than every other week, with one meeting per month to accommodate different timezones 15:25:45 a+ 15:25:47 q+ 15:25:50 s/a+/ 15:26:17 ACTION: jacoscaz to send email to lws list asking about alternative times 15:26:25 ack next 15:26:54 pchampin: re managment of actions, we could invite another bot which records actions as GH issues. 15:27:07 ... we're using it in RDF-star 15:27:36 ... currenlty, the only recording of actions is in the minutes 15:27:52 +1 create github issues for each action (for tracking) 15:27:56 acoburn: right now we are not doing a lot of work in github, but I can see more value in that later. 15:28:04 ... let's defer this decision. 15:28:22 Zakim, next agendum 15:28:22 agendum 1 -- meeting cadence -- taken up [from ericP] 15:28:24 topic: Use cases template 15:28:27 Zakim, next agendum 15:28:27 agendum 1 was just opened, ericP 15:28:45 Zakim, close item 1 15:28:45 agendum 1, meeting cadence, closed 15:28:46 I see 1 item remaining on the agenda: 15:28:46 2. Use Cases template [from ericP] 15:28:54 Zakim, next agendum 15:28:54 agendum 2 -- Use Cases template -- taken up [from ericP] 15:28:55 Zakim, next item 15:28:56 agendum 2 was just opened, TallTed 15:30:08 -> https://github.com/w3c/lws-ucs/pull/5 Use Cases Template 15:30:18 s|agendum 1 -- meeting cadence -- taken up [from ericP]| 15:30:35 acoburn: Laurens has created a use-case template, there were a few comments. 15:31:12 ... csarven has a review as well, but he had to leave already. Other comments? 15:31:49 timbl: I have a general question. Is there only one level when we are talking about use-cases? 15:32:10 ... Some use-cases are "you should be able to use the protocol for medical data", very high level. 15:32:24 q+ to talk about LDP Use Cases 15:32:55 ... Other uses-cases involved scenarios, persona... Different characteristics. 15:33:13 ack ericP 15:33:13 ericP, you wanted to talk about LDP Use Cases 15:33:17 ... What level are those use-cases expected to be? 15:33:19 s/uses-cases/use-cases 15:33:43 ericP: I wanted to bring up the Linked Data Platform use-cases. 15:34:09 ... because a) they are also about a protocol, and b) they provide a base. 15:34:55 ... They contain a high level business case, then a more technical part from which requirements can be extracted. 15:35:35 timbl: can a business case be any level? Or you start high level, then get into details. 15:36:07 acoburn: TallTed, thanks also for your comments. 15:36:22 ... We are not going to get this merged today, but I would like people to look at this. 15:36:40 ... We don't need this template to be perfect, but as use-cases come on, I would like them to have some kind of consistent structure. 15:37:04 ... Imposing some kind of structure would improve the quality of use-cases. 15:37:15 q+ 15:37:22 ack ericP 15:37:25 q+ to propose drafting a couple examples 15:37:29 ack ericP 15:37:29 ericP, you wanted to propose drafting a couple examples 15:38:01 ericP: rather than looking at the template, it might be easier to use it to encode some of the TPAC use-cases, 15:38:23 ... then let the editors of the UC document adjust the template. 15:38:43 ... And let them approve the PR when they feel it is good. 15:39:22 acoburn: please write a proposal. 15:40:23 PROPOSAL: let Adrian Z approve pr#5 and/or modify the Use Case template as he (or other editors) see fit 15:40:37 s/Adrian/Hadrian/ 15:41:00 +1 15:41:14 +1 15:41:15 +1 15:41:16 +1 15:41:18 +1 15:41:22 +1 15:41:32 +1 15:41:34 +1 15:41:45 +1 15:41:49 +1 15:41:51 +1 15:41:57 +1 15:42:13 +1 15:42:15 +1 15:42:22 RESOLVED: let Adrian Z approve pr#5 and/or modify the Use Case template as he (or other editors) see fit 15:42:31 s/Adrian/Hadrian/ 15:43:06 acoburn: that does it for what we have on the agenda; with a weekly cadence, our next meeting would be next monday. 15:43:22 present- 15:43:45 ... Please note that the US is out of DST, so the meeting time will remain consistent from one week to the other now (unlikes last week). 15:43:51 ... Any closing remarks? 15:43:56 [crickets] 15:43:59 Zakim, please draft minutes 15:43:59 I don't understand 'please draft minutes', ericP 15:44:07 ... Then we can adjourn early. Thanks everyone for joining. 15:44:08 RRSAgent, please draft minutes 15:44:10 I have made the request to generate https://www.w3.org/2024/11/04-lws-minutes.html ericP 15:44:33 jacoscaz has left #lws 15:44:34 hadrian has left #lws 15:45:31 s|agendum 2 -- Use Cases template -- taken up [from ericP]| 15:45:55 RRSAgent, make minutes 15:45:56 I have made the request to generate https://www.w3.org/2024/11/04-lws-minutes.html pchampin 15:46:59 jacoscaz has joined #lws 15:47:24 i|I'm Tobias|scribe+ eric 15:47:29 i|I'm Tobias|scribe+ ericP 15:47:36 RRSAgent, make minutes 15:47:37 I have made the request to generate https://www.w3.org/2024/11/04-lws-minutes.html pchampin 15:49:22 agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20241104T100000/#agenda 15:49:23 pchampin, sorry, I did not recognize any agenda in https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20241104T100000/#agenda 15:50:24 RRSAgent, make minutes 15:50:26 I have made the request to generate https://www.w3.org/2024/11/04-lws-minutes.html pchampin 16:56:30 acoburn has joined #lws 16:56:53 acoburn has left #lws 17:08:39 timbl has joined #lws 21:53:44 timbl has joined #lws