Skip to content
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

Improve WAC groups management API #1259

Open
srosset81 opened this issue May 23, 2024 · 0 comments
Open

Improve WAC groups management API #1259

srosset81 opened this issue May 23, 2024 · 0 comments

Comments

@srosset81
Copy link
Contributor

srosset81 commented May 23, 2024

Right now we use a custom API to create groups (we must POST to the /_groups path)

However WAC groups can be created like any other resources. The only requirement in the specs is:

The acl:agentGroup predicate denotes a group of agents being given the access permission. The object of an acl:agentGroup statement is an instance of vcard:Group, where the members of the group are specified with the vcard:hasMember predicate.

It is up to the group owner to ensure that it is protected correctly.

WAC groups should be on the own named graphs, like any other LDP resource. It will be possible once we get rid of the Fuseki WAC extension.

They will probably be put in a /vcard/group container... which is where contacts groups are also located. It doesn't seem to be a problem (contact groups will be considered as valid WAC groups), but maybe we should do something on the frontend to not show automatically-generated groups (there are many of them, possibly one for every AS collection).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant