14:57:36 RRSAgent has joined #lws 14:57:40 logging to https://www.w3.org/2025/01/27-lws-irc 14:57:44 Zakim has joined #lws 14:58:00 agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20250127T100000/ 14:58:01 clear agenda 14:58:01 agenda+ Introductions and announcements 14:58:01 agenda+ Pending -> action items https://github.com/w3c/lws-protocol/issues?q=is%3Aopen+is%3Aissue+label%3Aaction 14:58:01 agenda+ Use cases update 14:58:02 agenda+ Consensus on shared context -> issues https://github.com/w3c/lws-ucs/issues 14:58:46 zakim, start meeting 14:58:46 RRSAgent, make logs Public 14:58:48 topic: Linked Web Storage WG -- 2025-01-27 14:58:48 please title this meeting ("meeting: ..."), acoburn 14:58:52 eBremer has joined #lws 14:58:55 meeting: Linked Web Storage 14:58:59 present+ 14:59:09 present+ 14:59:24 present+ 15:00:10 present+ 15:01:40 present+ 15:02:04 kaefer3000 has joined #lws 15:02:08 bendm has joined #lws 15:02:30 hadrian has joined #lws 15:02:49 present+ 15:03:02 -> https://github.com/w3c/lws-protocol/wiki/Scribe-list Scribe list 15:03:38 chair: laurens 15:04:06 scribe+ 15:04:26 thelounge has joined #lws 15:04:38 present+ 15:04:39 present+ 15:04:40 present+ 15:04:42 RRSAgent, draft minutes 15:04:43 I have made the request to generate https://www.w3.org/2025/01/27-lws-minutes.html TallTed 15:04:50 present+ 15:05:03 laurens: any annoucement? 15:05:16 ryey has joined #lws 15:05:23 present+ 15:05:24 pchampin: W3C is organising a breakout day in March 15:05:45 ... halfway between 2 TPACs 15:05:53 ... we could organise a session of LWS 15:05:55 previous meeting: https://www.w3.org/2025/01/20-lws-minutes.html 15:05:55 next meeting: https://www.w3.org/2025/02/03-lws-minutes.html 15:05:56 https://github.com/w3c/breakouts-day-2025/ 15:06:25 ... it is not an obligation 15:06:55 scribe+ 15:07:01 scribe: AZ 15:07:29 scribe- 15:07:43 q? 15:07:59 I have made the request to generate https://www.w3.org/2025/01/27-lws-minutes.html TallTed 15:08:14 balessan has joined #lws 15:08:14 Zakim, open next item 15:08:14 agendum 1 -- Introductions and announcements -- taken up [from agendabot] 15:08:18 laurens: there are 2 action items 15:08:26 Zakim, close item 1 15:08:26 agendum 1, Introductions and announcements, closed 15:08:27 I see 3 items remaining on the agenda; the next one is 15:08:27 2. Pending -> action items https://github.com/w3c/lws-protocol/issues?q=is%3Aopen+is%3Aissue+label%3Aaction [from agendabot] 15:08:35 ... assigned to Hadrian 15:08:38 zakim, open next item 15:08:38 agendum 2 -- Pending -> action items https://github.com/w3c/lws-protocol/issues?q=is%3Aopen+is%3Aissue+label%3Aaction -- taken up [from agendabot] 15:08:49 I have made the request to generate https://www.w3.org/2025/01/27-lws-minutes.html TallTed 15:08:55 hadrian: the labels are done 15:09:09 uvdsl has joined #lws 15:09:49 ... the one that needs discussion today is basic storage 117 15:10:09 see https://github.com/w3c/lws-ucs/issues/117 15:10:10 https://github.com/w3c/lws-ucs/issues/117 -> Issue 117 Basic Storage Context (by hzbarcea) [needs-discussion] 15:11:05 ... the "needs discussion" must be curated continuously until we have list of requirements 15:11:05 q+ 15:11:11 present+ 15:11:31 Zakim, open next item 15:11:31 I see a speaker queue remaining and respectfully decline to close this agendum, laurens 15:11:37 q? 15:11:46 hadrian: I went through issues and started getting requirements 15:12:07 ... many UCs have a context assumed 15:13:07 ... for every issue raised, things related to the context should not be discussed in the issue 15:13:16 ... the discussion should be more focused 15:13:27 ... I'm now working on a second batch 15:13:52 ... there's something related to local storage 15:13:56 q+ 15:14:29 ... there are things about query engines, about processing 15:14:46 q? 15:14:51 I have made the request to generate https://www.w3.org/2025/01/27-lws-minutes.html TallTed 15:14:57 ack csarven 15:15:13 csarven: I'd like to understand the Basic Storage Context 15:15:40 ... some of them are new UCs and some of them are new, relative to issue 117 15:16:19 ... not sure if these (which one?) are strong UCs as UCs 15:16:21 Anyhting of significane should have a URI: https://www.w3.org/DesignIssues/Axioms.html#Universality2 15:16:55 ... if you give everything of significance a URI 15:17:23 ... this is more something of a requirement 15:17:38 q? 15:17:40 ... I'm a bit confused about what we do with basic storage 15:18:25 ... can you elaborate more Hadrian? 15:18:45 hadrian: you say that these UCs are more like requirements 15:18:56 ... true, I'll gather requirements from these UCs 15:19:17 ... I'll distill these UCs into finer grained ICs 15:19:23 s/ICs/UCs 15:20:09 ... I'll take all these things into one basic storage context (?) 15:20:18 ericP has joined #lws 15:20:58 csarven: if the intention is to have the context be related to requirements, don't use the UC template 15:21:08 +1 to sarven's point 15:21:22 hadrian: I understand your point 15:21:25 q+ 15:21:52 q? 15:22:07 ... at smoe point we talked about identity of storage end users (?) 15:22:18 q? 15:22:21 ack kaefer 15:22:42 kaefer3000: don't call requirements UCs 15:23:08 ... it's important that they are linked back to chich UC they come 15:23:30 hadrian: we did not discuss yet how we capture requirements 15:24:28 laurens: there is an action to be done, that is to have a template for requirements, or context 15:24:35 "proto-requirement"? 15:24:36 +1 15:24:37 hadrian: I support that 15:24:42 ACTION: hadrian to define a requirements template for the lws-ucs repository 15:24:50 Created -> action #13 https://github.com/w3c/lws-protocol/issues/13 15:24:51 present+ ericP 15:25:09 hadrian: the requirements should be linked to the UCs 15:25:27 ... should then the UC issue closed? 15:25:27 q? 15:25:30 ack laurens 15:25:36 laurens: it's how I understand it yes 15:26:14 q? 15:26:33 hadrian: the problematic UCs should be phrased as requirements not user stories 15:27:12 laurens: is there anything to add on this topic 15:27:31 laurens: AOB? 15:27:46 topic: Basic storage context (https://github.com/w3c/lws-ucs/issues/117) 15:27:47 https://github.com/w3c/lws-ucs/issues/117 -> Issue 117 Basic Storage Context (by hzbarcea) [needs-discussion] 15:28:20 q+ 15:28:37 hadrian: we can discuss the issue on basic storage context 15:28:57 ack ericP 15:29:05 ericP: need clarification 15:29:35 ... do we split the UCs into ??? 15:30:13 laurens: iti s best to have this kind of discussion asynchronously 15:31:24 https://github.com/w3c/lws-ucs/issues/110 15:31:25 https://github.com/w3c/lws-ucs/issues/110 -> Issue 110 [UC] Ability to split or aggregate storages (by hzbarcea) [usecase] [review] 15:31:34 ericP: the question was about whether to splitting pods 15:32:23 laurens: if you haven't additional issues to discuss now, we can continue asynchronously 15:32:34 laurens: maybe one issue of interest is 108 15:32:59 https://github.com/w3c/lws-ucs/issues/108 15:33:00 https://github.com/w3c/lws-ucs/issues/108 -> Issue 108 [UC] Uniquely identify storage globally (by hzbarcea) [usecase] [uc-identity] [review] 15:33:27 laurens: I'm looking for solutiosn to this 15:33:53 hadrian: you can have part of URL that is globally unique 15:34:31 laurens: we don't need to discuss solutions yet but talk in terms of requirements 15:34:34 q? 15:34:49 q+ 15:35:11 laurens: will leave comments to github issues 15:35:13 ack csarven 15:36:14 q+ 15:36:17 csarven: if I look at issue 112 for instance, with linked data glasses, I don't se an issue to meet the use case 15:36:51 ... but different people will see them in different ways 15:37:21 hadrian: in this issue, this is about being able to move to a different storage provider 15:37:28 q? 15:37:28 q+ 15:38:00 laurens: what you said csarven is related to acceptance requirements 15:38:01 ack laurens 15:38:07 ack uvdsl 15:38:28 uvdsl: could hadrian add explanation to the issues 15:38:55 ... maybe just a few bullet points so we can understand better 15:39:06 s/meet the use case/meet the use case. UC's Acceptance Criteria would help to determine what might be needed on an atomic level. So, e.g., moving from one provider to another and what that might entail. 15:39:15 q? 15:39:43 laurens: we can help in clarifying the issues 15:40:25 hadrian: commenting on the issues help in clarifying the UC or issue 15:40:40 ... so please respond to the Github issues 15:40:59 topic: Identity & WebID 15:41:11 hadrian: what do we do about WebID in this group? 15:41:28 ... this is a key decision to be made 15:41:51 laurens: this requires more elaborate discussion than we can have today 15:42:02 ... but we can talk about it a bit 15:42:08 ... it relates to the requirements 15:42:08 q+ 15:42:20 q? 15:42:25 ack pchampin 15:42:30 ... what's the group member's opinion about WebID? 15:42:52 pchampin: previously DID specified the DID document 15:43:06 ... that has an intersection with WebID 15:43:09 +1 15:43:12 https://www.w3.org/TR/controller-document/ 15:43:23 ... we need to explore this in liaison with DID WG 15:43:41 ... some part of DID work was moved to VC WG 15:44:13 q+ 15:44:28 ... I agree that this is something that will need further discussion and clearer discussion once requirements are in 15:44:32 q? 15:44:36 ack csarven 15:45:06 csarven: we had a discussion in December about scope 15:45:18 ... to know what's acceptable to take on or update 15:45:32 ... say we need authorisation 15:45:37 +1 pchampain, i wasn't aware of it, very helpful, I agree with the path you suggest 15:45:41 ... as a feature 15:46:08 ... whether a solution must depend on a spec, we don't necessarily need to have a spec covering all of it 15:47:06 ... e.g. WebID does not have to cover all aspects, all UCs 15:47:23 q+ 15:47:40 q+ 15:47:57 ack laurens 15:48:17 ... we have too many UCs to address that cannot be covered entirely with existing spec 15:49:07 ack acoburn 15:49:31 acoburn: there is no way that we will have a single spec that covers all the UCs 15:49:42 ... we have to prioritise the requirements 15:49:51 ... then we can look for solutions 15:49:56 +1 15:50:11 q? 15:50:20 ... at the moment, discussing the merits of solution A vs solution B is not very productive 15:50:53 laurens: no other business, then we can ajourn 15:50:56 rrsagent, make minutes 15:50:58 I have made the request to generate https://www.w3.org/2025/01/27-lws-minutes.html acoburn 15:51:44 scribenick: AZ 15:51:49 RRSAgent, make minutes 15:51:51 I have made the request to generate https://www.w3.org/2025/01/27-lws-minutes.html pchampin 15:52:25 acoburn has left #lws 15:52:52 i!laurens: any annoucement!scribe+ AZ 15:52:55 RRSAgent, make minutes 15:52:56 I have made the request to generate https://www.w3.org/2025/01/27-lws-minutes.html pchampin 15:54:21 s/i!laurens: any annoucement!scribe+ AZ/ 15:54:31 i/laurens: any annoucement/scribe+ AZ 15:54:35 RRSAgent, make minutes 15:54:36 I have made the request to generate https://www.w3.org/2025/01/27-lws-minutes.html pchampin 15:56:05 RRSAgent, bye 15:56:05 I see 1 open action item saved in https://www.w3.org/2025/01/27-lws-actions.rdf : 15:56:05 ACTION: hadrian to define a requirements template for the lws-ucs repository [1] 15:56:05 recorded in https://www.w3.org/2025/01/27-lws-irc#T15-24-42