Linked Web Storage Working Group - Activity in 2026
No matches.
TR publications
-
8 documents published.
-
Linked Web Storage Protocol 1.0 published 5 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
-
6 meetings.
GitHub
w3c/lws-protocol
-
8 issues opened.
-
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.
-
-
9 issues closed.
-
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.
-
-
26 issues received 57 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)
-
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)
-
-
15 pull requests opened.
-
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.
-
-
14 pull requests merged.
-
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.
-
-
12 pull requests received 34 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)
-
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)
-
TR publications
-
8 documents published.
-
Linked Web Storage Protocol 1.0 published 3 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
GitHub
w3c/lws-protocol
-
13 issues opened.
-
clarify ETag requirements for Containers (recursively) w3c/lws-protocol#240, by @ghurlbot.
-
follow up on changelogs for the specification w3c/lws-protocol#239, by @ghurlbot.
-
Extensibility of metadata categories w3c/lws-protocol#238, by @termontwouter.
-
`realm` and `aud` assumptions w3c/lws-protocol#236, by @jeswr.
-
Spec examples w3c/lws-protocol#235, by @jeswr.
-
plan recurring test suite task force meetings w3c/lws-protocol#232, by @ghurlbot.
-
adjust the SSI-CID suite to be more clearly compatible with DID methods w3c/lws-protocol#231, by @ghurlbot.
-
Improving Access Requests and Access Grants w3c/lws-protocol#230, by @elf-pavlik.
-
Unable to currently Implement Read operation as specified w3c/lws-protocol#223, by @gibsonf1.
-
StorageResource definition w3c/lws-protocol#220, by @acoburn.
-
remove mentions of the Slug header from the LWS protocol text w3c/lws-protocol#217, by @ghurlbot.
-
Add a content digest to the JSON-LD section w3c/lws-protocol#216, by @ghurlbot.
-
discuss with Ivan on the use of oneOf in yml2vocab w3c/lws-protocol#215, by @ghurlbot.
-
-
11 issues closed.
-
plan recurring test suite task force meetings w3c/lws-protocol#232.
-
Vocab terms for media type w3c/lws-protocol#204.
-
remove mentions of the Slug header from the LWS protocol text w3c/lws-protocol#217.
-
LWS Vocabulary w3c/lws-protocol#59.
-
LWS Type Index Feature w3c/lws-protocol#104.
-
provide definition of "resource", as interface, not implementation w3c/lws-protocol#146.
-
Add Privacy Considerations sections to the authentication suites w3c/lws-protocol#119.
-
LWS JSON-LD Context w3c/lws-protocol#60.
-
Remove references to ACL w3c/lws-protocol#70.
-
Handling of content-negotiation on resources in LWS w3c/lws-protocol#91.
-
-
36 issues received 104 new comments.
-
Unable to currently Implement Read operation as specified w3c/lws-protocol#223 (12 comments by @acoburn, @elf-pavlik, @gibsonf1)
-
Include supported CID resolution schemes in "5.2.2 Authorization Server Metadata" w3c/lws-protocol#151 (8 comments by @acoburn, @elf-pavlik, @uvdsl)
-
Create reference explaining consistent use of HTTP content-type, profile, prefer etc. w3c/lws-protocol#188 (4 comments by @elf-pavlik, @TallTed, @termontwouter)
-
Improving Access Requests and Access Grants w3c/lws-protocol#230 (4 comments by @elf-pavlik, @uvdsl)
-
plan recurring test suite task force meetings w3c/lws-protocol#232 (3 comments by @elf-pavlik, @jeswr)
-
Define capabilties affecting Resource Identification (URI allocation) w3c/lws-protocol#207 (3 comments by @acoburn, @elf-pavlik)
-
Confirm "Agent" is defined in the terminology section w3c/lws-protocol#195 (3 comments by @acoburn, @elf-pavlik)
-
Extensibility of metadata categories w3c/lws-protocol#238 (2 comments by @elf-pavlik, @termontwouter)
-
Reconsider optional metadata of resources such as media-type and size w3c/lws-protocol#92 (2 comments by @jeswr)
-
Handling of non-URI structured metadata in specification text w3c/lws-protocol#89 (2 comments by @elf-pavlik, @termontwouter)
-
Potential issues of Authorization Request and Grant being source of truth w3c/lws-protocol#144 (2 comments by @acoburn, @elf-pavlik)
-
Editorial: Link to Authentication Suites from the Core Protocol? w3c/lws-protocol#193 (2 comments by @acoburn, @uvdsl)
-
Allow for an alternative claim for the LWS subject identifier in the OIDC suite w3c/lws-protocol#152 (2 comments by @elf-pavlik, @termontwouter)
-
clarify ETag requirements for Containers (recursively) w3c/lws-protocol#240 (1 comment by @elf-pavlik)
-
Define GET/POST fallback for Search / Type Index when QUERY is unavailable w3c/lws-protocol#205 (1 comment by @acoburn)
-
Does LWS10-AUTHN-SSI-CID already include LWS10-AUTHN-SSI-DID-KEY? w3c/lws-protocol#141 (1 comment by @uvdsl)
-
Why are OAuth/OIDC Security Considerations applicable to SSI-CID/DID-based LWS 1.0 Authentication Suites (FPWD)? w3c/lws-protocol#139 (1 comment by @uvdsl)
-
remove mentions of the Slug header from the LWS protocol text w3c/lws-protocol#217 (1 comment by @elf-pavlik)
-
14 pull requests opened.
-
Propose topic-based notifications for issues and PRs w3c/lws-protocol#242, by @jeswr.
-
Specify create Target Not Found as 404 w3c/lws-protocol#241, by @ebremer.
-
Define how resources move between containers w3c/lws-protocol#237, by @laurensdeb.
-
Add lws:StorageResource to the vocabulary w3c/lws-protocol#234, by @ebremer.
-
Clarify DID support in the SSI-CID authentication suite w3c/lws-protocol#233, by @acoburn.
-
Discontinue authn-ssi-did-key w3c/lws-protocol#229, by @pchampin.
-
Clarify specific ETag requirements and align with RFC 9110 w3c/lws-protocol#228, by @acoburn.
-
Add subject_identifier_types_supported property to AS Metadata w3c/lws-protocol#227, by @acoburn.
-
Remove lws10-authn-ssi-did-key specification w3c/lws-protocol#226, by @uvdsl.
-
Clarify why OAuth best practices are applicable to lws10-authn-ssi-cid w3c/lws-protocol#225, by @uvdsl.
-
fix: remove Slug header mentions from LWS protocol text w3c/lws-protocol#224, by @laurensdeb.
-
Rename metadata name for token subject types w3c/lws-protocol#221, by @acoburn.
-
Replace Activity Streams vocabulary terms with dcterms and LWS equivalents w3c/lws-protocol#219, by @acoburn.
-
Integrate access request terminology with main terminology section w3c/lws-protocol#218, by @acoburn.
-
-
11 pull requests merged.
-
Replace Activity Streams vocabulary terms with dcterms and LWS equivalents w3c/lws-protocol#219.
-
Integrate access request terminology with main terminology section w3c/lws-protocol#218.
-
Clarify why OAuth best practices are applicable to lws10-authn-ssi-cid w3c/lws-protocol#225.
-
fix: remove Slug header mentions from LWS protocol text w3c/lws-protocol#224.
-
Rename metadata name for token subject types w3c/lws-protocol#221.
-
WIP: Add LWS threat model document w3c/lws-protocol#202.
-
Add privacy considerations to the authentication suites w3c/lws-protocol#206.
-
Add terms used by the Access Request feature w3c/lws-protocol#199.
-
Rework JSON-LD context section w3c/lws-protocol#187.
-
remove acl references w3c/lws-protocol#203.
-
Consolidate ConNeg requirements into the LWS Media Type Section w3c/lws-protocol#190.
-
-
2 pull requests closed.
-
Remove lws10-authn-ssi-did-key specification w3c/lws-protocol#226.
-
Simplify gh action dependencies w3c/lws-protocol#208.
-
-
18 pull requests received 85 new comments.
-
Clarify specific ETag requirements and align with RFC 9110 w3c/lws-protocol#228 (30 comments by @acoburn, @raucao, @TallTed)
-
Add subject_identifier_types_supported property to AS Metadata w3c/lws-protocol#227 (11 comments by @acoburn, @elf-pavlik, @TallTed, @termontwouter, @uvdsl)
-
Discontinue authn-ssi-did-key w3c/lws-protocol#229 (8 comments by @ebremer, @laurensdeb, @pchampin, @TallTed, @uvdsl)
-
Add privacy considerations to the authentication suites w3c/lws-protocol#206 (4 comments by @acoburn, @elf-pavlik, @TallTed)
-
Add lws:StorageResource to the vocabulary w3c/lws-protocol#234 (3 comments by @ebremer, @elf-pavlik)
-
Clarify DID support in the SSI-CID authentication suite w3c/lws-protocol#233 (3 comments by @elf-pavlik, @uvdsl)
-
Replace Activity Streams vocabulary terms with dcterms and LWS equivalents w3c/lws-protocol#219 (2 comments by @acoburn, @TallTed)
-
feat(notifications): Add WebSocket and Server-Sent Event channels w3c/lws-protocol#162 (2 comments by @elf-pavlik)
-
Remove lws10-authn-ssi-did-key specification w3c/lws-protocol#226 (2 comments by @acoburn, @pchampin)
-
Clarify why OAuth best practices are applicable to lws10-authn-ssi-cid w3c/lws-protocol#225 (1 comment by @acoburn)
-
fix: remove Slug header mentions from LWS protocol text w3c/lws-protocol#224 (1 comment by @acoburn)
-
Integrate access request terminology with main terminology section w3c/lws-protocol#218 (1 comment by @acoburn)
-
Consolidate ConNeg requirements into the LWS Media Type Section w3c/lws-protocol#190 (1 comment by @elf-pavlik)
-
w3c/lws-ucs
-
1 pull request opened.
-
Validate use case source issues and correct citations w3c/lws-ucs#230, by @ebremer.
-
TR publications
-
4 documents published.
-
Linked Web Storage Protocol 1.0 published 3 times as a Working Draft. History of Linked Web Storage Protocol 1.0
-
Linked Web Storage Vocabulary published as a Draft Note. History of Linked Web Storage Vocabulary
-
Past meetings
Participants
-
1 participant joined.
-
Jeremy Caine (W3C Invited Experts) joined.
-
GitHub
w3c/lws-protocol
-
12 issues opened.
-
ampersand-escaped curly apostrophes (`’` or `’`) vs the unescaped straight (`'`) w3c/lws-protocol#212, by @TallTed.
-
Define capabilties affecting Resource Identification (URI allocation) w3c/lws-protocol#207, by @elf-pavlik.
-
Define GET/POST fallback for Search / Type Index when QUERY is unavailable w3c/lws-protocol#205, by @ebremer.
-
Vocab terms for media type w3c/lws-protocol#204, by @jeswr.
-
Ensure the OIDC suite affords for FedCM w3c/lws-protocol#200, by @jeswr.
-
Well define slug w3c/lws-protocol#197, by @jeswr.
-
LWS mapping to ODRL w3c/lws-protocol#196, by @riannella.
-
Confirm "Agent" is defined in the terminology section w3c/lws-protocol#195, by @jeswr.
-
Editorial: Link to Authentication Suites from the Core Protocol? w3c/lws-protocol#193, by @uvdsl.
-
Linkset profiles and preferences w3c/lws-protocol#189, by @termontwouter.
-
Create reference explaining consistent use of HTTP content-type, profile, prefer etc. w3c/lws-protocol#188, by @elf-pavlik.
-
Document use of SSI-CID and HTTP Signatures w3c/lws-protocol#186, by @elf-pavlik.
-
-
8 issues closed.
-
propose a way of bringing the core of notifications into lws-core as a PR. w3c/lws-protocol#175.
-
Well define slug w3c/lws-protocol#197.
-
to change terminology to extend from the not allowed on virtual resources w3c/lws-protocol#149.
-
Controller discovery should be in the document, not Link headers w3c/lws-protocol#64.
-
(Recursive) resource/container deletion and virtual resources w3c/lws-protocol#69.
-
Containers: specify behavior on deleting non-empty containers w3c/lws-protocol#88.
-
Reconsider Strict Tree layout w3c/lws-protocol#135.
-
Make Resource identifiers really unique within the system w3c/lws-protocol#71.
-
-
2 issues reopened.
-
Need for a deterministic mechanism to declare the Abstract State Infoset Type of a resource w3c/lws-protocol#110, by @TallTed.
-
Confirm "Agent" is defined in the terminology section w3c/lws-protocol#195, by @jeswr.
-
-
48 issues received 90 new comments.
-
Does LWS10-AUTHN-SSI-CID already include LWS10-AUTHN-SSI-DID-KEY? w3c/lws-protocol#141 (4 comments by @acoburn, @elf-pavlik, @jeswr, @uvdsl)
-
Handling of non-URI structured metadata in specification text w3c/lws-protocol#89 (4 comments by @acoburn, @elf-pavlik, @termontwouter)
-
Why are OAuth/OIDC Security Considerations applicable to SSI-CID/DID-based LWS 1.0 Authentication Suites (FPWD)? w3c/lws-protocol#139 (3 comments by @acoburn, @jeswr, @uvdsl)
-
ampersand-escaped curly apostrophes (`’` or `’`) vs the unescaped straight (`'`) w3c/lws-protocol#212 (3 comments by @acoburn, @jeremycaine, @TallTed)
-
Consider using ODRL profile for access requests as an access control profile w3c/lws-protocol#143 (3 comments by @acoburn, @jeswr, @riannella)
-
Distinguish between Container and Data Resources in the metadata w3c/lws-protocol#90 (3 comments by @acoburn, @gibsonf1, @termontwouter)
-
Include supported CID resolution schemes in "5.2.2 Authorization Server Metadata" w3c/lws-protocol#151 (2 comments by @acoburn, @elf-pavlik)
-
Allow for an alternative claim for the LWS subject identifier in the OIDC suite w3c/lws-protocol#152 (2 comments by @acoburn, @elf-pavlik)
-
make PR extracting move of resources between containers w3c/lws-protocol#148 (2 comments by @acoburn, @elf-pavlik)
-
propose a way of bringing the core of notifications into lws-core as a PR. w3c/lws-protocol#175 (2 comments by @acoburn, @elf-pavlik)
-
Use of the Slug header in the LWS protocol text w3c/lws-protocol#94 (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)
-
Need for a deterministic mechanism to declare the Abstract State Infoset Type of a resource w3c/lws-protocol#110 (2 comments by @acoburn, @TallTed)
-
Handling of the case where a resource is created in a non-existent container w3c/lws-protocol#87 (2 comments by @acoburn, @TallTed)
-
to change terminology to extend from the not allowed on virtual resources w3c/lws-protocol#149 (2 comments by @acoburn)
-
Potential issues of Authorization Request and Grant being source of truth w3c/lws-protocol#144 (2 comments by @elf-pavlik)
-
Add example GET application/ld+json on resource that is both data and a container w3c/lws-protocol#181 (1 comment by @acoburn)
-
Define GET/POST fallback for Search / Type Index when QUERY is unavailable w3c/lws-protocol#205 (1 comment by @ebremer)
-
Controller discovery should be in the document, not Link headers w3c/lws-protocol#64 (1 comment by @acoburn)
-
(Recursive) resource/container deletion and virtual resources w3c/lws-protocol#69 (1 comment by @acoburn)
-
Containers: specify behavior on deleting non-empty containers w3c/lws-protocol#88 (1 comment by @acoburn)
-
Make Resource identifiers really unique within the system w3c/lws-protocol#71 (1 comment by @acoburn)
-
Does Authorization Server need to get user consent again for resource authorization grant? w3c/lws-protocol#74 (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)
-
provide definition of "resource", as interface, not implementation w3c/lws-protocol#146 (1 comment by @acoburn)
-
open an issue to track implementation feedback on the type search feature w3c/lws-protocol#170 (1 comment by @acoburn)
-
Reconsider optional metadata of resources such as media-type and size w3c/lws-protocol#92 (1 comment by @termontwouter)
-
Access Requests & Grants: State relationship to inboxes w3c/lws-protocol#142 (1 comment by @acoburn)
-
clarify the distinction of a linkset being an aux resource and other aux resources and clarify in the terminology w3c/lws-protocol#147 (1 comment by @acoburn)
-
14 pull requests opened.
-
Link to the test suite from README w3c/lws-protocol#213, by @elf-pavlik.
-
Add dependabot support for github-actions on a weekly schedule w3c/lws-protocol#209, by @acoburn.
-
Simplify gh action dependencies w3c/lws-protocol#208, by @acoburn.
-
Add privacy considerations to the authentication suites w3c/lws-protocol#206, by @acoburn.
-
remove acl references w3c/lws-protocol#203, by @ebremer.
-
WIP: Add LWS threat model document w3c/lws-protocol#202, by @renyuneyun.
-
update terminology for Agent to align with system componentsadded clarity to agent definition w3c/lws-protocol#201, by @jeremycaine.
-
Add terms used by the Access Request feature w3c/lws-protocol#199, by @acoburn.
-
update terminology for Agent to align with system components w3c/lws-protocol#198, by @jeremycaine.
-
[vocab] fix links in broken snapshot w3c/lws-protocol#194, by @pchampin.
-
Pchampin vocab 1st snapshot w3c/lws-protocol#192, by @pchampin.
-
[vocab] improve template and regenerate DNOTE snapshot w3c/lws-protocol#191, by @pchampin.
-
Consolidate ConNeg requirements into the LWS Media Type Section w3c/lws-protocol#190, by @ebremer.
-
Rework JSON-LD context section w3c/lws-protocol#187, by @acoburn.
-
-
9 pull requests merged.
-
Add introduction section w3c/lws-protocol#158.
-
Add scope diagrams section with C4 Level 1 and Level 2 diagrams w3c/lws-protocol#159.
-
Define Storage Description Resources as a specialization of CID-1.0 w3c/lws-protocol#183.
-
Add dependabot support for github-actions on a weekly schedule w3c/lws-protocol#209.
-
Integrate core notification data model into lws10-core w3c/lws-protocol#185.
-
[vocab] fix links in broken snapshot w3c/lws-protocol#194.
-
Replace GET/POST with new HTTP QUERY RFC10008 w3c/lws-protocol#179.
-
Pchampin vocab 1st snapshot w3c/lws-protocol#192.
-
[vocab] improve template and regenerate DNOTE snapshot w3c/lws-protocol#191.
-
-
3 pull requests closed.
-
test: create strawman test suite w3c/lws-protocol#145.
-
update terminology for Agent to align with system components w3c/lws-protocol#198.
-
-
17 pull requests received 155 new comments.
-
Add introduction section w3c/lws-protocol#158 (32 comments by @acoburn, @elf-pavlik, @gibsonf1, @jeremycaine, @jeswr, @pchampin, @renyuneyun, @TallTed, @w3cbot)
-
Add scope diagrams section with C4 Level 1 and Level 2 diagrams w3c/lws-protocol#159 (30 comments by @elf-pavlik, @gibsonf1, @jeremycaine, @TallTed, @w3cbot)
-
Replace GET/POST with new HTTP QUERY RFC10008 w3c/lws-protocol#179 (16 comments by @ebremer, @jeremycaine, @pchampin, @reschke, @TallTed)
-
Add privacy considerations to the authentication suites w3c/lws-protocol#206 (14 comments by @acoburn, @elf-pavlik, @jeswr, @TallTed, @w3cbot)
-
WIP: Add LWS threat model document w3c/lws-protocol#202 (11 comments by @acoburn, @elf-pavlik, @renyuneyun, @TallTed, @w3cbot)
-
Define Storage Description Resources as a specialization of CID-1.0 w3c/lws-protocol#183 (11 comments by @acoburn, @elf-pavlik, @pchampin, @renyuneyun, @termontwouter, @w3cbot)
-
update terminology for Agent to align with system components w3c/lws-protocol#198 (7 comments by @acoburn, @elf-pavlik, @jeremycaine)
-
Rework JSON-LD context section w3c/lws-protocol#187 (6 comments by @acoburn, @BigBlueHat, @elf-pavlik, @jeswr, @w3cbot)
-
LWS Implementation tracking w3c/lws-protocol#171 (6 comments by @acoburn, @elf-pavlik, @gibsonf1, @jeswr)
-
Consolidate ConNeg requirements into the LWS Media Type Section w3c/lws-protocol#190 (5 comments by @acoburn, @ebremer, @TallTed, @w3cbot)
-
update terminology for Agent to align with system componentsadded clarity to agent definition w3c/lws-protocol#201 (4 comments by @acoburn, @elf-pavlik, @jeremycaine)
-
Add terms used by the Access Request feature w3c/lws-protocol#199 (3 comments by @pchampin, @w3cbot)
-
Support for auxiliary resources and manifest (#67) w3c/lws-protocol#113 (2 comments by @elf-pavlik, @ericPxKanda)
-
TR publications
-
9 documents published.
-
Linked Web Storage Protocol 1.0 published 5 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
Participants
-
1 participant joined.
-
Benjamin Young (Digital Bazaar) joined.
-
-
1 participant left.
-
Jeremy Caine (W3C Invited Experts) left.
-
-
1 organization joined.
-
Digital Bazaar joined.
-
GitHub
w3c/lws-protocol
-
9 issues opened.
-
Adopting HTTP QUERY method w3c/lws-protocol#184, by @elf-pavlik.
-
Add example GET application/ld+json on resource that is both data and a container w3c/lws-protocol#181, by @gibsonf1.
-
Orthogonality of specifications w3c/lws-protocol#178, by @namedgraph.
-
Create Threat Model Note w3c/lws-protocol#177, by @elf-pavlik.
-
TPAC 2026 Agenda w3c/lws-protocol#176, by @acoburn.
-
propose a way of bringing the core of notifications into lws-core as a PR. w3c/lws-protocol#175, by @ghurlbot.
-
Link from core draft to LWS Notifications draft w3c/lws-protocol#174, by @elf-pavlik.
-
Idempotent Create w3c/lws-protocol#173, by @elf-pavlik.
-
open an issue to track implementation feedback on the type search feature w3c/lws-protocol#170, by @ghurlbot.
-
-
13 issues closed.
-
Abstract 'containers' as Link Set representations of arbitrary relational metadata w3c/lws-protocol#116.
-
Storage itself to behave as a Container w3c/lws-protocol#137.
-
Question: Linkset json -> RDF? w3c/lws-protocol#128.
-
Linkset URI (not resource) w3c/lws-protocol#127.
-
Why is Linkset required to be an additional resource rather than a representation? w3c/lws-protocol#125.
-
Resource both Data and Container w3c/lws-protocol#123.
-
Container Requirements Problem w3c/lws-protocol#65.
-
Data Resource = file? w3c/lws-protocol#124.
-
Link from core draft to LWS Notifications draft w3c/lws-protocol#174.
-
TotalItems: count MUST be exact: propose to SHOULD w3c/lws-protocol#114.
-
LWS Notifications Feature w3c/lws-protocol#103.
-
LWS Access Request and Grant feature w3c/lws-protocol#105.
-
-
1 issue reopened.
-
GET Container potential conflict w3c/lws-protocol#126, by @gibsonf1.
-
-
29 issues received 52 new comments.
-
Define Virtual Resource w3c/lws-protocol#150 (7 comments by @acoburn, @gibsonf1, @jeremycaine, @renyuneyun)
-
Reconsider optional metadata of resources such as media-type and size w3c/lws-protocol#92 (5 comments by @acoburn, @elf-pavlik, @TallTed)
-
Abstract 'containers' as Link Set representations of arbitrary relational metadata w3c/lws-protocol#116 (2 comments by @CxRes, @laurensdeb)
-
Handling of non-URI structured metadata in specification text w3c/lws-protocol#89 (2 comments by @acoburn, @elf-pavlik)
-
Controller discovery should be in the document, not Link headers w3c/lws-protocol#64 (2 comments by @jeswr, @melvincarvalho)
-
Does Authorization Server need to get user consent again for resource authorization grant? w3c/lws-protocol#74 (1 comment by @elf-pavlik)
-
Provide an overview of Link relations in LWS and whether they are server- or client-managed w3c/lws-protocol#93 (1 comment by @elf-pavlik)
-
Handling of the case where a resource is created in a non-existent container w3c/lws-protocol#87 (1 comment by @acoburn)
-
What is the scope of the LWS protocol and this has bearing on whether we need Virtual Resource w3c/lws-protocol#155 (1 comment by @jeremycaine)
-
provide definition of "resource", as interface, not implementation w3c/lws-protocol#146 (1 comment by @elf-pavlik)
-
-
10 pull requests opened.
-
Integrate core notification data model into lws10-core w3c/lws-protocol#185, by @laurensdeb.
-
Define Storage Description Resources as a specialization of CID-1.0 w3c/lws-protocol#183, by @acoburn.
-
lws10-vocab snapshot for first publication w3c/lws-protocol#182, by @pchampin.
-
Link set profile w3c/lws-protocol#180, by @termontwouter.
-
Replace GET/POST with new HTTP QUERY RFC10008 w3c/lws-protocol#179, by @ebremer.
-
Add missing local.css files to authentication suites w3c/lws-protocol#172, by @acoburn.
-
LWS Implementation tracking w3c/lws-protocol#171, by @elf-pavlik.
-
Clarify relationship to OAuth 2.0 w3c/lws-protocol#169, by @acoburn.
-
Remove 'Unstable Features' section w3c/lws-protocol#168, by @acoburn.
-
auxiliary resource as a role w3c/lws-protocol#167, by @pchampin.
-
-
9 pull requests merged.
-
lws10-vocab snapshot for first publication w3c/lws-protocol#182.
-
auxiliary resource as a role w3c/lws-protocol#167.
-
Remove 'Unstable Features' section w3c/lws-protocol#168.
-
Clarify relationship to OAuth 2.0 w3c/lws-protocol#169.
-
add Type Index Section w3c/lws-protocol#115.
-
Add missing local.css files to authentication suites w3c/lws-protocol#172.
-
Link terminology to definitions w3c/lws-protocol#164.
-
feat(notifications): LWS Notifications base specification with Webhooks w3c/lws-protocol#161.
-
Add editors draft for LWS Access Requests and Access Grants w3c/lws-protocol#106.
-
-
2 pull requests closed.
-
Define aux & meta in terms of representations w3c/lws-protocol#165.
-
prior-art: group based access policies w3c/lws-protocol#31.
-
-
14 pull requests received 161 new comments.
-
add Type Index Section w3c/lws-protocol#115 (70 comments by @acoburn, @ebremer, @elf-pavlik, @gibsonf1, @laurensdeb, @TallTed, @w3cbot)
-
Define aux & meta in terms of representations w3c/lws-protocol#165 (22 comments by @acoburn, @elf-pavlik, @pchampin, @TallTed, @termontwouter, @w3cbot, @woutermont)
-
Add introduction section w3c/lws-protocol#158 (16 comments by @ebremer, @jeremycaine, @laurensdeb, @TallTed)
-
Add scope diagrams section with C4 Level 1 and Level 2 diagrams w3c/lws-protocol#159 (13 comments by @acoburn, @elf-pavlik, @laurensdeb, @TallTed)
-
Replace GET/POST with new HTTP QUERY RFC10008 w3c/lws-protocol#179 (9 comments by @ebremer, @gibsonf1, @jeswr, @TallTed)
-
feat(notifications): Add WebSocket and Server-Sent Event channels w3c/lws-protocol#162 (9 comments by @CxRes, @elf-pavlik, @TallTed)
-
auxiliary resource as a role w3c/lws-protocol#167 (4 comments by @acoburn, @pchampin, @termontwouter)
-
Add editors draft for LWS Access Requests and Access Grants w3c/lws-protocol#106 (2 comments by @TallTed, @w3cbot)
-
feat(notifications): LWS Notifications base specification with Webhooks w3c/lws-protocol#161 (1 comment by @w3cbot)
-
w3c/lws-ucs
-
1 issue opened.
-
[UC] Provability of Institutional Records (RecordWeb) w3c/lws-ucs#228, by @Jenziner.
-
-
2 issues received 2 new comments.
Past meetings
Participants
-
2 participants joined.
-
Pavlik elf (W3C Invited Experts) joined.
-
Emanuel Silva (HM Government) joined.
-
-
2 participants left.
-
Emanuel Silva (HM Government) left.
-
Huw Diprose (HM Government) left.
-
GitHub
w3c/lws-protocol
-
1 issue opened.
-
What is the scope of the LWS protocol and this has bearing on whether we need Virtual Resource w3c/lws-protocol#155, by @jeremycaine.
-
-
1 issue closed.
-
Terminology: Resource Manager / Resource Controller / ... w3c/lws-protocol#27.
-
-
2 issues received 6 new comments.
-
What is the scope of the LWS protocol and this has bearing on whether we need Virtual Resource w3c/lws-protocol#155 (1 comment by @jeremycaine)
-
12 pull requests opened.
-
set up echidna w3c/lws-protocol#166, by @pchampin.
-
Define aux & meta in terms of representations w3c/lws-protocol#165, by @termontwouter.
-
Link terminology to definitions w3c/lws-protocol#164, by @acoburn.
-
Define aux & meta in terms of representations w3c/lws-protocol#163, by @termontwouter.
-
feat(notifications): Add WebSocket and Server-Sent Event channels w3c/lws-protocol#162, by @laurensdeb.
-
feat(notifications): LWS Notifications base specification with Webhooks w3c/lws-protocol#161, by @laurensdeb.
-
move former editors to Acknowledgement section w3c/lws-protocol#160, by @pchampin.
-
Add scope diagrams section with C4 Level 1 and Level 2 diagrams w3c/lws-protocol#159, by @jeremycaine.
-
Add introduction section w3c/lws-protocol#158, by @jeremycaine.
-
Change totalItems from MUST to SHOULD w3c/lws-protocol#157, by @ebremer.
-
Rename container section to 'Containers' w3c/lws-protocol#154, by @acoburn.
-
Refine terminology section w3c/lws-protocol#153, by @acoburn.
-
-
6 pull requests merged.
-
set up echidna w3c/lws-protocol#166.
-
move former editors to Acknowledgement section w3c/lws-protocol#160.
-
Rename container section to 'Containers' w3c/lws-protocol#154.
-
Change totalItems from MUST to SHOULD w3c/lws-protocol#157.
-
Refine terminology section w3c/lws-protocol#153.
-
fix Editor's Draft URIs in Authn Suite specifications w3c/lws-protocol#138.
-
-
4 pull requests closed.
-
Define aux & meta in terms of representations w3c/lws-protocol#163.
-
Terminology section formatting fixes w3c/lws-protocol#122.
-
Review and restructure Access Grant Proposal w3c/lws-protocol#109.
-
-
10 pull requests received 32 new comments.
-
Refine terminology section w3c/lws-protocol#153 (13 comments by @acoburn, @gibsonf1, @jeremycaine, @pchampin, @TallTed, @w3cbot)
-
Change totalItems from MUST to SHOULD w3c/lws-protocol#157 (4 comments by @ebremer, @laurensdeb, @TallTed, @w3cbot)
-
Propose Web-CID Profile for Agent Identification w3c/lws-protocol#96 (4 comments by @TallTed, @uvdsl)
-
Define aux & meta in terms of representations w3c/lws-protocol#165 (2 comments by @acoburn, @gibsonf1)
-
Add editors draft for LWS Access Requests and Access Grants w3c/lws-protocol#106 (2 comments by @acoburn, @gibsonf1)
-
feat(notifications): Add WebSocket and Server-Sent Event channels w3c/lws-protocol#162 (1 comment by @laurensdeb)
-
feat(notifications): LWS Notifications base specification with Webhooks w3c/lws-protocol#161 (1 comment by @laurensdeb)
-
feat(notifications): Introduce the LWS notifications specification as an optional service w3c/lws-protocol#129 (1 comment by @laurensdeb)
-
TR publications
-
4 documents published.
-
LWS 1.0 Authentication Suite: OpenID Connect published as a First Public Working Draft. History of LWS 1.0 Authentication Suite: OpenID Connect
-
LWS 1.0 Authentication Suite: SAML 2.0 published as a First Public Working Draft. History of LWS 1.0 Authentication Suite: SAML 2.0
-
LWS 1.0 Authentication Suite: Self-signed Identity using Controlled Identifiers published as a First Public Working Draft. History of LWS 1.0 Authentication Suite: Self-signed Identity using Controlled Identifiers
-
LWS 1.0 Authentication Suite: Self-signed Identity using did:key published as a First Public Working Draft. History of LWS 1.0 Authentication Suite: Self-signed Identity using did:key
-
Past meetings
Participants
-
1 participant joined.
-
Wouter Termont (imec) joined.
-
-
1 participant left.
-
Sam Gbafa (TinyCloud) left.
-
-
1 organization left.
-
TinyCloud left.
-
GitHub
w3c/lws-protocol
-
23 issues opened.
-
Allow for an alternative claim for the LWS subject identifier in the OIDC suite w3c/lws-protocol#152, by @laurensdeb.
-
Include supported CID resolution schemes in "5.2.2 Authorization Server Metadata" w3c/lws-protocol#151, by @laurensdeb.
-
Define Virtual Resource w3c/lws-protocol#150, by @renyuneyun.
-
to change terminology to extend from the not allowed on virtual resources w3c/lws-protocol#149, by @ghurlbot.
-
make PR extracting move of resources between containers w3c/lws-protocol#148, by @ghurlbot.
-
provide definition of "resource", as interface, not implementation w3c/lws-protocol#146, by @ghurlbot.
-
Potential issues of Authorization Request and Grant being source of truth w3c/lws-protocol#144, by @renyuneyun.
-
Consider using ODRL profile for access requests as an access control profile w3c/lws-protocol#143, by @jeswr.
-
Access Requests & Grants: State relationship to inboxes w3c/lws-protocol#142, by @jeswr.
-
Does LWS10-AUTHN-SSI-CID already include LWS10-AUTHN-SSI-DID-KEY? w3c/lws-protocol#141, by @uvdsl.
-
Missing Authentication Protocol in FPWD for SSI-CID/DID-based LWS 1.0 Authentication Suites? w3c/lws-protocol#140, by @uvdsl.
-
Storage itself to behave as a Container w3c/lws-protocol#137, by @gibsonf1.
-
Reconsider Strict Tree layout w3c/lws-protocol#135, by @damooo.
-
Add video link to the meeting pages for April 2026 face-to-face w3c/lws-protocol#133, by @acoburn.
-
Question: Linkset json -> RDF? w3c/lws-protocol#128, by @gibsonf1.
-
Linkset URI (not resource) w3c/lws-protocol#127, by @gibsonf1.
-
GET Container potential conflict w3c/lws-protocol#126, by @gibsonf1.
-
Why is Linkset required to be an additional resource rather than a representation? w3c/lws-protocol#125, by @gibsonf1.
-
Data Resource = file? w3c/lws-protocol#124, by @gibsonf1.
-
Resource both Data and Container w3c/lws-protocol#123, by @gibsonf1.
-
Add Privacy Considerations sections to the authentication suites w3c/lws-protocol#119, by @acoburn.
-
-
4 issues closed.
-
Possible contradiction with respect to resource relocation w3c/lws-protocol#72.
-
set up yml2vocab for the as-is terms in the specification w3c/lws-protocol#101.
-
Add video link to the meeting pages for April 2026 face-to-face w3c/lws-protocol#133.
-
Have separate auxiliary resource for containment index w3c/lws-protocol#86.
-
-
1 issue reopened.
-
Add video link to the meeting pages for April 2026 face-to-face w3c/lws-protocol#133, by @pchampin.
-
-
23 issues received 72 new comments.
-
Linkset URI (not resource) w3c/lws-protocol#127 (22 comments by @acoburn, @elf-pavlik, @gibsonf1, @laurensdeb, @pchampin)
-
GET Container potential conflict w3c/lws-protocol#126 (5 comments by @elf-pavlik, @gibsonf1, @pchampin, @TallTed)
-
Reconsider Strict Tree layout w3c/lws-protocol#135 (4 comments by @damooo, @gibsonf1, @pchampin, @renyuneyun)
-
Resource both Data and Container w3c/lws-protocol#123 (4 comments by @elf-pavlik, @gibsonf1, @pchampin, @renyuneyun)
-
Add Privacy Considerations sections to the authentication suites w3c/lws-protocol#119 (4 comments by @acoburn, @elf-pavlik, @pchampin)
-
Clarifications around containers and roots w3c/lws-protocol#117 (4 comments by @gibsonf1, @kaefer3000, @pchampin)
-
Why are OAuth/OIDC Security Considerations applicable to SSI-CID/DID-based LWS 1.0 Authentication Suites (FPWD)? w3c/lws-protocol#139 (3 comments by @acoburn, @elf-pavlik)
-
Why is Linkset required to be an additional resource rather than a representation? w3c/lws-protocol#125 (3 comments by @elf-pavlik, @gibsonf1, @pchampin)
-
Abstract 'containers' as Link Set representations of arbitrary relational metadata w3c/lws-protocol#116 (3 comments by @elf-pavlik, @termontwouter)
-
Need for a deterministic mechanism to declare the Abstract State Infoset Type of a resource w3c/lws-protocol#110 (3 comments by @damooo, @pchampin, @TallTed)
-
(Recursive) resource/container deletion and virtual resources w3c/lws-protocol#69 (2 comments by @jeremycaine, @renyuneyun)
-
Have separate auxiliary resource for containment index w3c/lws-protocol#86 (2 comments by @damooo, @elf-pavlik)
-
Consider using ODRL profile for access requests as an access control profile w3c/lws-protocol#143 (1 comment by @TallTed)
-
Access Requests & Grants: State relationship to inboxes w3c/lws-protocol#142 (1 comment by @TallTed)
-
Containers: specify behavior on deleting non-empty containers w3c/lws-protocol#88 (1 comment by @laurensdeb)
-
Distinguish between Container and Data Resources in the metadata w3c/lws-protocol#90 (1 comment by @laurensdeb)
-
Does LWS10-AUTHN-SSI-CID already include LWS10-AUTHN-SSI-DID-KEY? w3c/lws-protocol#141 (1 comment by @acoburn)
-
Missing Authentication Protocol in FPWD for SSI-CID/DID-based LWS 1.0 Authentication Suites? w3c/lws-protocol#140 (1 comment by @acoburn)
-
Add video link to the meeting pages for April 2026 face-to-face w3c/lws-protocol#133 (1 comment by @pchampin)
-
-
11 pull requests opened.
-
test: create strawman test suite w3c/lws-protocol#145, by @ericprud.
-
fix Editor's Draft URIs in Authn Suite specifications w3c/lws-protocol#138, by @pchampin.
-
remove confusing analogy w3c/lws-protocol#136, by @pchampin.
-
Add missing version to authn suites w3c/lws-protocol#134, by @pchampin.
-
chore: add vocab to readme and remove node_modules from pages deploy w3c/lws-protocol#132, by @laurensdeb.
-
fix: resolve dependency issue in github pages build w3c/lws-protocol#131, by @laurensdeb.
-
fix: generate html for readme file in repo root w3c/lws-protocol#130, by @laurensdeb.
-
feat(notifications): Introduce the LWS notifications specification as an optional service w3c/lws-protocol#129, by @laurensdeb.
-
Terminology section formatting fixes w3c/lws-protocol#122, by @ebremer.
-
Agenda for April F2F meetings w3c/lws-protocol#121, by @acoburn.
-
Authentication suite FPWD snapshots w3c/lws-protocol#120, by @acoburn.
-
-
10 pull requests merged.
-
Add missing version to authn suites w3c/lws-protocol#134.
-
remove confusing analogy w3c/lws-protocol#136.
-
chore: add vocab to readme and remove node_modules from pages deploy w3c/lws-protocol#132.
-
fix: resolve dependency issue in github pages build w3c/lws-protocol#131.
-
fix: generate html for readme file in repo root w3c/lws-protocol#130.
-
feat(vocab): setup yml2vocab for managing the LWS vocabulary and json-ld context w3c/lws-protocol#112.
-
Authentication suite FPWD snapshots w3c/lws-protocol#120.
-
Add affiliation information for all authors and editors w3c/lws-protocol#111.
-
Align name of OAuth Client ID Metadata Document draft w3c/lws-protocol#98.
-
lws-core prepare fpwd snapshop w3c/lws-protocol#99.
-
-
2 pull requests closed.
-
Agenda for April F2F meetings w3c/lws-protocol#121.
-
Multiple Containment for LWS Containers w3c/lws-protocol#83.
-
-
12 pull requests received 111 new comments.
-
Add editors draft for LWS Access Requests and Access Grants w3c/lws-protocol#106 (51 comments by @acoburn, @ebremer, @elf-pavlik, @jeswr, @pchampin, @renyuneyun, @TallTed, @termontwouter, @uvdsl)
-
add Type Index Section w3c/lws-protocol#115 (14 comments by @acoburn, @ebremer, @elf-pavlik, @gibsonf1, @TallTed)
-
Agenda for April F2F meetings w3c/lws-protocol#121 (8 comments by @acoburn, @elf-pavlik, @jeswr, @renyuneyun)
-
Support for auxiliary resources and manifest (#67) w3c/lws-protocol#113 (8 comments by @damooo, @gibsonf1, @pchampin)
-
feat(vocab): setup yml2vocab for managing the LWS vocabulary and json-ld context w3c/lws-protocol#112 (4 comments by @iherman, @jeswr, @pchampin)
-
feat(notifications): Introduce the LWS notifications specification as an optional service w3c/lws-protocol#129 (3 comments by @acoburn, @elf-pavlik, @jeswr)
-
w3c/lws-ucs
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
Linked Web Storage Protocol 1.0 published as a First Public Working Draft. History of Linked Web Storage Protocol 1.0
-
Past meetings
Participants
-
2 participants joined.
-
Femke Ongenae (imec) joined.
-
Roberto Sequerra Koogan Breitman (Open Data Institute) joined.
-
-
1 participant left.
-
Chris Johnson (W3C Invited Experts) left.
-
GitHub
w3c/lws-protocol
-
21 issues opened.
-
Thank you w3c/lws-protocol#118, by @vivien35af.
-
Clarifications around containers and roots w3c/lws-protocol#117, by @kaefer3000.
-
Abstract 'containers' as Link Set representations of arbitrary relational metadata w3c/lws-protocol#116, by @termontwouter.
-
TotalItems: count MUST be exact: propose to SHOULD w3c/lws-protocol#114, by @bjdmeest.
-
Need for a deterministic mechanism to declare the Abstract State Infoset Type of a resource w3c/lws-protocol#110, by @damooo.
-
LWS Access Request and Grant feature w3c/lws-protocol#105, by @acoburn.
-
LWS Type Index Feature w3c/lws-protocol#104, by @acoburn.
-
LWS Notifications Feature w3c/lws-protocol#103, by @acoburn.
-
LWS Test Suite w3c/lws-protocol#102, by @acoburn.
-
set up yml2vocab for the as-is terms in the specification w3c/lws-protocol#101, by @ghurlbot.
-
open GitHub issues for each of the work items: test suite, notifications, type index w3c/lws-protocol#100, by @ghurlbot.
-
Right approach to mark some likely editorial issues of the docs? w3c/lws-protocol#97, by @renyuneyun.
-
Specify Container representation to be compound representation w3c/lws-protocol#95, by @damooo.
-
Use of the Slug header in the LWS protocol text w3c/lws-protocol#94, by @laurensdeb.
-
Provide an overview of Link relations in LWS and whether they are server- or client-managed w3c/lws-protocol#93, by @laurensdeb.
-
Reconsider optional metadata of resources such as media-type and size w3c/lws-protocol#92, by @laurensdeb.
-
Handling of content-negotiation on resources in LWS w3c/lws-protocol#91, by @laurensdeb.
-
Distinguish between Container and Data Resources in the metadata w3c/lws-protocol#90, by @laurensdeb.
-
Handling of non-URI structured metadata in specification text w3c/lws-protocol#89, by @laurensdeb.
-
Containers: specify behavior on deleting non-empty containers w3c/lws-protocol#88, by @bjdmeest.
-
Handling of the case where a resource is created in a non-existent container w3c/lws-protocol#87, by @laurensdeb.
-
-
11 issues closed.
-
Thank you w3c/lws-protocol#118.
-
Right approach to mark some likely editorial issues of the docs? w3c/lws-protocol#97.
-
open GitHub issues for each of the work items: test suite, notifications, type index w3c/lws-protocol#100.
-
resource identifier needs clarification w3c/lws-protocol#79.
-
irrelevant MUST statement? w3c/lws-protocol#78.
-
Reasons for separate rest bindings w3c/lws-protocol#24.
-
Specify Container representation to be compound representation w3c/lws-protocol#95.
-
what does "hierarchy arrays for ancestors" mean? w3c/lws-protocol#80.
-
Concerns about container creation w3c/lws-protocol#77.
-
Scalability and implementation concerns regarding permission-based filtering w3c/lws-protocol#73.
-
LWS Container Media Type w3c/lws-protocol#61.
-
-
24 issues received 51 new comments.
-
Have separate auxiliary resource for containment index w3c/lws-protocol#86 (17 comments by @acoburn, @bjdmeest, @damooo, @elf-pavlik, @gibsonf1, @kaefer3000, @pchampin, @TallTed)
-
Abstract 'containers' as Link Set representations of arbitrary relational metadata w3c/lws-protocol#116 (4 comments by @kaefer3000, @termontwouter)
-
Handling of the case where a resource is created in a non-existent container w3c/lws-protocol#87 (4 comments by @bjdmeest, @pchampin, @TallTed)
-
Right approach to mark some likely editorial issues of the docs? w3c/lws-protocol#97 (3 comments by @acoburn, @w3cbot)
-
Need for a deterministic mechanism to declare the Abstract State Infoset Type of a resource w3c/lws-protocol#110 (2 comments by @acoburn, @damooo)
-
Specify Container representation to be compound representation w3c/lws-protocol#95 (2 comments by @acoburn, @damooo)
-
(Recursive) resource/container deletion and virtual resources w3c/lws-protocol#69 (1 comment by @pchampin)
-
Make Resource identifiers really unique within the system w3c/lws-protocol#71 (1 comment by @laurensdeb)
-
open GitHub issues for each of the work items: test suite, notifications, type index w3c/lws-protocol#100 (1 comment by @acoburn)
-
Handling of non-URI structured metadata in specification text w3c/lws-protocol#89 (1 comment by @acoburn)
-
Reconsider optional metadata of resources such as media-type and size w3c/lws-protocol#92 (1 comment by @acoburn)
-
Scalability and implementation concerns regarding permission-based filtering w3c/lws-protocol#73 (1 comment by @laurensdeb)
-
Containers: specify behavior on deleting non-empty containers w3c/lws-protocol#88 (1 comment by @TallTed)
-
-
11 pull requests opened.
-
add Type Index Section w3c/lws-protocol#115, by @ebremer.
-
Support for auxiliary resources and manifest (#67) w3c/lws-protocol#113, by @damooo.
-
feat(vocab): setup yml2vocab for managing the LWS vocabulary and json-ld context w3c/lws-protocol#112, by @laurensdeb.
-
Add affiliation information for all authors and editors w3c/lws-protocol#111, by @acoburn.
-
Review and restructure Access Grant Proposal w3c/lws-protocol#109, by @jeswr.
-
Link auth term instances to their definitions w3c/lws-protocol#108, by @acoburn.
-
Add localBiblio reference for the did:key specification w3c/lws-protocol#107, by @acoburn.
-
Add editors draft for LWS Access Requests and Access Grants w3c/lws-protocol#106, by @acoburn.
-
lws-core prepare fpwd snapshop w3c/lws-protocol#99, by @pchampin.
-
Align name of OAuth Client ID Metadata Document draft w3c/lws-protocol#98, by @acoburn.
-
Propose Web-CID Profile for Agent Identification w3c/lws-protocol#96, by @uvdsl.
-
-
5 pull requests merged.
-
Pagination for LWS Containers w3c/lws-protocol#82.
-
Link auth term instances to their definitions w3c/lws-protocol#108.
-
Add localBiblio reference for the did:key specification w3c/lws-protocol#107.
-
Move Aaron Coburn from editor to author in authN suites w3c/lws-protocol#85.
-
Introducing support for Containers in the LWS protocol w3c/lws-protocol#81.
-
-
10 pull requests received 231 new comments.
-
Add editors draft for LWS Access Requests and Access Grants w3c/lws-protocol#106 (75 comments by @acoburn, @bjdmeest, @elf-pavlik, @jeswr, @laurensdeb, @renyuneyun, @uvdsl)
-
Propose Web-CID Profile for Agent Identification w3c/lws-protocol#96 (71 comments by @acoburn, @aharth, @angelo-v, @dmitrizagidulin, @elf-pavlik, @jacoscaz, @jeswr, @kaefer3000, @laurensdeb, @msporny, @pchampin, @TallTed, @uvdsl, @w3cbot)
-
Pagination for LWS Containers w3c/lws-protocol#82 (28 comments by @acoburn, @bjdmeest, @elf-pavlik, @gibsonf1, @laurensdeb, @pchampin, @TallTed, @w3cbot)
-
Introducing support for Containers in the LWS protocol w3c/lws-protocol#81 (28 comments by @acoburn, @bjdmeest, @damooo, @gibsonf1, @laurensdeb, @pchampin)
-
Review and restructure Access Grant Proposal w3c/lws-protocol#109 (13 comments by @acoburn, @elf-pavlik, @maxleonard, @renyuneyun)
-
feat(vocab): setup yml2vocab for managing the LWS vocabulary and json-ld context w3c/lws-protocol#112 (3 comments by @laurensdeb, @pchampin)
-
TR publications
-
1 document published.
-
Linked Web Storage Use Cases published as a Draft Note. History of Linked Web Storage Use Cases
-
Past meetings
Participants
-
1 participant joined.
-
Jeremy Caine (W3C Invited Experts) joined.
-
GitHub
w3c/lws-protocol
-
11 issues opened.
-
Have separate auxiliary resource for containment index w3c/lws-protocol#86, by @damooo.
-
what does "hierarchy arrays for ancestors" mean? w3c/lws-protocol#80, by @pchampin.
-
resource identifier needs clarification w3c/lws-protocol#79, by @pchampin.
-
irrelevant MUST statement? w3c/lws-protocol#78, by @pchampin.
-
Concerns about container creation w3c/lws-protocol#77, by @pchampin.
-
Does Authorization Server need to get user consent again for resource authorization grant? w3c/lws-protocol#74, by @damooo.
-
Scalability and implementation concerns regarding permission-based filtering w3c/lws-protocol#73, by @wkerckho.
-
Possible contradiction with respect to resource relocation w3c/lws-protocol#72, by @wkerckho.
-
Make Resource identifiers really unique within the system w3c/lws-protocol#71, by @gvseghbr.
-
Remove references to ACL w3c/lws-protocol#70, by @gvseghbr.
-
(Recursive) resource/container deletion and virtual resources w3c/lws-protocol#69, by @renyuneyun.
-
-
3 issues closed.
-
Consider draft-parecki-oauth-client-id-metadata-document for input w3c/lws-protocol#38.
-
Prior Art Collection w3c/lws-protocol#18.
-
open PR to simplify and clarify the "Use of Storage Providers" requirement w3c/lws-protocol#34.
-
-
15 issues received 47 new comments.
-
Scalability and implementation concerns regarding permission-based filtering w3c/lws-protocol#73 (9 comments by @acoburn, @gibsonf1, @laurensdeb, @w3cbot)
-
Agent Identification w3c/lws-protocol#57 (8 comments by @acoburn, @elf-pavlik, @jacoscaz, @laurensdeb, @uvdsl, @w3cbot)
-
Does Authorization Server need to get user consent again for resource authorization grant? w3c/lws-protocol#74 (6 comments by @damooo, @elf-pavlik)
-
Reasons for separate rest bindings w3c/lws-protocol#24 (4 comments by @acoburn, @ebremer, @jacoscaz, @uvdsl)
-
Terminology: Resource Manager / Resource Controller / ... w3c/lws-protocol#27 (4 comments by @acoburn, @elf-pavlik)
-
Have separate auxiliary resource for containment index w3c/lws-protocol#86 (3 comments by @damooo, @pchampin)
-
resource identifier needs clarification w3c/lws-protocol#79 (3 comments by @pchampin, @TallTed, @w3cbot)
-
(Recursive) resource/container deletion and virtual resources w3c/lws-protocol#69 (2 comments by @laurensdeb, @renyuneyun)
-
Cool URIs for the Semantic Web: 303 URIs forwarding to Different Documents w3c/lws-protocol#39 (1 comment by @elf-pavlik)
-
Possible contradiction with respect to resource relocation w3c/lws-protocol#72 (1 comment by @laurensdeb)
-
-
7 pull requests opened.
-
Move Aaron Coburn from editor to author in authN suites w3c/lws-protocol#85, by @acoburn.
-
fix editors list w3c/lws-protocol#84, by @ebremer.
-
Multiple Containment for LWS Containers w3c/lws-protocol#83, by @laurensdeb.
-
Pagination for LWS Containers w3c/lws-protocol#82, by @laurensdeb.
-
Introducing support for Containers in the LWS protocol w3c/lws-protocol#81, by @laurensdeb.
-
a container is not, and does not represent, a resource *type* w3c/lws-protocol#76, by @pchampin.
-
merge rest bindings into operations section w3c/lws-protocol#75, by @ebremer.
-
-
3 pull requests merged.
-
a container is not, and does not represent, a resource *type* w3c/lws-protocol#76.
-
fix editors list w3c/lws-protocol#84.
-
merge rest bindings into operations section w3c/lws-protocol#75.
-
-
6 pull requests received 54 new comments.
-
Introducing support for Containers in the LWS protocol w3c/lws-protocol#81 (38 comments by @bjdmeest, @damooo, @laurensdeb, @pchampin, @TallTed, @w3cbot)
-
Multiple Containment for LWS Containers w3c/lws-protocol#83 (3 comments by @elf-pavlik, @TallTed, @w3cbot)
-
a container is not, and does not represent, a resource *type* w3c/lws-protocol#76 (2 comments by @TallTed)
-
w3c/lws-ucs
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Re-order requirements to align with WG votes w3c/lws-ucs#227.
-
-
1 pull request received 38 new comments.
TR publications
-
2 documents published.
-
Linked Web Storage Use Cases published twice as a Draft Note. History of Linked Web Storage Use Cases
-
Past meetings
GitHub
w3c/lws-protocol
-
11 issues opened.
-
Ability to have general metadata w3c/lws-protocol#68, by @damooo.
-
Generalized notion of auxiliary resources w3c/lws-protocol#67, by @damooo.
-
Solid Compatibility / Migration Work Item w3c/lws-protocol#66, by @acoburn.
-
Container Requirements Problem w3c/lws-protocol#65, by @gibsonf1.
-
Controller discovery should be in the document, not Link headers w3c/lws-protocol#64, by @melvincarvalho.
-
ETag Requirements w3c/lws-protocol#62, by @acoburn.
-
LWS Container Media Type w3c/lws-protocol#61, by @acoburn.
-
LWS JSON-LD Context w3c/lws-protocol#60, by @acoburn.
-
LWS Vocabulary w3c/lws-protocol#59, by @acoburn.
-
Agent Identification w3c/lws-protocol#57, by @uvdsl.
-
add root-vs-subject issue to text merged from #53 w3c/lws-protocol#54, by @ghurlbot.
-
-
7 issues closed.
-
add root-vs-subject issue to text merged from #53 w3c/lws-protocol#54.
-
configure PR-Preview for preview/diff on PRs in https://github.com/w3c/lws-ucs w3c/lws-protocol#6.
-
Proposed order of topics w3c/lws-protocol#23.
-
Break discovery section in two w3c/lws-protocol#32.
-
Cool URIs for the Semantic Web: 303 URIs forwarding to Different Documents w3c/lws-protocol#39.
-
use of "relative URI" w3c/lws-protocol#46.
-
-
15 issues received 50 new comments.
-
Agent Identification w3c/lws-protocol#57 (16 comments by @acoburn, @elf-pavlik, @melvincarvalho, @TallTed, @uvdsl)
-
LWS Container Media Type w3c/lws-protocol#61 (6 comments by @acoburn, @elf-pavlik, @rubensworks, @uvdsl)
-
Reasons for separate rest bindings w3c/lws-protocol#24 (3 comments by @acoburn, @pietercolpaert, @w3cbot)
-
Consider draft-parecki-oauth-client-id-metadata-document for input w3c/lws-protocol#38 (2 comments by @acoburn, @elf-pavlik)
-
Cool URIs for the Semantic Web: 303 URIs forwarding to Different Documents w3c/lws-protocol#39 (2 comments by @acoburn, @elf-pavlik)
-
Terminology: Resource Manager / Resource Controller / ... w3c/lws-protocol#27 (1 comment by @w3cbot)
-
present a weekly overview of closed issues in the https://github.com/w3c/lws-ucs/issues repository w3c/lws-protocol#16 (1 comment by @acoburn)
-
-
4 pull requests opened.
-
Fix authentication suite titles w3c/lws-protocol#63, by @acoburn.
-
Clarify storage description URI w3c/lws-protocol#58, by @acoburn.
-
Change 'end-user credential' to 'authentication credential' w3c/lws-protocol#56, by @acoburn.
-
Update unresolvable informative references w3c/lws-protocol#55, by @acoburn.
-
-
11 pull requests merged.
-
Clarify storage description URI w3c/lws-protocol#58.
-
Update unresolvable informative references w3c/lws-protocol#55.
-
Change 'end-user credential' to 'authentication credential' w3c/lws-protocol#56.
-
Fix authentication suite titles w3c/lws-protocol#63.
-
Consolidate privacy considerations w3c/lws-protocol#49.
-
Consolidate security considerations w3c/lws-protocol#50.
-
Replace 'absolute URI' with 'URI' w3c/lws-protocol#48.
-
LWS Storage Description Resource w3c/lws-protocol#53.
-
Initial CRUD with proposed metadata handling w3c/lws-protocol#37.
-
Adjust access token example w3c/lws-protocol#51.
-
Fix link header example w3c/lws-protocol#52.
-
-
8 pull requests received 53 new comments.
-
LWS Storage Description Resource w3c/lws-protocol#53 (14 comments by @acoburn, @elf-pavlik, @pchampin, @renyuneyun, @TallTed)
-
Change 'end-user credential' to 'authentication credential' w3c/lws-protocol#56 (1 comment by @w3cbot)
w3c/lws-ucs
-
1 issue opened.
-
[UC] Indexing a Volunteer Profile w3c/lws-ucs#226, by @matthieubosquet.
-
-
3 issues received 21 new comments.
-
[UC] Mechanism to access a resource identifier in a storage with identifier that points to a different storage w3c/lws-ucs#215 (16 comments by @acoburn, @elf-pavlik, @gibsonf1, @pchampin, @uvdsl)
-
Include Solid User Stories and various UCRs into LWS UCR w3c/lws-ucs#229 (2 comments by @acoburn, @w3cbot)
-
-
1 pull request opened.
-
Re-order requirements to align with WG votes w3c/lws-ucs#227, by @acoburn.
-
-
2 pull requests merged.
-
Add Notification Service definition and miscellaneous updates w3c/lws-ucs#224.
-
Update cross-links among glossary terms w3c/lws-ucs#225.
-
-
2 pull requests received 2 new comments.
-
Add Notification Service definition and miscellaneous updates w3c/lws-ucs#224 (1 comment by @TallTed)