Solid Gate

Your Solid pod, with an API surface you define.

What is this?

Solid is great for storing your personal RDF data in a pod you control. The problem: every app that wants to read your data needs to speak LDP, understand your specific vocabularies, and parse RDF. Almost none do.

Solid Gate is the adapter layer. Define a mapping template once, and your pod data is exposed as whatever format a consuming app actually wants — RSS, iCal, JSON, a REST endpoint, anything.

Think of it as SPARQL-Anything in reverse: SPARQL-Anything lets you query arbitrary formats as if they were RDF. Solid Gate lets you serve your RDF as if it were any arbitrary format.

How it works

Authenticate — grant Solid Gate read access to your pod via Solid OIDC
Deploy a template — pick one from the library or write your own
Get a stable URL — your transformed data is cached and served at a permanent endpoint
Stays fresh — Solid Notifications trigger recomputation when your pod data changes; stale cache is served in between

Your Solid Pod  →  Solid Gate  →  stable URL (RSS / iCal / JSON / ...)
                       ↑
             mapping template
            (yours or community)

Example use cases

Bookmarks → RSS — publish a "what I'm reading" feed from your pod bookmarks
Events → iCal — expose your RDF event data to any calendar app
Contacts → vCard — bridge your pod contacts to legacy address book apps
Any RDF → REST API — give legacy apps a familiar interface to your pod data

Deployment

Self-hosted

Coming soon.

Hosted

Coming soon. Authenticate with your Solid identity, deploy a template, done.

Status

Early design phase. Part of the Aleph Garden personal semantic web project.

Solid Project
SPARQL-Anything — the spiritual mirror of this project

2 KiB Raw Blame History