Relation between ACL, vcard:Group and vcard:Kind subclasses
Chiyo-no-sake opened this issue · 0 comments
The SOLID Specification states that a group is represented by having a type of vcard:Group
.
Then members of the vcard:Group
can be added using the vcard:hasMember
.
However, the vCard ontology declares that vcard:hasMember
can point to subclasses of the vcard:Kind
class.
Does this mean that the personal profile document (pointed by the WebId .../card#me
) must be a subclass of type vcard:Kind
(such as vcard:Individual
)?
Since webIds already are of type PersonalProfileDocument
, how can they be added to a group that requires them to be of type vcard:Individual
?
Also how does the whole ACL thing applies when a pod wants to use also the other classes such as vcard:Organization
?
Is it possible to use an Organization as an access subject for ACLs?
sources:
I read the solid specification here: https://solidproject.org/TR/protocol
Along with the WAC Spec: https://solid.github.io/web-access-control-spec/
And the vcard onthology here: https://www.w3.org/TR/vcard-rdf/#d4e1667