-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of WAC implementations #139
Comments
I implemented rww-play using the ACL ontology. |
https://www.w3.org/wiki/WebAccessControl#Implementations includes some. The wiki hasn't been updated for awhile though. https://dokie.li/ used to create ACLs - its function is not currently called but I can bring that back in. Implements WAC-Allow. I was close to implementing Signing HTTP Messages in dokieli around the time we were reviewing the spec :S Got sidetracked. Perhaps we should revisit https://github.com/solid/authentication-panel/blob/master/HttpSignature.md ? |
I implemented support in a client library ( I did not (intentionally, at least :) ) diverge from the ontology. |
Test suite for WAC: https://github.com/solid/web-access-control-tests |
Possibly irrelevant : solid-rest will allow a backend to pass access information. Currently this means that, for file:// URLs, it checks the native file system permissions and sends a wac-allow header based on the local permissions. For example, write perms on *nix get sent back as a wac-allow header of user="Write Append Control". |
It would be helpful to have a document listing all the servers and clients libraries that implemented the WAC starting from the acl ontology. Also useful would be for each of those to have some idea how they may have diverged from the ontology.
The text was updated successfully, but these errors were encountered: