Linked Web Storage Working Group - Activity
No matches.
TR publications
-
3 documents published.
-
LWS 1.0 Authentication Suite: SAML 2.0 published as a Working Draft. History of LWS 1.0 Authentication Suite: SAML 2.0
-
Linked Web Storage Protocol 1.0 published twice as a Working Draft. History of Linked Web Storage Protocol 1.0
-
Past meetings
GitHub
w3c/lws-protocol
-
2 issues opened.
-
[lws-authn-openid] Confusing "should" in Security Consideration Section w3c/lws-protocol#297, by @pchampin.
-
Is the "Protected Resource Metadata" too granular? w3c/lws-protocol#296, by @pchampin.
-
-
2 issues received 4 new comments.
-
Is the "Protected Resource Metadata" too granular? w3c/lws-protocol#296 (2 comments by @acoburn, @elf-pavlik)
-
Implementation Report with passing/falinig tests w3c/lws-protocol#286 (2 comments by @elf-pavlik, @TallTed)
-
-
4 pull requests opened.
-
Use invalid_token in the token validation example w3c/lws-protocol#301, by @JinDX.
-
Fix todo link for preview w3c/lws-protocol#300, by @acoburn.
-
Extract an LWS OAuth profile from the core specification w3c/lws-protocol#299, by @acoburn.
-
Fix the remaining outer Signature closing tag in the SAML example w3c/lws-protocol#298, by @JinDX.
-
-
3 pull requests merged.
-
Fix the remaining outer Signature closing tag in the SAML example w3c/lws-protocol#298.
-
replace static section references with respec dynamic references w3c/lws-protocol#281.
-
Fix todo link for preview w3c/lws-protocol#300.
-
-
2 pull requests received 8 new comments.
-
LWS 1.0 Notification Suite: HTTP Streaming w3c/lws-protocol#284 (6 comments by @benfrancis, @elf-pavlik)
-
Fix the remaining outer Signature closing tag in the SAML example w3c/lws-protocol#298 (2 comments by @acoburn, @w3cbot)
-
w3c/lws-ucs
-
1 issue opened.
-
[UC] An AI agent acting for a person reads and writes their storage w3c/lws-ucs#266, by @maxchop.
-
-
33 pull requests opened.
-
[Class 4] Requirement Profile Interaction UI: delete w3c/lws-ucs#265, by @jeswr.
-
[Class 4] Requirement Legal Basis Enforcement: delete w3c/lws-ucs#264, by @jeswr.
-
[Class 4] Requirement Timeseries Data Support: delete w3c/lws-ucs#263, by @jeswr.
-
[Class 4] Requirement Auditable Trail: delete w3c/lws-ucs#262, by @jeswr.
-
[Class 4] Requirement Personal Data Projection: delete w3c/lws-ucs#261, by @jeswr.
-
[Class 4] Requirement Inbox: delete w3c/lws-ucs#260, by @jeswr.
-
[Class 4] Requirement Resource Versioning: delete w3c/lws-ucs#259, by @jeswr.
-
[Class 4] Requirement Federated Data Queries: delete w3c/lws-ucs#258, by @jeswr.
-
[Class 4] Requirement End-to-End Encryption: delete w3c/lws-ucs#257, by @jeswr.
-
[Class 4] Requirement Loose Coupling of Underlying Protocols: delete w3c/lws-ucs#256, by @jeswr.
-
[Class 4] Requirement View-Based Data Sharing: delete w3c/lws-ucs#255, by @jeswr.
-
[Class 4] Requirement Scalable Storage Management: delete w3c/lws-ucs#254, by @jeswr.
-
[Class 4] Requirement Transfer of Control: delete w3c/lws-ucs#253, by @jeswr.
-
[Class 4] Requirement Data Integrity Verification: delete w3c/lws-ucs#252, by @jeswr.
-
[Class 4] Requirement Profile Management: delete w3c/lws-ucs#251, by @jeswr.
-
[Class 4] Requirement Delegation of Access Rights: delete w3c/lws-ucs#250, by @jeswr.
-
[Class 4] Requirement Serialization Format: delete w3c/lws-ucs#249, by @jeswr.
-
[Class 4] Requirement Delegation of Control: delete w3c/lws-ucs#248, by @jeswr.
-
[Class 4] Requirement Group-Based Access Control: delete w3c/lws-ucs#247, by @jeswr.
-
[Class 4] Requirement Resource Metadata: add w3c/lws-ucs#246, by @jeswr.
-
[Class 3] Requirement Concurrency and Offline Use: modify w3c/lws-ucs#245, by @jeswr.
-
[Class 3] Requirement Performance and Scalability: modify w3c/lws-ucs#244, by @jeswr.
-
[Class 4] Requirement Search and Query: modify w3c/lws-ucs#243, by @jeswr.
-
[Class 4] Requirement Storage Portability: modify w3c/lws-ucs#242, by @jeswr.
-
[Class 3] Requirement Service Independence and Trust: modify w3c/lws-ucs#241, by @jeswr.
-
[Class 3] Requirement Discovery: modify w3c/lws-ucs#240, by @jeswr.
-
[Class 3] Requirement Storage Control: modify w3c/lws-ucs#239, by @jeswr.
-
[Class 3] Requirement Notifications: modify w3c/lws-ucs#238, by @jeswr.
-
[Class 3] Requirement Identification: modify w3c/lws-ucs#237, by @jeswr.
-
[Class 3] Requirement Authentication: modify w3c/lws-ucs#236, by @jeswr.
-
[Class 4] Requirement Access Requests and Grants: modify w3c/lws-ucs#235, by @jeswr.
-
[Class 3] Requirement Authorization: modify w3c/lws-ucs#234, by @jeswr.
-
[Class 3] Requirement Create, Read, Update, Delete: modify w3c/lws-ucs#233, by @jeswr.
-
TR publications
-
9 documents published.
-
Linked Web Storage Protocol 1.0 published 6 times as a Working Draft. History of Linked Web Storage Protocol 1.0
-
LWS 1.0 Authentication Suite: OpenID Connect published as a Working Draft. History of LWS 1.0 Authentication Suite: OpenID Connect
-
LWS 1.0 Authentication Suite: SAML 2.0 published as a Working Draft. History of LWS 1.0 Authentication Suite: SAML 2.0
-
Past meetings
-
9 meetings.
GitHub
w3c/lws-protocol
-
19 issues opened.
-
draft a spec sketch with the mechanics of the metadata aux resource w3c/lws-protocol#295, by @ghurlbot.
-
take on integrating schemata into the LWS protocol, supported by pchampin w3c/lws-protocol#294, by @ghurlbot.
-
look into adding deterministic identifiers on requirements w3c/lws-protocol#292, by @ghurlbot.
-
propose a mechanism for discovering the supported version of the LWS protocol. w3c/lws-protocol#291, by @ghurlbot.
-
reach out to christoph and wouter on group based access control w3c/lws-protocol#289, by @ghurlbot.
-
progress on the Portability Consideration section with jeremycaine w3c/lws-protocol#288, by @ghurlbot.
-
write up clearer claim that remote contexts should avoided as a mechanism rather than eg. cached. w3c/lws-protocol#287, by @ghurlbot.
-
Implementation Report with passing/falinig tests w3c/lws-protocol#286, by @jeswr.
-
Making requirements clearer w3c/lws-protocol#285, by @jeswr.
-
human readable labels for storage resources? w3c/lws-protocol#282, by @pchampin.
-
Access request/grant to container members w3c/lws-protocol#280, by @bourgeoa.
-
LWS and FedCM integration w3c/lws-protocol#279, by @acoburn.
-
Agent identity scheme requirements w3c/lws-protocol#278, by @acoburn.
-
Re-evaluate application/lws+json Media Type w3c/lws-protocol#276, by @acoburn.
-
application/lws+cid Media Type w3c/lws-protocol#267, by @acoburn.
-
Authentication Suite MUST-implement requirements w3c/lws-protocol#266, by @acoburn.
-
follow-up on how we could indicate sections where implementer feedback is wanted. w3c/lws-protocol#262, by @ghurlbot.
-
expires - JSON-LD context conflict between CID and LWS w3c/lws-protocol#258, by @elf-pavlik.
-
-
15 issues closed.
-
TPAC 2026 Agenda w3c/lws-protocol#176.
-
Define how storage implementations can declare their URI semantics w3c/lws-protocol#247.
-
LWS mapping to ODRL w3c/lws-protocol#196.
-
Improving Access Requests and Access Grants w3c/lws-protocol#230.
-
Handling of the case where a resource is created in a non-existent container w3c/lws-protocol#87.
-
Ensure the OIDC suite affords for FedCM w3c/lws-protocol#200.
-
make PR extracting move of resources between containers w3c/lws-protocol#148.
-
expires - JSON-LD context conflict between CID and LWS w3c/lws-protocol#258.
-
Remove requirement that `application/ld+json` and `application/json` must be framed w3c/lws-protocol#246.
-
Confirm "Agent" is defined in the terminology section w3c/lws-protocol#195.
-
Define GET/POST fallback for Search / Type Index when QUERY is unavailable w3c/lws-protocol#205.
-
`realm` and `aud` assumptions w3c/lws-protocol#236.
-
Reconsider supported media types for JSON updates w3c/lws-protocol#254.
-
Does LWS10-AUTHN-SSI-CID already include LWS10-AUTHN-SSI-DID-KEY? w3c/lws-protocol#141.
-
-
34 issues received 73 new comments.
-
application/lws+cid Media Type w3c/lws-protocol#267 (6 comments by @acoburn, @elf-pavlik, @TallTed, @uvdsl)
-
Authentication Suite MUST-implement requirements w3c/lws-protocol#266 (5 comments by @acoburn, @elf-pavlik, @TallTed, @uvdsl)
-
expires - JSON-LD context conflict between CID and LWS w3c/lws-protocol#258 (5 comments by @acoburn, @elf-pavlik, @pchampin)
-
Agent identity scheme requirements w3c/lws-protocol#278 (4 comments by @acoburn, @elf-pavlik, @uvdsl)
-
Re-evaluate application/lws+json Media Type w3c/lws-protocol#276 (4 comments by @acoburn, @elf-pavlik, @pchampin, @uvdsl)
-
follow-up on how we could indicate sections where implementer feedback is wanted. w3c/lws-protocol#262 (4 comments by @elf-pavlik, @TallTed)
-
Distinguish between Container and Data Resources in the metadata w3c/lws-protocol#90 (2 comments by @acoburn)
-
Create reference explaining consistent use of HTTP content-type, profile, prefer etc. w3c/lws-protocol#188 (2 comments by @msporny, @termontwouter)
-
look into adding deterministic identifiers on requirements w3c/lws-protocol#292 (1 comment by @elf-pavlik)
-
write up clearer claim that remote contexts should avoided as a mechanism rather than eg. cached. w3c/lws-protocol#287 (1 comment by @elf-pavlik)
-
Define how storage implementations can declare their URI semantics w3c/lws-protocol#247 (1 comment by @acoburn)
-
Remove requirement that `application/ld+json` and `application/json` must be framed w3c/lws-protocol#246 (1 comment by @jeswr)
-
Potential issues of Authorization Request and Grant being source of truth w3c/lws-protocol#144 (1 comment by @acoburn)
-
Editorial: Link to Authentication Suites from the Core Protocol? w3c/lws-protocol#193 (1 comment by @acoburn)
-
Define GET/POST fallback for Search / Type Index when QUERY is unavailable w3c/lws-protocol#205 (1 comment by @ebremer)
-
Does LWS10-AUTHN-SSI-CID already include LWS10-AUTHN-SSI-DID-KEY? w3c/lws-protocol#141 (1 comment by @acoburn)
-
-
18 pull requests opened.
-
Small editorial fixes w3c/lws-protocol#293, by @ebremer.
-
LWS 1.0 Notification Suite: HTTP Streaming w3c/lws-protocol#284, by @elf-pavlik.
-
replace static section references with respec dynamic references w3c/lws-protocol#281, by @pchampin.
-
Describe media type and size per representation in container listings w3c/lws-protocol#277, by @ebremer.
-
Editorial and consistency updates to LWS Core w3c/lws-protocol#275, by @wonsuk73.
-
Fix vocabulary w3c/lws-protocol#274, by @pchampin.
-
Editorial updates to the Self-signed Identity using Controlled Identifiers Authentication Suite w3c/lws-protocol#273, by @wonsuk73.
-
Fix XML syntax issues in the SAML authentication credential example w3c/lws-protocol#271, by @wonsuk73.
-
Improve OpenID terminology and wording in LWS 1.0 Authentication Suite: OpenID Connect spec w3c/lws-protocol#269, by @wonsuk73.
-
Align URI terminology in notification vocabulary descriptions w3c/lws-protocol#268, by @wonsuk73.
-
Fix outdated and broken LWS specification references in vocabulary w3c/lws-protocol#265, by @wonsuk73.
-
Drop leftover name hint from the create example w3c/lws-protocol#264, by @ebremer.
-
Replace the "MUST ... unless" 404 rule for create in a missing container w3c/lws-protocol#263, by @ebremer.
-
add index services types to JSON-LD context w3c/lws-protocol#260, by @elf-pavlik.
-
replace conflicting expires with valid w3c/lws-protocol#259, by @elf-pavlik.
-
latest implementation reports w3c/lws-protocol#257, by @elf-pavlik.
-
Use RFC-9728 OAuth 2.0 Protected Resource Metadata for auth discovery w3c/lws-protocol#256, by @acoburn.
-
-
15 pull requests merged.
-
Replace the "MUST ... unless" 404 rule for create in a missing container w3c/lws-protocol#263.
-
Define how resources move between containers w3c/lws-protocol#237.
-
Fix vocabulary w3c/lws-protocol#274.
-
Drop leftover name hint from the create example w3c/lws-protocol#264.
-
Require LWS container shape only for application/lws+json w3c/lws-protocol#253.
-
Editorial and consistency updates to LWS Core w3c/lws-protocol#275.
-
Align URI terminology in notification vocabulary descriptions w3c/lws-protocol#268.
-
Fix outdated and broken LWS specification references in vocabulary w3c/lws-protocol#265.
-
Fix XML syntax issues in the SAML authentication credential example w3c/lws-protocol#271.
-
latest implementation reports w3c/lws-protocol#257.
-
Use RFC-9728 OAuth 2.0 Protected Resource Metadata for auth discovery w3c/lws-protocol#256.
-
Switch baseline PATCH format from JSON Merge Patch to JSON Patch w3c/lws-protocol#255.
-
-
3 pull requests closed.
-
feat(notifications): Add WebSocket and Server-Sent Event channels w3c/lws-protocol#162.
-
Specify create Target Not Found as 404 w3c/lws-protocol#241.
-
replace conflicting expires with valid w3c/lws-protocol#259.
-
-
16 pull requests received 40 new comments.
-
Use RFC-9728 OAuth 2.0 Protected Resource Metadata for auth discovery w3c/lws-protocol#256 (7 comments by @acoburn, @elf-pavlik, @TallTed, @uvdsl)
-
Propose Web-CID Profile for Agent Identification w3c/lws-protocol#96 (5 comments by @elf-pavlik, @jacoscaz, @uvdsl)
-
Require LWS container shape only for application/lws+json w3c/lws-protocol#253 (4 comments by @acoburn, @elf-pavlik, @gibsonf1, @jeswr)
-
Define how resources move between containers w3c/lws-protocol#237 (3 comments by @acoburn, @jeremycaine, @TallTed)
-
Switch baseline PATCH format from JSON Merge Patch to JSON Patch w3c/lws-protocol#255 (3 comments by @acoburn, @ericprud)
-
LWS 1.0 Notification Suite: HTTP Streaming w3c/lws-protocol#284 (2 comments by @elf-pavlik, @pietercolpaert)
-
replace static section references with respec dynamic references w3c/lws-protocol#281 (1 comment by @elf-pavlik)
-
Describe media type and size per representation in container listings w3c/lws-protocol#277 (1 comment by @pchampin)
-
feat(notifications): Add WebSocket and Server-Sent Event channels w3c/lws-protocol#162 (1 comment by @elf-pavlik)
-
Propose topic-based notifications for issues and PRs w3c/lws-protocol#242 (1 comment by @elf-pavlik)
-
w3c/lws-ucs
-
1 issue opened.
-
Question: Markers for moved/deleted data? w3c/lws-ucs#232, by @Potherca.
-
-
2 issues received 5 new comments.
-
Question: Pseudonymization of user IDs? w3c/lws-ucs#195 (3 comments by @elf-pavlik, @Potherca, @TallTed)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 8 January 2027.
-
TR publications
-
4 documents published.
-
Linked Web Storage Protocol 1.0 published twice as a Working Draft. History of Linked Web Storage Protocol 1.0
-
LWS 1.0 Authentication Suite: Self-signed Identity using did:key published as a Discontinued Draft. History of LWS 1.0 Authentication Suite: Self-signed Identity using did:key
Past meetings
-
6 meetings.
Participants
-
1 chair appointed.
-
Laurens Debackere became a chair.
-
-
1 chair stepped down.
-
Laurens Debackere stepped down as a chair.
-
-
1 participant joined.
-
Laurens Debackere (W3C Invited Experts) joined.
-
-
1 participant left.
-
Laurens Debackere (W3C Invited Experts) left.
-
GitHub
w3c/lws-ucs
-
1 issue opened.
-
Compare style / format to other W3C notes w3c/lws-ucs#231, by @elf-pavlik.
-
-
1 issue received 2 new comments.
w3c/lws-protocol
-
4 issues opened.
-
Reconsider supported media types for JSON updates w3c/lws-protocol#254, by @acoburn.
-
Define how storage implementations can declare their URI semantics w3c/lws-protocol#247, by @jeswr.
-
Remove requirement that `application/ld+json` and `application/json` must be framed w3c/lws-protocol#246, by @jeswr.
-
Implementors guidance on `ETags` w3c/lws-protocol#245, by @jeswr.
-
-
19 issues closed.
-
Adopting HTTP QUERY method w3c/lws-protocol#184.
-
LWS Test Suite w3c/lws-protocol#102.
-
Generalized notion of auxiliary resources w3c/lws-protocol#67.
-
adjust the SSI-CID suite to be more clearly compatible with DID methods w3c/lws-protocol#231.
-
Include supported CID resolution schemes in "5.2.2 Authorization Server Metadata" w3c/lws-protocol#151.
-
ampersand-escaped curly apostrophes (`’` or `’`) vs the unescaped straight (`'`) w3c/lws-protocol#212.
-
StorageResource definition w3c/lws-protocol#220.
-
Unable to currently Implement Read operation as specified w3c/lws-protocol#223.
-
GET Container potential conflict w3c/lws-protocol#126.
-
Handling of non-URI structured metadata in specification text w3c/lws-protocol#89.
-
Ability to have general metadata w3c/lws-protocol#68.
-
discuss with Ivan on the use of oneOf in yml2vocab w3c/lws-protocol#215.
-
Clarifications around containers and roots w3c/lws-protocol#117.
-
open an issue to track implementation feedback on the type search feature w3c/lws-protocol#170.
-
Create Threat Model Note w3c/lws-protocol#177.
-
ETag Requirements w3c/lws-protocol#62.
-
Use of the Slug header in the LWS protocol text w3c/lws-protocol#94.
-
-
26 issues received 52 new comments.
-
Consider using ODRL profile for access requests as an access control profile w3c/lws-protocol#143 (6 comments by @acoburn, @elf-pavlik, @jeswr, @riannella, @TallTed)
-
Access Requests & Grants: State relationship to inboxes w3c/lws-protocol#142 (6 comments by @acoburn, @elf-pavlik, @TallTed, @uvdsl)
-
Implementors guidance on `ETags` w3c/lws-protocol#245 (5 comments by @acoburn, @gibsonf1, @TallTed, @uvdsl)
-
clarify ETag requirements for Containers (recursively) w3c/lws-protocol#240 (5 comments by @elf-pavlik, @gibsonf1, @raucao)
-
Define how storage implementations can declare their URI semantics w3c/lws-protocol#247 (4 comments by @elf-pavlik, @jeswr, @uvdsl)
-
Handling of non-URI structured metadata in specification text w3c/lws-protocol#89 (2 comments by @acoburn, @elf-pavlik)
-
Missing Authentication Protocol in FPWD for SSI-CID/DID-based LWS 1.0 Authentication Suites? w3c/lws-protocol#140 (2 comments by @acoburn, @elf-pavlik)
-
ampersand-escaped curly apostrophes (`’` or `’`) vs the unescaped straight (`'`) w3c/lws-protocol#212 (2 comments by @acoburn, @TallTed)
-
Create reference explaining consistent use of HTTP content-type, profile, prefer etc. w3c/lws-protocol#188 (2 comments by @msporny, @TallTed)
-
Add example GET application/ld+json on resource that is both data and a container w3c/lws-protocol#181 (1 comment by @acoburn)
-
Provide an overview of Link relations in LWS and whether they are server- or client-managed w3c/lws-protocol#93 (1 comment by @acoburn)
-
Define capabilties affecting Resource Identification (URI allocation) w3c/lws-protocol#207 (1 comment by @pchampin)
-
Remove requirement that `application/ld+json` and `application/json` must be framed w3c/lws-protocol#246 (1 comment by @elf-pavlik)
-
Does Authorization Server need to get user consent again for resource authorization grant? w3c/lws-protocol#74 (1 comment by @acoburn)
-
-
9 pull requests opened.
-
Switch baseline PATCH format from JSON Merge Patch to JSON Patch w3c/lws-protocol#255, by @ebremer.
-
Require LWS container shape only for application/lws+json w3c/lws-protocol#253, by @jeswr.
-
chore(authn-ssi-did-key): update DISC snapshot before publication w3c/lws-protocol#252, by @pchampin.
-
add missing local.css to snapshots directories w3c/lws-protocol#251, by @pchampin.
-
Use straight quotes and apostrophes w3c/lws-protocol#250, by @acoburn.
-
Use lws10-index for LWS index feature w3c/lws-protocol#249, by @acoburn.
-
[wiki] notes on HTTP QUERY method w3c/lws-protocol#248, by @elf-pavlik.
-
add missing CID context in the webhook snippet w3c/lws-protocol#244, by @elf-pavlik.
-
Automate the implementer changelog with editor review w3c/lws-protocol#243, by @jeswr.
-
-
13 pull requests merged.
-
[wiki] notes on HTTP QUERY method w3c/lws-protocol#248.
-
Link to the test suite from README w3c/lws-protocol#213.
-
chore(authn-ssi-did-key): update DISC snapshot before publication w3c/lws-protocol#252.
-
add missing local.css to snapshots directories w3c/lws-protocol#251.
-
Clarify DID support in the SSI-CID authentication suite w3c/lws-protocol#233.
-
Add subject_identifier_types_supported property to AS Metadata w3c/lws-protocol#227.
-
add missing CID context in the webhook snippet w3c/lws-protocol#244.
-
Use lws10-index for LWS index feature w3c/lws-protocol#249.
-
Use straight quotes and apostrophes w3c/lws-protocol#250.
-
Add lws:StorageResource to the vocabulary w3c/lws-protocol#234.
-
LWS Implementation tracking w3c/lws-protocol#171.
-
Discontinue authn-ssi-did-key w3c/lws-protocol#229.
-
Clarify specific ETag requirements and align with RFC 9110 w3c/lws-protocol#228.
-
-
1 pull request closed.
-
Link set profile w3c/lws-protocol#180.
-
-
16 pull requests received 40 new comments.
-
Define how resources move between containers w3c/lws-protocol#237 (10 comments by @acoburn, @elf-pavlik, @laurensdeb)
-
Clarify DID support in the SSI-CID authentication suite w3c/lws-protocol#233 (4 comments by @acoburn, @TallTed)
-
feat(notifications): Add WebSocket and Server-Sent Event channels w3c/lws-protocol#162 (3 comments by @acoburn, @elf-pavlik)
-
Propose topic-based notifications for issues and PRs w3c/lws-protocol#242 (3 comments by @elf-pavlik, @jeswr)
-
Switch baseline PATCH format from JSON Merge Patch to JSON Patch w3c/lws-protocol#255 (2 comments by @acoburn, @jeswr)
-
Require LWS container shape only for application/lws+json w3c/lws-protocol#253 (2 comments by @elf-pavlik)
-
Add subject_identifier_types_supported property to AS Metadata w3c/lws-protocol#227 (2 comments by @acoburn)
-
Automate the implementer changelog with editor review w3c/lws-protocol#243 (2 comments by @elf-pavlik, @gibsonf1)
-
Clarify specific ETag requirements and align with RFC 9110 w3c/lws-protocol#228 (1 comment by @TallTed)
-
feat(notifications): LWS Notifications base specification with Webhooks w3c/lws-protocol#161 (1 comment by @elf-pavlik)
-