You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we used N3-patch like we do for containers and resources, it would uniformize our API and it would also allow to remove permissions without risks (right now we first GET the WAC permissions, filter out the permissions we don't want anymore, and then do a PUT, but if the resource is modified between the GET and the PUT, data may be lost).
Of course we could also support Sparql-Patch if we keep this format for other resources...
Even if nothing in the WAC spec prevent someone with a acl:Control right to write whatever they want in a WAC permission, we should probably check that only WAC-related predicates are added or removed. The @type and acl:accessTo triples (added automatically on creation) should not be modified.
The text was updated successfully, but these errors were encountered:
Currently WAC permissions use a special format to update WAC permissions through PATCH, as can be seen here:
https://github.com/assemblee-virtuelle/semapps/blob/next/src/frontend/packages/auth-provider/src/authProvider.js#L296-L310
If we used N3-patch like we do for containers and resources, it would uniformize our API and it would also allow to remove permissions without risks (right now we first GET the WAC permissions, filter out the permissions we don't want anymore, and then do a PUT, but if the resource is modified between the GET and the PUT, data may be lost).
Of course we could also support Sparql-Patch if we keep this format for other resources...
Even if nothing in the WAC spec prevent someone with a
acl:Control
right to write whatever they want in a WAC permission, we should probably check that only WAC-related predicates are added or removed. The@type
andacl:accessTo
triples (added automatically on creation) should not be modified.The text was updated successfully, but these errors were encountered: