Conversation
csarven
left a comment
There was a problem hiding this comment.
The CG did not call for something like this let alone for solid26.
Based on the data published by the CG: https://github.com/w3c-cg/solid/blob/main/implementations/wac-acp.2026-04-01.csv , I think it would be more sensible / useful to help the outlier implementations align with the rest of the ecosystem. So, perhaps the suggestions in this document should be passed on to implementations that would like to conform to WAC if they are arriving from ACP.
|
I think this should be a separate document which could be referenced from State of Solid 26 report as work in progress. |
|
I am not sure whether the target audience of this content is the same or sufficiently overlaps with the target audience of the Solid26 Implementation Guide. My gut feeling is that transformations from ACP to WAC and vice versa are an implementation detail that is not universally applicable across all clients... Clients might choose to handle their implementations differently and distinctly / in separate style, especially given the advisement of Solid26 to consider relying on dedicated authorization applications. |
Adding a section about WAC & ACP based on #776 (comment)
Preview