Issues

• Duplicate information in an invocation

  w3c-ccg/zcap-spec#139 · Filter by author alanhkarp opened on Oct 5, 2026

• An invocation zcap must be for a specific resource

  w3c-ccg/zcap-spec#138 · Filter by author alanhkarp opened on Oct 1, 2026

• avoid "A verifier will accept delegations" text, which could be interpreted as a normative requirement

  w3c-ccg/zcap-spec#137 · Filter by author gobengo opened on Oct 1, 2026
  

• do we need to require delegation.parentCapability since delegation.proof[].capabilityChain[-1] already embeds it

  w3c-ccg/zcap-spec#135 · Filter by author gobengo opened on Oct 1, 2026
  2

• allow root zcap to have a proof property

  w3c-ccg/zcap-spec#134 · Filter by author gobengo opened on Oct 1, 2026

• show example of providing a capability as a invocation parameter

  w3c-ccg/zcap-spec#130 · Filter by author gobengo opened on Oct 1, 2026
  1

• require allowedAction in delegated capability

  w3c-ccg/zcap-spec#129 · Filter by author gobengo opened on Oct 1, 2026

• url based attenuation /foo/?limit=5 authorizes /foo/?limit=5&limit=10 (et al)

  w3c-ccg/zcap-spec#127 · Filter by author gobengo opened on Sep 29, 2026
  4

• gh-pages: when I access /v0.3.0/ (or any version other than latest), I should see a warning that this is an old version, and a link I can click to go to the latest stable version

  w3c-ccg/zcap-spec#126 · Filter by author gobengo opened on Sep 17, 2026 · v0.5.0
  

• add JCS hash of zcap-v1.jsonld

  w3c-ccg/zcap-spec#125 · Filter by author gobengo opened on Sep 17, 2026

• zcap-spec 0.3.0 errata

  w3c-ccg/zcap-spec#123 · Filter by author gobengo opened on Sep 16, 2026
  2

• is invocationTarget required on delegated capability?

  w3c-ccg/zcap-spec#122 · Filter by author gobengo opened on Sep 16, 2026
  2

  

• prevention of CRLF "normalization" vandalism by GitHub

  w3c-ccg/zcap-spec#120 · Filter by author TallTed opened on Sep 14, 2026
  1

• release zcap-spec v0.4.0

  w3c-ccg/zcap-spec#112 · Filter by author gobengo opened on Sep 10, 2026 · v0.4.0
  

• drop "The capability action SHOULD be read or write."

  w3c-ccg/zcap-spec#109 · Filter by author gobengo opened on Sep 10, 2026

• drop @context property requirements

  w3c-ccg/zcap-spec#108 · Filter by author gobengo opened on Sep 10, 2026 · v0.5.0
  3

  

• 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 · Filter by author gobengo opened on Sep 9, 2026 · 2026-10-01 W3C CCG Capability-based Storage TF Call
  1

• reword: "The key used to create the HTTP signature must be either ..." in Invocation HTTP Signature

  normative
  w3c-ccg/zcap-spec#103 · Filter by author gobengo opened on Sep 9, 2026 · 2026-09-17 W3C CCG Capability-based Storage TF Call
  6

• document how to realize lds-ocap cloud storage scenario using zcap

  usecase
  w3c-ccg/zcap-spec#102 · Filter by author gobengo opened on Sep 3, 2026
  1

  

• Make context files immutable.

  w3c-ccg/zcap-spec#101 · Filter by author BigBlueHat opened on Sep 2, 2026 · v0.4.0
  16

  

• spec should offer guidance for how to file an implementation report

  w3c-ccg/zcap-spec#93 · Filter by author gobengo opened on Aug 27, 2026
  1

• https://w3id.org/zcap/v1 should serve JSON-LD context published from w3c-ccg/zcap-spec repo

  w3c-ccg/zcap-spec#89 · Filter by author gobengo opened on Aug 24, 2026 · v0.5.0
  1

  

• Clarify allowedAction and caveat.type ranges are to be specified by profiles of ZCAP spec

  w3c-ccg/zcap-spec#84 · Filter by author kezike opened on Aug 20, 2026
  7

  

• Add a plan for Milestone v0.5

  w3c-ccg/zcap-spec#83 · Filter by author gobengo opened on Aug 17, 2026 · v0.5.0
  2

  

• why is the root ZCAP not signed?

  w3c-ccg/zcap-spec#79 · Filter by author lemoustachiste opened on Aug 11, 2026
  4