sempods

the index

One page instead of hunting through six hosts

sempods is a specification, an implementation, a set of published artifacts and a handful of hosts that each do exactly one thing. That is the right shape for the project and a bad shape for a first visit, so this page says what each one is and why you would open it.

Read

  • spec.sempods.org — the specification: core chapters for contexts, grants, authorization, CRUD, SPARQL and find, plus optional modules for MCP, media and an OIDC bridge. Every normative statement carries an identifier and its own anchor, so it can be cited rather than paraphrased. Descriptive until 0.1.
  • the HTTP surface — the OpenAPI descriptions rendered as a client. The closest thing to reading the specification with your hands.
  • schema.sempods.org — the vocabulary the requirements are written against. It negotiates content: Turtle for a program, a readable page for a browser, and a module identifier reaches its own chapter.
  • Governance — how a requirement is added, reworded, withdrawn, and — only until 0.1 is tagged — deleted outright.

Code

  • sempods-spec — the specification's repository. The chapters, the OpenAPI descriptions and the vocabulary are all authored here; the rendered site above is built from it.
  • sempods-kotlin — the reference implementation: server, client, the MCP endpoint and the local deployment. The specification was extracted from it, which is why the implementation currently wins any disagreement.
  • sempods-website — this site. Astro, static, no runtime.
  • the sempods organisation — everything else, including the apps that are still experimental enough not to be linked individually.

Run against

  • a live public pod — the aaltra venue in Chemnitz serves its events from its own pod. The Start page carries the query; the pod's context list is the shorter proof that it is there.
  • Maven Central — the JVM artifacts, version 0.1.0, Java 21 bytecode. The Gradle coordinates are on Start.
  • apps.sempods.org — preview apps that connect to a pod by URL. Early, and honest about it.

Ask

  • Discussions — the open room for the project as a whole, questions about the specification included.
  • Issues, where something is wrong rather than unclear: sempods-kotlin for behaviour, sempods-spec for the text.
  • hello@sempods.org — for anything that does not belong in public, a hosted test pod included.

Start with sempodsSee how it worksRead the specification