Towards an architecture to bind the Java and OWL languages

Jose M. Alcaraz Calero, Jorge Bernal Bernabe, Juan M. Marin Perez, Diego Sevilla Ruiz, Félix J. García Clemente, Gregorio Martínez Pérez

Research output: Contribution to journalArticlepeer-review

3 Citations (Scopus)


There exists a well-known trade off between imperative and declarative languages. Imperative languages such as Java are suitable to describe processes and how these processes should be done. Declarative languages such as OWL are used to describe systems and what is available in them. Each one has advantages and disadvantages and each one is more convenient in some circumstances than in others. For example, graphical interfaces might be easily implemented using the Java language whereas the description of the state of a system might be easily described in the OWL language. Hence, this proposal describes a binding process between Java and OWL to provide an architecture enabling the usage of both languages during software development and at run-time. The architecture allows getting the advantages of both programming paradigms, declarative and imperative, together. As a result, the reasoning capabilities provided by OWL could be used in Java applications whereas the flow control of applications and the I/O functions available in Java could be used seamlessly for OWL ontologies. The aim is to speed up software developments using the facilities provided by both types of languages. As a proof of concept, the proposed architecture has been implemented as an open source framework, and some technical details of this implementation together with statistical results of performance and scalability are discussed in this paper.
Original languageEnglish
Pages (from-to)17-41
Number of pages25
JournalJournal of Research and Practice in Information Technology
Issue number1
Publication statusPublished - 29 Feb 2012
Externally publishedYes


Dive into the research topics of 'Towards an architecture to bind the Java and OWL languages'. Together they form a unique fingerprint.

Cite this