diff --git a/.github/workflows/qc.yml b/.github/workflows/qc.yml
index 4c560cf..8e96293 100644
--- a/.github/workflows/qc.yml
+++ b/.github/workflows/qc.yml
@@ -19,7 +19,7 @@ jobs:
ontology_qc:
# The type of runner that the job will run on
runs-on: ubuntu-latest
- container: obolibrary/odkfull:v1.4
+ container: obolibrary/odkfull:v1.4.3
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
diff --git a/.gitignore b/.gitignore
index 3e5c002..45bda8f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -41,3 +41,5 @@ pyproject.toml
poetry.lock
.idea/*
src/templates/.~lock.vibso_classes.tsv\#
+docs/images/.$VIBSO_T-Box_graph_views.drawio.bkp
+*.dtmp
diff --git a/README.md b/README.md
index 1f9c213..48d1506 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,5 @@
[![License: CC-BY 4.0](https://img.shields.io/badge/License-CC%20BY%204.0-green.svg)](https://creativecommons.org/licenses/by/4.0/)
-![Build Status](https://github.com/NFDI4Chem/VibrationSpectroscopyOntology/workflows/CI/badge.svg)
+[![CI](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/actions/workflows/qc.yml/badge.svg)](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/actions/workflows/qc.yml)
# Vibrational Spectroscopy Ontology
_Work In Progress - NOT READY FOR PRODUCTION!_
diff --git a/docs/contributing.md b/docs/contributing.md
index 8b07dc6..99511df 100644
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -7,6 +7,5 @@ There are different ways in which you can help:
* [Open up a new issue](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/issues/new/choose): For any kind of contributions we rely on the GitHub infrastructure for documentation. Thus, it is always preferred that you use one of our issue templates to let us know what needs to be done and how you might plan on contributing, before working on a pull request (PR). (However, feel free to do a quick PR patch for any typos off course.)
* Use [this template](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/issues/new?assignees=&labels=&template=bug_report.md&title=) to file bugs within the ontology or its CI/CD pipeline,
- * [this one](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/issues/new?assignees=&labels=New+Term+Request&template=new-term-request-issue-template.md&title=%5BNTR%5D) to make a new term request,
+ * [this one](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/issues/new?assignees=&labels=New+Term+Request&template=new-term-request-issue-template.md&title=%5BNTR%5D) to make a new term request (but please read the [How to add new terms to VIBSO section](ntr_workflow.md) first),
* or [this one](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/issues/new?assignees=&labels=documentation&template=documentation-related-issue.md&title=%5BDocs%5D) to help us improve this documentation and ask questions about VIBSO.
-* [Add new terms to VIBSO](ntr_workflow.md).
diff --git a/docs/design_patterns.md b/docs/design_patterns.md
index 71eb20c..aadd44f 100644
--- a/docs/design_patterns.md
+++ b/docs/design_patterns.md
@@ -1,22 +1,55 @@
# Design Patterns & Decisions
-**This page is still a stub and will be updated regularly in the iterative development of VIBSO to document modeling decisions and design patterns.**
+**This page will be updated regularly in the iterative development of VIBSO to document modeling decisions and design patterns.**
-Following best practices in ontology development, we will reuse well established design patterns whenever possible.
+Following best practices in ontology development, we will reuse established design patterns whenever possible. Since most ontologies we reuse are OBO Foundry based, we also reuse their design patterns to be logically sound and interoperable. Some of these patterns are provided in the logical definitions of the reused classes in form of asserted `rdfs:subclassOf` or `rdfs:equivalentTo` axioms. Others are only implicitly provided in the textual definitions of the reused terms and the domain and range restrictions of suitable OBO relations.
-## Planned Process Pattern
- OBI's way of modeling [data and values](https://github.com/obi-ontology/obi/wiki/Data-and-Values) is a very prominent pattern in many OBO ontologies and thus one we also use. Please read their documentation in order to understand how we model values and data. Here is an illustrative example graphic from that documentation: ![measurement process pattern example](images/data_john_mass.png) Using this OBI pattern allows us to differentiate data values of qualities (aka attributes) of a material entity, such as the spectroscope or sample, into data values that represent settings and those that represent measurements. From a data repository use case perspective, we might not need this fine-grained approach and defining qualities/attributes and their value specifications might suffice. Yet in order to allow the integration of VIBSO in Electronic Lab Notebooks, such a differentiation will most likely be very useful.
+## VIBSO TBox
-Lars Vogt and Tobias Kuhn demonstrate the use of this pattern within a grander research context as follows (cited from their preprint [DOI:10.13140/RG.2.2.13742.59203](http://doi.org/10.13140/RG.2.2.13742.59203), p.8):
-![measurement process pattern example](images/Fig4_10.13140_RG.2.2.13742.59203.png)
+Here you can see VIBSO's current terminology box that focuses on vibrational Raman spectroscopy and which also shows how VIBSO depends on reusing existing ontology classes, relations and design patterns.
- > Figure 3: A detailed machine-actionable representation of the metadata relating to a weight measurement datum documented as an RDF ABox graph. The representation takes the form of an ABox semantic graph following the RDF syntax. The graph documents a mass measurement process using a balance. It relates an instance of mass measurement assay (OBI:0000445) with instances of various other classes from different ontologies, specifying who conducted the measurement, where and when it took place, following which protocol and using which device (i.e., balance). The graph furthermore specifies the particular material entity that served as subject and thus as input of the measurement process (i.e., ‘objectX’), and it specifies the data that is the output of the observation, which is contained in a particular weight measurement assertion.
+![Raman spectroscopy terminology box](images/VIBSO_Raman_Tbox.png)
+This TBox is supposed to be updated iteratively whenever a new term is being discussed for inclusion. We hope that it might be easier for domain experts to define technical terms in this ontological framework by adding them here first.
-## Vibrational Raman Spectroscopy
+A higher resolution HTML version with links to the used terms in the NFDI4Chem Terminology Service can be found [here](images/VIBSO_TBox_graph_views.html).
-Here you can see the first draft of VIBSO's terminology box that focuses on vibrational Raman spectroscopy and which also shows how VIBSO depend on reusing existing ontology classes, relations and design patterns. The initially identified needed terms, depicted here with a red border, were derived from a Raman spectrometer output.
+The source file to edit the TBox with the [draw.io](https://draw.io) app is [here](images/VIBSO_T-Box_graph_views.drawio).
-![Raman spectroscopy terminology box](images/VIBSO_Raman_Tbox.png)
+## Assay Pattern
+As the scope of VIBSO covers the definitions of various types of vibrational spectroscopy assays and their specific research information outputs, we need to reuse the class `assay` from the Ontology for Biomedical Investigations (OBI). It is defined as:
+
+ A planned process that has the objective to produce information about a material entity (the evaluant) by examining it.
+
+Along with this textual definition, the logical axioms asserted on this class constitute a core design pattern of OBO based ontologies, which can be represented graphically like this:
+
+![OBI_asserted_assay_pattern](images/OBI_asserted_assay_pattern.png)
+
+## Assay Pattern with Device Settings
+Since we also want to say what kind of devices were used in VIBSO specific assays and how these were set, we extend the assay pattern by importing these classes and relations:
+
+![OBI_asserted_assay_pattern](images/OBO_setting_pattern.png)
+
+## Assay Pattern with Data Transformation, Investigation and Sampling
+To zoom out a bit further, this is the pattern proposed to be able to also express:
+
+* who performed an assay,
+* what kind of data transformations where performed on the data output of an assay,
+* what kind of sampling process was done before the assay,
+* and in which grander investigation process the assay is a part of.
+
+![OBI_asserted_assay_pattern](images/OBO_Investigation_Assay_Pattern.png)
+
+-----
+
+## Measurement Example KG of the Assay Pattern
+Lars Vogt and Tobias Kuhn demonstrate the use of the OBO assay pattern within a grander research context as follows (cited from their preprint [DOI:10.13140/RG.2.2.13742.59203](http://doi.org/10.13140/RG.2.2.13742.59203), p.8):
+![measurement process pattern example](images/Fig4_10.13140_RG.2.2.13742.59203.png)
+
+ > Figure 3: A detailed machine-actionable representation of the metadata relating to a weight measurement datum documented as an RDF ABox graph. The representation takes the form of an ABox semantic graph following the RDF syntax. The graph documents a mass measurement process using a balance. It relates an instance of mass measurement assay (OBI:0000445) with instances of various other classes from different ontologies, specifying who conducted the measurement, where and when it took place, following which protocol and using which device (i.e., balance). The graph furthermore specifies the particular material entity that served as subject and thus as input of the measurement process (i.e., ‘objectX’), and it specifies the data that is the output of the observation, which is contained in a particular weight measurement assertion.
-What is needed next are iterative reviews of this draft by domain experts to expand it and to ensure that the [competency questions](competency_questions.md) of VIBSO can be answered.
\ No newline at end of file
+## Quality & Quantity Pattern
+![measurement process pattern example](images/data_john_mass.png)
+ Since we are reusing OBO ontologies and their patterns, we also try to reuse OBI's way of modeling [data and values](https://github.com/obi-ontology/obi/wiki/Data-and-Values). Please read their documentation for more background.
+ Using this OBI pattern allows us to differentiate data values of qualities (aka attributes) of a material entity, such as the spectroscope or sample, into data values that represent settings and those that represent measurements. From a data repository use case perspective, we might not need this fine-grained approach and defining qualities/attributes and their value specifications might suffice. Yet in order to allow the integration of VIBSO in Electronic Lab Notebooks, such a differentiation will most likely be very useful.
+Although this pattern seems to work in many OBO use cases, we need to see, if we have to adjust it for our needs. Other ontologies like QUDT or SIO use slightly different patterns to model qualities and their quantitative representations.
\ No newline at end of file
diff --git a/docs/development_approach.md b/docs/development_approach.md
index eb6ded5..8154b07 100644
--- a/docs/development_approach.md
+++ b/docs/development_approach.md
@@ -29,9 +29,11 @@ In both TSV templates there are the following columns:
* **term replaced by**: This column should be used to provide the term that replaces a deprecated term. This is important to ensure backwards compatibility.
In the **vibso_classes.tsv**, there is also the column:
+
* **super class**: This column is to be used to provide the parent of the owl:Class that is being defined. It is fine to use the label of the parent class here instead of its IRI or CURIE, as long as the class is already an [imported term](ntr_workflow.md#importing terms).
In the **vibso_classes.tsv**, there are also the columns:
+
* **super property**: This column is to be used to provide the parent of the `owl:ObjectProperty` or `owl:DatatypeProperty` that is being defined, via its label.
* **inverse property**: This column can be used to define the inverse of an `owl:ObjectProperty`, via its label.
* **domain**: This column can be used to restrict an `owl:ObjectProperty` in terms of being allowed to be used only on a certain subject.
diff --git a/docs/images/OBI_asserted_assay_pattern.png b/docs/images/OBI_asserted_assay_pattern.png
new file mode 100644
index 0000000..03f46cc
Binary files /dev/null and b/docs/images/OBI_asserted_assay_pattern.png differ
diff --git a/docs/images/OBO_Investigation_Assay_Pattern.png b/docs/images/OBO_Investigation_Assay_Pattern.png
new file mode 100644
index 0000000..1c95331
Binary files /dev/null and b/docs/images/OBO_Investigation_Assay_Pattern.png differ
diff --git a/docs/images/OBO_assay_pattern_example_instances.png b/docs/images/OBO_assay_pattern_example_instances.png
new file mode 100644
index 0000000..28da229
Binary files /dev/null and b/docs/images/OBO_assay_pattern_example_instances.png differ
diff --git a/docs/images/OBO_setting_pattern.png b/docs/images/OBO_setting_pattern.png
new file mode 100644
index 0000000..4318e89
Binary files /dev/null and b/docs/images/OBO_setting_pattern.png differ
diff --git a/docs/images/Raman spectroscopy T-Box-Raman T-Box.drawio.png b/docs/images/Raman spectroscopy T-Box-Raman T-Box.drawio.png
deleted file mode 100644
index f4f99fe..0000000
Binary files a/docs/images/Raman spectroscopy T-Box-Raman T-Box.drawio.png and /dev/null differ
diff --git a/docs/images/Raman_spectroscopy_T-Box.drawio b/docs/images/Raman_spectroscopy_T-Box.drawio
deleted file mode 100644
index 9013ef9..0000000
--- a/docs/images/Raman_spectroscopy_T-Box.drawio
+++ /dev/null
@@ -1,2520 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/images/VIBSO_Raman_Tbox.png b/docs/images/VIBSO_Raman_Tbox.png
index a984e81..ddb1e86 100644
Binary files a/docs/images/VIBSO_Raman_Tbox.png and b/docs/images/VIBSO_Raman_Tbox.png differ
diff --git a/docs/images/VIBSO_Raman_Tbox.svg b/docs/images/VIBSO_Raman_Tbox.svg
deleted file mode 100644
index cbd43a5..0000000
--- a/docs/images/VIBSO_Raman_Tbox.svg
+++ /dev/null
@@ -1,4 +0,0 @@
-
-
-
-
\ No newline at end of file
diff --git a/docs/images/VIBSO_T-Box_graph_views.drawio b/docs/images/VIBSO_T-Box_graph_views.drawio
new file mode 100644
index 0000000..a78972f
--- /dev/null
+++ b/docs/images/VIBSO_T-Box_graph_views.drawio
@@ -0,0 +1,2362 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/images/VIBSO_TBox_graph_views.html b/docs/images/VIBSO_TBox_graph_views.html
new file mode 100644
index 0000000..06ac2ee
--- /dev/null
+++ b/docs/images/VIBSO_TBox_graph_views.html
@@ -0,0 +1,11 @@
+
+
+
+
+VIBSO_T-Box_graph_views
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/ntr_workflow.md b/docs/ntr_workflow.md
index 421fd15..336f7b7 100644
--- a/docs/ntr_workflow.md
+++ b/docs/ntr_workflow.md
@@ -12,9 +12,9 @@ Whenever you identify a term missing in VIBSO and you have found a suitable cand
Once it is decided to be needed, a pull request (PR) can be made to include it in the imports. For this it needs either be added in one of the existing text files where such term imports get declared (see [/src/ontology/imports](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/tree/main/src/ontology/imports)) and from which the OWL import modules are build automatically, according to the standard import workflow documented in [here](odk-workflows/UpdateImports.md). If the term is from an ontology that is not yet being used as an import module in VIBSO the [managing imports workflow](odk-workflows/RepoManagement.md#managing-imports) needs to be triggered.
## New Term Requests
-When you've identified a term that is needed within the scope of VIBSO and which is not yet defined in an existing compatible ontology, please file a [new term request (NRT) issue](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/issues/new?assignees=&labels=New+Term+Request&template=new-term-request-issue-template.md&title=%5BNTR%5D).
- This issue should then be used to engage the community in discussing the label, definition, position in the hierarchy as well as possible axiomatization. Once the discussion has reached a consensus, someone from the VIBSO team or maybe you, will have to make a PR in which the discussed changes to VIBSO will be implemented and can be reviewed.
+When you've identified a term that is needed within the scope of VIBSO and which is not yet defined in an existing compatible ontology, a new term request (NTR) should be filed in VIBSO's issue tracker. This issue should then be used to engage the community in discussing the label, definition, position in the hierarchy as well as possible axiomatization. Once the discussion has reached a consensus, someone from the VIBSO team or maybe you, will have to make a PR in which the discussed changes to VIBSO will be implemented and can be reviewed.
+Please [check the open NTR issues](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/issues?q=is%3Aissue+is%3Aopen+label%3A%22New+Term+Request%22) to make sure none exists for this term already. If it does, feel free to participate in the discussion. Else, please use this [issue template](https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology/issues/new?assignees=&labels=New+Term+Request&template=new-term-request-issue-template.md&title=%5BNTR%5D) to file your NTR.
## Adding New Terms to the TSV Template
diff --git a/src/ontology/Makefile b/src/ontology/Makefile
index 879f6da..c6469d9 100644
--- a/src/ontology/Makefile
+++ b/src/ontology/Makefile
@@ -1,7 +1,7 @@
# ----------------------------------------
# Makefile for vibso
# Generated using ontology-development-kit
-# ODK Version: v1.4.1
+# ODK Version: v1.4.3
# ----------------------------------------
# IMPORTANT: DO NOT EDIT THIS FILE. To override default make goals, use vibso.Makefile instead
@@ -43,7 +43,7 @@ REPORT_PROFILE_OPTS =
OBO_FORMAT_OPTIONS =
SPARQL_VALIDATION_CHECKS = owldef-self-reference iri-range label-with-iri multiple-replaced_by
SPARQL_EXPORTS = basic-report class-count-by-prefix edges xrefs obsoletes synonyms
-ODK_VERSION_MAKEFILE = v1.4.1
+ODK_VERSION_MAKEFILE = v1.4.3
TODAY ?= $(shell date +%Y-%m-%d)
OBODATE ?= $(shell date +'%d:%m:%Y %H:%M')
diff --git a/src/ontology/example_instances.ttl b/src/ontology/example_instances.ttl
index c81982b..f06de8c 100644
--- a/src/ontology/example_instances.ttl
+++ b/src/ontology/example_instances.ttl
@@ -1,12 +1,161 @@
-@prefix ex: .
+@prefix : .
+@prefix ex: .
+@prefix DOI: .
+@prefix ROR: .
+@prefix dce: .
@prefix obo: .
@prefix owl: .
@prefix rdf: .
+@prefix xml: .
+@prefix xsd: .
+@prefix prov: .
+@prefix rdfs: .
+@prefix skos: .
+@prefix ORCID: .
+@prefix schema: .
+@prefix dcterms: .
+@prefix wikipedia: .
+@base .
-ex:_RamanSpectrometerX rdf:type owl:NamedIndividual ,
- obo:CHMO_0001235 ;
- obo:OBI_0000293 ex:_objective_magnification_factor_setting_for_RamanSpectroscopeX .
+ rdf:type owl:Ontology ;
+ owl:imports ,
+ ,
+ ,
+ ,
+ ,
+ ,
+ ,
+ ,
+ ,
+ ;
+ dcterms:contributor ,
+ ,
+ ;
+ dcterms:creator ,
+ "VIBSO Workgroup"@en ;
+ dcterms:description "_WIP - NOT READY FOR PRODUCTION_ The Vibration Spectroscopy Ontology (VIBSO) is used to represent information regarding the excution and analysis of vibrational spectroscopy assays." ;
+ dcterms:license ;
+ dcterms:title "Vibrational Spectroscopy Ontology" .
-ex:_objective_magnification_factor_setting_for_RamanSpectroscopeX rdf:type owl:NamedIndividual ,
- obo:VIBSO_0000014 ;
- obo:OBI_0002815 "100x" .
+#################################################################
+# Annotation properties
+#################################################################
+
+### http://purl.org/dc/terms/contributor
+dcterms:contributor rdf:type owl:AnnotationProperty ;
+ rdfs:label "contributor" .
+
+
+### http://purl.org/dc/terms/creator
+dcterms:creator rdf:type owl:AnnotationProperty ;
+ rdfs:label "creator" .
+
+
+### http://purl.org/dc/terms/description
+dcterms:description rdf:type owl:AnnotationProperty ;
+ rdfs:label "description" .
+
+
+### http://purl.org/dc/terms/license
+dcterms:license rdf:type owl:AnnotationProperty ;
+ rdfs:label "license" .
+
+
+### http://purl.org/dc/terms/title
+dcterms:title rdf:type owl:AnnotationProperty ;
+ rdfs:label "title" .
+
+
+### https://schema.org/affiliation
+ rdf:type owl:AnnotationProperty .
+
+
+#################################################################
+# Classes
+#################################################################
+
+### http://purl.obolibrary.org/obo/NCBITaxon_9606
+obo:NCBITaxon_9606 rdfs:subClassOf obo:OBI_0100026 ;
+ rdfs:label "person" .
+
+
+#################################################################
+# Individuals
+#################################################################
+
+### https://example.instances/AssayObjective_O
+ex:AssayObjective_O rdf:type owl:NamedIndividual ,
+ obo:OBI_0000441 .
+
+
+### https://example.instances/Assay_A
+ex:Assay_A rdf:type owl:NamedIndividual ,
+ obo:OBI_0000070 ;
+ obo:BFO_0000055 ex:EvaluantRole_R ;
+ obo:OBI_0000293 ex:MaterialEntity_M ;
+ obo:OBI_0000299 ex:DataItem_D ;
+ obo:OBI_0000417 ex:AssayObjective_O ;
+ dce:description """The assay A is planned to produce as a specified output the data item D which is a specific kind of information about the material entity M, which has the evaluant role R that gets realized in this planned observation process.
+
+This example instance is part of the ontology to demonstrate the OBI assay pattern. The type and number of relations between this instance and other example instances are based on the subclassOf and equivalentTo axioms asserted on OBIs assay."""@en .
+
+
+### https://example.instances/DataItem_D
+ex:DataItem_D rdf:type owl:NamedIndividual ,
+ obo:IAO_0000027 ;
+ obo:IAO_0000136 ex:MaterialEntity_M .
+
+
+### https://example.instances/EvaluantRole_R
+ex:EvaluantRole_R rdf:type owl:NamedIndividual ,
+ obo:BFO_0000023 .
+
+
+### https://example.instances/MaterialEntity_M
+ex:MaterialEntity_M rdf:type owl:NamedIndividual ,
+ obo:BFO_0000040 ;
+ obo:RO_0000087 ex:EvaluantRole_R .
+
+
+### https://orcid.org/0000-0002-1595-3213
+ rdf:type owl:NamedIndividual ;
+ rdfs:label "Philip Strömert" ;
+ ,
+ ,
+ "VIBSO Workgroup"@en .
+
+
+### https://orcid.org/0000-0002-2239-3955
+ rdf:type owl:NamedIndividual ;
+ rdfs:label "Giacomo Lanza" ;
+ ,
+ ,
+ "VIBSO Workgroup"@en .
+
+
+### https://orcid.org/0000-0002-4378-6061
+ rdf:type owl:NamedIndividual ;
+ rdfs:label "Johannes Hunold" ;
+ ,
+ ,
+ "VIBSO Workgroup"@en .
+
+
+### https://ror.org/04aj4c181
+ rdf:type owl:NamedIndividual ;
+ rdfs:label "German National Library of Science and Technology Hannover"@en ,
+ "Technische Informationsbibliothek (TIB)"@de .
+
+
+### https://ror.org/05r3f7h03
+ rdf:type owl:NamedIndividual ;
+ rdfs:label "German National Metrology Institute"@en ,
+ "Physikalisch-Technische Bundesanstalt (PTB)"@de .
+
+
+### https://www.wikidata.org/wiki/Q96678459
+ rdf:type owl:NamedIndividual ;
+ rdfs:label "NFDI4Chem" .
+
+
+### Generated by the OWL API (version 4.5.25.2023-02-15T19:15:49Z) https://github.com/owlcs/owlapi
diff --git a/src/ontology/imports/bfo_import.owl b/src/ontology/imports/bfo_import.owl
index caa3f3f..bd0c91f 100644
--- a/src/ontology/imports/bfo_import.owl
+++ b/src/ontology/imports/bfo_import.owl
@@ -7,9 +7,9 @@ Prefix(rdfs:=)
Ontology(
-
+
Annotation()
-Annotation(owl:versionInfo "2023-06-21")
+Annotation(owl:versionInfo "2023-11-27")
Declaration(Class())
Declaration(Class())
diff --git a/src/ontology/imports/chmo_import.owl b/src/ontology/imports/chmo_import.owl
index 2be2b1d..78aa028 100644
--- a/src/ontology/imports/chmo_import.owl
+++ b/src/ontology/imports/chmo_import.owl
@@ -12,8 +12,8 @@
xmlns:terms="http://purl.org/dc/terms/"
xmlns:oboInOwl="http://www.geneontology.org/formats/oboInOwl#">
-
- 2023-06-21
+
+ 2023-11-27
@@ -2581,5 +2581,5 @@
-
+
diff --git a/src/ontology/imports/iao_import.owl b/src/ontology/imports/iao_import.owl
index f4fda27..52e9148 100644
--- a/src/ontology/imports/iao_import.owl
+++ b/src/ontology/imports/iao_import.owl
@@ -7,9 +7,9 @@ Prefix(rdfs:=)
Ontology(
-
+
Annotation()
-Annotation(owl:versionInfo "2023-06-21")
+Annotation(owl:versionInfo "2023-11-27")
Declaration(Class())
Declaration(Class())
diff --git a/src/ontology/imports/obi_import.owl b/src/ontology/imports/obi_import.owl
index 0f6340a..c6e32e9 100644
--- a/src/ontology/imports/obi_import.owl
+++ b/src/ontology/imports/obi_import.owl
@@ -12,9 +12,9 @@
xmlns:terms="http://purl.org/dc/terms/"
xmlns:protege="http://protege.stanford.edu/plugins/owl/protege#">
-
- 2023-06-21
-
+
+ 2023-11-27
+
@@ -217,7 +217,7 @@
-
+
@@ -225,7 +225,7 @@
-
+
@@ -233,7 +233,7 @@
-
+
@@ -241,7 +241,7 @@
-
+
@@ -249,7 +249,7 @@
-
+
@@ -274,7 +274,7 @@
PERSON: Larry HunterPERSON: Melanie Coutot
-
+ has_specified_input
@@ -290,7 +290,7 @@
A relation between a planned process and a continuant participating in that process that is not created during the process. The presence of the continuant during the process is explicitly specified in the plan specification which the process realizes the concretization of.Alan RuttenbergPERSON:Bjoern Peters
-
+ is_specified_input_of
@@ -314,7 +314,7 @@
PERSON: Larry HunterPERSON: Melanie Courtot
-
+ has_specified_output
@@ -331,7 +331,7 @@
Alan RuttenbergPERSON:Bjoern Peters
-
+ is_specified_output_of
@@ -347,7 +347,7 @@
BP, AR, PPPB branchPPPB branch derivedmodified according to email thread from 1/23/09 in accordince with DT and PPPB branch
-
+ achieves_planned_objective
@@ -361,7 +361,7 @@
This relation obtains between an objective specification and a planned process when the criteria specified in the objective specification are met at the end of the planned process.OBIOBI
-
+ objective_achieved_by
@@ -376,7 +376,7 @@
A relation between a planned process and a continuant where the continuant can be a person, organization or device (such as a robot controlled by software workflow management system) that performs the planned process.OBIOBI
-
+ The 'has performer' relation covers the need to report on who performed a planned processed. It has to cover processes done by People or Devices (such as a robot controlled by software WF management system).has performer
@@ -386,7 +386,7 @@
-
+
@@ -394,7 +394,7 @@
-
+
@@ -414,7 +414,7 @@
-
+
@@ -422,7 +422,7 @@
-
+
@@ -430,7 +430,7 @@
-
+
@@ -438,7 +438,7 @@
-
+
@@ -475,7 +475,7 @@
-
+
@@ -495,7 +495,7 @@
-
+
@@ -503,7 +503,7 @@
-
+
@@ -511,7 +511,7 @@
-
+
@@ -525,7 +525,7 @@
-
+
@@ -545,7 +545,7 @@
-
+
@@ -578,7 +578,7 @@ objectives is a planned process.
This class merges the previously separated objective driven process and planned process, as they the separation proved hard to maintain. (1/22/09, branch call)6/11/9: Edited at workshop. Used to include: is initiated by an agent
-
+ planned process
@@ -604,7 +604,7 @@ objectives is a planned process.
Is a material entity that is created or changed during material processing.PERSON: Alan Ruttenberg
-
+ processed material
@@ -641,7 +641,7 @@ editor = PRS
Could add specific objective specificationstudy
-
+ investigation
@@ -672,7 +672,7 @@ editor = PRS
GROUP: Role BranchOBIFeb 10, 2009. changes after discussion at OBI Consortium Workshop Feb 2-6, 2009. accepted as core term.
-
+ evaluant role
@@ -741,15 +741,16 @@ editor = PRS
assayAssay the wavelength of light emitted by excited Neon atoms. Count of geese flying over a house.
- A planned process with the objective to produce information about the material entity that is the evaluant, by physically examining it or its proxies.
+ A planned process that has the objective to produce information about a material entity (the evaluant) by examining it.12/3/12: BP: the reference to the 'physical examination' is included to point out that a prediction is not an assay, as that does not require physical examiniation.
+ Discussion on OBI call 2023-05-01 resulted in an agreement to revise the textual definition of 'assay'. https://github.com/obi-ontology/obi/issues/1683.PlanAndPlannedProcess Branchmeasuringscientific observationOBI branch derivedstudy assayany method
-
+ assay
@@ -771,7 +772,7 @@ editor = PRS
PlanAndPlannedProcess BranchstudyOBI branch derived
-
+ sample preparation for assay
@@ -791,7 +792,7 @@ editor = PRS
Feb 10, 2009. changes after discussion at OBI Consortium Workshop Feb 2-6, 2009. accepted as core term.
May 28 2013. Updated definition taken from ReO based on discussions initiated in Philly 2011 workshop. Former defnition described a narrower view of reagents in chemistry that restricts bearers of the role to be chemical entities ("a role played by a molecular entity used to produce a chemical reaction to detect, measure, or produce other substances"). Updated definition allows for broader view of reagents in the domain of biomedical research to include larger materials that have parts that participate chemically in a molecular reaction or interaction.
-
+ (copied from ReO)
Reagents are distinguished from instruments or devices that also participate in scientific techniques by the fact that reagents are chemical or biological in nature and necessarily participate in or have parts that participate in some chemical interaction or reaction during their intended participation in some technique. By contrast, instruments do not participate in a chemical reaction/interaction during the technique.
@@ -836,7 +837,7 @@ In regard to the statement that reagents are 'distinct' from the speci
PERSON: Philippe Rocca Serramaterial transformationOBI branch derived
-
+ material processing
@@ -877,7 +878,7 @@ specimen can later be subject.
GROUP: Role BranchOBI
-
+ specimen role
@@ -935,7 +936,7 @@ specimen can later be subject.
OBIFeb 10, 2009. changes after discussion at OBI Consortium Workshop Feb 2-6, 2009. accepted as core term.study person role
-
+ Philly2013: Historically, this role would have been borne only by humans or organizations. However, we now also want to enable investigations run by robot scientists such as ADAM (King et al, Science, 2009)investigation agent role
@@ -982,7 +983,7 @@ for now.
PERSON: Philippe Rocca-SerraPERSON: Susanna SansoneGROUP: OBI
-
+ organization
@@ -999,7 +1000,7 @@ for now.
PlanAndPlannedProcess BranchOBI branch derived + wikipedia (http://en.wikipedia.org/wiki/Protocol_%28natural_sciences%29)study protocol
-
+ protocol
@@ -1028,7 +1029,7 @@ for now.
Bjoern PetersBjoern PetersPlans and Planned Processes Branch
-
+ planning
@@ -1045,7 +1046,7 @@ for now.
Daniel SchoberFrank GibsonMelanie Courtot
-
+ magnify function
@@ -1071,7 +1072,7 @@ for now.
An image acquisition function is a function to acquire an image of a materialFrank Gibson
-
+ image acquisition function
@@ -1098,7 +1099,7 @@ for now.
Frank Gibsonimage acquisition devicesep:00096
-
+ image creation device
@@ -1115,7 +1116,7 @@ for now.
Daniel SchoberFrank GibsonMelanie Courtot
-
+ solid support function
@@ -1131,7 +1132,7 @@ for now.
an objective specification to determine a specified type of information about an evaluated entity (the material entity bearing evaluant role)PPPB branchPPPB branch
-
+ assay objective
@@ -1166,7 +1167,7 @@ for now.
PERSON: Helen ParkinsonPERSON: Melanie CourtotPERSON:Frank Gibson
-
+ measure function
@@ -1187,7 +1188,7 @@ for now.
PERSON: Philippe Rocca-Serraartifact creation objectiveGROUP: OBI PlanAndPlannedProcess Branch
-
+ material transformation objective
@@ -1216,7 +1217,7 @@ for now.
Manufacturer role is a role which inheres in a person or organization and which is realized by a manufacturing process.GROUP: Role BranchOBI
-
+ manufacturer role
@@ -1238,7 +1239,7 @@ for now.
a quality inheres_in some device and is concretization of some (device_setting_specification and is_about a quality of the deviceThere is some question of whether 'device setting' is really best modelled as a quality. To be revisited after assay terms have been worked through. See https://github.com/obi-ontology/obi/issues/133PERSON: Frank Gibson
-
+ device setting
@@ -1284,7 +1285,7 @@ http://sourceforge.net/p/obi/obi-terms/716/
specimen collection5/31/2012: This process is not necessarily an acquisition, as specimens may be collected from materials already in posession6/9/09: used at workshop
-
+ specimen collection process
@@ -1300,7 +1301,7 @@ http://sourceforge.net/p/obi/obi-terms/716/
A objective specification to obtain a material entity for potential use as an input during an investigation.Bjoern PetersBjoern Peters
-
+ specimen collection objective
@@ -1316,7 +1317,7 @@ http://sourceforge.net/p/obi/obi-terms/716/
A material sample role is a specimen role borne by a material entity that is the output of a material sampling process.7/13/09: Note that this is a relational role: between the sample taken and the 'sampled' material of which the sample is thought to be representative off.
-
+ material sample role
@@ -1345,7 +1346,7 @@ http://sourceforge.net/p/obi/obi-terms/716/
sample populationsample
-
+ material sample
@@ -1372,7 +1373,7 @@ http://sourceforge.net/p/obi/obi-terms/716/
A device in which a measure function inheres.GROUP:OBI Philly workshopOBI
-
+ measurement device
@@ -1400,8 +1401,8 @@ http://sourceforge.net/p/obi/obi-terms/716/
manufacturer
- A person or organization that has a manufacturer role
-
+ A person or organization that has a manufacturer role.
+ manufacturer
@@ -1442,7 +1443,7 @@ In the examples above, a reagent is an operational component of a device, but th
PERSON: Helen ParkinsoninstrumentOBI development call 2012-12-17.
-
+ device
@@ -1470,7 +1471,7 @@ In the examples above, a reagent is an operational component of a device, but th
A planned process that captures an image of an object.PERSON: Jie Zhengimage acquisition
-
+ image creation
@@ -1487,7 +1488,7 @@ In the examples above, a reagent is an operational component of a device, but th
specimen IDNIAID GSCID-BRC metadata working groupSpecimen ID
-
+ NIAID GSCID-BRCspecimen identifier
@@ -1505,7 +1506,7 @@ In the examples above, a reagent is an operational component of a device, but th
NIAID GSCID-BRC metadata working groupstudy titleproject title
-
+ NIAID GSCID-BRCinvestigation title
@@ -1547,7 +1548,7 @@ In the examples above, a reagent is an operational component of a device, but th
PERSON: Chris Stoeckert, Jie ZhengNIAID GSCID-BRC metadata working groupComments
-
+ NIAID GSCID-BRCcomment on investigation
@@ -1571,7 +1572,7 @@ OBI doesn't take position as to when an organism starts or ends being an o
This issue is outside the scope of OBI.
GROUP: OBI Biomaterial BranchWEB: http://en.wikipedia.org/wiki/Organism
-
+ organism
@@ -1601,7 +1602,7 @@ This issue is outside the scope of OBI.
PERSON: Philippe Rocca-SerraGROUP: OBI Biomaterial Branch
-
+ specimen
@@ -1660,7 +1661,7 @@ This issue is outside the scope of OBI.
data processingBranch editors
-
+ data transformation
@@ -1677,7 +1678,7 @@ This issue is outside the scope of OBI.
Modified definition in 2013 Philly OBI workshopJames MalonePERSON: James Malone
-
+ data transformation objective
@@ -1693,7 +1694,7 @@ This issue is outside the scope of OBI.
solvent role is a role which inheres in a molecular entity capable of ensuring the dissolution of another chemical entity and realized by the process of solvationPhilippe Rocca-Serraadpated from wikipedia (http://en.wikipedia.org/wiki/Solvatation)
-
+ solvent role
@@ -1721,7 +1722,7 @@ This issue is outside the scope of OBI.
A microscope is an instrument which magnifies the view on objects (too small to be viewed by the naked eye) under increased resolution. A microscope can be an optical instrument but also and electronic instrument. There are various kind of optical microscopes, e.g confocal microscope, epifluoresence microscope)PERSON: Phillippe Rocca-Serrawikipedia
-
+ microscope
@@ -1743,7 +1744,7 @@ This issue is outside the scope of OBI.
A microscope slide is a device usually made of glass which is used as a solid matrix for (biological) material deposited on its surface and which is compatible for use with a microscope instrumentPERSON: Phillippe Rocca-SerraOBI biomaterial branch
-
+ microscope slide
@@ -1768,7 +1769,7 @@ This issue is outside the scope of OBI.
experimental designrediscussed at length (MC/JF/BP). 12/9/08). The definition was clarified to differentiate it from protocol.
-
+ study design
@@ -1878,7 +1879,7 @@ This issue is outside the scope of OBI.
Person:Alan RuttenbergPerson:Helen Parkinson2009/09/28 Alan Ruttenberg. Fucoidan-use-case
-
+ is member of organization
@@ -2014,7 +2015,7 @@ This issue is outside the scope of OBI.
See tracker:
https://sourceforge.net/tracker/index.php?func=detail&aid=3512902&group_id=177891&atid=886178Person: Jie Zheng
-
+ has organization member
@@ -2092,5 +2093,5 @@ https://sourceforge.net/tracker/index.php?func=detail&aid=3512902&group_
-
+
diff --git a/src/ontology/imports/omo_import.owl b/src/ontology/imports/omo_import.owl
index deef468..ca2d68b 100644
--- a/src/ontology/imports/omo_import.owl
+++ b/src/ontology/imports/omo_import.owl
@@ -7,9 +7,9 @@ Prefix(rdfs:=)
Ontology(
-
-Annotation()
-Annotation(owl:versionInfo "2023-06-21")
+
+Annotation()
+Annotation(owl:versionInfo "2023-11-27")
Declaration(Class())
Declaration(Class())
@@ -58,6 +58,7 @@ Declaration(NamedIndividual())
Declaration(NamedIndividual())
Declaration(NamedIndividual())
Declaration(NamedIndividual())
+Declaration(NamedIndividual())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
@@ -102,6 +103,11 @@ Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
+Declaration(AnnotationProperty())
+Declaration(AnnotationProperty())
+Declaration(AnnotationProperty())
+Declaration(AnnotationProperty())
+Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
@@ -120,7 +126,7 @@ Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
-Declaration(AnnotationProperty())
+Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
Declaration(AnnotationProperty())
@@ -190,7 +196,7 @@ We don't have definitions of 'meaning' or 'expression' or 'property'. For 'refer
Personally, I am more comfortable weakening definition to documentation, with instructions as to what is desirable.
-We also have the outstanding issue of how to aim different definitions to different audiences. A clinical audience reading chebi wants a different sort of definition documentation/definition from a chemistry trained audience, and similarly there is a need for a definition that is adequate for an ontologist to work with. "@en)
+We also have the outstanding issue of how to aim different definitions to different audiences. A clinical audience reading chebi wants a different sort of definition documentation/definition from a chemistry trained audience, and similarly there is a need for a definition that is adequate for an ontologist to work with."@en)
AnnotationAssertion( "PERSON:Daniel Schober"@en)
AnnotationAssertion( "GROUP:OBI:"@en)
AnnotationAssertion(rdfs:label "definition"@en)
@@ -509,7 +515,7 @@ AnnotationAssertion()
AnnotationAssertion( "2023-03-03"^^xsd:date)
AnnotationAssertion(rdfs:label "abbreviation")
-SubAnnotationPropertyOf()
+SubAnnotationPropertyOf()
# Annotation Property: (ambiguous synonym)
@@ -518,7 +524,7 @@ AnnotationAssertion()
AnnotationAssertion( "2023-03-03"^^xsd:date)
AnnotationAssertion(rdfs:label "ambiguous synonym")
-SubAnnotationPropertyOf()
+SubAnnotationPropertyOf()
# Annotation Property: (dubious synonym)
@@ -527,7 +533,7 @@ AnnotationAssertion()
AnnotationAssertion( "2023-03-03"^^xsd:date)
AnnotationAssertion(rdfs:label "dubious synonym")
-SubAnnotationPropertyOf()
+SubAnnotationPropertyOf()
# Annotation Property: (layperson synonym)
@@ -537,7 +543,7 @@ AnnotationAssertion()
AnnotationAssertion( "2023-03-03"^^xsd:date)
AnnotationAssertion(rdfs:label "layperson synonym")
-SubAnnotationPropertyOf()
+SubAnnotationPropertyOf()
# Annotation Property: (plural form)
@@ -547,7 +553,7 @@ AnnotationAssertion()
AnnotationAssertion( "2023-03-03"^^xsd:date)
AnnotationAssertion(rdfs:label "plural form")
-SubAnnotationPropertyOf()
+SubAnnotationPropertyOf()
# Annotation Property: (UK spelling synonym)
@@ -557,7 +563,7 @@ AnnotationAssertion()
AnnotationAssertion( "2023-03-03"^^xsd:date)
AnnotationAssertion(rdfs:label "UK spelling synonym")
-SubAnnotationPropertyOf()
+SubAnnotationPropertyOf()
# Annotation Property: (misspelling)
@@ -566,7 +572,7 @@ AnnotationAssertion()
AnnotationAssertion( "2023-03-03"^^xsd:date)
AnnotationAssertion(rdfs:label "misspelling")
-SubAnnotationPropertyOf()
+SubAnnotationPropertyOf()
# Annotation Property: (misnomer)
@@ -575,7 +581,58 @@ AnnotationAssertion()
AnnotationAssertion( "2023-03-03"^^xsd:date)
AnnotationAssertion(rdfs:label "misnomer")
-SubAnnotationPropertyOf()
+SubAnnotationPropertyOf()
+
+# Annotation Property: (previous name)
+
+AnnotationAssertion( "MAPT, the gene that encodes the Tau protein, has a previous name DDPAC. Note: in this case, the name type is more specifically the gene symbol.")
+AnnotationAssertion( "A synonym type for names that have been used as primary labels in the past.")
+AnnotationAssertion()
+AnnotationAssertion()
+AnnotationAssertion( "2023-07-25"^^xsd:date)
+AnnotationAssertion(rdfs:label "previous name")
+SubAnnotationPropertyOf()
+
+# Annotation Property: (legal name)
+
+AnnotationAssertion( "The legal name for Harvard University (https://ror.org/03vek6s52) is President and Fellows of Harvard College")
+AnnotationAssertion( "A synonym type for the legal entity name")
+AnnotationAssertion()
+AnnotationAssertion()
+AnnotationAssertion( "2023-07-27"^^xsd:date)
+AnnotationAssertion(rdfs:label "legal name")
+SubAnnotationPropertyOf()
+
+# Annotation Property: (International Nonproprietary Name)
+
+AnnotationAssertion( "CHEBI:46195 has been assigned the english International Nonproproprietary Name (INN) \"paracetamol\". In some cases such as this one, the INN might be the same as the ontology's primary label")
+AnnotationAssertion( "The International Nonproprietary Name (INN) is a standardize name for a pharmaceutical drug or active ingredient issued by the World Health Organization (WHO) meant to address the issues with country- or language-specific brand names. These are issued in several languages, including English, Latin, French, Russian, Spanish, Arabic, and Chinese.")
+AnnotationAssertion()
+AnnotationAssertion()
+AnnotationAssertion( "2023-09-30"^^xsd:date)
+AnnotationAssertion( "INN")
+AnnotationAssertion(rdfs:label "International Nonproprietary Name")
+SubAnnotationPropertyOf()
+
+# Annotation Property: (latin term)
+
+AnnotationAssertion( "nasopharynx (UBERON:0001728) has the latin name \"pars nasalis pharyngis")
+AnnotationAssertion( "A synonym type for describing Latin term synonyms.")
+AnnotationAssertion(