Home.md

@@ -86,6 +86,17 @@ With emg.owl we intend to provide stable semantics. This is ensured by classes g
 ### OWL build pipeline
 The classes, class hierarchy and annotation properties are all sourced from the [yaml files](https://codebase.helmholtz.cloud/em_glossary/em_glossary/-/tree/main/terms) that are the output of our community process. Every merge to main in our [community repository](https://codebase.helmholtz.cloud/em_glossary/em_glossary) triggers a CI/CD pipeline that automatically assembles [emg-edit.owl](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/-/blob/main/development/emg-edit.owl). Keys for annotation properties are sourced from external well-established vocabularies which are set up in [empty.owl](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/-/blob/main/development/empty.owl). The empty.owl is the input for the parsing routine in [yaml_to_owl.py](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/-/blob/main/development/yaml_to_owl.py).
 
+Here we list which yaml keys are mapped to which annotation properties in owl: 
+| YAML | OWL | IRI |
+| -- | -- | -- |
+| definition | IAO:Definition | http://purl.obolibrary.org/obo/IAO_0000115 |
+| | |
+| | |
+| | |
+| | |
+
+
+
 # Other info
 
 ### Cite this repository