-
Notifications
You must be signed in to change notification settings - Fork 6
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
Restore the juggling of webids to that Group ACLs work again #38
Comments
Can it be simplified ?. To just add the
On NSS this does allow the contact Group to be used as an acl Group (tried locally). |
This seem to solve the issue, but with a strange
|
As can be seen below
|
@timbl The question of 2 contacts sharing a same webID is depending on the meaning of Person.
As
|
The tabont: thing looks like then result of smush processing .. historically the mashlib, in its role of making mashups of data form multiple sources would replaces all occurrences of multiple URIs for the same thing with just one of them ... and then IIRC use something like tabont:ui to track the orignal ones so they were not completely lost. We need to make sure those features are disabled. Its the |
The tabont:uri is because we have not fixed linkeddata/rdflib.js#458... not wise to play with sameAs at all until that is fixed, or the sameAs will be processed internally by the store, leading to a tabont:uri (I think solid-ui used to originally set the features of the store to [] but I bey that has been lost in the move to solid-logic just guessing.) |
As regards simplification, the version which has two 'member' arcs leads to confusion as to how many members in the group |
PR #43 uses |
The way groups are stored has to be a compromise between the way to naturally one store them in an AddressBook's vcard:Group (using an internal URI in the local vcard) and the needs of the ACL system, where the public webId of the person must be used directly in the group shape, as that is the only place it looks.
This means that when a we have bother the local card ID for the person and their WebId, we must store it like this.
or
This means the ACL system works without modification, but the contacts management has to be smarter.
This functionality existed recently (as group ACLs worked) but has broken in the splitting out of the logic into a separate file.
Note owl:sameAs is self-inverse, and so it is unreasonable to require it to be one way around or the other way round, they mean the same thing.
The text was updated successfully, but these errors were encountered: