A system to automate part of the collaborative ontology development process. Given a repository with an owl file, OnToology will survey it and produce diagrams, a complete documentation and validation based on common pitfalls.
Create a repository on GitHub with your ontologies. Add your repo to OnToology (e.g. user/reponame). Everything will be generated automatically and a pull request will be sent. You can visit the progress page to see in real time what is going on with your repository. A pull request will be created automatically with all of the resources (docs, diagrams, evaluation report, and JSON-LD). see the Step by Step page for more info.
English alphabets (caps and small), underscores, dashes, and dots. Other alphabets and characters are not supported.
We tested OnToology with: Chrome, Opera, Firefox, and Safari.
You can see what is going in the runs page . It show what is currently happening.
This is because chrome and firefox by default disable ajax on local html files. If you publish your ontology using OnToology you will be able to see it.
You can contact us by email: ontoology (at) delicias.dia.fi.upm.es .
Since the release of the tool, OnToology has been adopted by many projects (more than 100 repositories containing more than 500 ontologies). It has been used for ontologies in wide range of domains (e.g. energy, e-science, building, environment, smart cities, etc.). In this section, we present details on how OnToology was adopted in the development workflow of two different projects: VICINITY and ETSI Specialist Task Force 513.
VICINITY is a European project that contains a network of ontologies in the domain of
Internet of Things. The project has a GitHub repository for each ontology in the network, which is used to
store the ontology and to track all the issues related to it. In order to propose changes, the ontology
development team has to create a branch where all the proposed changes are made. Once OnToology generates
all the resources for this new branch, the developers create a pull request to the master branch to discuss
the modifications done to the ontology. If the ontology development team agrees on the changes the pull
request is accepted and the changes are merged to the master branch. Users also propose changes through the
GitHub issue tracker.
The ontologies are published under the domain http://vicinity.iot.linkeddata.es
and, therefore, the publication is not done with OnToology and the w3id services. However, the documentation
generated by OnToology is used for the publication of the ontologies.
The Figure below shows the VICINITY portal where all the ontologies for VICINITY project are listed.
ETSI Specialist Task Force 513 is a project endorsed by ETSI and European Commission in which context the SAREF4BLDG and SAREF4ENVI ontologies were developed. These two ontologies are stored in the same repository, and the ontology developers contribute to their implementation collaboratively. Both ontologies have been published with OnToology, which automatically publish the ontologies with persistent URI using w3id.