Issues

• Right now the spec assumes everything a client talks to sits inside a storage

  w3c/lws-protocol#304 · Filter by author ebremer opened on Nov 11, 2026

• ODRL usage with LWS Access Profile

  access-request
  w3c/lws-protocol#303 · Filter by author acoburn opened on Nov 10, 2026
  5

• [lws-authn-openid] Confusing "should" in Security Consideration Section

  w3c/lws-protocol#297 · Filter by author pchampin opened on Nov 3, 2026
  2

• Is the "Protected Resource Metadata" too granular?

  w3c/lws-protocol#296 · Filter by author pchampin opened on Nov 2, 2026
  2

• draft a spec sketch with the mechanics of the metadata aux resource

  action
  w3c/lws-protocol#295 · Filter by author ghurlbot opened on Oct 29, 2026
  

• take on integrating schemata into the LWS protocol, supported by pchampin

  action
  w3c/lws-protocol#294 · Filter by author ghurlbot opened on Oct 29, 2026
  

• look into adding deterministic identifiers on requirements

  action
  w3c/lws-protocol#292 · Filter by author ghurlbot opened on Oct 29, 2026
  1

  

• propose a mechanism for discovering the supported version of the LWS protocol.

  action
  w3c/lws-protocol#291 · Filter by author ghurlbot opened on Oct 29, 2026
  

• draft a proposal for SSI-CID with HTTPS identifier and OpenID connect as an authentication baseline.

  action
  w3c/lws-protocol#290 · Filter by author ghurlbot opened on Oct 29, 2026
  

• reach out to christoph and wouter on group based access control

  action
  w3c/lws-protocol#289 · Filter by author ghurlbot opened on Oct 29, 2026
  13

  

• progress on the Portability Consideration section with jeremycaine

  action
  w3c/lws-protocol#288 · Filter by author ghurlbot opened on Oct 27, 2026
  

• write up clearer claim that remote contexts should avoided as a mechanism rather than eg. cached.

  action
  w3c/lws-protocol#287 · Filter by author ghurlbot opened on Oct 27, 2026
  1

  

• Implementation Report with passing/failing tests

  w3c/lws-protocol#286 · Filter by author jeswr opened on Oct 27, 2026
  2

• Making requirements clearer

  w3c/lws-protocol#285 · Filter by author jeswr opened on Oct 27, 2026
  1

  

• human readable labels for storage resources?

  w3c/lws-protocol#282 · Filter by author pchampin opened on Oct 23, 2026
  1

• Access request/grant to container members

  w3c/lws-protocol#280 · Filter by author bourgeoa opened on Oct 21, 2026
  1

• LWS and FedCM integration

  authentication
  w3c/lws-protocol#279 · Filter by author acoburn opened on Oct 20, 2026
  5

• Agent identity scheme requirements

  w3c/lws-protocol#278 · Filter by author acoburn opened on Oct 19, 2026
  4

• Re-evaluate application/lws+json Media Type

  w3c/lws-protocol#276 · Filter by author acoburn opened on Oct 16, 2026
  4

• Re-evaluate application/lws+cid Media Type

  w3c/lws-protocol#267 · Filter by author acoburn opened on Oct 12, 2026
  6

• Authentication Suite MUST-implement requirements

  authentication
  w3c/lws-protocol#266 · Filter by author acoburn opened on Oct 12, 2026
  5

• follow-up on how we could indicate sections where implementer feedback is wanted.

  action
  w3c/lws-protocol#262 · Filter by author ghurlbot opened on Oct 5, 2026
  4

  

• Implementors guidance on ETags

  w3c/lws-protocol#245 · Filter by author jeswr opened on Sep 14, 2026
  5

  

• clarify ETag requirements for Containers (recursively)

  action
  w3c/lws-protocol#240 · Filter by author ghurlbot opened on Aug 31, 2026
  6

  

• follow up on changelogs for the specification

  documentationeditorialpr-exists
  w3c/lws-protocol#239 · Filter by author ghurlbot opened on Aug 31, 2026
  2