View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Linked Open Terms |  Architecture Request for Comments |  Architecture Architecture Decision Record |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | Wochen bis Monate | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 2-4 h |
Participantsdifferent | 2-8 | 3-20 Reviewer | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | OntologyMethodologyAgileSemantic | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | OntologyKnowledge graphScopeRequirementsSemantic |