AD4M link language that syncs Perspective triples to Solid pods via LDP (Linked Data Platform), stored as RDF/Turtle resources.
- Commits: links → RDF/Turtle resources created in an LDP container on a Solid pod
- Sync: polls container for new resources → local links
- Query: indexed local store (source, target, predicate)
- Native Linked Data: links become first-class RDF, browseable in any Solid app (Penny, Mashlib)
- Access control: Web Access Control (WAC) for fine-grained permissions
| Variable | Description |
|---|---|
SOLID_POD_URL |
Solid pod base URL |
SOLID_CONTAINER_PATH |
Container path within the pod |
SOLID_IDP_URL |
Identity Provider URL |
SOLID_WEBID |
WebID for authentication |
NEIGHBOURHOOD_META |
AD4M neighbourhood metadata |
pnpm install
deno run --allow-all esbuild.tsRequires @coasys/ad4m-ldk at ../ad4m/ad4m-ldk/js/ or set AD4M_LDK_ENTRY.
node --experimental-vm-modules --import tsx --test tests/*.test.ts194 tests across 10 suites.
Same pure/impure pattern as all AD4M link languages. Protocol-specific modules:
src/ldp.ts/ldp.pure.ts— LDP container operationssrc/rdf.ts/rdf.pure.ts— RDF/Turtle serializationsrc/acl.ts— Web Access Control managementsrc/auth.ts/auth.pure.ts— WebID-OIDC / CSS token authenticationsrc/ontology.ts— AD4M link ontology in RDFsrc/translate.ts/translate.pure.ts— link ↔ RDF translationsrc/dual-language.ts— dual-language supportsrc/sdna.ts— social DNA definitionssrc/settings.ts— language settingssrc/sync.ts— sync orchestration
ad4m:host imports confined to 4 adapter files + index.ts.
CAL-1.0