After the Ontology Summit 2013 hackathon

In this post I am going to briefly talk about and show the outcomes from the Ontology Summit 2013 Hackathon. As I said in my previous post, OOPS! was involved in the projects “HC-03 Evaluation of OOPS!, OQuaRE and Other Tools for FIBO Ontologies” and “HC-07 Ontohub-OOR-OOPS! Integration”.

During the first project, we scanned a merged version of the FIBO OWL ontologies with OOPS! and analyse and discuss every pitfall detected. After this process, FIBO development team established that “most of the metrics were ones we would want to apply to the FIBO Business Conceptual Ontologies, not just operational ontologies.” Next steps were to apply also OQuaRE and OntoQA metrics to FIBO ontologies. Finally, we took another working day to determine how to apply OQuaRE characteristics to FIBO ontologies and map them to OntoQA metrics and OOPS! pitfalls. This set of slides summarizes the good and intensive work that the HC-03 team carried out during the project that was awarded with the “First IAOA Best OntologySummit Hackathon-Clinic Prize” during the Ontology Summit 2013 Symposium.

During the second project, OOPS! was integrated into Ontohub web interface and an API for the Ontohub-OOR integration was proposed. The great work mainly done by Ontohub development team is summarised in these slides. OOPS! team work during this project was overall about supporting and helping the Ontohub-OOPS! integration when needed providing details about the OOPS! RESTful web service.

Finally, here there is an example of an ontology analysed with OOPS! within the Ontohub portal. In the first screenshot there is a “Test with OOPS!” button that is active before the ontology is being scanned.

Example ontology before being scanned

Example ontology before being scanned

While OOPS! is scanning the ontology, the Ontohub interface shows the status information “OOPS State: pending” as in this screenshot:

Example of ontology during the scanning process

Example of ontology during the scanning process

When the process is done, the number of pitfalls detected, if any, is displayed (“5 responses” in this example) and an explanation of them is provided when clicking in the ontology element affected by the pitfall, as shown in the last screenshot:

Example of results for an object property

Example of results for an object property

Finally, these and other results from the Ontology Summit were presented at the Ontology Summit 2013 Symposium together with the Ontology Summit 2013 Comunique.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s