14:41:16 RRSAgent has joined #lws 14:41:21 logging to https://www.w3.org/2026/01/19-lws-irc 14:41:22 Zakim has joined #lws 14:42:15 zakim, start meeting 14:42:15 RRSAgent, make logs Public 14:42:17 please title this meeting ("meeting: ..."), acoburn 14:42:23 meeting: Linked Web Storage 14:44:38 acoburn has changed the topic to: Linked Web Storage - 19 January, 2026 - https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20260119T100000/ 14:48:05 agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20260119T100000/#agenda 14:48:05 clear agenda 14:48:05 agenda+ Introductions & Announcements 14:48:05 agenda+ CRUD & Metadata PR -> #37 https://github.com/w3c/lws-protocol/pull/37 14:48:05 agenda+ Storage Description Resource PR -> #53 https://github.com/w3c/lws-protocol/pull/53 14:48:06 agenda+ "End User Credential" terminology 14:48:08 agenda+ Other -> open PRs https://github.com/w3c/lws-protocol/pulls 14:59:12 eBremer has joined #lws 15:00:00 present+ 15:00:31 gibsonf1 has joined #lws 15:00:40 present+ 15:00:40 present+ 15:01:28 present+ 15:02:00 AZ has joined #lws 15:02:22 Luke has joined #lws 15:03:35 present+ 15:03:44 present+ 15:04:02 Zakim, next agendum 15:04:02 agendum 1 -- Introductions & Announcements -- taken up [from agendabot] 15:04:44 scribe+ 15:04:54 ericP: new introductions 15:05:23 Luke: I am from IBM 15:05:33 Zakim, next agendum 15:05:33 agendum 2 -- CRUD & Metadata PR -> #37 https://github.com/w3c/lws-protocol/pull/37 -- taken up [from agendabot] 15:05:42 s/I am from IBM/I am new and I am from IBM 15:05:48 ryey has joined #lws 15:05:58 present+ 15:06:01 ericP: we have a PR that has been here for a while 15:06:45 eBremer: this has been there for a while but people asked for more time on it 15:06:59 ... we could swap some sections and other edits 15:07:02 q+ 15:07:14 ... and then other things could be done with other PRs 15:07:30 ack next 15:09:09 pchampin: I think reversing sec. 7 & 8 would be an improvement 15:09:30 ... I have a few remarks but don't want to stand in the way so let us go ahead 15:09:47 ... it would have been better to split this PR into pieces 15:10:10 ... so we could discuss things separately and it would have been easier 15:10:20 ... in the future, let us work on smaller PRs 15:10:30 PROPOSED: merge PR#37 after eBremer has swapped sections 7 and 8 15:10:31 Issue 37 not found 15:11:26 PROPOSED: merge PR#37 after eBremer has swapped sections 7 and 8 15:11:26 Issue 37 not found 15:11:51 https://github.com/w3c/lws-protocol/pull/37 15:11:52 https://github.com/w3c/lws-protocol/pull/37 -> Pull Request 37 Initial CRUD with proposed metadata handling (by ebremer) 15:12:04 +0 (I don't know enough about the PR) 15:12:06 +1 15:12:06 +1 15:12:07 +1 15:12:09 +1 15:12:10 +1 15:12:21 +0.5 15:12:56 +1 15:13:10 APPROVED: merge PR#37 after eBremer has swapped sections 7 and 8 15:13:43 eBremer: I'll do the changes tomorrow and merge 15:13:51 zakim, next agendum 15:13:51 agendum 3 -- Storage Description Resource PR -> #53 https://github.com/w3c/lws-protocol/pull/53 -- taken up [from agendabot] 15:15:01 acoburn: it is about describing capabilities of storages, and endpoints that extend capabilities 15:15:23 ... discovery mechanisms fit into this PR 15:15:50 ... we can go ahead and vote on accepting the PR 15:15:55 q+ to ask about uri 15:16:14 ack next 15:16:15 gibsonf, you wanted to ask about uri 15:17:10 gibsonf1: there is the issue of semantic URI for the storage itself different from the root container of the storage 15:17:33 q+ 15:17:41 acoburn: I think it is an important issue but it is orthogonal 15:17:48 ack next 15:17:51 pchampin: agree it is orthogonal 15:18:44 ... with caveat that the example uses certain URIs and we need to make them better to avoid confusion 15:19:15 acoburn: I can record an issue for this 15:19:19 ACTION: acoburn to add root-vs-subject issue to text merged from #53 15:19:26 Created -> action #54 https://github.com/w3c/lws-protocol/issues/54 15:19:34 PROPOSED: merge PR#53 - Storage Description Resource 15:19:35 Issue 53 not found 15:19:39 +1 15:19:40 +1 15:19:41 s/for this/for the identification issue of storage vs root container 15:19:43 +1 15:19:46 +1 15:19:46 +1 15:20:03 +0.5 15:20:07 +1 15:20:20 APPROVED: merge PR#53 - Storage Description Resource 15:20:33 +0.5 15:20:45 Zakim, next agendum 15:20:45 agendum 4 -- "End User Credential" terminology -- taken up [from agendabot] 15:21:00 acoburn: will work on it this week 15:21:48 [acoburn shows the draft for LWS Protocol on his screen] 15:22:05 Agent? 15:22:11 acoburn: I would liek to propose changing the terminology on user credential 15:22:19 s/liek/like 15:22:40 acoburn: I'd like to call it "Identification credential" 15:23:19 ... I thought about alternatives: "Agent credential" but may evoke AI Agents 15:23:19 +1 "Identification credential" 15:24:04 +1 on "Authentication Credential" 15:24:21 s/"Identification credential"/"Authentication Credential" 15:24:23 s/"Identification credential"/"Authentication credential" 15:24:51 +1 15:24:52 matthieu has joined #lws 15:24:59 I have made the request to generate https://www.w3.org/2026/01/19-lws-minutes.html pchampin 15:25:14 acoburn: if there is further discussion, we can have it in the PR request 15:25:14 zakim, take up next agendum 15:25:14 agendum 5 -- Other -> open PRs https://github.com/w3c/lws-protocol/pulls -- taken up [from agendabot] 15:27:33 acoburn: the 2 issues that begin with "consolidate" related auth and ident have been open for a while 15:27:46 ... they are more editorial than the previous 2 we takled about 15:28:12 ... the last one is about terminology 15:28:28 ... to clarify what we mean when we say URI 15:29:15 q+ to ask about EUC naming 15:29:20 ... if you have objections, please comment otherwise it will be merged by the editors 15:29:32 ack next 15:29:33 elf-pavlik, you wanted to ask about EUC naming 15:29:37 https://www.ietf.org/archive/id/draft-ietf-oauth-identity-assertion-authz-grant-01.html#name-identity-assertion-jwt-auth 15:30:49 elf-pavlik: in the doc I provide above, there is something about identity and authorization, do we have the same? 15:31:23 acoburn: the intention is that something like this would be supported 15:32:33 acoburn: we could say this is identity assertion (where we say "end-suer credential" in hte draft) 15:33:09 elf-pavlik: [something related to the webid group] 15:35:10 q+ to comment on * token 15:35:31 scribe+ 15:35:39 dmitriz: the question is... 15:35:47 dmitriz: the term "identify assertion" would prevent us from using zcap 15:35:53 s/dmitriz: the question is...// 15:35:57 scribe- 15:36:32 acoburn: going back to the credential discussion of previous PRs 15:36:44 ... we have different options 15:37:02 ... we could go for identity assertion 15:37:28 ... but could include other things 15:37:40 +1 on including more detail in discussion of "Authentication Credential" 15:38:30 elf-pavlik: we use "token" and we should be cautious 15:39:19 ... if it's focused on authentication, then authentication credition is good 15:39:24 q? 15:39:28 q- 15:39:40 +1 to more detail 15:39:56 acoburn: I will use authentical credential and I will add more details 15:40:26 q+ to ask about Membership with WAC 15:40:49 ericP: back to the pending PRs 15:41:38 elf-pavlik: related to PR31, we have a planning roadmap for SEG(?) 15:41:56 ... this is related to access control policiies 15:42:14 ... there are different approaches taken one related to delegation 15:42:26 ... there is a use case related to autonoumous groups 15:42:30 ack next 15:42:31 gibsonf, you wanted to ask about Membership with WAC 15:43:03 q+ to ask about twinpod 15:43:08 gibsonf1: the issue that CSS(?) has is not being able to tell access 15:44:07 ... on twinpot(?) we do ??? [something related to access control on triples] 15:44:44 dmitriz: a confusion is coming up often and we need to fix ot 15:44:47 s/ot/it 15:45:48 gibsonf1: single triple has its own URI, metadata, etc 15:46:10 ... if you make a group private, what happens? 15:46:42 this conversation is following up discussion about this PR https://github.com/w3c/lws-protocol/pull/31 15:46:43 https://github.com/w3c/lws-protocol/pull/31 -> Pull Request 31 prior-art: group based access policies (by elf-pavlik) 15:47:32 dmitriz: if you make a URI private (ie you don't give right to access the URI) 15:47:49 q+ to say there may be a confusion between same-server vs group-on-any-server 15:47:50 can't perform LWS Read operation, would that be clear? 15:48:05 q- yielding to ericP 15:48:21 gibsonf1: server delivers data in funciton of access right, but it must access the data to know about access rights 15:48:46 q- dmitriz clarified it 15:48:50 dmitriz: there are two separate servers, for data and authorization 15:50:37 [acoburn drawing a diagram on screen shared to explain the issue] 15:51:09 elf-pavlik has joined #lws 15:51:27 gibsonf1: how can you separate these things? how would this work? 15:52:20 acoburn: the issue is, there are two server models, a 1-server model and a 2-server model 15:52:27 q+ to mention MANDAT requirements 15:52:44 ack next 15:52:45 elf-pavlik, you wanted to ask about twinpod and to mention MANDAT requirements 15:52:50 ... a 2-server model can be specificied but it must implementable 15:52:51 q+ 15:53:08 q- 15:53:50 elf-pavlik: there are cases in prior work where there are different needs on disclosing info 15:54:12 ack next 15:54:24 ... in the CG group (fedid?) we plan to do a workshop to discuss cases 15:54:32 Solid CG 15:54:48 gibsonf1: how would you do search in that scenario? 15:55:25 ... ie if there is a different server for auth 15:55:41 ... it would be very slow 15:55:50 https://github.com/w3c-cg/solid/issues/60 15:55:51 https://github.com/w3c-cg/solid/issues/60 -> Issue 60 [Proposed Work Item]: Organization, Group, Team, Role support in Solid (by elf-pavlik) 15:56:24 ... who has a 2-server model? 15:56:44 acoburn: in ACP we chose to have an ACP matcher act as a group 15:57:01 q+ re SAI teams/roles 15:57:24 ... but it enforces all the ACP and auth rules to be in one place 15:57:30 ack next\ 15:57:39 q? 15:57:44 ack next 15:57:45 elf-pavlik, you wanted to discuss SAI teams/roles 15:58:19 elf-pavlik: depending if you have something where you can use delegation 15:58:47 ADJOURNED 15:59:17 elf-pavlik has joined #lws 15:59:22 use case https://github.com/w3c/lws-ucs/issues/104 15:59:23 https://github.com/w3c/lws-ucs/issues/104 -> Issue 104 [UC] Access delegation by autonomous groups/organizations (by elf-pavlik) [triage] [usecase] 16:00:36 RRSAgent, make minutes 16:00:37 I have made the request to generate https://www.w3.org/2026/01/19-lws-minutes.html pchampin 16:01:11 present+ dmitriz, elf-pavlik, ericP 16:01:12 RRSAgent, make minutes 16:01:14 I have made the request to generate https://www.w3.org/2026/01/19-lws-minutes.html pchampin 16:02:13 https://github.com/w3c/lws-protocol/pull/37 -> Pull Request 37 Initial CRUD with proposed metadata handling (by ebremer) 16:03:48 rrsagent, make minutes 16:03:50 I have made the request to generate https://www.w3.org/2026/01/19-lws-minutes.html acoburn 16:04:02 Issue 37 not found 16:04:57 acoburn has left #lws