PerfectO: An Online Toolkit for Improving Quality …
173
3.6 Limitations of the Related Work
PerfectO and Widoco [49] (a tool not introduced yet) have the common objective
of helping developers to create more reusable ontologies. Widoco is an open-source
ontology documentation standalone Java application. Widoco is not integrated yet
within our PerfectO approach since it does not provide a web service to ease a fast
development. Widoco focuses on ontology documentation which refers to one step
in our ontology improvement methodology explained in Sect. 4.2.
The current literature focused on methodologies or validation tools (used in Table
3) to design good ontologies. We did not find any work surveying the existing webbased tools and designing the methodology which integrates current web services
to support better the design of reusable ontologies. Our PerfectO approach aims to
assist the LOV project by providing a web site to provide more guidance to help
ontology designers fixing ontology errors encountered with the validation tools.
4 PerfectO: Architecture and Implementation
The PerfectO architecture and its components are described in this section. PerfectO
demonstrates its applicability and validated experience for enhancing ontologies on
a particular use case for the Internet of Things.
4.1 PerfectO Architecture
The PerfectO architecture (depicted in Fig. 1) follows interoperability principles
established with the intention to exchange data with common ontologies [22]. The
architecture comprises GUIs, APIs, and core components. Ontology designers interact with our web-based software using Graphical User Interfaces (GUIs). Application
Programming Interfaces (APIs) are either employed by the GUI or by the ontology
designers and are developed according to RESTful principles [50]. The core components of the architecture are as follows:
1. Ontology improvement methodology encourages ontology designers to improve
the ontology (explained in Sect. 4.2). Improvement methodologies for datasets,
queries or reasoning mechanisms are left for future work.
2. Catalogs of Tools refers to state of the art (see Sect. 3). State of the art is also
shared online through clickable links and interactive mind maps
5 (introduced in
Sect. 6).
3. Dr. PerfectO Availability of Validation Tools (DPAT) checks the availability of
tools (see Sect. 7.3).
4. PerfectO Guidance selects a subset of validation tools (introduced in Sect. 7.3).
5 http://perfectsemanticweb.appspot.com/?p=ontology_sota.
173
3.6 Limitations of the Related Work
PerfectO and Widoco [49] (a tool not introduced yet) have the common objective
of helping developers to create more reusable ontologies. Widoco is an open-source
ontology documentation standalone Java application. Widoco is not integrated yet
within our PerfectO approach since it does not provide a web service to ease a fast
development. Widoco focuses on ontology documentation which refers to one step
in our ontology improvement methodology explained in Sect. 4.2.
The current literature focused on methodologies or validation tools (used in Table
3) to design good ontologies. We did not find any work surveying the existing webbased tools and designing the methodology which integrates current web services
to support better the design of reusable ontologies. Our PerfectO approach aims to
assist the LOV project by providing a web site to provide more guidance to help
ontology designers fixing ontology errors encountered with the validation tools.
4 PerfectO: Architecture and Implementation
The PerfectO architecture and its components are described in this section. PerfectO
demonstrates its applicability and validated experience for enhancing ontologies on
a particular use case for the Internet of Things.
4.1 PerfectO Architecture
The PerfectO architecture (depicted in Fig. 1) follows interoperability principles
established with the intention to exchange data with common ontologies [22]. The
architecture comprises GUIs, APIs, and core components. Ontology designers interact with our web-based software using Graphical User Interfaces (GUIs). Application
Programming Interfaces (APIs) are either employed by the GUI or by the ontology
designers and are developed according to RESTful principles [50]. The core components of the architecture are as follows:
1. Ontology improvement methodology encourages ontology designers to improve
the ontology (explained in Sect. 4.2). Improvement methodologies for datasets,
queries or reasoning mechanisms are left for future work.
2. Catalogs of Tools refers to state of the art (see Sect. 3). State of the art is also
shared online through clickable links and interactive mind maps
5 (introduced in
Sect. 6).
3. Dr. PerfectO Availability of Validation Tools (DPAT) checks the availability of
tools (see Sect. 7.3).
4. PerfectO Guidance selects a subset of validation tools (introduced in Sect. 7.3).
5 http://perfectsemanticweb.appspot.com/?p=ontology_sota.