Contacts Group ACL : some tests on CSS and NSS
Closed this issue · 3 comments
I'm logged-in with https://bourgeoa.solidcommunity.net/profile/card#me
Group ACL is https://solidos.solidcommunity.net/Contacts/Group/SolidOS_Team.ttl#this
and able to edit the file http://localhost/public/test.txt
The CSS server has been created using https://github.com/solidos/css-mashlib. Start the server with npm run start
It is running CSS 5.0.1 and mashlib 1.8.5
This is part of the SolidOS development setup. Documentation is missing. Shall be soon
I went my AddressBook and was prompted to fix the group structure, agreed, it said it fixed t. But then people in the group could not get access.
The group file had before been hand-edited to have the webids directly as members of the group, like:
@prefix c2: <https://timbl.inrupt.net/profile/card#>.
# ...
c2:me owl:sameAs in:this; vcard:fn "Tim BL (at inrupt.net)".
:this
a vcard:Group;
vcard:fn "Office of TBL Staff";
vcard:hasMember
c:me, c0:me, c2:me, c3:me , c4:me .
but after the fix, it was the wrong way round, ending
# ...
<https://timbl.com/timbl/Data/Contacts/Person/003FC8C8-634C-4C29-A0BF-649C65DC546D/index.ttl#this> <http://www.w3.org/2002/07/owl#sameAs> <https://timbl.inrupt.net/profile/card#me>.
<#this> <http://www.w3.org/2006/vcard/ns#fn> "Office of TBL Staff";
a <http://www.w3.org/2006/vcard/ns#Group>;
<http://www.w3.org/2006/vcard/ns#hasMember> <https://timbl.com/timbl/Data/Contacts/Person/504A6E77-8029-4EF7-983C-4565E240944A/index.ttl#this>, <https://timbl.com/timbl/Data/Contacts/Person/2A2E2A6B-D1AB-4FB7-8A73-F30600C34098/index.ttl#this>, <https://timbl.com/timbl/Data/Contacts/Person/9784f082-bd66-4ed7-bfe0-e1c868d790b6/index.ttl#this>, <https://timbl.com/timbl/Data/Contacts/Person/9db8dd2a-3828-4ac8-98e0-a6ddc728afae/index.ttl#this>, <https://timbl.com/timbl/Data/Contacts/Person/003FC8C8-634C-4C29-A0BF-649C65DC546D/index.ttl#this>.
In this form the group access does not work with CSS.
OK.
I shall look at the code to see if there is a way to cover your situation (not the old data-model neither the new one).
To resolve your problem you can just apply the revert function in the tools and reload the contact-pane. The app will propose a migration that will work. Tested without issue.