first commit

LICENSE

@@ -0,0 +1,29 @@
+BSD 3-Clause License
+
+Copyright (c) 2023, BASF SE
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

README.md

@@ -0,0 +1,49 @@
+# EPPO Ontology
+
+## Purpose and scope
+
+The EPPO ontology aims to represent the information available in the [EPPO Global database](https://gd.eppo.int/) and the relationships between the concepts identified therein. Therefore, this ontology is not limited to be used by a specific application, but has been developed in the interest of having a single, harmonized, and flexible source of the EPPO code system information.
+
+The scope of the vocabulary include taxonomic and non-taxonomic codes along with their code types, parent-child relationship per code, phytosanitary categorization, and their taxonomy level (if applicable). Further details on the information available in taxonomic and non-taxonomic classifications is presented in the following figure:
+
+<p align="center">
+ <img src="images/TaxoVsNonTaxo.jpg?raw=true" alt="schema" width="600"/>
+</p>
+
+## Ontology development methodology
+This ontology was developed according to the development lifecycle and guidelines proposed in the [BASF Governance Operational Model for Ontologies (GOMO)](https://zenodo.org/record/7007495#.ZFkjyxHP2Uk).
+
+### Requirements
+The requirements can be found [here](https://github.com/basf/EPPOontology/blob/main/requirements/requirements.xlsx), and are specified with an identifier, competency question and expected answer.
+
+### Ontology model
+
+This conceptual model shows a general overview of the classes and properties of the ontology. This model is depicted as a diagram which follows the [Chowlk notation](https://chowlk.linkeddata.es/notation.html).
+
+<p align="center">
+ <img src="images/OntologyDiagram.jpg" alt="schema" width="950"/>
+</p>
+
+Note that, due to the large number of terms contained in the EPPO Global database, this diagram only shows the main classes and properties represented in the ontology, but the ontology file contains all the hierarchical classifications included in the database for each class depicted in the diagram.
+
+### Ontology (OWL)
+
+The encoded ontology in the Web Ontology Language (OWL) can be found [here](https://github.com/basf/EPPOontology/blob/main/ontology/eppo.zip).
+
+## Contribute
+Contributions to improve the ontology or address any issues are welcome.
+The management of issues and improvements suggested for this ontology is done by addressing [issues](https://github.com/basf/EPPOontology/issues) in the repository. In order to push your contribution, just push your pull request to the develop branch. The master branch has only the code associated to the latest release.
+
+## Authors
+* Aarón Ayllón-Benitez - [aaron.ayllon@basf.com](mailto:aaron.ayllon@basf.com)
+* José Antonio Bernabé-Diaz - [jose-antonio.bernabe-diaz@basf.com](mailto:jose-antonio.bernabe-diaz@basf.com)
+* Paola Espinoza-Arias - [paola.espinoza@basf.com](mailto:paola.espinoza@basf.com)
+* Iker Esnaola-Gonzalez - [iker.esnaola@basf.com](mailto:iker.esnaola@basf.com)
+* Delphine S.A. Beeckman - [delphine.beeckman@basf.com](mailto:delphine.beeckman@basf.com)
+* Bonnie McCaig - [bonnie.mccaig@basf.com](mailto:bonnie.mccaig@basf.com)
+* Kristin Hanzlik - [kristin.hanzlik@basf.com](mailto:kristin.hanzlik@basf.com)
+* Toon Cools - [toon.cools@partners@basf.com](mailto:toon.cools@partners.basf.com)
+* Carlos Castro Iragorri
+* Nicolás Palacios
+
+BASF, May 2023 - Present