-
Notifications
You must be signed in to change notification settings - Fork 23
Best Practice Principles
stap-m edited this page Oct 22, 2019
·
16 revisions
Based on the book Building Ontologies with Basic Formal Ontology by Robert Arp, Barry Smith and Andrew D. Spear, MIT Press 2015, some best practice principles are derived for the OpenEnergyOntology OEO. The collection is a guideline for OEO developers and reviewers to achieve and maintain a high quality of the ontology.
1. What is to consider for the chioce of terms? Principles for Terminology
2. What is to consider for creating definitions? Principles for Definitions
Always provide all (nonroot) terms with definitions.
3. What is to consider for the OEO structure? Principles for Taxonomy
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