-
Notifications
You must be signed in to change notification settings - Fork 23
Principles for Taxonomy
madbkr edited this page Sep 11, 2024
·
3 revisions
Strive to build the ontology monohierarchically, i.e. each term has at most one parent.
Bad example:
role
/ \
socialRole biologicalRole
\ /
motherRole
Good example:
role
|
motherRole
/ \
biologicalMotherRole adoptedMotherRole
More than one hierarchy can be implemented using equivalent classes. See Explanation on mass nouns for an example.
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