13:58:28 RRSAgent has joined #lws 13:58:32 logging to https://www.w3.org/2026/04/13-lws-irc 13:58:40 eBremer has joined #lws 13:58:45 zakim, start meeting 13:58:45 RRSAgent, make logs Public 13:58:47 please title this meeting ("meeting: ..."), acoburn 13:58:54 meeting: Linked Web Storage 13:59:02 rrsagent, make minutes 13:59:03 I have made the request to generate https://www.w3.org/2026/04/13-lws-minutes.html acoburn 13:59:25 previous meeting: https://www.w3.org/2026/04/06-lws-minutes.html 13:59:36 next meeting: https://www.w3.org/2026/04/20-lws-minutes.html 13:59:37 present+ 13:59:44 termontwouter has joined #lws 13:59:48 chair: ericP 13:59:48 gibsonf1 has joined #lws 13:59:55 present+ 14:00:17 present_ 14:00:20 present+ 14:00:50 present+ 14:00:53 scribe+ 14:01:15 present+ 14:02:22 TallTed has joined #lws 14:02:34 Zakim, take up agendaum 1 14:02:34 'um\ 1' does not match any agenda item, ericP 14:02:39 Zakim, take up agendum 1 14:02:39 agendum 1 -- Introductions and announcements -- taken up [from agendabot] 14:02:43 bendm has joined #lws 14:03:05 laurens has joined #lws 14:03:18 present+ 14:03:31 present+ 14:04:15 ericP: welcome and introductions 14:05:09 jeswr has joined #lws 14:05:13 jeswr+ 14:05:17 present+ 14:05:37 jeswr: running inperson lws wg f2f 14:05:40 present+ 14:05:50 ... hackathon in parallel 27th and 28th 14:06:03 .. if you want to help mentor...contact Jesse 14:06:05 q+ to ask about remote joining information 14:06:16 ack next 14:06:17 acoburn, you wanted to ask about remote joining information 14:06:18 ... symposium Thursday and Friday of that week 14:06:36 acoburn: people can join remotely for f2f 14:06:46 RazaN has joined #lws 14:06:50 ryey has joined #lws 14:06:53 present+ 14:06:56 present+ 14:07:01 ... pchampin if you can add to the agenda the zoom link 14:07:15 q? 14:07:16 pchampin: i cant take of that 14:07:21 I arrive to London on 25th, is there an option to join as an observer? 14:07:28 ericP: any other annoucements or intros? 14:07:38 Zakim, take up next agendum 14:07:38 agendum 2 -- Agenda for F2F #121 -- taken up [from agendabot] 14:08:07 ... agenda in a PR#121 14:08:07 https://github.com/w3c/PR/issues/121 -> PR#121 14:08:32 acoburn: high priority things I want to front load 14:09:10 ... starting point. keep in mind ordering for remote people 14:09:28 ... we wont be getting to TR status in time...so rechartering... 14:09:34 ... what will that process look like 14:09:38 ... goals? scope? 14:09:50 ... dont want to take up whole day 14:09:54 -> https://www.w3.org/2024/09/linked-web-storage-wg-charter.html Linked Web Storage Working Group Charter 14:10:04 ... we have recommendation track which need significant work to make sure they all land 14:10:27 ... Access requests, Type Index, Notifications, test suite 14:10:42 ... a lot of feed back on ARs. some on TI 14:10:55 ... I would like to move all of them along 14:11:12 ...we will need a test suite. implementations not part of this 14:11:28 ... ODI has been taking some of this work on 14:11:44 -> https://github.com/w3c/lws-protocol/pull/106 LWS Access Requests and Access Grants 14:11:45 https://github.com/w3c/lws-protocol/pull/106 -> Pull Request 106 Add editors draft for LWS Access Requests and Access Grants (by acoburn) 14:11:49 ... those are things we have committee to that need work 14:12:06 ... couple of items in our recommendation track that aren't fully clarified 14:12:12 ... spend some time working through those 14:12:22 -> https://github.com/w3c/lws-protocol/pull/115 Type Index Section 14:12:23 https://github.com/w3c/lws-protocol/pull/115 -> Pull Request 115 add Type Index Section (by ebremer) 14:12:32 AZ has joined #lws 14:12:37 present+ 14:12:39 ... some non-rec documents that need some attention 14:12:43 present+ 14:12:51 ... primer, best practices... 14:13:00 ... a solid compatibility document 14:13:26 ... dont necessarily need them right away, possibly push that out a bit further 14:13:39 -> https://w3c.github.io/lws-ucs/spec/ UC&R doc 14:13:52 ... PR just a proposal. any suggestions changes? 14:13:57 q? 14:14:33 q+ 14:14:36 ... anything remote people would prefer to see morning or afternoon? 14:14:44 ack next 14:15:11 ryey: I'll be joinung froim UTC +8. I will be able to attend mornings and early afternoon 14:15:26 ... thats restriction from my side 14:15:40 ... interested in AR, TI, notification for the first day 14:15:44 q+ 14:16:26 acoburn: would like to timebox feature section to an hour 14:17:01 ... Rui we dont need to restrict and can adjust things around as needed 14:17:02 ack next 14:17:28 ggibsonf1: I'm california time 14:17:35 ... after lunch will be easier 14:17:55 ... what happens when container is both container and data resource 14:18:19 ... what happens when a get is done on it? 14:18:49 q+ to suggest to move terminology/container vs resource first 14:18:55 acoburn: I do think this is terminology. Can they be bother? is a disjoint set? My understanding it is, but it will require a group discussion 14:19:21 s/ggibsonf1/gibsonf1 14:19:34 ack next 14:19:35 bendm, you wanted to suggest to move terminology/container vs resource first 14:19:52 bendm: suggestion to move this point to first day after lunch 14:20:01 ... since it affects many things 14:21:28 ryey: TI after lunch is fine 14:21:57 I have made the request to generate https://www.w3.org/2026/04/13-lws-minutes.html TallTed 14:22:03 acoburn: we can adjust on the day as well 14:22:09 ... just dont want to miss anything major 14:22:37 Zakim, take up next agendum 14:22:37 agendum 3 -- Vocabularies #112 -- taken up [from agendabot] 14:22:54 s/present_// 14:22:56 s/jeswr+// 14:23:07 https://github.com/w3c/lws-protocol/pull/112 14:23:07 https://github.com/w3c/lws-protocol/pull/112 -> MERGED Pull Request 112 feat(vocab): setup yml2vocab for managing the LWS vocabulary and json-ld context (by laurensdeb) [editorial] 14:23:13 laurens: vocabularies relates to PR and took the liberty to merge it #112 14:23:14 https://github.com/w3c/lws-protocol/pull/112 -> MERGED Pull Request 112 feat(vocab): setup yml2vocab for managing the LWS vocabulary and json-ld context (by laurensdeb) [editorial] 14:23:26 ... non-normative document for LWS 14:23:36 ... creates as turtle and json-ld. all non-normative 14:23:52 ... update to github actions for how gh pages have been built 14:24:06 ... we have context and vocabulary now being built 14:24:09 q+ 14:24:15 i/welcome and introductions/agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20260413T100000/ 14:24:19 ack next 14:24:20 ack pchampin 14:24:26 I have made the request to generate https://www.w3.org/2026/04/13-lws-minutes.html TallTed 14:24:32 ... we need a WG decision to publish that non-normative vocab and context 14:24:57 pchampin: we need decision to publish the HTML doc or rendering for some reason 14:25:06 laurens: will remove from my proposal 14:25:25 PROPOSAL: The LWS WG shall publish the non-normative LWS Vocabularies as FPWD documents: https://w3c.github.io/lws-protocol/lws-10-vocab/ 14:25:35 ... we weill have straw poll on the publication of LWS voab HTML 14:25:41 s/for some reason/. For some reason the TTL and JSON-LD context artifacts are not covered by the W3C process. 14:25:50 +1 14:25:51 +1 14:25:51 +1 14:25:53 +1 14:25:54 +1 14:25:56 +1 14:25:57 +1 14:25:59 +1 14:26:07 q+ 14:26:14 +1 14:26:30 +1 14:26:38 +0 (I need to take a closer look to it) 14:26:48 tallted: resolution should include a date stamp on the documents 14:26:48 ack next 14:27:20 RESOLVED: The LWS WG shall publish the non-normative LWS Vocabularies as draft note documents in their state as of 2026-04-13: https://w3c.github.io/lws-protocol/lws-10-vocab/index.html 14:27:20 q+ 14:27:20 ericP: anyone else want to vote? issues? 14:27:31 ack next 14:27:47 bendm: I have tech questions I will put in as an issue 14:28:20 ... voc adds the domain of LWS container to activity streams ...doesnt feel clean to me... 14:28:35 q+ 14:28:44 laurens: have discussion to reference or include a choice we will have to make 14:28:55 ack next 14:29:18 pchampin: yaml to vocab tool developed in-house by Ivan Hermann from W3C 14:29:26 ... we can ask for adjustments 14:29:36 s/https://w3c.github.io/lws-protocol/lws-10-vocab/index.html/https://w3c.github.io/lws-protocol/lws10-vocab/index.html/ 14:29:49 s/Hermann/Herman 14:30:03 Zakim, take up next agendum 14:30:03 agendum 4 -- Access Request Proposal #106: Open questions -- taken up [from agendabot] 14:31:09 acoburn: any questions? 14:31:18 nevermind my comment on vocab, I manually interpreted the yaml file as if it would create the actual rdfs:domain triples in the ttl file, but it doesn't, so my issue is no longer valid 14:32:21 acoburn: should we remove 7.3 Endpoint Authorization? 14:32:42 ... will go into security guidance anything. dont know if we actually need 7.3 14:32:51 +1 to remove, I prefer best practices than prematurely limiting future usage 14:32:56 +1 to removal 14:33:00 +1 to removal 14:35:13 acoburn: 6.2 actions - in core of lws we define read, modify, create, delete... 14:35:23 ... jesse suggested adding append 14:35:23 q+ to ask about target 14:36:06 acoburn: I would suggest not unless its just bytes 14:36:16 ... would require deeper parsing for other types 14:36:25 dmitriz has joined #lws 14:36:36 ack next 14:36:37 gibsonf, you wanted to ask about target 14:36:44 ... doesnt mean you can never have append 14:37:19 gibsonf1: on the target, your including the URI for the resource and also having to tell the resource what kind it is. not understanding... 14:39:10 gibson: easier to indicate the relation youre looking for rather than having to force 14:39:18 s/gibson/gibsonf1 14:39:59 acoburn: idea is that when you give access to container but everything inside the container 14:40:07 ... how they work in many other contexts 14:40:41 ... if you give access to individual resources, it wouldn't include anything else 14:41:47 gibsonf1: in the storage approach, you would give access to full hierarchy, but consider the that someone could have rights to the container but not the children 14:42:05 acoburn: suggest commenting on PR to accommodate what you are saying 14:42:31 ... Ben brought up a couple of times in the reviews but has not been fully integrated here... 14:42:38 q+ 14:42:46 ... hard connection between JSON-LD and this data model 14:42:55 ... there could be other serializations 14:42:58 ack next 14:43:17 tallted: Ive heard and read in past couple of days, people dont want to do X because it will break stuff 14:43:36 ... implementations that call themselves LWS aren't really 14:44:07 ... I want to be really careful that we dont say we cant do X, which is the best idea because it will break stuff 14:44:09 Zakim, take up next agendum 14:44:09 agendum 5 -- Type Index Proposal #115: Clarification of scope -- taken up [from agendabot] 14:44:28 scrbe+ 14:44:33 scribe+ 14:44:41 s/scrbe+/ 14:44:51 eBremer: current proposal PR#115 14:44:51 https://github.com/w3c/PR/issues/115 -> PR#115 14:45:09 https://github.com/w3c/lws-protocol/pull/115 14:45:09 https://github.com/w3c/lws-protocol/pull/115 -> Pull Request 115 add Type Index Section (by ebremer) 14:45:16 ... happy to change the name to distinguish from the SOLID Type Index implementation 14:45:34 s|https://github.com/w3c/PR/issues/115 -> PR#115| 14:45:40 ... this index is a union of what you're allowed to see based on your credentials 14:46:08 ... deref gives you the URIs and the total items (that you're allowed to see) 14:46:40 gibsonf1 suggested loosening to allow non-HTTP-link-headers 14:47:25 gibsonf1, i disagreed on the ordering. you suggested search before types but I view types as orientation that then informs search 14:47:40 q+ to ask that everyone familiarize themselves with this and other proposals before the f2f mtg 14:47:58 s/gibsonf1, i disagreed on the ordering. you suggested search before types but I view types as orientation that then informs search/ebremer: gibsonf1, i disagreed on the ordering. you suggested search before types but I view types as orientation that then informs search 14:48:11 gibsonf1: we have search without types 14:48:40 ... we could query types but just add other query parms to ehance to their desired expressivity 14:48:52 eBremer: sure; happy with extensibility 14:49:12 ack next 14:49:13 acoburn, you wanted to ask that everyone familiarize themselves with this and other proposals before the f2f mtg 14:49:48 acoburn: we want to reach consensus at the f2f to please read up in the next two weeks 14:50:08 acoburn: please familiarize yourself with the proposals so we can come to consensus at the f2f 14:50:11 ... we should know if we're going to take these features to CR 14:50:20 q? 14:50:30 scribe- 14:50:34 scribe+ 14:50:46 zakim, take up next agendum 14:50:46 agendum 6 -- Issue triage -- taken up [from agendabot] 14:52:10 acoburn: please review issues and respond if you have any thoughts 14:52:47 RRSAgent, please draft minutes 14:52:48 I have made the request to generate https://www.w3.org/2026/04/13-lws-minutes.html ericP 14:52:58 RRSAgent, make minutes 14:53:00 I have made the request to generate https://www.w3.org/2026/04/13-lws-minutes.html pchampin 14:53:53 ericP has left #lws 14:55:08 ACTION: pchampin will add a video link to the f2f calendar pages 14:55:16 Cannot create action. Validation failed. Maybe pchampin will add a video link is not a valid user for w3c/lws-protocol? 14:58:38 acoburn has left #lws