-
Notifications
You must be signed in to change notification settings - Fork 23
Discussion Workflow
madbkr edited this page Sep 11, 2024
·
7 revisions
When new terms should be included in the ontology we recommend the following workflow:
- Find a definition and a label without using "BFO words" to encourage domain experts
- Look for parent classes and rewrite definition
- Add relations
- Make counterproposals when you disagree
- "Follow through" with issues (no long breaks)
- Encourage phone calls
- Cluster issues (meta-issues, specialised meetings)
When an issue reaches over 20 comments the new compromise process is initialised:
- All sides formulate concrete proposals
- Compromise meeting: neutral person (assigned per dev meeting) and all sides try to find compromise
- If compromise meeting is unsuccessful: discussion in next developer meeting with vote to decide
- When an agreement is reached:
- Assign person for implementation
- Discussion shouldn't be reopened for ~ 6 months
You already know what to do? Perfect, make sure that you miss no step by using checklists
Symbols used in this wiki:
🐙➔ github | 🔶➔ git | 📙➔ protégé | 📝➔ text editor | 🤖➔ robot
-
Home
- Welcome! How to participate
- Use Cases
- Best Practice Principles
- Structure of the OEO
-
Tutorials: How to...
- ...Get Involved (First Steps)
- ...Contribute
- ...Use Protégé to Change the Ontology
- ...Test the Ontology
- ...Write Competency Questions
- ...Choose a Class Type
- ...Deal with Ambiguous Terms
- ...Use Term Tracker Annotations
- ...Use the GitHub Labels
- ...Set up OwlViz for Visualisation
- ...Use Automation of Recurring Text Entries
- ...Manually Merge Terms from Other Ontologies 🤖
- ...Release a New Ontology Version
- ...Translate Into Turtle RDF
- Setup your Work Environment and Get Involved
- ...Maintain automated Workflows for GitHub Issues and PRs
- Get to Know the Workflow This sections will contain the full workflow in the future
- Tools and Utilities
- Community