Repository navigation
Every ontology composes with every other, and with what tg init writes.
Changed
- One owner per name. Putting the gallery ontologies in one folder with the schemas
tg initwrites found clashes: the requirements ontology declared the code ontology's six types and nine of its edges again, the code ontology declaredcontradictsa second time, and the 0.29 team map declaredPersonandAgent, which OKF and the agents ontology already declare. Each name now has exactly one owner, and two tests keep it that way: one composes all eight gallery ontologies with notes labelled from two at once, and one composes the core, code, every spec framework's ontology and the team map with every gallery schema note. Both report no diagnostic. - Shared core in tg projects.
tg initwritesTypes/core-types.md(contradicts,derived_from,cites), byte-identical to the gallery's core, and the code ontology no longer declarescontradicts.tg initandtg upgrademove an unchangedcontradictsout of an existingTypes/code-types.md. One you changed is kept, with a note, and the core is then not written, so nothing is declared twice. The core'scontradictstakesreason,untilandticket; the gallery core's formerwhyis nowreason. - Code types are open to other ontologies. The six code types no longer close their outgoing edges with an
edgeslist, so other ontologies can add edges to them (ships_infrom a Requirement,decided_byfrom a Decision). Each edge type'sfromandtostill say where it may start and end;introduced_bynow starts only at a Requirement, andchanged_byonly at a Decision or Requirement. The code ontology also gains a MoSCoWpriorityon Requirement. The agents ontology'sAgentis open in the same way. - Team map types are
Member,TeamandTeamAgent(they werePerson,TeamandAgentin 0.29). A note that belongs to both ontologies takes both labels:type: [Person, Member]with OKF,type: [Agent, TeamAgent]with the agents ontology. Thetg-teamskill andtg gen team-types.mduse the new names. If you saved the 0.29 team ontology, runtg gen team-types.md > Types/team-types.mdagain and renametype: PersontoMemberandtype: AgenttoTeamAgentin your docs.
Added
codeandteamin the ontology gallery, as the same filestg initandtg gen team-types.mdwrite, with payment-team examples.requirementsis now only the product layer (stakeholders, releases, risks) built oncode.ontologies/requires.jsonlists what each ontology builds on, and its download includes it. The gallery page has tabs and cards for both, and the team map article and composable ontologies explain the rules.
Full Changelog: 0.29.0...0.30.0