1
for Roads
Deliverable 3.4.1
Methodology guidelines and tools to develop (national) object libraries Editor
Esra Bektaş (TNO) Authors
Michel Böhms, Johan Taal, Bart Luiten, Peter Willems (TNO) Draft Version 1.0
30 September 2013
This document is an internal deliverable for V-Con parties. It will be used as a basis for further activities in the V-Con project.
-Con
.
-Con
.
2
Management Summary
The Virtual Construction for Roads (V-Con) project aims at improving the efficiency and effectiveness of the National Road Authorities by improving data exchange in the civil infrastructure sector using the Building Information Modelling (BIM) approach. As elaborated in D3.2, V-Con has two primary objectives;
1. establishing a draft version of a standardised information exchange structure,
2. procuring and testing software systems in a Pre-Commercial Procurement (PCP) that comply with this structure.
The V-Con project will develop a set of comprehensive ontologies to structure and manage road information, using the strengths of the existing standardization initiatives. An ontology editor, a prototype environment for developing the distributed collaborative ontologies will be set up, including user guides and the mappings, translations and conversions between different technologies. Based on this set of comprehensive ontologies, a Road Information Model server will be specified by the V-Con partners, and later developed by software vendors in a PCP process. Similarly, interfaces between this RIM server and end-user software applications will be specified by V-Con and later developed by software vendors. This deliverable will focus on an ontology editor environment as described in V-Con Deliverable 3.2, D32 Selection of information exchange standards.
3
Table of Contents
Management Summary ... 2
1. Introduction ... 4
1.1 The Focus of Deliverable 3.4.1 in Task 3.4 ... 4
1.2 Document Structure... 6
2. V-Con Ontology Editor... 7
3. CMO ... 9
4. Conclusion ... 10
References ... 11
Appendix A: Installation of V-Con Servers ... 12
Installation basic Ubuntu server ... 12
Installation WebProtege application server ... 15
Installation Fuseki application server ... 16
Installation Virtuoso application server ... 17
Appendix B: Modelling Guide... 19
Appendix C: CMO Approach ... 20
4
1. Introduction
This document is called Deliverable 3.4.1 (D3.4.1). It corresponds to the first part of task 3.4, which is defined as ‘develop national Object Libraries for highways” (DoW 2012, p.12). D3.4.1 comprises ‘making available an approach, tools and guidelines to enable the two road authorities (RWS and TV) to develop their own object libraries that allow these authorities to specify the information requirements details which then support their processes’. V-Con is a 4 year project that started in October 2012 with selecting the approach for the standardised information exchange structure in Task 3.1 and Task 3.2 of Work Package 3 (WP3). This document is the result of the first months of task 3.4 (T34), and is based on the results of T31 and T32. Below, the focus of this deliverable is clarified.
1.1 The Focus of Deliverable 3.4.1 in Task 3.4
The objective of T3.4 is to develop (national) object type libraries. As described in D32, the (national) object type libraries are the nation, company and project specific parts of a
distributed modelling structure. See
Figure 1-1for a snap shot of Figure 6.3 of D32. The object type libraries are extensions of an International Road Ontology, which is an extension of the general Concept Modelling Ontology (CMO). All these ontologies are represented in the same language, OWL2. Therefore, all these ontologies can be developed using one Ontology Editor.
Figure 1-1 Ontology structure in the V-Con approach, Snap shot of Figure 6.3 from D32. T3.4 splits into two main parts (See D.3.2 p.43):
1. Making an approach, tools and guidelines available for ontology development,
2. These results will be used by RWS and TRV to develop their own ontologies on top of the international Road Ontology (of T3.3) as illustrated in Figure 1-2.
5 Figure 1-2 shows that after making the ontology or object type library editor available, the road authorities, RWS and TRV will develop their ontologies.
D3.4.1 deals with the first part of T3.4, and its objective is to make ontology / object type library editor available. D3.4.1 thus will develop an ontology modelling environment, which is usable by ICT experts, called the Ontology Editor.
The Ontology Editor includes the following actions (See also Figure 1-3) from D3.2 Section 6.3;
· c19. Make the Ontology Editor available for (international, national, organization, and project) ontology development based on existing open source software tool like Protégé or free version of the commercial TopBraid Composer of TopQuadrant. · c18. Develop and agree the generic Concept Modelling Ontology (CMO) (archetypes,
decomposition, measures/units, and requirements) including modelling guidelines for OWL/CMO.
6 Figure 1-3 the deliverables described in D341 in the ontology structure of V-Con (See D3.2).
1.2 Document Structure
This document is structured as follows:
Chapter 1 provides an introduction about the context of this deliverable. It positions the D3.4.1 into main task –T3.4 as D3.4.1 is to develop an ontology modelling environment, which is usable by ICT experts, called the Ontology Editor.
Chapter 2 reports the progress on V-Con Ontology Editor. It presents the choice of using an existing software tool for ontology (“object library”) development and looking into different ontology editors such as TopQuadrant’s TopBraid Composer (TBC), TopBraid Composer Live, Stanford’s Protégé, Web Protégé and NeOn.
Chapter 3 reports the progress on CMO.
Chapter 4 provides the conclusions from the selection of the ontology editor and the CMO progress. These conclusions deal with 1) both the degree of easiness of the tools that is to develop ontologies (in international, national, company and project levels) and making them openly available; 2) the strength of the selected V-Con approach (in relation with the degree of easiness of the tools);
Appendix A provides the details of the installation of the three servers of V-Con. Appendix B presents the modelling guidelines.
Appendix C presents the CMO approach.
7
2. V-Con Ontology Editor
In V-Con, we decided to use an existing software tool for ontology (“object library”) development. Requirements from the existing software tool were established such as being open source, ease of implementation, strength of OWL support, strength of developing organisation, future proof etc. The complementing database server making use of the developed ontologies will be developed later by the software industry in a PCP process. For the ontology editor, we looked into several alternative ontology editors, including TopQuadrant’s TopBraid Composer (TBC), TopBraid Composer Live, Stanford’s Protégé, Web Protégé and NeOn (See Appendix A: Installation of V-Con Servers).
WebProtege is an open source, lightweight, web-based ontology editor. It provides a friendly and highly configurable user interface that can be adapted for the use of domain experts. It has support for form-based editing and full-fledged collaboration.
Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP.
Virtuoso is a next-generation Universal Server that facilitates the development and deployment of a new generation of Enterprise-wide, Internet, Intranet, and Extranet-based solutions, transcending prevalent enterprise challenge areas such as Disparate Databases and Data Sources, Web Service Composition, and Business Process Management. Ubuntu includes packages with pre-built Virtuoso binaries.
In order to accomplish an installation of Webprotege, Fuseki / Jena and Virtuoso, there was a need for a basic system configuration available. For V-Con, we selected using an open source system configuration based on the UBUNTU Linux version, which is a well spread Linux version, stable and commonly used in the Linux world. We used the Ubuntu 12.04.3 LTS desktop version. The installation needed a few basic libraries and additional libraries for each server application (See Appendix A: Installation of V-Con Servers). For the configuration, we chose to use 3 different Linux Ubuntu systems to avoid unnecessary problems arise between dependent libraries of different server applications. The basic server configurations we used are the same for the 3 servers. The installation steps were defined in details in Appendix A.
For the selection of the ontology editors, we decided to use Web Protégé (build 106 of 11. September 2013). Java-based Web Protégé is developed by Stanford University. Key factors for this choice are as follows:
· Strict support for the W3C Semantic Web open standards (RDF, RDFS, OWL2) · Fully Open Source Software (OSS) implementation at no cost (on multiple platforms) · Easy deployment and use anywhere in the cloud
· Unique multi-user collaboration support for large-scale ontology development · Support for GUID-based identification of ontology elements (classes, properties,
individuals)
· Large and active user group · Extension of user interface
8 In V-Con TNO deployed the ontology editor at
· http://vcon1.tno.nl:8080/webprotege More info on this software is available at:
· http://protege.stanford.edu/
9
3. CMO
Semantic Web technology developed by the World Wide Web Consortium (W3C) is the perfect medium for developing large-scale, web-based, multi-stakeholder information structures or ontologies that can be used for knowledge management and/or data exchange. Some modeling capabilities are however missing that we do not want to reinvent in every modeling case. These essential ingredients are modeled one time and CMO and then reused every time we need them.
Concept Modelling Ontology (CMO) is a reusable, generic ontology that enables full-power, pure semantic, parametric modelling adding extra semantic modelling capabilities cleanly on top of the existing W3C OWL language like:
• Decomposition (via Dublin Core’s dcterms:haspart), • Quantities (via the NASA “QUDT” unit model), • Typical properties and typical values,
• Links to documents & drawings (via “Dublin Core”).
The generic CMO ontology can be imported in any other CMO/OWL2-compliant end-user ontology.
CMO is a fully open standard that can be freely reused without any constraints besides mentioning trademark holders TNO, CSTB and RDF. This CMO is co-developed/used in several European projects (Odysseus, Proficient, V-Con, EcoDistrict) by TNO (NL), CSTB (FR) & RDF (BG)) but also in the Dutch BIR CB-NL initiative developing an ontology (concept library) for the Dutch construction sector (See Appendix C: CMO ). In other words, a first version of this CMO has been developed using experience from several EC RTD projects and national developments in the Netherlands.
10
4. Conclusion
Relatively easily the tools to develop the international, national, company and project ontologies have been made available in the cloud using generic, strong, free, fully supported open source software. This shows the strength of the selected V-Con approach based on the W3C Semantic Web open standards.
The top layer of the distributed modelling structure, the Concept Modelling Ontology, contains those generic modelling constructs “all model developers agree upon, but are not inherent to the language”. A first version of this CMO has been developed using experience from several EC RTD projects and national developments in the Netherlands. The ontology and the accompanying guidelines how to use the ontology are available openly.
The ontology editor and CMO are ready to be used in V-Con, both for developing the international Road Models (as a combination of BIM, GIS and Systems Engineering) and the object type libraries. At first, the tool will be used by ICT experts. In the course of the project also domain experts will use the tool. If deemed necessary the user interface of the ontology editor can be simplified by hiding parts of its functionality to the non-ICT experts.
11
References
CMO explanation: http://www.modelservers.org/public/documents/cmo.pptx CMO ontology: http://www.modelservers.org/public/ontologies/cmo.ttl
QUDT: http://qudt.org/ DCMI: http://dublincore.org/ W3C SW: http://www.w3.org/standards/semanticweb/ RDF: http://www.w3.org/TR/rdf-schema/ RDFS: http://www.w3.org/TR/rdf-schema/ OWL2: http://www.w3.org/TR/owl2-overview/ Turtle: http://www.w3.org/TeamSubmission/turtle/ SPARQL: http://www.w3.org/TR/rdf-sparql-query/ Fuseki: http://jena.apache.org/documentation/serving_data/index.html Protégé: http://protege.stanford.edu/
Deployed Web Protégé: http://vcon1.tno.nl:8080/webprotege/
TBC: http://www.topquadrant.com/products/TB_Composer.html Deployed Fuseki: http://vcon2.tno.nl:3030/
12
Appendix A: Installation of V-Con Servers
To accomplish an installation of Webprotege, Fuseki/Jena and Virtuoso there must be a basic system configuration available. For V-Con, we selected using an open source system configuration based on the UBUNTU Linux version. This is a well spread Linux version, stable and commonly used in the Linux world. For the configuration we chose to use 3 different Linux Ubuntu systems to avoid unnecessary problems arise between dependent libraries of different server applications. The basic server configurations we used are the same for the 3 servers.
Installation basic Ubuntu server
Ubuntu knows different distributions. We used the Ubuntu 12.04.3 LTS desktop version. This is a long-term support release. It has continuous hardware support improvements as well as guaranteed security and support updates until April 2017. This version is easy to use by the graphical user interface.
You can install Ubuntu on a regular Personal computer with an i3, i5 or i7 Intel processor. The hardware requirements for single use are:
- Intel processor (i3, i5, i7)
- Memory minimum 4 Gbyte
- Mimimum Disk capacity 100 Gb
- Mimimum VGA graphics
The installation needs a few basic libraries and additional libraries for each server application. The basis needed libraries will be installed step by step in this chapter. The specific libraries for applications will be discussed later.
Step by step basis installation
Execute the next steps to install Ubuntu:
1. Download the Linux Ubuntu distribution from: http://www.ubuntu.com/download/desktop
2. Select the 64 bit version. The 32 bit version is for older type processors like the single core Pentium IV processor
3. You can burn a CD with every common program like free CDburnerXP that can be downloaded at: http://cdburnerxp.se/nl/download
13 1. the system is started it will show you the next screen:
2. Click on the “Install Ubuntu” button
3. Check if every item on your system is correct and click on CONTINUE
4. Select the installation on the disk you want. Mostly you will do a complete clean installation and use the entire disk space but you can also install Ubuntu beside your windows system.
14 5. Click Install now
6. Select the country you are in by clicking on the right spot on the map
7. Select the keyboard layout you want to use and click on Continue
8. Fill in the name you like for your system and fill in your user information with the password you want
9. The installation will now be started and will show you all the features when it is installing. After a while the installation is completed and the system will ask you to restart. Please also remove the CD from the PC so it can restart from the new installation.
10.After the reboot you can login to your Ubuntu system with the userid and password given during installation.
15
Installation WebProtege application server
WebProtege is an open source, lightweight, web-based ontology editor. WebProtege provides a friendly and highly configurable user interface that can be adapted for the use of domain experts. It has support for form-based editing and full-fledged collaboration. To run Webprotege you have to install:
A. Tomcat B. MongoDB
C. Download the webprotege WAR file
A. Tomcat installation step by step
· Download command: get http://mirror.atlanticmetro.net/apache/tomcat/tomcat-7/v7.0.29/bin/apache-tomcat-7.0.29.tar.gz
· Uncompress the download: tar xvzf apache-tomcat-7.0.29.tar.gz · Install java dependencies: sudo apt-get install default-jdk
· Add the next environment variable to your shell: o export JAVA_HOME=/usr/lib/jvm/default-java o export CATALINA_HOME=~/path/to/tomcat · activate your environment by: source .bashrc
· start tomcat with the command: CATALINA_HOME/bin/startup.sh
To check if tomcat is working you can startup your Internet browser with the URL: http://your_IP_address:8080. When it startup ok it will show you:
B. MongoDB installation step by step
· first you have to configure the package management system with: sudo apt-key adv --keyserver hkp://--keyserver.ubuntu.com:80 --recv 7F0CEB10
· Create a /etc/apt/sources.list.d/mongodb.list file using the following command: repo/ubuntu-upstart dist 10gen' | sudo tee /etc/apt/sources.list.d/mongodb.list · Update the software with: sudo apt-get update
· And upgrade with: sudo apt-get upgrade
16 · Start MongoDB wit: sudo service mongodb start
C. Download the protégé WAR file
· http://protege.stanford.edu/download/webprotege/webprotege_2013.07.24-105.zip · Unpack the downloaded ZIP file and copy the WAR file to the data directory
/data/webprotege or to /var/lib/tomcat7/webapps/webprotege and make a softlink from /data/webprotege to it
· Startup your Internet browser with the URL: http://<your_IP_address>:8080/webprotege
if everything works ok the next screen will appear in your viewer:
Installation Fuseki application server
Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP.
· Download the most recent Fuseki distribution (look for a recent jena-fuseki-*-distribution.tar.gz) on the directory: http://www.apache.org/dist/jena/binaries/ · Unzip the download in the destination folder you want
· Make the binary file executable with the command: chmod +x fuseki-server s-*
· Start the server with the command: ./fuseki-server --mem /ds
· If the binaries are correctly installed there will be some startup lines shown in your startup window
17 · When the Fuseki application server is complaining at startup it is possible that
some depended libraries are needed in the standard linux distribution. Look at the error messages and install the needed libraries with the command: sudo apt-het install <librarie>
· Start you Internet browser with the URL: http://<your_IP_address>:3030/ If Fuseki server is started correctly you will see the next window on your screen:
Installation Virtuoso application server
Virtuoso is a next-generation Universal Server that facilitates the development and deployment of a new generation of Enterprise-wide, Internet, Intranet, and Extranet-based solutions, transcending prevalent enterprise challenge areas such as Disparate Databases and Data Sources, Web Service Composition, and Business Process Management. Ubuntu includes packages with pre-built Virtuoso binaries. You can install Virtuoso using these, or, if a newer version is available upstream or you want to specify your own configuration options, you can build directly from source. Follow the next steps to install Vurtuoso on Unbuntu Linux server:
· Start updating the system software and dependencies with the commands: o sudo apt-get update
o sudo apt-get upgrade
· Ubuntu have split Virtuoso into a handful of packages so you can install only the bits you require; further, the packages cater for both minimal installations and as a
database in its own right: apt-cache search '^virtuoso'
· Now start the basic installation with the command: sudo aptitude install virtuoso-opensource
· As part of the installation, Ubuntu will ask you for passwords to use for the DBA (main database administrative) and DAV users. If you leave these blank, the Virtuoso
18 service will not start after installation. Fill the password you want.
· After the installation is ended start-up your Internet browser with the URL: http://<your_IP_address>:8890/conductor
19
Appendix B: Modelling Guide
20
Appendix C: CMO Approach
21
Appendix D: List of Abbreviations
BIM: Building Information Model(ling)
CB-NL: De Nederlandse Conceptenbibliotheek CMO: Concept Modelling Ontology
DoW: Description of Work
GIS: Geographic information system
GUID/UID: Globally Unique Identifier/Universally Unique Identifier OWL: Web Ontology Language
OWL2: Web Ontology Language (Second Edition) OSS: Open Source Software
PCP: Pre-Commercial Procurement
QUDT: Quantities, Units, Dimensions and Data Types Ontologies RDF: Resource Description Framework
RDFS: Resource Description Framework Schema
RWS Rijkswaterstaat the National Road Authorities in the Netherlands TBC: TopBraid Composer
TRV Trafikverket the National Road Authorities in Sweden W3C: World Wide Web Consortium