180
A. Gyrard et al.
5.1 Ontology Quality Evaluation
We complete a detailed evaluation with 26 IoT or smart cities ontologies referenced within the LOV4IoT ontology catalog (summarized in Table 4 and accessible
online
13 ). However, the PerfectO approach is generic enough to be applied to any
ontologies (e.g., from the LOV ontology catalog). Those ontologies are tested with six
ontology improvement tools (Parrot, WebVOWL, Oops, TripleChecker, LODE, and
Vapour) mentioned in Table 3. Numerous ontologies cannot be successfully loaded
with all of the tools and show that multiple errors are encountered. The LODE tool is
preferred because more ontologies can be automatically documented, as compared
to the Parrot tool. Furthermore, in March 2019, the Parrot automatic documentation
web service does not seem maintained anymore.
As an example, a set of errors encountered with those tools:
• [Parrot] Unable to read input document: invalid mimeType “application/octetstream” (returned by URI) for parrot.
• [Parrot] No error encountered when loaded the ontology, but nothing is displayed.
• [Parrot] I/O Error: Server returned HTTP response code: 403 for URL.
• [Parrot] Unable to read input document: applicationrdfxml parse error: Content
is not allowed in prolog.
• [TripleChecker] Misuse of terms from Dublin Core namespace and date format
with TripleChecker.
• [TripleChecker] ERROR: VERY close match to “license.”
• [TripleChecker] Error loading—No parser available.
• [WebVOWL] ERROR “There is nothing to visualize.”
• [OOPS] OOPS Pitfall P36: URI contains file extension.
• [OOPS] OOPS Pitfall P37: Ontology not available on the Web.
• [LODE] Reason: An empty sequence is not allowed as the value of variable $rdf.
• [LODE] Reason: A sequence of more than one item is not allowed as the @select
attribute of xsl:sort.
• [LODE] Reason: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
• [LODE] The source can’t be downloaded in any permitted format. Connection
reset Connection reset Connection reset Connection reset Connection reset Connection reset.
• [LODE] The source can’t be downloaded in any permitted format. Received fatal
alert: protocol_version.
• [LOV] Bad IRI: http://example.com Code: 57/REQUIRED_COMPONENT_
MISSING in HOST: A component that is required by the schema is missing.
Some errors are more complicated to fix such as the server configuration. Also,
when the syntax is checked with tools such as OWL Manchester validators, errors
still arise when loading the ontologies.
13 http://perfectsemanticweb.appspot.com/?p=evaluation_lov4iot_perfecto.
A. Gyrard et al.
5.1 Ontology Quality Evaluation
We complete a detailed evaluation with 26 IoT or smart cities ontologies referenced within the LOV4IoT ontology catalog (summarized in Table 4 and accessible
online
13 ). However, the PerfectO approach is generic enough to be applied to any
ontologies (e.g., from the LOV ontology catalog). Those ontologies are tested with six
ontology improvement tools (Parrot, WebVOWL, Oops, TripleChecker, LODE, and
Vapour) mentioned in Table 3. Numerous ontologies cannot be successfully loaded
with all of the tools and show that multiple errors are encountered. The LODE tool is
preferred because more ontologies can be automatically documented, as compared
to the Parrot tool. Furthermore, in March 2019, the Parrot automatic documentation
web service does not seem maintained anymore.
As an example, a set of errors encountered with those tools:
• [Parrot] Unable to read input document: invalid mimeType “application/octetstream” (returned by URI) for parrot.
• [Parrot] No error encountered when loaded the ontology, but nothing is displayed.
• [Parrot] I/O Error: Server returned HTTP response code: 403 for URL.
• [Parrot] Unable to read input document: applicationrdfxml parse error: Content
is not allowed in prolog.
• [TripleChecker] Misuse of terms from Dublin Core namespace and date format
with TripleChecker.
• [TripleChecker] ERROR: VERY close match to “license.”
• [TripleChecker] Error loading—No parser available.
• [WebVOWL] ERROR “There is nothing to visualize.”
• [OOPS] OOPS Pitfall P36: URI contains file extension.
• [OOPS] OOPS Pitfall P37: Ontology not available on the Web.
• [LODE] Reason: An empty sequence is not allowed as the value of variable $rdf.
• [LODE] Reason: A sequence of more than one item is not allowed as the @select
attribute of xsl:sort.
• [LODE] Reason: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
• [LODE] The source can’t be downloaded in any permitted format. Connection
reset Connection reset Connection reset Connection reset Connection reset Connection reset.
• [LODE] The source can’t be downloaded in any permitted format. Received fatal
alert: protocol_version.
• [LOV] Bad IRI: http://example.com Code: 57/REQUIRED_COMPONENT_
MISSING in HOST: A component that is required by the schema is missing.
Some errors are more complicated to fix such as the server configuration. Also,
when the syntax is checked with tools such as OWL Manchester validators, errors
still arise when loading the ontologies.
13 http://perfectsemanticweb.appspot.com/?p=evaluation_lov4iot_perfecto.