Download as PDF, PPTX
![Ontology development basic tools © María Poveda Villalón and Alba Fernández Izquierdo
Referenced artefacts from other
activities
Ontology implementation
Ontology
conceptualization
Ontology model
Ontology
encoding
Ontology
evaluation
Ontology code
Evaluated
ontology
Ontology reuse
Ont. Devel.
Users
Experts
Ont. Devel.
Ont. Devel.
Users
Experts
Ont. Devel.
Ontology
requirements
specification
ORSD
Ontology
publication
Online ontology
Ontology
maintenance
Issues, bugs, etc.
8
6
7
2,6,8
9
6,7
6, 7
2
6
Data documentation &
examples
ORSD
Implementation - Evaluation
14
Online and notifications in GitHub repository
https://github.com/mariapoveda/vicinity-ontology-wot
• It refers to the activity of checking the technical quality of
an ontology against a frame of reference. [NeOn]
• Logical consistency checking
• Domain coverage
• Check common errors
• Check functional requirements Themis (http://themis.linkeddata.es)
OOPS! (http://oops.linkeddata.es/)](https://image.slidesharecdn.com/tools-marriapoveda-220202095209/75/Ontology-development-basic-tools-14-2048.jpg)
![Ontology development basic tools © María Poveda Villalón and Alba Fernández Izquierdo
Evaluation - OOPS! – OntOlogy Pitfall Scanner!
16
§ Implements the 48 detection methods for 33 pitfalls
o Pitfalls selection
o Selection by dimensions and aspects
§ Web user interface http://oops.linkeddata.es/
§ Web service http://oops-ws.oeg-upm.net/
URI input
OWL
code
input
Importance level
Pitfall
description
Affected
elements
1. OOPS! USER INTERFACE AND WEB SERVICE
– oops:hasDescription: indicates the description of the suggestion value.
– oops:hasAffectedElement: this element will contain as many URIs as ele-
ments detected during the analysis.
Listing ?? shows an example of response provided by the web service in format
RDF/XML for the request shown in Listing ??. It can be observed that the request
indicated three pitfalls to be detected from which only two have been found.
1 <rdf:RDF
2 xmlns:rdf=" http: //www. w3 . org /1999/02/22´ rdf´syntax´ns#"
3 xmlns:owl=" http: //www. w3 . org /2002/07/ owl#"
4 xmlns:xsd=" http: //www. w3 . org /2001/XMLSchema#"
5 xmlns:oops=" http: //www. oeg´upm. net /oops#"
6 xmlns:rdfs=" http: //www. w3 . org /2000/01/ rdf´schema#" >
7 <r d f : D e s c r i p t i o n rdf:about=" http: //www. oeg´upm. net /oops#suggestion ">
8 <r d f : t y p e r d f : r e s o u r c e=" http: //www. w3 . org /2002/07/ owl#Class "/>
9 </ r d f : D e s c r i p t i o n>
10 <r d f : D e s c r i p t i o n rdf:about=" http: //www. oeg´upm. net /oops/ fdea1aa6 ´71d6´4557´
a17a´dc3244ff536b ">
11 <oops:hasCode rdf:datatype=" http: //www. w3 . org /2001/XMLSchema#s t r i n g ">P10</
oops:hasCode>
12 <oops:hasName rdf:datatype=" http: //www. w3 . org /2001/XMLSchema#s t r i n g ">Missing
d i s j o i n t n e s s [ 1 , 2 , 3 ]</oops:hasName>
13 <oops:hasDescription rdf:datatype=" http: //www. w3 . org /2001/XMLSchema#s t r i n g ">
The ontology l a c k s d i s j o i n t axioms between c l a s s e s or between p r o p e r t i e s
that should be defined as d i s j o i n t .</ oops:hasDescription> <r d f : t y p e
r d f : r e s o u r c e=" http: //www. oeg´upm. net /oops#p i t f a l l "/>
14 <oops:hasImportanceLevel rdf:datatype=" http: //www. w3 . org /2001/XMLSchema#
s t r i n g ">Important</ oops:hasImportanceLevel>
15 <oops:hasNumberAffectedElements rdf:datatype=" http: //www. w3 . org /2001/
XMLSchema#i n t e g e r ">1</ oops:hasNumberAffectedElements>
16 </ r d f : D e s c r i p t i o n>
17 <r d f : D e s c r i p t i o n rdf:about=" http: //www. oeg´upm. net /oops /496 ae03d ´48c6 ´406d´8
d07´530bf05c9ac1 ">
18 <o o p s : h a s P i t f a l l r d f : r e s o u r c e=" http: //www. oeg´upm. net /oops/ fdea1aa6 ´71d6
´4557´a17a´dc3244ff536b "/>
19 <r d f : t y p e r d f : r e s o u r c e=" http: //www. oeg´upm. net /oops#response "/>
20 </ r d f : D e s c r i p t i o n>
21 <r d f : D e s c r i p t i o n rdf:about=" http: //www. oeg´upm. net /oops#p i t f a l l ">
22 <r d f : t y p e r d f : r e s o u r c e=" http: //www. w3 . org /2002/07/ owl#Class "/>
23 </ r d f : D e s c r i p t i o n>
24 </rdf:RDF>
Listing 1.4: Example of XML/RDF response from the web service
Pitfall name
Pitfall frequency
Slide taken from “Trendy Practices and Tools in Ontological Engineering” by Dr. María Poveda Villalón](https://image.slidesharecdn.com/tools-marriapoveda-220202095209/75/Ontology-development-basic-tools-16-2048.jpg)
Uploaded byMaría Poveda Villalón
Ontology development basic tools
This document describes the ontology development process and provides basic tools and guidelines for ontology development. It outlines the typical activities in ontology development including requirement specification, conceptualization, implementation, evaluation, and maintenance. It provides examples and templates for creating an ontology requirements specification document and discusses techniques for requirement analysis including use cases and competency questions. The document also provides guidelines for conceptualizing an ontology model and encoding it using ontology languages like OWL.
More Related Content
Similar to Ontology development basic tools
![[BDD 2025 - Mobile Development] Exploring Apple’s On-Device FoundationModels](https://cdn.slidesharecdn.com/ss_thumbnails/md-exploringappleson-devicefoundationmodels-251124030840-d690542c-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Artificial Intelligence] Building AI Systems That Users (and Comp...](https://cdn.slidesharecdn.com/ss_thumbnails/ai-buildingaisystemsthatusersandcompanieslove-251124030845-038f7732-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Mobile Development] Crafting Immersive UI with E2E and AGSL Shade...](https://cdn.slidesharecdn.com/ss_thumbnails/md-craftingimmersiveuiwithe2eandagslshaderveronicaputrianggraini-251124030840-0c677f44-thumbnail.jpg?width=640&height=640&fit=bounds)
Ontology development basic tools
- 1. María Poveda Villalón,Ontology Engineering Group Alba Fernández Izquierdo, Ontology Engineering Group Universidad Politécnica de Madrid, Spain Ontology development basic tools @MariaPovedaV mpoveda@fi.upm.es Cronos Training
- 2. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Ontology development process overview 2 http://lot.linkeddata.es/ Legend Activity Artefacts Actors output Ontology requirements specification ORSD Ontology implementation Ontology Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. Ont. Devel. Users Experts Ont. Devel. Users Experts Ont. Devel. Users Experts Ont. Devel. Users Experts activity flow X (input) Artefact reference
- 3. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Requirement specification 3 Ontology requirements specification Functional Ont requirements proposal Use case specification Purpose and scope identification Functional Ont requirements proposal Functional Ont requirements completion Use cases Ontology purpose and scope Functional Ont requirements (early stage) Functional Ont requirements (verified) Data exchange identification Data documentation & examples ORSD formalization ORSD Ont. Devel. Users Experts Ont. Devel. Users Experts Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology implementation Ontology Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. Ont. Devel. Users Experts 1,2,3,4 5 Use case specification Purpose and scope identification Functional Ont requirements proposal Functional Ont requirements completion Data exchange identification ORSD formalization Ont. Devel. Users Experts 1,2,3,4 Use case specification Purpose and scope identification Functional Ont requirements completion Data exchange identification ORSD formalization Ont. Devel. Users Experts 1,2,3,4 1,2,3 1,2 5 Functional Ont requirements proposal Use case specification Purpose and scope identification Functional Ont requirements proposal Functional Ont requirements completion Ontology purpose and scope Functional Ont requirements (early stage) Functional Ont requirements (verified) Data exchange identification ORSD formalization ORSD Ont. Devel. Users Experts Ont. Devel. Users Experts Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology implementation Ontology Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. Ont. Devel. Users Experts 1,2,3,4 5 Use case specification Purpose and scope identification Functional Ont requirements proposal Functional Ont requirements completion Data exchange identification ORSD formalization Ont. Devel. Users Experts 6 1,2,3,4 Use case specification Purpose and scope identification Functional Ont requirements completion Data exchange identification ORSD formalization Ont. Devel. Users Experts 1 2 3 4 5 1,2,3,4 1,2,3 1,2 5 Functional Ont Requirements formalization (optional) Test suite Ont. Devel. Functional Ont Requirements formalization (optional) Functional Ont Requirements formalization (optional) Functional Ont Requirements formalization (optional) Test suite Ont. Devel. Functional Ont Requirements formalization (optional) Functional Ont Requirements formalization (optional) 7
- 4. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Requirement specification 4 Ontology requirements specification Functional Ont requirements proposal Use case specification Purpose and scope identification Functional Ont requirements proposal Functional Ont requirements completion Use cases Ontology purpose and scope Functional Ont requirements (early stage) Functional Ont requirements (verified) Data exchange identification Data documentation & examples ORSD formalization ORSD Ont. Devel. Users Experts Ont. Devel. Users Experts Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology implementation Ontology Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. Ont. Devel. Users Experts 1,2,3,4 5 Use case specification Purpose and scope identification Functional Ont requirements proposal Functional Ont requirements completion Data exchange identification ORSD formalization Ont. Devel. Users Experts 1,2,3,4 Use case specification Purpose and scope identification Functional Ont requirements completion Data exchange identification ORSD formalization Ont. Devel. Users Experts 1,2,3,4 1,2,3 1,2 5 Functional Ont requirements proposal Use case specification Purpose and scope identification Functional Ont requirements proposal Functional Ont requirements completion Ontology purpose and scope Functional Ont requirements (early stage) Functional Ont requirements (verified) Data exchange identification ORSD formalization ORSD Ont. Devel. Users Experts Ont. Devel. Users Experts Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology implementation Ontology Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. Ont. Devel. Users Experts 1,2,3,4 5 Use case specification Purpose and scope identification Functional Ont requirements proposal Functional Ont requirements completion Data exchange identification ORSD formalization Ont. Devel. Users Experts 6 1,2,3,4 Use case specification Purpose and scope identification Functional Ont requirements completion Data exchange identification ORSD formalization Ont. Devel. Users Experts 1 2 3 4 5 1,2,3,4 1,2,3 1,2 5 Functional Ont Requirements formalization (optional) Test suite Ont. Devel. Functional Ont Requirements formalization (optional) Functional Ont Requirements formalization (optional) Functional Ont Requirements formalization (optional) Test suite Ont. Devel. Functional Ont Requirements formalization (optional) Functional Ont Requirements formalization (optional) 7 https://lists.w3.org/Archives/Public/public-wot-ig/2016Dec/0016.html http://w3c.github.io/wot/current-practices/wot-practices
- 5. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Requirement specification - Tables 5 § Following METHONTOLOGY Gómez-Pérez, A., Corcho, O., and Fernández-López, M. (2004). Ontological Engineering: with examples from the areas of Knowledge Management, e-Commerce and the Semantic Web. Advanced Information and Knowledge Processing. Springer.
- 6. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Requirement specification – Competency Questions 6 § Following Competency Questions technique Grüninger, M. and Fox, M. S. (1995). Methodology for the design and evaluation of ontologies. In IJCAI’95, Workshop on Basic Ontological Issues in Knowledge Sharing Shared in online spreadsheets
- 7. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Requirement specification 7 CORAL corpus provides examples and requirements patterns http://coralcorpus.linkeddata.es/
- 8. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo ORSD example 8 Ontology Requirements Specification Document Template 1 Purpose The general goal of the BIMERR ontology and data model is to facilitate data sharing and interoperability among the BIMERR components through the BIMERR Interoperability Framework. 2 Scope The scope of the BIMERR ontologies is limited to the data shared through the BIF and external data sources needed in the energy efficiency domain and related domains like: KPIs, project management, weather, occupancy behavior, information objects, building geometry, building elements, materials and renovation measurements. 3 Implementation Language Ontology Web Language 4 Intended End-Users BIMERR components and application developers BIMERR end-users and stakeholders 5 Intended Uses Data model generation External data sources integration 6 Ontology Requirements a. Non-Functional Requirements Annotated in English Linked to standards when possible Open license Modular Online availability b. Functional Requirements: Groups of Competency Questions This section is provided for each specific domain in the confluence pages. ORSD template https://github.com/oeg-upm/LOT-resources/tree/master/ORSD
- 9. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Referenced artefacts from other activities Ontology implementation Ontology conceptualization Ontology model Ontology encoding Ontology evaluation Ontology code Evaluated ontology Ontology reuse Ont. Devel. Users Experts Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology requirements specification ORSD Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. 8 6 7 2,6,8 9 6,7 6, 7 2 6 Data documentation & examples ORSD Implementation 9
- 10. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Implementation - Conceptualization 10 • Goal: build an ontology model from the ontological requirements identified. • Could be graphical or described in a formal system • You can use • Chowlk (UML based notation) • Blackboard • Pen & pencil • Drawing tools (diagrams.net, visio, yEd…) 1 creationDate:: dateTime (1) Unit WebThing * (1..1) identifier:: String (F) ObservationLog hasPropertyObservationLog entryTimeStamp:: dateTime ObservationEntry hasObservationEntry name:: String description:: String ssn:SensingDevice ssn:Sensor WebThingProperty ssn:Property DynamicWebThingProperty ParameterWebThingProperty observedBy representsParameterProperty representsDynamicProperty representsProperty <<rdfs:subPropertyOf>> <<rdfs:subPropertyOf>> measuredInUnits modificationDate:: dateTime tag:: Literal Service exposesWebThing 1 isExposedByService <<owl:exactCardinality>> isPartOfWebThing WebThing * <<owl:exactCardinality>> observedBy 1 hasWebThingProperty isPartOfWebThing <<owl:inverseOf>> value:: Literal hasLatestEntry 1 hasObservationLog WebThingAction WebThingEntity wot:providesInter actionPattern wot:Thing wot:InteractionPattern wot:Property wot:Action wot:isAccessibleThrough wot:Endpoint wot:hasValueType wot:hasOutputData (1..1) wot:thingName:: String (0..1) wot:baseURI:: String (0..1) wot:isWritable:: Boolean (F) (0..1) wot:isRequired:: Boolean (F) (1..1) wot:interactionName:: String wot:DataFormat wot:DataType wot:UnitOfMeasure wot:isMeasuredIn (1..1) wot:href:: String (F) wot:MediaType wot:hasMediaType wot:VirtualThing wot:PhysicalThing wot:Communication Protocol wot:isProvidedOver Protocol (F) wot:hasInputData wot:hasOutputData wot:hasOutputData wot:isMeasuredIn wot:isAccessible Through wot:contains wot:contains (0..1) wot:defaultValue:: Literal wot:providesInterac tionPattern (0..N) wot:Thing wot:InteractionPattern wot:Event wot:isAccessibleThrough (0..N) wot:hasValueType (0..1) wot:hasOutputData (1..N) (1..1) wot:thingName:: String (0..1) wot:baseURI:: String (0..1) wot:isWritable:: Boolean (F) (0..1) wot:isRequired:: Boolean (F) (1..1) wot:interactionName:: String (0..N) wot:interactionDescription:: String wot:DataType om:Unit_of_measure wot:isMeasuredIn (0..1) (1..1) wot:href:: String (F) (1..1) wot:hasMediaType:: String [F) wot:Communication Protocol wot:isProvidedOver Protocol (F) (1..1) wot:hasInputData (0..1) wot:hasOutputData (1..N) wot:hasOutputData (1..N) wot:isMeasuredIn (0..1) wot:defaultValue:: Literal wot:Property wot:DataSchema wot:Security wot:isAccessibleThrough (0..N) wot:implements Security (0..N) wot:Link wot:isReadableThrough (0..N) wot:isWritableThrough (0..N) <<rdfs:subPropertyOf>> (0..1) wot:isQueueable:: Boolean (F) wot:Action wot:hasInputData (0..N) wot:hasOutputData (0..N)
- 11. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Implementation - Encoding 11 GitHub repository https://github.com/mariapoveda/vicinity-ontology-wot Openly managed in GitHub wot:providesInterac tionPattern (0..N) wot:Thing wot:InteractionPattern wot:Event wot:isAccessibleThrough (0..N) wot:hasValueType (0..1) wot:hasOutputData (1..N) (1..1) wot:thingName:: String (0..1) wot:baseURI:: String (0..1) wot:isWritable:: Boolean (F) (0..1) wot:isRequired:: Boolean (F) (1..1) wot:interactionName:: String (0..N) wot:interactionDescription:: String wot:DataType om:Unit_of_measure wot:isMeasuredIn (0..1) (1..1) wot:href:: String (F) (1..1) wot:hasMediaType:: String [F) wot:Communication Protocol wot:isProvidedOver Protocol (F) (1..1) wot:hasInputData (0..1) wot:hasOutputData (1..N) wot:hasOutputData (1..N) wot:isMeasuredIn (0..1) wot:defaultValue:: Literal wot:Property wot:DataSchema wot:Security wot:isAccessibleThrough (0..N) wot:implements Security (0..N) wot:Link wot:isReadableThrough (0..N) wot:isWritableThrough (0..N) <<rdfs:subPropertyOf>> (0..1) wot:isQueueable:: Boolean (F) wot:Action wot:hasInputData (0..N) wot:hasOutputData (0..N)
- 12. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Implementation - Encoding 12
- 13. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Referenced artefacts from other activities Ontology implementation Ontology conceptualization Ontology model Ontology encoding Ontology evaluation Ontology code Evaluated ontology Ontology reuse Ont. Devel. Users Experts Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology requirements specification ORSD Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. 8 6 7 2,6,8 9 6,7 6, 7 2 6 Data documentation & examples ORSD Implementation - Reuse 13 § Reusing knowledge resources … Look for existing ontologies: https://lov.linkeddata.es https://bioportal.bioontology.org/search Etc.
- 14. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Referenced artefacts from other activities Ontology implementation Ontology conceptualization Ontology model Ontology encoding Ontology evaluation Ontology code Evaluated ontology Ontology reuse Ont. Devel. Users Experts Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology requirements specification ORSD Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. 8 6 7 2,6,8 9 6,7 6, 7 2 6 Data documentation & examples ORSD Implementation - Evaluation 14 Online and notifications in GitHub repository https://github.com/mariapoveda/vicinity-ontology-wot • It refers to the activity of checking the technical quality of an ontology against a frame of reference. [NeOn] • Logical consistency checking • Domain coverage • Check common errors • Check functional requirements Themis (http://themis.linkeddata.es) OOPS! (http://oops.linkeddata.es/)
- 15. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Referenced artefacts from other activities Ontology implementation Ontology conceptualization Ontology model Ontology encoding Ontology evaluation Ontology code Evaluated ontology Ontology reuse Ont. Devel. Users Experts Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology requirements specification ORSD Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. 8 6 7 2,6,8 9 6,7 6, 7 2 6 Data documentation & examples ORSD Implementation - Evaluation 15 Online and integrated in OnToology with result in your GitHub repository http://oops.linkeddata.es Slide taken from “Trendy Practices and Tools in Ontological Engineering” by Dr. María Poveda Villalón
- 16. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Evaluation - OOPS! – OntOlogy Pitfall Scanner! 16 § Implements the 48 detection methods for 33 pitfalls o Pitfalls selection o Selection by dimensions and aspects § Web user interface http://oops.linkeddata.es/ § Web service http://oops-ws.oeg-upm.net/ URI input OWL code input Importance level Pitfall description Affected elements 1. OOPS! USER INTERFACE AND WEB SERVICE – oops:hasDescription: indicates the description of the suggestion value. – oops:hasAffectedElement: this element will contain as many URIs as ele- ments detected during the analysis. Listing ?? shows an example of response provided by the web service in format RDF/XML for the request shown in Listing ??. It can be observed that the request indicated three pitfalls to be detected from which only two have been found. 1 <rdf:RDF 2 xmlns:rdf=" http: //www. w3 . org /1999/02/22´ rdf´syntax´ns#" 3 xmlns:owl=" http: //www. w3 . org /2002/07/ owl#" 4 xmlns:xsd=" http: //www. w3 . org /2001/XMLSchema#" 5 xmlns:oops=" http: //www. oeg´upm. net /oops#" 6 xmlns:rdfs=" http: //www. w3 . org /2000/01/ rdf´schema#" > 7 <r d f : D e s c r i p t i o n rdf:about=" http: //www. oeg´upm. net /oops#suggestion "> 8 <r d f : t y p e r d f : r e s o u r c e=" http: //www. w3 . org /2002/07/ owl#Class "/> 9 </ r d f : D e s c r i p t i o n> 10 <r d f : D e s c r i p t i o n rdf:about=" http: //www. oeg´upm. net /oops/ fdea1aa6 ´71d6´4557´ a17a´dc3244ff536b "> 11 <oops:hasCode rdf:datatype=" http: //www. w3 . org /2001/XMLSchema#s t r i n g ">P10</ oops:hasCode> 12 <oops:hasName rdf:datatype=" http: //www. w3 . org /2001/XMLSchema#s t r i n g ">Missing d i s j o i n t n e s s [ 1 , 2 , 3 ]</oops:hasName> 13 <oops:hasDescription rdf:datatype=" http: //www. w3 . org /2001/XMLSchema#s t r i n g "> The ontology l a c k s d i s j o i n t axioms between c l a s s e s or between p r o p e r t i e s that should be defined as d i s j o i n t .</ oops:hasDescription> <r d f : t y p e r d f : r e s o u r c e=" http: //www. oeg´upm. net /oops#p i t f a l l "/> 14 <oops:hasImportanceLevel rdf:datatype=" http: //www. w3 . org /2001/XMLSchema# s t r i n g ">Important</ oops:hasImportanceLevel> 15 <oops:hasNumberAffectedElements rdf:datatype=" http: //www. w3 . org /2001/ XMLSchema#i n t e g e r ">1</ oops:hasNumberAffectedElements> 16 </ r d f : D e s c r i p t i o n> 17 <r d f : D e s c r i p t i o n rdf:about=" http: //www. oeg´upm. net /oops /496 ae03d ´48c6 ´406d´8 d07´530bf05c9ac1 "> 18 <o o p s : h a s P i t f a l l r d f : r e s o u r c e=" http: //www. oeg´upm. net /oops/ fdea1aa6 ´71d6 ´4557´a17a´dc3244ff536b "/> 19 <r d f : t y p e r d f : r e s o u r c e=" http: //www. oeg´upm. net /oops#response "/> 20 </ r d f : D e s c r i p t i o n> 21 <r d f : D e s c r i p t i o n rdf:about=" http: //www. oeg´upm. net /oops#p i t f a l l "> 22 <r d f : t y p e r d f : r e s o u r c e=" http: //www. w3 . org /2002/07/ owl#Class "/> 23 </ r d f : D e s c r i p t i o n> 24 </rdf:RDF> Listing 1.4: Example of XML/RDF response from the web service Pitfall name Pitfall frequency Slide taken from “Trendy Practices and Tools in Ontological Engineering” by Dr. María Poveda Villalón
- 17. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Referenced artefacts from other activities Ontology implementation Ontology conceptualization Ontology model Ontology encoding Ontology evaluation Ontology code Evaluated ontology Ontology reuse Ont. Devel. Users Experts Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology requirements specification ORSD Ontology publication Online ontology Ontology maintenance Issues, bugs, etc. 8 6 7 2,6,8 9 6,7 6, 7 2 6 Data documentation & examples ORSD Implementation - Evaluation 17 Available as an online web application and a REST API. Also integrated in OnToology http://themis.linkeddata.es THEMIS
- 18. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Evaluation - Themis 18 URI input File input URI input File input Test input Export tests in RDF § Tool to execute tests to verify an ontology § Based on a controlled testing language § Allows to load test files § Web user interface http://themis.linkeddata.es/ Results description
- 19. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Publication 19 Ontology publication Propose release candidate Ontology documentation Online publication Ontology release candidate HTML documentation Online ontology Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology requirements specification ORSD Ontology implementation Ontology Ontology maintenance Issues, bugs, etc. 11 12 9 10 9,11 9 Referenced artefacts from other activities 9 Evaluated ontology • HTML generation from OWL code • Multilingual • Separated sections +Diagrams +Descriptions +Examples • Own URI • purl, w3id, etc. • Content negotiation • Registry
- 20. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Ontology publication Propose release candidate Ontology documentation Online publication Ontology release candidate HTML documentation Online ontology Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology requirements specification ORSD Ontology implementation Ontology Ontology maintenance Issues, bugs, etc. 11 12 9 10 9,11 9 Referenced artefacts from other activities 9 Evaluated ontology Publication 20
- 21. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Publication (bundle) 21 Download bundle http://delta.linkeddata.es/def/core# Content Negotiation upload bundle Server
- 22. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Publication – Share your ontology 22 Ontology publication Propose release candidate Ontology documentation Online publication Ontology release candidate HTML documentation Online ontology Ont. Devel. Ont. Devel. Users Experts Ont. Devel. Ontology requirements specification ORSD Ontology implementation Ontology Ontology maintenance Issues, bugs, etc. 11 12 9 10 9,11 9 Referenced artefacts from other activities 9 Evaluated ontology https://lov.linkeddata.es § Mission: promote and facilitate the reuse of well documented vocabularies in the Linked Data ecosystem § Vocabularies registry and index § Datalift o http://datalift.org/ § Started at 2011 § Hosted by OEG
- 23. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Maintenance 23 Ontology requirements specification ORSD Ontology implementation Ontology Ontology publication Online ontology Ontology maintenance Bug detection New requirements Issues, bugs, etc. Ont. Devel. Users Experts Ont. Devel. 13 Referenced artefacts from other activities 9 Evaluated ontology 8,11 9,11 9,11 11 HTML documentation Openly reported in GitHub issue tracker: new needs, bugs, etc.
- 24. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Handle versions and distributed environments 24 Evaluation reports HTML documentation Diagrams Permanent Ids Content negotiation Bundle Pre-view http://ontoology.linkeddata.es Drag&Drop (BETA version) https://ontoologydd.linkeddata.es/
- 25. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Methodology in practice 25 http://vicinity.iot.linkeddata.es/ This slide has been taken from Raúl García Castro presentation at EMSE
- 26. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Questions 26 @MariaPovedaV mpovedavillalon mariapoveda MariaPovedaVillalon thepetiteontologist mpoveda@fi.upm.es Thanks for your attention!
- 27. Ontology development basictools © María Poveda Villalón and Alba Fernández Izquierdo Useful links 27 § Ontology conceptualization o Chowlk framework (notation + converter) https://chowlk.linkeddata.es/ § Ontology evaluation o OOPS! OntOlogy Pitfall Scanner http://oops.linkeddata.es/ § Vocabulary documentation o HTML: Widoco https://github.com/dgarijo/Widoco/ o Vocabulary registry • OEG vocabularies http://vocab.linkeddata.es/ o Vocabulary distributed development o OnToology http://ontoology.linkeddata.es/
- 28. María Poveda Villalón,Ontology Engineering Group Alba Fernández Izquierdo, Ontology Engineering Group Universidad Politécnica de Madrid, Spain Ontology development basic tools @MariaPovedaV mpoveda@fi.upm.es Cronos Training