Before we can give industry recommendations for incorporating ontology technology into its IT systems, we must consider two types of evaluation: content evaluation and ontology technology evaluation. Evaluating content is a must for preventing applications from using inconsistent, incorrect, or redundant ontologies. It’s unwise to publish an ontology that one or more software applications will use without first evaluating it. A well-evaluated ontology won’t guarantee the absence of problems, but it will make its use safer. Similarly, evaluating ontology technology will ease its integration with other software environments, ensuring a correct technology transfer from the academic to the industrial world. In this contribution, I explore both evaluation dimensions to try to answer the following questions:
[1]
Thomas R. Gruber,et al.
Toward principles for the design of ontologies used for knowledge sharing?
,
1995,
Int. J. Hum. Comput. Stud..
[2]
E. T. K. Sang.
Memory-Based Shallow Parsing
,
2002,
Journal of machine learning research.
[3]
Barry Smith,et al.
Formal Ontology in Information Systems (FOIS)
,
2001
.
[4]
Walter Daelemans,et al.
Mining for Lexons: Applying Unsupervised Learning Methods to Create Ontology Bases
,
2003,
CoopIS/DOA/ODBASE.
[5]
Asunción Gómez-Pérez,et al.
Results of Taxonomic Evaluation of RDF(S) and DAML+OIL ontologies using RDF(S) and DAML+OIL Validation Tools and Ontology Platforms import services
,
2003,
EON.