IF Commons GitHub

The Planning ontology

0003Active

0003-planning-terms · owner if · domain commons

The ontology

FR-001checkpassing

The library MUST state the ontology plan: in src/planning/ as typed values over the library rdf, with the namespace https://www.intellectualfrontiers.com/ontology/planning#, the version 1.0.0 with its version IRI, and a description that names the four kinds of item, the events, the observations and the patches.

Enforced (check): .github: cd commons/ontology && bun test suite/ — planning-ontology.test.ts

Proved by: ontology/suite/planning-ontology.test.ts

Written in: ontology/src/planning/mod.ts, ontology/src/planning/planning.ts

Tests: passed: suite/planning-ontology.test.ts the ontology has its namespace, the version 1.0.0 with its version IRI and a description n

FR-002checkpassing

The ontology MUST hold the classes plan:Item, plan:Event, plan:Actor, plan:Observation, plan:Locator, plan:Trace, plan:Link, plan:Patch, plan:Preview and plan:Source, each with a label and a definition, and the class of each code list of FR-003, and the properties that carry the external id, the deferral day, the principal's basis, the fields a source carries (motivation, blocker, target, source, priority, size, goals, engines, cites, evidence) and the severity as the source wrote it.

Enforced (check): .github: cd commons/ontology && bun test suite/ — planning-ontology.test.ts

Proved by: ontology/suite/planning-ontology.test.ts

Written in: ontology/src/planning/planning.ts

Tests: passed: suite/planning-ontology.test.ts the ten classes of the model and the thirteen of the code lists are there, each with a def

FR-003checkpassing

The ontology MUST hold these closed code lists, each member with a label and a definition: four kinds of item (issue, task, todo, finding), five states (proposed, open, in progress, deferred, closed), three close reasons (completed, not planned, duplicate), three severities (error, warning, note), four verdicts (accept, minor revision, major revision, reject), four kinds of link (blocks, same as, relates to, parent of), seven capabilities (read, create, append event, edit, close, assign, delete), four authorities of a field (source, store, latest, person), three origins (declared, derived, inferred), three kinds of actor (person, agent, tool), three kinds of locator (file span, URL, commit), fourteen types of event and four bases of a principal (session, argument, configuration, commit author).

Enforced (check): .github: cd commons/ontology && bun test suite/ — planning-ontology.test.ts

Proved by: ontology/suite/planning-ontology.test.ts

Written in: ontology/src/planning/planning.ts

Tests: passed: suite/planning-ontology.test.ts the thirteen code lists have the members the specification counts

FR-004checkpassing

A value that another standard names (the SARIF level of a severity, the iCalendar status of a state, the Web Annotation motivation of a kind of item, the reason a Git host gives for closing) MUST be a name in a property of the member that says whose it is, read in the standard's own text, and its definition MUST cite the document, its version and the section; the ontology MUST NOT write an IRI that was not read in a standard's text, and the only ones it writes are in the namespace of the ontology and http://www.w3.org/.

Enforced (check): .github: cd commons/ontology && bun test suite/ — planning-ontology.test.ts

Proved by: ontology/suite/planning-ontology.test.ts

Written in: ontology/src/planning/planning.ts

Tests: passed: suite/planning-ontology.test.ts a name from another standard is a name in a property that says whose it is, read in the st

Audit and boundaries

FR-005checkpassing

Every class of the ontology MUST have a record of its basis (commons 0018-standards-first FR-003), each specializing a term of PROV-O or SKOS that the library rdf holds, and none is unaligned.

Enforced (check): .github: cd commons/ontology && bun test suite/ — planning-ontology.test.ts

Proved by: ontology/suite/planning-ontology.test.ts

Written in: ontology/src/planning/planning.ts

Tests: passed: suite/planning-ontology.test.ts every class has a record of its basis, specializing a PROV-O or SKOS term, and none is una

FR-006checkpassing

The modules MUST import only core, rdf and the ontologies of this library by relative path, and the ontology MUST be published like the others (Turtle, SHACL shapes, SSSOM, code lists) by bun commons/libraries/src/generate-ontology.ts.

Enforced (check): .github: cd commons/ontology && bun test suite/ — planning-ontology.test.ts

Proved by: ontology/suite/planning-ontology.test.ts

Written in: ontology/src/planning/planning.ts

Tests: passed: suite/planning-ontology.test.ts the modules import only core, rdf and the ontologies of the library

Acceptance scenarios

  1. Given the ontology, When its classes are read, Then the ten classes of the model and the thirteen classes of the code lists are there, per FR-002.
  2. Given the code lists, When their members are counted, Then there are 4, 5, 3, 3, 4, 4, 7, 4, 3, 3, 3, 14 and 4, per FR-003.
  3. Given the severity Error, When its SARIF level is read, Then it is the name error and the property's definition cites SARIF 2.1.0 sections 3.27.9 and 3.27.10, per FR-004.
  4. Given every class, When the audit is read, Then each has a record that specializes a PROV-O or SKOS term and none is unaligned, per FR-005.
  5. Given the modules of the ontology, When their imports are read, Then none is outside core, rdf and the library, per FR-006.

Out of scope

  • What the terms mean for a program: commons 0037-planning.
  • Terms of the sources (a Markdown task list, a code comment, a Git host): their own specifications, when they are built.

Edge cases

  • A name from a standard: kept as a name with its section cited, and the audit's basis stays PROV-O or SKOS, per FR-004 and FR-005.
  • The verdicts: a verdict is the data of a decided event, and no kind of item is a decision, per FR-003.

Assumptions

  • The standards named in FR-004 were read from their primary texts on 2026-11-21 (commons 0037-planning, Standards considered); an agent's principal is prov:actedOnBehalfOf of PROV-O, which the library rdf already holds, so no property of this ontology says it.

Open questions

OQ-1open question

(closed by the owner): The prefix is plan:.

OQ-2open question

(closed by the owner on 2026-11-21): The owner cut the kinds roadmap item, question and decision, the event seen, the link kind derived from and the locator kind row (commons 0037-planning OQ-9); the ontology holds the rest.

Key entities

  • Item - a piece of planning content of one of four kinds.
  • Observation - what one source saw in one place.
  • Patch - a change to write back to one source.

Success criteria

SC-001success criterion

Every term the specification commons 0037-planning uses is in this ontology, with its basis, before the specification names it.

Review & acceptance checklist

  • [x] Every requirement is testable (MUST / MUST NOT), not aspirational
  • [x] No company fact is asserted here
  • [x] Every open item is marked, not silently decided

Titles, headings, exports, tables, columns and requirements. Esc closes.