From OntologPSMW

Jump to: navigation, search
[ ]

This is one of the "OntologySummit2013_Hackathon_Clinics" Projects ...     (1)

Contents

Hackathon Project (HC-07): Ontohub-OOR-OOPS! Integration     (2)

Event Date / Time: (Day-3) Sat 2013.04.13 ... see: [ details]     (2B)

Archived work output can be found here     (2C)

Participant Volunteers:     (2D)

Add your name below, along with any time constraints or other participation-related comments. Thank you!     (2E)

Schedule Sat(-Sun) 2013.04.13(~14)     (2R)

Abstract     (2S)

The project aims at the integration of OOPS! [1] into the Ontohub [2,3] and OOR[4] ontology repositories. A user of Ontohub.org would see a button "evaluate with OOPS!". Then Ontohub.org or OOR instance would call the OOPS! webservice (or even a local installation of OOPS!), and display the results. The results should also be displayed in a per-class and per-property way in Ontohub.     (2S1)

see: [ [ Project document] ]     (2S2)

Collaborators     (2T)

Co-champions of this hackathon project team are mainly members of Ontohub team, the OOR team and the OOPS! team     (2T1)

We warmly welcome further Hackathon contributors.     (2T11)

Objective and Goals     (2U)

The Open Ontology Repository [4] is a joint effort in providing an ontology repository that significantly goes beyond the BioPortal repository in being more general (more domains and ontology languages), providing more services and being based on a decentralized architecture decoupled into several services [5]. Ontohub.org is a distributed heterogeneous ontology repository that aims at implementing the open ontology repository architecture [5]. OOPS! is a web service detecting some of the most common pitfalls appearing when developing ontologies. When combined, the result will be a web-based repository storing the feedback provided by OOPS! for many OWL ontologies, making it web-searchable and versioned. This means that the evolution of ontologies according to the feedback can be traced. This hackathon project will provide as well very useful feedback to improve OOPS!, maybe by including new cases or analysis false positive we might get and making it more precise.     (2U1)

Expected Deliverables     (2V)

  • webservices API that allows OOPS! to integrate with Ontohub, OOR or possible other software tools and environments.     (2V1)
  • code in the Ontohub code repository [2] providing the described functionality     (2V2)
  • functionality provided online at Ontohub.org     (2V3)

Work Plan     (2W)

The API that OOPS! provides [6,7] can be used for an ad-hoc integration with OntoIOp. We want to integrate the OOPS! output into the Ontohub.org display of classes and properties, and it would be valuable to get feedback on this integration. The idea is to have an agile development, with multiple concept - implementation - feedback loops during the day.     (2W1)

Moreover, we want to discuss a general API (in the OOR context) for services like OOPS!, and have this as an extension of the BioPortal resp. OOR API.     (2W2)

New proposed Ontohub architecture, inspired by OOR architecture [5]     (2X)

OOR API and Ontohub's needs     (2Y)

The OOR API is currently a REST API and is the same as BioPortal, see [8]. Note that Ontohub needs a much richer and sometimes also different API. This is because Ontohub not only supports OWL ontologies, but also ontologies written in other languages, e.g. Common Logic. (If I recall right, OOR shares this goal.) We will develop new APIs for federation, static analysis, inference etc. The new APIs are developed in this shared docuemnt.     (2Y1)

Resource / References     (2Z)


This page has been migrated from the OntologWiki - Click here for original page     (2Z11)