Credentials Community Group - Activity
No matches.
Past meetings
Participants
-
7 participants joined.
-
Alessandro Malventano (The European Decentralisation Institute) joined.
-
Gabriel Ferrão joined.
-
XINGHUA ZHAO joined.
-
Pierre Thierry joined.
-
Thomas Lancaster joined.
-
Eric Chan joined.
-
Luis Antonio Galvez Bommer joined.
-
-
1 participant left.
-
Clare Nelson (Decentralized Identity Foundation (DIF)) left.
-
-
1 organization joined.
-
The European Decentralisation Institute joined.
-
GitHub
w3c-ccg/community
-
1 issue opened.
-
[PROPOSED WORK ITEM] Cross-Border Interoperability Tracker w3c-ccg/community#264, by @aledecentral.
-
w3c-ccg/zcap-spec
-
8 issues opened.
-
Duplicate information in an invocation w3c-ccg/zcap-spec#139, by @alanhkarp.
-
An invocation zcap must be for a specific resource w3c-ccg/zcap-spec#138, by @alanhkarp.
-
avoid "A verifier will accept delegations" text, which could be interpreted as a normative requirement w3c-ccg/zcap-spec#137, by @gobengo.
-
allow root zcap to have a `proof` property w3c-ccg/zcap-spec#134, by @gobengo.
-
show example of providing a capability as a invocation parameter w3c-ccg/zcap-spec#130, by @gobengo.
-
require allowedAction in delegated capability w3c-ccg/zcap-spec#129, by @gobengo.
-
Allow Data Integrity proof chains for zcap delegation w3c-ccg/zcap-spec#128, by @gobengo.
-
-
2 issues closed.
-
Allow Data Integrity proof chains for zcap delegation w3c-ccg/zcap-spec#128.
-
zcap JSON-LD context should include term DataIntegrityProof w3c-ccg/zcap-spec#95.
-
-
7 issues received 11 new comments.
-
url based attenuation /foo/?limit=5 authorizes /foo/?limit=5&limit=10 (et al) w3c-ccg/zcap-spec#127 (4 comments by @alanhkarp, @gobengo)
-
do we need to require delegation.parentCapability since delegation.proof[].capabilityChain[-1] already embeds it w3c-ccg/zcap-spec#135 (2 comments by @alanhkarp, @gobengo)
-
is invocationTarget required on delegated capability? w3c-ccg/zcap-spec#122 (1 comment by @alanhkarp)
-
show example of providing a capability as a invocation parameter w3c-ccg/zcap-spec#130 (1 comment by @alanhkarp)
-
document how to realize lds-ocap cloud storage scenario using zcap w3c-ccg/zcap-spec#102 (1 comment by @gobengo)
-
zcap-spec should refer to vc-data-integrity when describing how to add proof and verify proof set w3c-ccg/zcap-spec#63 (1 comment by @gobengo)
-
zcap JSON-LD context should include term DataIntegrityProof w3c-ccg/zcap-spec#95 (1 comment by @gobengo)
-
-
5 pull requests opened.
-
index.html title says this is 0.4.0, not 0.4.0-rc.6 w3c-ccg/zcap-spec#140, by @gobengo.
-
remove requirement for verifier to cap delegations at 10 w3c-ccg/zcap-spec#136, by @gobengo.
-
WIP: Cloud Storage Use Case w3c-ccg/zcap-spec#133, by @gobengo.
-
remove note atop section 3 because it used old terminology and can cause confusion w3c-ccg/zcap-spec#132, by @gobengo.
-
Clarify delegated capability proof property w3c-ccg/zcap-spec#131, by @gobengo.
-
-
2 pull requests merged.
-
release v0.4.0-rc as stable v0.4.0 w3c-ccg/zcap-spec#113.
-
index.html title says this is 0.4.0, not 0.4.0-rc.6 w3c-ccg/zcap-spec#140.
-
-
3 pull requests received 7 new comments.
-
remove requirement for verifier to cap delegations at 10 w3c-ccg/zcap-spec#136 (5 comments by @alanhkarp, @gobengo)
-
remove 'The capability action SHOULD be read or write.' w3c-ccg/zcap-spec#115 (1 comment by @dlongley)
-
w3c-ccg/capability-based-storage-tf
-
2 issues opened.
-
Agenda for the 2026-11-05 TF Call w3c-ccg/capability-based-storage-tf#7, by @dmitrizagidulin.
-
Agenda for the 2026-10-15 TF Call w3c-ccg/capability-based-storage-tf#6, by @dmitrizagidulin.
-
-
2 issues closed.
-
Agenda for the 2026-10-01 TF Call w3c-ccg/capability-based-storage-tf#5.
-
Agenda for the 2026-09-17 TF call. w3c-ccg/capability-based-storage-tf#4.
-
-
1 issue received 1 new comment.
w3c-ccg/wallet-attached-storage-spec
-
2 issues closed.
-
combine description and meta objects for collections w3c-ccg/wallet-attached-storage-spec#63.
-
Rename spec from W.A.S. to 'Portable Web Spaces' w3c-ccg/wallet-attached-storage-spec#70.
-
-
2 issues received 5 new comments.
-
Rename spec from W.A.S. to 'Portable Web Spaces' w3c-ccg/wallet-attached-storage-spec#70 (4 comments by @dmitrizagidulin, @jorgefl0)
-
combine description and meta objects for collections w3c-ccg/wallet-attached-storage-spec#63 (1 comment by @dmitrizagidulin)
-
-
4 pull requests opened.
-
Add the created-by service-description feature token. w3c-ccg/wallet-attached-storage-spec#86, by @dmitrizagidulin.
-
State that a /meta write leaves the Resource's updatedAt and ETag. w3c-ccg/wallet-attached-storage-spec#85, by @dmitrizagidulin.
-
Make the changes-feed checkpoint an opaque, server-scoped string. w3c-ccg/wallet-attached-storage-spec#84, by @dmitrizagidulin.
-
List Spaces lists every Space and carries each item's type. w3c-ccg/wallet-attached-storage-spec#83, by @dmitrizagidulin.
-
-
8 pull requests merged.
-
Add the created-by service-description feature token. w3c-ccg/wallet-attached-storage-spec#86.
-
State that a /meta write leaves the Resource's updatedAt and ETag. w3c-ccg/wallet-attached-storage-spec#85.
-
Make the changes-feed checkpoint an opaque, server-scoped string. w3c-ccg/wallet-attached-storage-spec#84.
-
List Spaces lists every Space and carries each item's type. w3c-ccg/wallet-attached-storage-spec#83.
-
Nest the Collection generator as { id, origin, url, name }. w3c-ccg/wallet-attached-storage-spec#82.
-
Move Chunked Resources and the EDV appendix to PWS-EC. w3c-ccg/wallet-attached-storage-spec#81.
-
Extract the zCap authorization profile into a companion spec. w3c-ccg/wallet-attached-storage-spec#80.
-
Rename the specification to Portable Web Spaces (PWS). w3c-ccg/wallet-attached-storage-spec#79.
-
-
8 pull requests received 9 new comments.
-
Rename the specification to Portable Web Spaces (PWS). w3c-ccg/wallet-attached-storage-spec#79 (2 comments by @alexfigtree, @dmitrizagidulin)
-
Add the created-by service-description feature token. w3c-ccg/wallet-attached-storage-spec#86 (1 comment by @dmitrizagidulin)
-
State that a /meta write leaves the Resource's updatedAt and ETag. w3c-ccg/wallet-attached-storage-spec#85 (1 comment by @dmitrizagidulin)
-
Make the changes-feed checkpoint an opaque, server-scoped string. w3c-ccg/wallet-attached-storage-spec#84 (1 comment by @dmitrizagidulin)
-
List Spaces lists every Space and carries each item's type. w3c-ccg/wallet-attached-storage-spec#83 (1 comment by @dmitrizagidulin)
-
Nest the Collection generator as { id, origin, url, name }. w3c-ccg/wallet-attached-storage-spec#82 (1 comment by @dmitrizagidulin)
-
Move Chunked Resources and the EDV appendix to PWS-EC. w3c-ccg/wallet-attached-storage-spec#81 (1 comment by @dmitrizagidulin)
-
Extract the zCap authorization profile into a companion spec. w3c-ccg/wallet-attached-storage-spec#80 (1 comment by @dmitrizagidulin)
-
w3c-ccg/data-integrity-test-suite-assertion
-
1 pull request received 1 new comment.
-
Fix eddsa-rdfc-2022 previousProof chain tests w3c-ccg/data-integrity-test-suite-assertion#134 (1 comment by @Executioner1939)
-
Capability-based Storage Task Force
Past meetings
-
2 meetings of the Capability-based Storage Task Force.
Past meetings
Participants
-
16 participants joined.
-
Daniel Pelegero (Capital One Discover Network) joined.
-
Jo Spencer (Sezoo) joined.
-
Serenity Thompson joined.
-
Sunny Lee joined.
-
Jennifer Strickland joined.
-
Pratap Potakamuri joined.
-
John Phillips (Sezoo) joined.
-
Vincent Lee joined.
-
Atul Singh joined.
-
Kelvin Chau joined.
-
Aaron Olson joined.
-
ACLAS COLLEGE (Atlanta College of Liberal Arts and Sciences) joined.
-
Parthiv Rawat joined.
-
Nik Jenzer (TRIEBWERKSTATT GmbH) joined.
-
Daniel Mantei joined.
-
Fatih Kockesen (Solidus Network) joined.
-
-
4 participants left.
-
Pratap Potakamuri left.
-
ACLAS COLLEGE (Atlanta College of Liberal Arts and Sciences) left.
-
Alex Higuera (Digital Credentials Consortium) left.
-
Nik Jenzer (TRIEBWERKSTATT GmbH) left.
-
-
4 organizations joined.
-
Sezoo joined.
-
Atlanta College of Liberal Arts and Sciences joined.
-
TRIEBWERKSTATT GmbH joined.
-
Solidus Network joined.
-
-
3 organizations left.
-
Atlanta College of Liberal Arts and Sciences left.
-
Digital Credentials Consortium left.
-
Schweizerische Bundeskanzlei left.
-
GitHub
w3c-ccg/zcap-spec
-
16 issues opened.
-
url based attenuation /foo/?limit=5 authorizes /foo/?limit=5&limit=10 (et al) w3c-ccg/zcap-spec#127, by @gobengo.
-
add JCS hash of zcap-v1.jsonld w3c-ccg/zcap-spec#125, by @gobengo.
-
zcap-spec 0.3.0 errata w3c-ccg/zcap-spec#123, by @gobengo.
-
is invocationTarget required on delegated capability? w3c-ccg/zcap-spec#122, by @gobengo.
-
prevention of CRLF "normalization" vandalism by GitHub w3c-ccg/zcap-spec#120, by @TallTed.
-
release zcap-spec v0.4.0 w3c-ccg/zcap-spec#112, by @gobengo.
-
drop "The capability action SHOULD be read or write." w3c-ccg/zcap-spec#109, by @gobengo.
-
drop `@context` property requirements w3c-ccg/zcap-spec#108, by @gobengo.
-
How should example JSON be formatted? Let's have consistent norms around whitespace w3c-ccg/zcap-spec#105, by @gobengo.
-
reword: "The key used to create the HTTP signature must be either ..." in Invocation HTTP Signature w3c-ccg/zcap-spec#103, by @gobengo.
-
document how to realize lds-ocap cloud storage scenario using zcap w3c-ccg/zcap-spec#102, by @gobengo.
-
Make context files immutable. w3c-ccg/zcap-spec#101, by @BigBlueHat.
-
Fix or remove gh-pages publishing "extras" that are breaking spec index output. w3c-ccg/zcap-spec#100, by @BigBlueHat.
-
zcap JSON-LD context should include term DataIntegrityProof w3c-ccg/zcap-spec#95, by @gobengo.
-
-
3 issues closed.
-
How should example JSON be formatted? Let's have consistent norms around whitespace w3c-ccg/zcap-spec#105.
-
Fix or remove gh-pages publishing "extras" that are breaking spec index output. w3c-ccg/zcap-spec#100.
-
Update examples to use recent Data Integrity suites w3c-ccg/zcap-spec#69.
-
-
1 issue reopened.
-
Make context files immutable. w3c-ccg/zcap-spec#101, by @gobengo.
-
-
14 issues received 52 new comments.
-
Make context files immutable. w3c-ccg/zcap-spec#101 (16 comments by @davidlehn, @dlongley, @filip26, @gobengo, @msporny, @TallTed)
-
zcap JSON-LD context should include term DataIntegrityProof w3c-ccg/zcap-spec#95 (8 comments by @BigBlueHat, @dlongley, @gobengo, @msporny)
-
reword: "The key used to create the HTTP signature must be either ..." in Invocation HTTP Signature w3c-ccg/zcap-spec#103 (6 comments by @dlongley, @dmitrizagidulin, @gobengo)
-
Clarify `allowedAction` and `caveat.type` ranges are to be specified by profiles of ZCAP spec w3c-ccg/zcap-spec#84 (5 comments by @dlongley, @gobengo, @kezike)
-
drop `@context` property requirements w3c-ccg/zcap-spec#108 (3 comments by @dlongley, @filip26, @gobengo)
-
How should example JSON be formatted? Let's have consistent norms around whitespace w3c-ccg/zcap-spec#105 (3 comments by @gobengo, @TallTed)
-
Fix or remove gh-pages publishing "extras" that are breaking spec index output. w3c-ccg/zcap-spec#100 (2 comments by @gobengo)
-
prevention of CRLF "normalization" vandalism by GitHub w3c-ccg/zcap-spec#120 (1 comment by @TallTed)
-
spec should offer guidance for how to file an implementation report w3c-ccg/zcap-spec#93 (1 comment by @gobengo)
-
What if gzipped capability-invocation header is still too big for http server? What if an invocation http request fails with status 431? w3c-ccg/zcap-spec#104 (1 comment by @gobengo)
-
-
16 pull requests opened.
-
remove a duplicated word in the hiring example w3c-ccg/zcap-spec#124, by @jameseaster.
-
add recent work to v0.4.0-rc w3c-ccg/zcap-spec#121, by @gobengo.
-
add zcap-v1.jsonld hash w3c-ccg/zcap-spec#119, by @gobengo.
-
Format all example JSON consistently w3c-ccg/zcap-spec#117, by @gobengo.
-
format example jsons consistently w3c-ccg/zcap-spec#116, by @gobengo.
-
remove 'The capability action SHOULD be read or write.' w3c-ccg/zcap-spec#115, by @gobengo.
-
(wait until after release 0.4.0) initial v0.5.0-draft w3c-ccg/zcap-spec#114, by @gobengo.
-
release v0.4.0-rc as stable v0.4.0 w3c-ccg/zcap-spec#113, by @gobengo.
-
Release v0.4.0 as new `stable` w3c-ccg/zcap-spec#111, by @gobengo.
-
rename /context/ to /contexts/ w3c-ccg/zcap-spec#99, by @gobengo.
-
add backlog items for specifying proof/verification algorithms w3c-ccg/zcap-spec#98, by @gobengo.
-
add DataIntegrityProof to context/zcap-v1.jsonld w3c-ccg/zcap-spec#96, by @gobengo.
-
replace Ed25519Signature20* with DataIntegrityProof w3c-ccg/zcap-spec#94, by @gobengo.
-
-
10 pull requests merged.
-
remove a duplicated word in the hiring example w3c-ccg/zcap-spec#124.
-
add recent work to v0.4.0-rc w3c-ccg/zcap-spec#121.
-
Format all example JSON consistently w3c-ccg/zcap-spec#117.
-
add zcap-v1.jsonld hash w3c-ccg/zcap-spec#119.
-
add backlog items for specifying proof/verification algorithms w3c-ccg/zcap-spec#98.
-
rename /context/ to /contexts/ w3c-ccg/zcap-spec#99.
-
replace Ed25519Signature20* with DataIntegrityProof w3c-ccg/zcap-spec#94.
-
-
4 pull requests closed.
-
format example jsons consistently w3c-ccg/zcap-spec#116.
-
Release v0.4.0 as new `stable` w3c-ccg/zcap-spec#111.
-
WIP: v0.4.0-draft - This PR shows all changes in editor's draft since v0.3.0 w3c-ccg/zcap-spec#76.
-
add DataIntegrityProof to context/zcap-v1.jsonld w3c-ccg/zcap-spec#96.
-
-
3 pull requests received 5 new comments.
-
add DataIntegrityProof to context/zcap-v1.jsonld w3c-ccg/zcap-spec#96 (2 comments by @dlongley, @gobengo)
-
add backlog items for specifying proof/verification algorithms w3c-ccg/zcap-spec#98 (2 comments by @gobengo, @TallTed)
-
w3c-ccg/wallet-attached-storage-spec
-
3 issues opened.
-
Provide guidance on spec evolution and versioning w3c-ccg/wallet-attached-storage-spec#77, by @dmitrizagidulin.
-
Space Metadata preconditions cite conditional-writes, but no backend governs a Space w3c-ccg/wallet-attached-storage-spec#75, by @dmitrizagidulin.
-
Rename spec from W.A.S. to 'Portable Web Spaces' w3c-ccg/wallet-attached-storage-spec#70, by @dmitrizagidulin.
-
-
1 issue closed.
-
Space Metadata preconditions cite conditional-writes, but no backend governs a Space w3c-ccg/wallet-attached-storage-spec#75.
-
-
3 issues received 6 new comments.
-
Rename spec from W.A.S. to 'Portable Web Spaces' w3c-ccg/wallet-attached-storage-spec#70 (4 comments by @dmitrizagidulin, @gobengo, @jchartrand)
-
Space Metadata preconditions cite conditional-writes, but no backend governs a Space w3c-ccg/wallet-attached-storage-spec#75 (1 comment by @dmitrizagidulin)
-
combine description and meta objects for collections w3c-ccg/wallet-attached-storage-spec#63 (1 comment by @dmitrizagidulin)
-
-
12 pull requests opened.
-
Nest the Collection generator as { id, origin, url, name }. w3c-ccg/wallet-attached-storage-spec#82, by @dmitrizagidulin.
-
Move Chunked Resources and the EDV appendix to PWS-EC. w3c-ccg/wallet-attached-storage-spec#81, by @dmitrizagidulin.
-
Extract the zCap authorization profile into a companion spec. w3c-ccg/wallet-attached-storage-spec#80, by @dmitrizagidulin.
-
Rename the specification to Portable Web Spaces (PWS). w3c-ccg/wallet-attached-storage-spec#79, by @dmitrizagidulin.
-
Remove the backend feature vocabulary. w3c-ccg/wallet-attached-storage-spec#78, by @dmitrizagidulin.
-
Remove 'storageMode' backend property. w3c-ccg/wallet-attached-storage-spec#76, by @dmitrizagidulin.
-
Add the Collection governing history log sub-resource. w3c-ccg/wallet-attached-storage-spec#74, by @dmitrizagidulin.
-
State the container rule and its two exceptions. w3c-ccg/wallet-attached-storage-spec#73, by @dmitrizagidulin.
-
Add the Service Description section and the service link relation. w3c-ccg/wallet-attached-storage-spec#72, by @dmitrizagidulin.
-
Move container descriptions to /meta and merge the Collection object. w3c-ccg/wallet-attached-storage-spec#71, by @dmitrizagidulin.
-
Add etag and metaEtag to the changes feed entry. w3c-ccg/wallet-attached-storage-spec#69, by @dmitrizagidulin.
-
Add the plaintext Collection member (plaintext.indexes). w3c-ccg/wallet-attached-storage-spec#68, by @dmitrizagidulin.
-
-
11 pull requests merged.
-
Remove the backend feature vocabulary. w3c-ccg/wallet-attached-storage-spec#78.
-
State the container rule and its two exceptions. w3c-ccg/wallet-attached-storage-spec#73.
-
Add the Service Description section and the service link relation. w3c-ccg/wallet-attached-storage-spec#72.
-
Move container descriptions to /meta and merge the Collection object. w3c-ccg/wallet-attached-storage-spec#71.
-
Add the Collection governing history log sub-resource. w3c-ccg/wallet-attached-storage-spec#74.
-
Remove 'storageMode' backend property. w3c-ccg/wallet-attached-storage-spec#76.
-
Add etag and metaEtag to the changes feed entry. w3c-ccg/wallet-attached-storage-spec#69.
-
Add the plaintext Collection member (plaintext.indexes). w3c-ccg/wallet-attached-storage-spec#68.
-
Add hmac descriptor validation. w3c-ccg/wallet-attached-storage-spec#67.
-
Make Cavage draft 12 the required signature suite; RFC 9421 is future direction. w3c-ccg/wallet-attached-storage-spec#65.
-
Admit did:webvh Space controllers via a controller DID method registry. w3c-ccg/wallet-attached-storage-spec#64.
-
-
12 pull requests received 14 new comments.
-
Add the Service Description section and the service link relation. w3c-ccg/wallet-attached-storage-spec#72 (2 comments by @dmitrizagidulin)
-
Move container descriptions to /meta and merge the Collection object. w3c-ccg/wallet-attached-storage-spec#71 (2 comments by @dmitrizagidulin, @jchartrand)
-
Nest the Collection generator as { id, origin, url, name }. w3c-ccg/wallet-attached-storage-spec#82 (1 comment by @dmitrizagidulin)
-
Move Chunked Resources and the EDV appendix to PWS-EC. w3c-ccg/wallet-attached-storage-spec#81 (1 comment by @dmitrizagidulin)
-
Extract the zCap authorization profile into a companion spec. w3c-ccg/wallet-attached-storage-spec#80 (1 comment by @dmitrizagidulin)
-
Rename the specification to Portable Web Spaces (PWS). w3c-ccg/wallet-attached-storage-spec#79 (1 comment by @dmitrizagidulin)
-
Remove the backend feature vocabulary. w3c-ccg/wallet-attached-storage-spec#78 (1 comment by @dmitrizagidulin)
-
State the container rule and its two exceptions. w3c-ccg/wallet-attached-storage-spec#73 (1 comment by @dmitrizagidulin)
-
Add the Collection governing history log sub-resource. w3c-ccg/wallet-attached-storage-spec#74 (1 comment by @dmitrizagidulin)
-
Add etag and metaEtag to the changes feed entry. w3c-ccg/wallet-attached-storage-spec#69 (1 comment by @dmitrizagidulin)
-
Add the plaintext Collection member (plaintext.indexes). w3c-ccg/wallet-attached-storage-spec#68 (1 comment by @dmitrizagidulin)
-
Admit did:webvh Space controllers via a controller DID method registry. w3c-ccg/wallet-attached-storage-spec#64 (1 comment by @dmitrizagidulin)
-
w3c-ccg/community
-
1 issue opened.
-
[PROPOSED WORK ITEM] Interoperability Task Force w3c-ccg/community#262, by @denkeni.
-
-
1 issue received 2 new comments.
-
[PROPOSED WORK ITEM] Interoperability Task Force w3c-ccg/community#262 (2 comments by @bumblefudge, @wip-abramson)
-
-
1 pull request opened.
-
Update default assignees w3c-ccg/community#263, by @denkeni.
-
w3c-ccg/capability-based-storage-tf
-
3 issues opened.
-
Agenda for the 2026-10-01 TF Call w3c-ccg/capability-based-storage-tf#5, by @dmitrizagidulin.
-
Agenda for the 2026-09-17 TF call. w3c-ccg/capability-based-storage-tf#4, by @dmitrizagidulin.
-
No agenda nor event cancellation for 2026-09-03 w3c-ccg/capability-based-storage-tf#3, by @TallTed.
-
-
2 issues closed.
-
Agenda for Capability Based Storage TF Call 2026-08-20 w3c-ccg/capability-based-storage-tf#2.
-
No agenda nor event cancellation for 2026-09-03 w3c-ccg/capability-based-storage-tf#3.
-
-
3 issues received 7 new comments.
-
Agenda for the 2026-09-17 TF call. w3c-ccg/capability-based-storage-tf#4 (5 comments by @gobengo, @TallTed)
-
No agenda nor event cancellation for 2026-09-03 w3c-ccg/capability-based-storage-tf#3 (1 comment by @dmitrizagidulin)
-
w3c-ccg/vc-api-verifier-test-suite
-
1 issue opened.
-
invalid VC DI test around `proof.created` w3c-ccg/vc-api-verifier-test-suite#48, by @lemoustachiste.
-
-
1 pull request closed.
-
fix: force a fresh version of this dep to get around vulnerability ad… w3c-ccg/vc-api-verifier-test-suite#47.
-
w3c-ccg/vc-test-suite-implementations
-
1 issue received 1 new comment.
-
w3c-ccg/vc-test-suite-implementations#135 (1 comment by @BigBlueHat)
-
-
1 pull request merged.
-
Update DigitalBazaar config. w3c-ccg/vc-test-suite-implementations#141.
-
w3c-ccg/data-integrity-test-suite-assertion
-
1 pull request received 1 new comment.
-
Fix eddsa-rdfc-2022 previousProof chain tests w3c-ccg/data-integrity-test-suite-assertion#134 (1 comment by @PatStLouis)
-
Capability-based Storage Task Force
Past meetings
-
2 meetings of the Capability-based Storage Task Force.
Participants
-
3 participants joined the Capability-based Storage Task Force.
-
Phillip Long joined.
-
Aaron Olson joined.
-
Kayode Ezike joined.
-
Past meetings
-
5 meetings.
Participants
-
14 participants joined.
-
Anton Sokolov (Tyche Institute) joined.
-
Mihir Bommisetty joined.
-
Abtin Aghagolian joined.
-
Anna Adamczyk (Axelote sp. z o.o.) joined.
-
Otto Mora joined.
-
Binbin Shen (Grid Heap, Inc.) joined.
-
Naomi Yoshizawa (W3C) joined.
-
Anrunya Patole joined.
-
Maxime Mansiet (2060.io) joined.
-
Kevin Triplett joined.
-
Alison Mukoma (TumiTrust) joined.
-
Christian Brenner (cb42 consulting) joined.
-
Jorge Flores (Entidad) joined.
-
Erica Trump (VeraLearning) joined.
-
-
1 participant left.
-
Yatharth (Arjun) Mishra left.
-
-
8 organizations joined.
-
Tyche Institute joined.
-
Axelote sp. z o.o. joined.
-
Grid Heap, Inc. joined.
-
2060.io joined.
-
TumiTrust joined.
-
cb42 consulting joined.
-
Entidad joined.
-
VeraLearning joined.
-
GitHub
w3c-ccg/zcap-spec
-
14 issues opened.
-
spec should offer guidance for how to file an implementation report w3c-ccg/zcap-spec#93, by @gobengo.
-
https://w3id.org/zcap/v1 should serve JSON-LD context published from w3c-ccg/zcap-spec repo w3c-ccg/zcap-spec#89, by @gobengo.
-
zcap-spec repo should contain intended referent of JSON-LD context URL https://w3id.org/zcap/v1 w3c-ccg/zcap-spec#86, by @gobengo.
-
examples should use `proofValue`, not `signatureValue` w3c-ccg/zcap-spec#85, by @gobengo.
-
Clarify `allowedAction` and `caveat.type` ranges are to be specified by profiles of ZCAP spec w3c-ccg/zcap-spec#84, by @kezike.
-
Add a plan for Milestone v0.5 w3c-ccg/zcap-spec#83, by @gobengo.
-
why is the root ZCAP not signed? w3c-ccg/zcap-spec#79, by @lemoustachiste.
-
Unknown Delegate w3c-ccg/zcap-spec#75, by @alanhkarp.
-
Move normative 'Root Capability' and 'Delegated Capability' sections out of Introduction w3c-ccg/zcap-spec#74, by @dmitrizagidulin.
-
Pausing a delegation: a reversible suspension state distinct from revocation w3c-ccg/zcap-spec#73, by @moisesja.
-
Combined zcap spec vs separate standalone specs w3c-ccg/zcap-spec#72, by @dmitrizagidulin.
-
validFrom / nbf field? w3c-ccg/zcap-spec#71, by @dmitrizagidulin.
-
Normalize proof terminology w3c-ccg/zcap-spec#70, by @dmitrizagidulin.
-
Update examples to use recent Data Integrity suites w3c-ccg/zcap-spec#69, by @dmitrizagidulin.
-
-
6 issues closed.
-
Remove TODOs expressed as spec text so the spec is more readable w3c-ccg/zcap-spec#56.
-
examples should use `proofValue`, not `signatureValue` w3c-ccg/zcap-spec#85.
-
Combined zcap spec vs separate standalone specs w3c-ccg/zcap-spec#72.
-
Normalize proof terminology w3c-ccg/zcap-spec#70.
-
Why embed the caveat in the ocap? w3c-ccg/zcap-spec#11.
-
19 issues received 38 new comments.
-
Combined zcap spec vs separate standalone specs w3c-ccg/zcap-spec#72 (6 comments by @dlongley, @dmitrizagidulin, @gobengo, @longpd, @msporny)
-
why is the root ZCAP not signed? w3c-ccg/zcap-spec#79 (4 comments by @dlongley, @dmitrizagidulin, @gobengo, @lemoustachiste)
-
Update examples to use recent Data Integrity suites w3c-ccg/zcap-spec#69 (2 comments by @dmitrizagidulin, @gobengo)
-
Clarify `allowedAction` and `caveat.type` ranges are to be specified by profiles of ZCAP spec w3c-ccg/zcap-spec#84 (2 comments by @dlongley, @gobengo)
-
Move normative 'Root Capability' and 'Delegated Capability' sections out of Introduction w3c-ccg/zcap-spec#74 (2 comments by @gobengo)
-
Must every capability document have an associated id? w3c-ccg/zcap-spec#16 (2 comments by @dmitrizagidulin, @gobengo)
-
Remove TODOs expressed as spec text so the spec is more readable w3c-ccg/zcap-spec#56 (2 comments by @gobengo)
-
examples should use `proofValue`, not `signatureValue` w3c-ccg/zcap-spec#85 (2 comments by @gobengo)
-
Pausing a delegation: a reversible suspension state distinct from revocation w3c-ccg/zcap-spec#73 (2 comments by @bumblefudge, @gobengo)
-
https://w3id.org/zcap/v1 should serve JSON-LD context published from w3c-ccg/zcap-spec repo w3c-ccg/zcap-spec#89 (1 comment by @gobengo)
-
zcap-spec repo should contain intended referent of JSON-LD context URL https://w3id.org/zcap/v1 w3c-ccg/zcap-spec#86 (1 comment by @gobengo)
-
-
15 pull requests opened.
-
add invocation examples and new sections for Invocation HTTP Request and Invocation JSON w3c-ccg/zcap-spec#92, by @gobengo.
-
Move section "Capabilities vs. Access Control Lists" out of "Introduction" to "Capabilities" w3c-ccg/zcap-spec#91, by @gobengo.
-
GitHub Pages can host prerelease/past versions of spec by deploying to `/{version}/` not just `/` w3c-ccg/zcap-spec#90, by @gobengo.
-
Add contexts/zcap-v1.jsonld so we can maintain the JSON-LD context in this repo w3c-ccg/zcap-spec#88, by @gobengo.
-
fix poor formatting from code snippets that used unescaped characters w3c-ccg/zcap-spec#82, by @gobengo.
-
changelog respec warning issue w3c-ccg/zcap-spec#80, by @gobengo.
-
fix Example 2 capabilityInvocation proof does not express the full invoked capability w3c-ccg/zcap-spec#77, by @gobengo.
-
WIP: v0.4.0-draft - This PR shows all changes in editor's draft since v0.3.0 w3c-ccg/zcap-spec#76, by @gobengo.
-
move examples out of index.html and into standalone files that respec includes via `data-include` w3c-ccg/zcap-spec#68, by @gobengo.
-
Move normative behavior for proving invocations from Introduction section to Invocation section w3c-ccg/zcap-spec#67, by @gobengo.
-
fix @context of examples to satisfy normative requirements w3c-ccg/zcap-spec#66, by @gobengo.
-
editorial cleanup of inline 'TODO:', '[link]', and '[Note:...]' w3c-ccg/zcap-spec#65, by @gobengo.
-
-
13 pull requests merged.
-
Add contexts/zcap-v1.jsonld so we can maintain the JSON-LD context in this repo w3c-ccg/zcap-spec#88.
-
add invocation examples and new sections for Invocation HTTP Request and Invocation JSON w3c-ccg/zcap-spec#92.
-
fix Example 2 capabilityInvocation proof does not express the full invoked capability w3c-ccg/zcap-spec#77.
-
fix poor formatting from code snippets that used unescaped characters w3c-ccg/zcap-spec#82.
-
changelog respec warning issue w3c-ccg/zcap-spec#80.
-
editorial cleanup of inline 'TODO:', '[link]', and '[Note:...]' w3c-ccg/zcap-spec#65.
-
fix @context of examples to satisfy normative requirements w3c-ccg/zcap-spec#66.
-
1 pull request closed.
-
6 pull requests received 31 new comments.
-
clarify delegation proof requires `capabilityChain` and update examples 3 & 4 to have a `capabilityChain` w3c-ccg/zcap-spec#78 (19 comments by @gobengo, @kezike)
-
fix Example 2 capabilityInvocation proof does not express the full invoked capability w3c-ccg/zcap-spec#77 (7 comments by @dlongley, @dmitrizagidulin, @gobengo)
-
editorial cleanup of inline 'TODO:', '[link]', and '[Note:...]' w3c-ccg/zcap-spec#65 (2 comments by @gobengo, @TallTed)
-
Add contexts/zcap-v1.jsonld so we can maintain the JSON-LD context in this repo w3c-ccg/zcap-spec#88 (1 comment by @gobengo)
-
fix ambiguous grammar in Capabilities section note "understands for what the meaning of those arguments are and for what they may be used" w3c-ccg/zcap-spec#81 (1 comment by @TallTed)
-
move examples out of index.html and into standalone files that respec includes via `data-include` w3c-ccg/zcap-spec#68 (1 comment by @gobengo)
-
w3c-ccg/data-integrity-test-suite-assertion
-
2 pull requests opened.
-
Fix eddsa-rdfc-2022 previousProof chain tests w3c-ccg/data-integrity-test-suite-assertion#134, by @BigBlueHat.
-
Update CI to Node.js 24 and setup-node@v4 w3c-ccg/data-integrity-test-suite-assertion#133, by @BigBlueHat.
-
w3c-ccg/community
-
1 issue received 1 new comment.
-
[PROPOSED WORK ITEM] Cryptographic Continuity and Post-Quantum Transition Patterns w3c-ccg/community#260 (1 comment by @myvault777)
-
w3c-ccg/vc-test-suite-implementations
-
2 pull requests opened.
-
Update DigitalBazaar config. w3c-ccg/vc-test-suite-implementations#141, by @BigBlueHat.
-
Update LearnCard VC-API endpoint and DID w3c-ccg/vc-test-suite-implementations#140, by @Custard7.
-
-
1 pull request merged.
-
Update LearnCard VC-API endpoint and DID w3c-ccg/vc-test-suite-implementations#140.
-
w3c-ccg/wallet-attached-storage-spec
-
1 issue opened.
-
combine description and meta objects for collections w3c-ccg/wallet-attached-storage-spec#63, by @jchartrand.
-
-
1 issue received 1 new comment.
-
combine description and meta objects for collections w3c-ccg/wallet-attached-storage-spec#63 (1 comment by @dmitrizagidulin)
-
-
6 pull requests opened.
-
Add hmac descriptor validation. w3c-ccg/wallet-attached-storage-spec#67, by @dmitrizagidulin.
-
Update roadmap / version history. w3c-ccg/wallet-attached-storage-spec#66, by @dmitrizagidulin.
-
Make Cavage draft 12 the required signature suite; RFC 9421 is future direction. w3c-ccg/wallet-attached-storage-spec#65, by @dmitrizagidulin.
-
Admit did:webvh Space controllers via a controller DID method registry. w3c-ccg/wallet-attached-storage-spec#64, by @dmitrizagidulin.
-
Add EDV-over-WAS profile appendix and encryption description versioning. w3c-ccg/wallet-attached-storage-spec#62, by @dmitrizagidulin.
-
Reserve the /import endpoint. w3c-ccg/wallet-attached-storage-spec#61, by @dmitrizagidulin.
-
-
5 pull requests merged.
-
Add optional `public` flag to Collection listing items w3c-ccg/wallet-attached-storage-spec#60.
-
Update roadmap / version history. w3c-ccg/wallet-attached-storage-spec#66.
-
Add EDV-over-WAS profile appendix and encryption description versioning. w3c-ccg/wallet-attached-storage-spec#62.
-
Add EDV-over-WAS section and 'chunked resource' definitions. w3c-ccg/wallet-attached-storage-spec#59.
-
Reserve the /import endpoint. w3c-ccg/wallet-attached-storage-spec#61.
-
-
3 pull requests received 3 new comments.
-
Add EDV-over-WAS profile appendix and encryption description versioning. w3c-ccg/wallet-attached-storage-spec#62 (1 comment by @dmitrizagidulin)
-
Add EDV-over-WAS section and 'chunked resource' definitions. w3c-ccg/wallet-attached-storage-spec#59 (1 comment by @dmitrizagidulin)
-
Reserve the /import endpoint. w3c-ccg/wallet-attached-storage-spec#61 (1 comment by @dmitrizagidulin)
-
w3c-ccg/capability-based-storage-tf
-
1 issue opened.
-
Agenda for Capability Based Storage TF Call 2026-08-20 w3c-ccg/capability-based-storage-tf#2, by @dmitrizagidulin.
-
-
1 issue closed.
-
Agenda for Capability Based Storage TF Call for 2026-08-06 w3c-ccg/capability-based-storage-tf#1.
-
-
2 issues received 6 new comments.
-
Agenda for Capability Based Storage TF Call 2026-08-20 w3c-ccg/capability-based-storage-tf#2 (3 comments by @dmitrizagidulin, @TallTed)
-
Agenda for Capability Based Storage TF Call for 2026-08-06 w3c-ccg/capability-based-storage-tf#1 (3 comments by @dmitrizagidulin, @moisesja)
-
w3c-ccg/vc-api-verifier-test-suite
-
1 issue received 1 new comment.
-
Update the default issuer in VC JWT tests w3c-ccg/vc-api-verifier-test-suite#33 (1 comment by @ashushukla0412)
-
w3c-ccg/cg-archiver
-
1 issue opened.
-
Ensure AI doesn't over-inject topic markers w3c-ccg/cg-archiver#2, by @msporny.
-
w3c-ccg/respec-oas
-
1 pull request opened.
-
Fix allof case where allof is an array not an object w3c-ccg/respec-oas#5, by @eric-schuh.
-
-
1 pull request merged.
-
Fix allof case where allof is an array not an object w3c-ccg/respec-oas#5.
-
Capability-based Storage Task Force
Past meetings
-
1 meeting of the Capability-based Storage Task Force.