solid-scheduling
Use when reading or writing Solid tasks and calendars through @jeswr/solid-scheduling, changing its SHACL or vocabulary use, or maintaining its sched:Task to wf:Task cross-serialisation.
- License 许可
- MIT
- 所属仓库
- jeswr/solid-sdk
- 最近更新
- 2026-11-15
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- solid-scheduling
- description
- Use when reading or writing Solid tasks and calendars through @jeswr/solid-scheduling, changing its SHACL or vocabulary use, or maintaining its sched:Task to wf:Task cross-serialisation.
02 资源文件 39
- 其他.roborev.toml386 B
- 参考文档biome.json242 B
- 参考文档codegen/codegen.config.json1.5 KB
- 其他codegen/scheduling.ontology.ttl2.2 KB
- 其他codegen/scheduling.shapes.ttl4.5 KB
- 参考文档DECISIONS.md10.9 KB
- 许可证LICENSE1.0 KB
- 参考文档package.json2.8 KB
- 参考文档README.md11.4 KB
- 其他scheduling.proposals.ttl12.6 KB
- 其他scheduling.shacl.ttl6.5 KB
- 脚本scripts/copy-generated.mjs411 B
- 脚本src/acl.test.ts5.5 KB
- 脚本src/acl.ts6.3 KB
- 脚本src/calendar.test.ts2.2 KB
- 脚本src/calendar.ts5.3 KB
- 脚本src/cross-app.test.ts4.9 KB
- 参考文档src/generated/codegen-manifest.json842 B
- 参考文档src/generated/codegen.lock.json434 B
- 脚本src/generated/model.d.ts3.8 KB
- 脚本src/generated/model.js12.4 KB
- 参考文档src/generated/model.json6.2 KB
- 其他src/generated/shapes.ttl5.8 KB
- 脚本src/index.ts3.4 KB
- 脚本src/iri.test.ts3.9 KB
- 脚本src/iri.ts3.5 KB
- 脚本src/nodes.ts8.3 KB
- 脚本src/shape.test.ts5.0 KB
- 脚本src/shape.ts2.7 KB
- 脚本src/task.test.ts13.0 KB
- 脚本src/task.ts18.3 KB
- 脚本src/vocab.test.ts2.6 KB
- 脚本src/vocab.ts10.1 KB
- 脚本test/codegen.test.ts1.2 KB
- 脚本test/compatibility.test.ts5.5 KB
- 脚本test/resource-url.test.ts2.1 KB
- 参考文档tsconfig.build.json148 B
- 参考文档tsconfig.json591 B
- 脚本vitest.config.ts177 B
03 SKILL.md 正文
<!-- AUTHORED-BY Claude Opus 5.5 -->
Solid scheduling model
Tasks (sched:Task), calendars (sched:Calendar), recurrence rules and reminders from
the federation scheduling sector; the package mints no IRIs. Task and calendar
build/parse run on a model generated from codegen/ (codegen Phase S, bead sst-ild.7.5):
src/task.ts and src/calendar.ts are facades over src/generated/model.js. Never edit
src/generated/; change codegen/scheduling.shapes.ttl or codegen/codegen.config.json,
then run pnpm run codegen --update-lock. The drift test (test/codegen.test.ts) and
the divergence pins (test/compatibility.test.ts, README "Exact divergences") must pass.
The generated composite covers the sched:Task core and its one sched:RecurrenceRule.
The facade adds what SHACL cannot express: the wf:Task overlay, unified completion,
frequency normalisation on write, dct:subject labels, and any number of
sched:hasReminder nodes through the typed views in src/nodes.ts.
Load-bearing behaviour (DECISIONS.md D2): every sched:Task is also written as the
shared wf:Task from @jeswr/solid-task-model on the same #it subject.
buildSchedulingTask builds the wf:Task store with task-model's buildTask, which owns
build-side http(s) IRI filtering and the wf:Open/wf:Closed state, then layers the
sched: triples. Do not re-implement that logic here. task-model's parseTask does not
filter IRIs and throws on a wrong term kind, so parseSchedulingTask guards that read and
http(s)-filters every wf: IRI it returns. The completion timestamp is computed
once and written to both sched:completedAt and prov:endedAtTime; an explicit
completed: false wins over a supplied completedAt.
scheduling.shacl.ttl is the published package profile (Task, RecurrenceRule, Reminder,
Calendar); codegen/scheduling.shapes.ttl is the generation input derived from it, with
the differences listed in its header;
src/shape.test.ts validates it with rdf-validate-shacl. scheduling.proposals.ttl holds
fedcon:Proposal candidates for sector gaps; do not edit the sector from here.
From the workspace root:
pnpm exec turbo run lint build typecheck test --filter=@jeswr/solid-scheduling
04 同仓库更多 Skills
storage-conformance
Work on @jeswr/storage-conformance, the shared storage conformance suite package in the Solid SDK workspace.
fetch-rdf-engine-tests
Maintain fetch-rdf's real Node WASM parser integration tests without introducing a reverse engine dependency in fetch-rdf.
alpha
Use when checking fixtures, including folded YAML descriptions.
widget
Use when testing package skills: YAML quoting works.
web-seo
Use when improving technical and entity SEO for a modern personal, portfolio, documentation, or marketing site, including crawlable HTML, canonical metadata, sitemap and robots, Person/ProfilePage JSON-LD, Core Web Vitals, and honest ranking expectations.
solid-wac
Use when implementing or auditing Solid server WAC authorization, ACL creation and inheritance, auxiliary-resource escalation, method-to-mode mapping, 401 versus 403 challenges, WAC-Allow, or defensive typed ACL parsing with @solid/object and @rdfjs/wrapper.