13:56:24 <RRSAgent> RRSAgent has joined #lws
13:56:28 <RRSAgent> logging to https://www.w3.org/2025/07/07-lws-irc
13:58:16 <kaefer3000> kaefer3000 has joined #lws
13:58:28 <acoburn> zakim, start meeting
13:58:28 <Zakim> RRSAgent, make logs Public
13:58:30 <Zakim> please title this meeting ("meeting: ..."), acoburn
13:58:34 <acoburn> meeting: Linked Web Storage
13:58:52 <acoburn> agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20250707T100000/#agenda
13:58:53 <agendabot> clear agenda
13:58:53 <agendabot> agenda+ Introduction and announcements
13:58:53 <agendabot> agenda+ Use cases & requirements update
13:58:53 <agendabot> agenda+ Research topics
13:59:00 <acoburn> chair: ericP
13:59:10 <eBremer> eBremer has joined #lws
13:59:12 <acoburn> RRSAgent, make minutes
13:59:13 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/07-lws-minutes.html acoburn
13:59:21 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/07-lws-minutes.html TallTed
13:59:36 <pchampin> present+
13:59:38 <ericP> present+
13:59:45 <acoburn> present+
13:59:48 <ericP> chair: ericP
13:59:49 <kaefer3000> present+
14:00:00 <TallTed> previous meeting: https://www.w3.org/2025/06/30-lws-minutes.html
14:00:00 <TallTed> next meeting: https://www.w3.org/2025/07/14-lws-minutes.html
14:00:00 <eBremer> present+
14:00:02 <TallTed> present+
14:00:22 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/07-lws-minutes.html TallTed
14:00:49 <uvdsl> present+
14:01:00 <ericP> scribe: kaefer3000
14:01:55 <gibsonf1> gibsonf1 has joined #lws
14:01:59 <ericP> topic: Introduction and announcements
14:02:03 <gibsonf1> present+
14:02:17 <bendm> bendm has joined #lws
14:02:23 <bendm> present+
14:03:11 <RazaN> RazaN has joined #lws
14:03:30 <Monsecom> Monsecom has joined #lws
14:03:53 <RazaN> present+
14:04:20 <jeswr> jeswr has joined #lws
14:04:45 <kaefer3000> ericP: Are there new introductions?
14:05:17 <kaefer3000> bengo: is new, was working on IPFS, is a Solid fan
14:05:29 <kaefer3000> ...has been working with dimitriz didcoop
14:05:38 <kaefer3000> ...experienced from the SocialWeb WG
14:05:58 <kaefer3000> s/didcoop/on didcoop/
14:06:09 <Monsecom> present+
14:06:24 <pchampin> q+
14:06:49 <ryey> ryey has joined #lws
14:07:05 <ryey> present+
14:07:29 <kaefer3000> joaquin: professor, has been working in formal methods, multimedia, data spaces protocols, cloud, blockchain
14:07:35 <jeswr> present+
14:07:43 <jeswr> q+
14:07:43 <bengo> bengo has joined #lws
14:07:46 <ryey> scribe?
14:08:08 <kaefer3000> pchampin: reports from a Geneva event
14:08:38 <kaefer3000> ...jeswr organised a session on Solid and LWS
14:08:46 <kaefer3000> ...the event brought a few people to LWS
14:08:46 <pchampin> https://globaldigitalcollaboration.org/
14:08:50 <jsalvachua> jsalvachua has joined #lws
14:09:21 <bengo> https://globaldigitalcollaboration.org/agenda?day=2025-07-02
14:09:33 <kaefer3000> jeswr: session on Solid + LWS - discussion on whether solid can be storage for web-based credentials
14:09:37 <ericP> ack next
14:09:40 <ericP> ack next
14:09:45 <ericP> ack next
14:09:55 <acoburn> RRSAgent, make minutes
14:09:56 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/07-lws-minutes.html acoburn
14:10:42 <kaefer3000> s/joaquin/jsalvachua/
14:11:18 <jeswr> Link to slides from Global Digital Collaboration session on LWS: https://docs.google.com/presentation/d/1nxeDF0BOv_-UyRreaL2gVPKlXVc_R5jJq3wq2AcWrV0/edit?usp=sharing
14:12:16 <jeswr> Link to hackMD from Global Digital Collaboration https://hackmd.io/oUdcr40QRN-SGzUWVObbzw
14:10:12 <ericP> topic: Use cases & requirements update
14:11:27 <pchampin> q+
14:11:30 <kaefer3000> eBremer: PRs on user stories have been merged, there are PRs being reviewed, feel free to provide comments
14:11:45 <ericP> ack next
14:12:14 <kaefer3000> pchampin: First draft of use-cases document published
14:12:17 <kaefer3000> ...auto-publication system fixed
14:12:29 <kaefer3000> ...there are HTML validation issues to be fixed
14:12:50 <kaefer3000> ...such that merged PRs get automatically published as new version
14:12:58 <kaefer3000> ...on w3.org/TR/
14:13:24 <acoburn> q+ to ask about expected timeframe for merging requirements PR
14:13:44 <bengo> Could someone link to FPWD of Use Cases? ty
14:14:00 <ericp> subtopic: w3c/lws-ucs#170
14:14:01 <ericP> ack next
04:14:33 <ericP> q+ to introduce https://github.com/w3c/lws-ucs/pull/169 -> + rationale for out-of-scope and deprioritized requirements
14:14:50 <kaefer3000>  acoburn: eBremer opened PR about this, can we agree on a timeframe?
14:15:03 <kaefer3000> eBremer: plan: to be merged by the end of the week
14:15:26 <kaefer3000> ericP: anyone who says this is unrealistic?
14:15:45 <ericP> ack next
14:15:50 <kaefer3000> TallTed: this is plenty of time
14:14:33 <ericP> subtopic: https://github.com/w3c/lws-ucs/pull/169 -> + rationale for out-of-scope and deprioritized requirements
14:16:22 <kaefer3000> ericP: it's my expectation to have UCs that include requirements that are out-of-scope or de-prioritised
14:17:07 <acoburn> bengo: current working draft of use cases doc at https://w3c.github.io/lws-ucs/spec/. Once Echidna is fixed it will be at https://www.w3.org/TR/lws-ucs/
14:17:12 <bendm> +1, diff LGTM
14:17:25 <bengo> acoburn tysm
14:18:01 <jsalvachua0> jsalvachua0 has joined #lws
14:18:08 <uvdsl> q+
14:18:14 <kaefer3000> ...reasons:  1) there may be upcoming technologies that provide, 2) UCs that may inform development of upcoming technologies, 3) UCs that help non-tech people build an understanding, 4) avoidance of duplicate UCs
14:18:16 <ericP> ack next
14:18:39 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/07-lws-minutes.html TallTed
14:18:45 <kaefer3000> uvdsl: how do we determine which use-case is in or out of scope?
14:20:04 <kaefer3000> ericP: the decision is editorial, there will be annotations about which UC is deemed out-of-scope
14:20:55 <kaefer3000> acoburn: at this stage of the process, we want to be comprehensive. Some UCs will have requirements that are out-of-scope.
14:21:11 <kaefer3000> ...imagine a UC has 5 requirements. 2 in-scope, 3 out-of-scope.
14:21:43 <kaefer3000> ...if the 2 requirements become too burdensome, we could drop the UC entirely
14:22:25 <kaefer3000> uvdsl: how is the process exactly?
14:22:54 <kaefer3000> ...when is the time to go through the list, when will be annotated?
14:23:18 <kaefer3000> ericP: there is no specific timeline
14:23:36 <kaefer3000> ...during prioritisation
14:24:02 <acoburn> q?
14:24:40 <kaefer3000> ericP: if you want to do a pass, that's possible
14:25:49 <acoburn> zakim, open agendum 3
14:25:49 <Zakim> agendum 3 -- Research topics -- taken up [from agendabot]
14:26:22 <kaefer3000> jeswr: email on topics sent on the mailing list
14:26:34 <kaefer3000> ...jackson and ben have answered
14:26:58 <ericP> ericP has joined #lws
14:27:09 <kaefer3000> jackson: will work on it after Tuesday
14:27:39 <kaefer3000> bendm: his lab has been worked on authorisation and consent
14:27:46 <kaefer3000> ...they could contribute
14:28:33 <kaefer3000> jeswr: at the moment it's about pointing to the state-of-the-art
14:29:04 <ryey> q+
14:29:09 <kaefer3000> ...consent + ODRL - please do not invest too much time here, as it will be likely out-of-scope
14:29:55 <kaefer3000> joaquin: is working on ODRL for data spaces
14:29:59 <ericP> ack next
14:30:00 <acoburn> ack next
14:30:01 <kaefer3000> ...could provide review
14:30:16 <kaefer3000> rui: usage control is probably too far
14:30:48 <kaefer3000> ...access control - should we collect practices closely to the Solid stack (WAC, ...) or also things farther away?
14:30:49 <jeswr> q+
14:30:56 <kaefer3000> ...there are other paradigms of access control
04:31:05 <ericP> q?
14:31:07 <ericP> ack next
14:31:20 <bendm> q+ to ask how we practically go about it: all input is managed via the lead, given it's a wiki?
14:31:25 <hadrian> hadrian has joined #lws
14:31:30 <hadrian> present+
14:31:56 <kaefer3000> jeswr: the UC document will define what is in scope; there are input documents in the charter
14:32:22 <kaefer3000> ...we should also be looking at how GDrive and AWS S3 are doing it
14:32:30 <kaefer3000> ...not just Solid prior art
14:33:10 <kaefer3000> rui: most services use role-based access control, there is also attribute-based access control - should they get included?
14:33:34 <kaefer3000> jeswr: we should not doing it academically here
14:33:53 <bendm> q+ to ask about practicalities, but also about policy language
14:33:57 <jsalvachua> jsalvachua has joined #lws
14:33:58 <kaefer3000> ...if there is a nice categorisation into RBAC, ... fine
14:34:02 <jsalvachua> we are considering Relation based (going from Google Zanzibar and Amazon Cedar)
14:34:08 <jeswr> https://github.com/w3c/lws-protocol/wiki/Research-Topic-Template-(using-Authorisation-as-an-example)
14:34:12 <jsalvachua> and joining it to an Odrl Profile
14:34:26 <jsalvachua> ReBac
14:34:41 <kaefer3000> rui: Mastodon has access control personal, site-only, global
04:35:07 <kaefer3000> jeswr: provide pointers, don't make the wiki massive
14:35:14 <ericP> q?
14:35:27 <jsalvachua> we are using OpenFGA as engine for policy evaluation
14:35:35 <jsalvachua> I will check how it match here
14:36:03 <kaefer3000> bendm: what's the process? Given it's a wiki, should pointers be sent via email to the page lead who fits it in?
14:36:18 <kaefer3000> jeswr: put them straight into the wiki
14:36:20 <ericP> q?
14:36:25 <ericP> ack next
14:36:28 <ryey> q+
14:36:30 <bengo> wrt Mastodon, it is completely different than what is required of an ActivityPub Conformant Server because it does not implement AP C2S
14:36:35 <ericP> ack next
14:37:05 <kaefer3000> rui: in the wiki, not everyone has access
14:37:06 <kaefer3000> ...how to get access?
14:37:23 <kaefer3000> ericP: you should be able to login
04:38:20 <kaefer3000> ...join a help channel on IRC: #sysreq
14:38:48 <kaefer3000> q+
14:38:55 <acoburn> q+ to talk about wiki access
14:38:59 <ericP> scribe+
14:39:01 <ericP> ack next
14:39:19 <dmitriz> re wiki: haha, 'group membership gives access to resource' use case is hard! :)
14:39:24 <ericP> kaefer3000: why "Research Topics"?
14:39:33 <kaefer3000> scribe+
14:39:43 <ericP> jeswr: i'll rename to "Prior Art"
14:39:46 <ericP> scribe-
14:39:54 <ericP> ack next
14:40:43 <kaefer3000> acoburn: was looking at the GitHub configuration. Edititing is restricted to people with push access, ie. editors and chairs
14:41:08 <kaefer3000> ...if we un-click that button, we don't know if ordinary GitHub users can edit the wiki
14:41:36 <kaefer3000> ericP: let's unclick and if we get undesired content, revert
14:41:53 <kaefer3000> ...please test it
14:41:55 <bendm> I can edit! :)
14:42:21 <ericP> agenda?
14:42:50 <acoburn> RRSAgent, make minutes
14:42:51 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/07-lws-minutes.html acoburn
14:43:11 <kaefer3000> ericP: we are through the agenda, is there any other business?
14:43:53 <kaefer3000> ericP: closes the meeting
14:43:58 <pchampin> RRSAgent, make minutes
14:44:00 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/07-lws-minutes.html pchampin
14:51:32 <pchampin> RRSAgent, bye
14:51:32 <RRSAgent> I see no action items