Relation between ACL, vcard:Group and vcard:Kind subclasses
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- authorization, documentation, security
Research direction
Start by comparing the Solid Protocol, WAC specification, and vCard RDF ontology sections linked in the issue. Trace how vcard:Group, vcard:Kind, PersonalProfileDocument, and ACL access subjects are defined. Done means the relationship and whether organizations can be ACL subjects are answered clearly in the specification or issue documentation.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- HTML
- Stars
- 563
- Forks
- 110
- Avg merge
- 5d 7m
- Merged PRs (30d)
- 3
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from solid/specification
-
new-work-item
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#806 · 11 comments · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#804 · 9 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
solid/specification#799 · 1 reaction ·
-
topic: resource access
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#797 · 4 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#788 · 4 comments · 1 reaction ·
All issues in solid/specification
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
qgis/QGIS-Plugins-Website#459 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug status/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
prowler-cloud/prowler#12887 · 1 comment ·
Maintainers usually reply within 1 day
-
A column of four 4-digit numbers is masked as a card number since line breaks became a separatorOpenbug P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
uttrflow/uttrflow-swift#2507 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
boxlite-ai/boxlite#1729 ·
Maintainers usually reply within 1 day