feat: reframe as hosted Walder with multi-tenancy and community hub
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
parent
a702dd69e6
commit
3735a9d077
1 changed files with 15 additions and 10 deletions
25
README.md
25
README.md
|
|
@ -1,27 +1,27 @@
|
||||||
# Solid Gate
|
# Solid Gate
|
||||||
|
|
||||||
> Your Solid pod, with an API surface you define.
|
> Hosted, multi-tenant [Walder](https://github.com/KNowledgeOnWebScale/walder) with a community template hub.
|
||||||
|
|
||||||
## What is this?
|
## What is this?
|
||||||
|
|
||||||
[Solid](https://solidproject.org/) 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](https://solidproject.org/) 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.
|
Solid Gate is the hosted service layer on top of [Walder](https://github.com/KNowledgeOnWebScale/walder) — a tool that builds websites and APIs on top of decentralized knowledge graphs. Walder proved the concept. Solid Gate productizes it: multi-tenancy, Solid OIDC auth per user, cache invalidation via Solid Notifications, and a community hub of one-click templates for common transformations.
|
||||||
|
|
||||||
Think of it as [SPARQL-Anything](https://sparql-anything.cc/) 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.
|
Think of it as [SPARQL-Anything](https://sparql-anything.cc/) 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
|
## How it works
|
||||||
|
|
||||||
1. **Authenticate** — grant Solid Gate read access to your pod via Solid OIDC
|
1. **Authenticate** — grant Solid Gate read access to your pod via Solid OIDC
|
||||||
2. **Deploy a template** — pick one from the library or write your own
|
2. **Deploy a template** — pick one from the community library or bring your own
|
||||||
3. **Get a stable URL** — your transformed data is cached and served at a permanent endpoint
|
3. **Get a stable URL** — your transformed data is cached and served at a permanent endpoint
|
||||||
4. **Stays fresh** — [Solid Notifications](https://solid.github.io/notifications/protocol) trigger recomputation when your pod data changes; stale cache is served in between
|
4. **Stays fresh** — [Solid Notifications](https://solid.github.io/notifications/protocol) trigger recomputation when your pod data changes; stale cache served in between
|
||||||
|
|
||||||
```
|
```
|
||||||
Your Solid Pod → Solid Gate → stable URL (RSS / iCal / JSON / ...)
|
Your Solid Pod → Solid Gate (Walder) → stable URL (RSS / iCal / JSON / ...)
|
||||||
↑
|
↑
|
||||||
mapping template
|
community template
|
||||||
(yours or community)
|
(or bring your own)
|
||||||
```
|
```
|
||||||
|
|
||||||
## Example use cases
|
## Example use cases
|
||||||
|
|
@ -31,6 +31,10 @@ Your Solid Pod → Solid Gate → stable URL (RSS / iCal / JSON / ...)
|
||||||
- **Contacts → vCard** — bridge your pod contacts to legacy address book apps
|
- **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
|
- **Any RDF → REST API** — give legacy apps a familiar interface to your pod data
|
||||||
|
|
||||||
|
## The community hub
|
||||||
|
|
||||||
|
The template library is the core value. Common transformations are one-click deploys. Power users publish their own. Think Vercel for Walder configs.
|
||||||
|
|
||||||
## Deployment
|
## Deployment
|
||||||
|
|
||||||
### Self-hosted
|
### Self-hosted
|
||||||
|
|
@ -45,7 +49,8 @@ Coming soon. Authenticate with your Solid identity, deploy a template, done.
|
||||||
|
|
||||||
Early design phase. Part of the [Aleph Garden](https://aph.gdn) personal semantic web project.
|
Early design phase. Part of the [Aleph Garden](https://aph.gdn) personal semantic web project.
|
||||||
|
|
||||||
## Related
|
## Prior art
|
||||||
|
|
||||||
- [Solid Project](https://solidproject.org/)
|
- [Walder](https://github.com/KNowledgeOnWebScale/walder) — the engine underneath; research prototype from IDLab/KNoWS (Ghent). Proved the concept, never productized.
|
||||||
- [SPARQL-Anything](https://sparql-anything.cc/) — the spiritual mirror of this project
|
- [SPARQL-Anything](https://sparql-anything.cc/) — the spiritual mirror of this project
|
||||||
|
- [ActivityPods](https://activitypods.org/) — ActivityPub + Solid combined; adjacent but different problem
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue