Re: WAC 2.0: Secure Access Conditions - draft published

Hi Melvin,

On Wednesday, April 15th, 2026 at 7:18 AM, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

> The key difference is in evaluation semantics: if a server encounters a condition it does not support, the authorization is treated as non-applicable. This ensures that access constraints are never silently ignored and avoids fail-open behaviour in mixed-capability deployments.
> 
> This is a breaking change, hence versioned as WAC 2.0. Servers that do not understand a condition must reject it, rather than evaluating the authorization as if the condition were absent.
> 
> Two implementations exist today:
> - JavaScriptSolidServer (JSS)
> - VisionClaw (via JSS) [3]
> 
> Feedback is very welcome, particularly from implementers. I’m also looking for co-editors and reviewers interested in shaping this work.

In a different PR https://github.com/solid/specification/pull/807
We established that based on technical merit CG can make breaking changes to CG-DRAFTs

"To your process point: the editor's draft is iteratively updated. If a future proposal (such as a PROV-O implementation) achieves sufficient support, it will naturally supersede and replace this text, even if that results in a non-backwards-compatible change."

If you are convinced that your changes are sound on technical merit. I would suggest you to make a PR directly on WAC CG-DRAFT and make a case for them. I beleive you will receive more feedback on such PR than on a fork.

You are also welcome, as any CG participant, to propose meeting agenda topics via:
* https://hackmd.io/@solid/cg-weekly
* this mailing list
* matrix

Best,
elf Pavlik

Received on Thursday, 3 September 2026 16:48:19 UTC