Proposal: Access-Controlled SPARQL Query over a Solid Pod
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Problem. There's no standard way to query a pod's RDF server-side — clients must fetch whole resources and filter locally.
Proposal. A read-only HTTP endpoint answering SPARQL over a pod, returning only the triples the authenticated agent may Read. A new read interface layered on the pod's existing authorization (WAC/ACP) — authentication-mechanism-agnostic, like the core Solid Protocol; not a new authorization model or wire protocol. Invariant: a query never reveals a triple the agent couldn't read directly.
Draft. https://github.com/jeswr/solid-specs/tree/main/specs/access-controlled-query
Live preview. https://jeswr.github.io/solid-specs/specs/access-controlled-query/
Status. Unofficial editor's draft, offered for the group's consideration and discussion.
Contributor guide
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.
Research direction
Start with the unofficial editor's draft at specs/access-controlled-query and compare it with the live preview linked in the issue. Determine whether the Solid group's requested outcome is a defined specification change and what review or acceptance criteria would mark the proposal complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authorization, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100