access-control

Enforce named-graph access control for RDF datasets using WAC and ACP.

8|1|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/sparq-org/sparq --skill access-control-sparq-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: access-control
Source: https://github.com/sparq-org/sparq/tree/main/skills/access-control
Command: npx skills add https://github.com/sparq-org/sparq --skill access-control-sparq-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sparq-core, sparq-engine, sparq-reason, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill implements Solid-style access control for RDF datasets, enabling fine-grained access control at the graph level.

Core Features & Use Cases

  • Named-Graph Access Control: Manages access control at the level of individual named graphs within an RDF dataset.
  • WAC/ACP Support: Integrates with Web Access Control (WAC) and Access Control Profile (ACP) standards.
  • Authorization View Materialization: Converts access control documents into a queryable authorization view.
  • Session-based Access: Filters SPARQL queries and updates based on the session's authorized graph set.
  • Use Case: Suitable for applications requiring fine-grained access control for their RDF data, such as Solid Pod services.

Quick Start

Load an RDF dataset into Sparq and use the materialize_wac function to create an authorization view from the WAC documents. Then, execute a SPARQL query using query_as to retrieve only the authorized data.

Frequently Asked Questions about access-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce access control for RDF datasets at the named-graph level?

Named-graph access control restricts SPARQL query results by materializing WAC or ACP documents into an authorization view, filtering data based on the session's authorized graph set to ensure users only retrieve permitted named graphs.

Can I use Web Access Control or ACP standards to manage Solid Pod authorization views?

Yes, both Web Access Control (WAC) and Access Control Profile (ACP) standards are supported. The system integrates these protocols to convert access control documents into queryable authorization views for fine-grained RDF dataset management.

What's the best way to filter SPARQL queries based on session authorization?

The best way to filter SPARQL queries by session authorization is to materialize the authorized graph set from access control documents, then execute queries using a session-aware function to retrieve only permitted data.

Do I need sparq-solid to implement fine-grained RDF access control?

Yes, implementing fine-grained RDF access control requires the sparq-solid integration alongside sparq-core, sparq-engine, and sparq-reason dependencies to enforce graph-level restrictions and materialize authorization views for Solid Pod services.

How does materialize_wac function create a queryable authorization view?

The materialize_wac function converts WAC documents into a queryable authorization view, which then restricts SPARQL query execution to retrieve only the data authorized for the current session.