paper - intro, core and evaluation updated

paper-eswc2015/src/conclusions.tex

@@ -1 +1,15 @@
-Small evaluation with few users? and compare with NeOn plugin maybe.
+We have conducted an initial user driven evaluation of the tool.
+
+
+\subsection{Settings}
+
+\subsection{Execution and collecting results}
+We have created a form with a set of questions that is available here\footnote{\url{https://docs.google.com/forms/d/1aEewd8c1RCn5kStVPDaPPXApGY08lSX9IiZnohA-tB0/edit}}
+
+
+\subsection{Findings and observations}
+Table\ref{} shows ...
+
+
+
+\section{Conclusions and Future Work}\label{sec:conclusions}

paper-eswc2015/src/eswc2015.tex

@@ -46,16 +46,16 @@
 \title{The Prot{\'e}g{\'e}LOV Plugin: Ontology Access and Reuse for Everyone }
 
 
-\author{ Nuria Garc\'ia-Santa\inst{1}, Ghislain Auguste Atemezing\inst{2},\\ and Boris Villaz{\'o}n-Terrazas\inst{1}}
+\author{Nuria Garc\'ia-Santa\inst{1}, Ghislain Auguste Atemezing\inst{2},\\ and Boris Villaz{\'o}n-Terrazas\inst{1}}
 
 \institute{
 Expert System Iberia, Campo de las Naciones, Madrid, Spain. \\
 \and MONDECA, 35 boulevard de Strasbourg, Paris, France .\\
-\email{[email protected],[email protected],[email protected] \\
+\email{\{ngarcia,bvillazon\}@expertsystem.com,[email protected]\\
 }
 }  
 
-\authorrunning{Nuria Garc\'ia, G.A. Atemezing, B. Villaz{\'o}n}
+\authorrunning{N. Garc\'ia-Santa, G.A. Atemezing, B. Villaz{\'o}n-Terrazas}
 \maketitle
 
 %%%%%%%%%%%%%%%%%%
@@ -65,7 +65,7 @@
 \begin{abstract}
 Here goes the abstract in less than 200 words.
 
-\keywords{Plugin, ontology engineering, LOV, Prot{\'e}g{\'e}} 
+\keywords{Ontology engineering, Reusing ontology terms, LOV, Prot{\'e}g{\'e}} 
 \end{abstract}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%
@@ -105,7 +105,7 @@ \section{Prot{\'e}g{\'e}LOV}\label{sec:classification}
 %%%  5. Conclusion and Future Work  %%%
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
-\section{Evaluation and Future Work}\label{sec:conclusion}
+\section{Evaluation}\label{sec:evaluation}
 \input{conclusions}
 
 

paper-eswc2015/src/intro.tex

@@ -1,10 +1,10 @@
-So far, Linked Data principles and practices are being adopted by an increasing number of data providers, getting as result a global data space on the Web containing hundreds of LOD datasets \cite{Heath_Bizer_2011}. There are already several guidelines for generating, publishing, interlinking, and consuming Linked Data \cite{}. An important task, within the generation process, is to build the vocabulary to be used for modelling the domain of the data sources, and the common recommendation is to reuse as much as possible available vocabularies \cite{}. This reuse approach speeds up the vocabulary development, and therefore, publishers will save time, efforts, and resources. 
+So far, Linked Data principles and practices are being adopted by an increasing number of data providers, getting as result a global data space on the Web containing hundreds of LOD datasets \cite{Heath_Bizer_2011}. There are already several guidelines for generating, publishing, interlinking, and consuming Linked Data \cite{}. An important task, within the generation process, is to build the vocabulary to be used for modelling the domain of the data sources, and the common recommendation is to reuse as much as possible available vocabularies \cite{Heath_Bizer_2011,hyland14}. This reuse approach speeds up the vocabulary development, and therefore, publishers will save time, efforts, and resources. 
 
-At the time of writing we have not found specific and detailed guidelines that describe how to reuse available vocabularies when building vocabularies. There are research efforts, like the NeOn Methodology \cite{}, and the W3C Working Group Note \cite{}, but they do not provide guidelines on how to reuse vocabularies at low fine grained, i.e., reusing specific classes and properties. Our claim is that this difficulty in how to reuse vocabularies at low fine grained is one of major barriers to the vocabulary development and in consequence to deployment of Linked Data.
+At the time of writing we have not found specific and detailed guidelines that describe how to reuse available vocabularies when building vocabularies. There are research efforts, like the NeOn Methodology \cite{suarezfigueroa2012ontology}, the Best Practices for Publishing Linked Data - W3C Working Group Note \cite{hyland14}, and the work proposed by Lonsdale et al. \cite{Lonsdale2010318} but they do not provide guidelines on how to reuse vocabularies at low fine grained, i.e., reusing specific classes and properties. Our claim is that this difficulty in how to reuse vocabularies at low fine grained is one of major barriers to the vocabulary development and in consequence to deployment of Linked Data.
 
 Moreover, the recent success of Linked Open Vocabularies (LOV\footnote{\url{http://lov.okfn.org/dataset/lov/}}) as a central point for curated catalog of ontologies is helping to convey on best practices to publish vocabularies on the Web, as well as to help in the Data publication activity on the Web. LOV comes with many features, such as an API, a search function and a SPARQL endpoint.
 
-In this paper we propose an initial set of guidelines for this task, and provide technological support by means of a plugin for \protege, which is one the popular framework for developing ontologies in a variety of formats including OWL, RDF(S), and XML Schema. It is backed by a strong community of developers and users in many domains. One success on \protege also lies on the availability to extend the core framework adding new functionalities by means of plug-ins. In addition, we propose to explore, design and implement a plug-in of LOV in \protege for easing the development of ontologies by reusing existing vocabularies at low fine grained level. The tool has to improve the modeling and reuse of ontologies used in the LOD cloud
+In this paper we propose an initial set of guidelines for this task, and provide technological support by means of a plugin for \protege, which is one the popular framework for developing ontologies in a variety of formats including OWL, RDF(S), and XML Schema. It is backed by a strong community of developers and users in many domains. One success on \protege also lies on the availability to extend the core framework adding new functionalities by means of plug-ins. In addition, we propose to explore, design and implement a plug-in of LOV in \protege for easing the development of ontologies by reusing existing vocabularies at low fine grained level. The tool has to improve the modeling and reuse of ontologies used in the LOD cloud.
 
 %, by providing the following features in Prot{\'e}g{\'e}:
 %\begin{itemize}
@@ -17,15 +17,16 @@
 
 %This paper presents \protege, a first implementation of the LOV realized as a plugin for the ontology editor \protege. 
 
-\section{Reusing vocabularies when building ontologies}
-In this section we describe the procedure of reusing available vocabulares when building ontologies. In a nutshell, the activity of building vocabularies by reusing available vocabularies consits of
+\section{Reusing vocabulary elements when building ontologies}\label{sec:reuse}
+In this section we describe the procedure of reusing available vocabulary terms when building ontologies. In a nutshell, the task of building vocabularies by reusing available vocabulary terms consists of
 \begin{itemize}
-	\item Search for suitable vocabularies to reuse. As we aforementioned, LOV is the current reference for vocabularies in the LOD cloud. We conduct this search using the terms of the application domain. 
-	\item Once we have selected the particular term, of a particular vocabulary, we have to reuse the term that we need from external ontologies, but do not explicitly import it. In this case we do not benefit from the axioms of the external ontology unless we copy the relevant axioms too. But we benefit from the fact that we are reusing existing terms that are possible well known. We have three alternatives here
-	\begin{enumerate}
-		\item Include the term in our current ontology and include the \emph{owl:equivalentClass}/\emph{owl:equivalentProperty} axiom with the local term.
-		\item Include the term in our current ontology and include the \emph{rdfs:subClassOf}/\emph{rdfs:subPropertyOf} axiom with the local term.
-		\item Reuse the term directly in the local ontology, i.e., include all the axioms related of the current term.
-	\end{enumerate}
-		We can combine all the approaches. The approach we choose in each case can be based on reasoning issues (expressiveness, size, conformance to DL, modularity), querying issues, robustness, linkage, reusability, taste, belief, mood, magnetic field, humour, weather, topology, spirituality, life, etc.
+	\item Search for suitable vocabulary terms to reuse from the LOV repository. The search should be conducted by using the terms of the application domain.
+	\item Assess the set of candidate terms from LOV repository. In this particular case the results coming from LOV repository included a score for each term retrieved.
+	\item Select the most appropriate term taking into the account the score of the term.
+	\item Include the selected term in the ontology that has being developed. There are three alternatives 
+	\begin{itemize}
+		\item Include the external term and define the local axioms in the local ontology.
+		\item Include the external term, create a local term, and define the {\tt rdfs:subClassOf/ rdfs:suPropertyOf} axiom to related both terms.
+		\item Include the external term, create a local term, and define the {\tt owl:equivalentClass/ owl:equivalentProperty} axiom to relate both terms. It is possible to include local axioms to the local term.				
+	\end{itemize}
 \end{itemize}

paper-eswc2015/src/plugin-core.tex

@@ -1,17 +1,29 @@
-Explain our implementations.. views, controllers\\
-strategy used for handling the results obtained from LOV catalogue
+Prot{\'e}g{\'e}LOV it is an open source tool that provides support to the methodological guidelines described in section \ref{sec:reuse}. It is written in Java programming language as a plugin for the \protege ontology editor. It can be easily installed by just copying the jar file provided at the Prot{\'e}g{\'e}LOV website\footnote{\url{http://lab.isoco.net/prolov/}} into the plugins directory of an existing \protege installation. Then upon a new start, the user should select \emph{Linked Open Vocabularies} item, within the \emph{Ontology views} menu item.
+
+Prot{\'e}g{\'e}LOV provides the following functionalities 
+
+\paragraph{Search for a particular term (class or property) in LOV repository}. %The user selects a particular 
+
+\paragraph{Browse the list of terms, from LOV repository, which matches the search criteria}
+
+\paragraph{Reuse directly a particular term from LOV repository}
+
+\paragraph{Add the particular term and define the rdf:subClassOf/rdfs:subPropertyOf axiom}
+
+\paragraph{Add the particular term and define the owl:equivalentClass/owl:equivalentProperty axiom}
+
 
 \begin{figure}[!bht]
 \center
-\includegraphics[scale=0.6]{img/LOVmockup.png}
+\includegraphics[scale=0.5]{img/LOVmockup.png}
 \label{fig:LOVresults}
 \caption{Panel showing the results for searching a term in the class hierarchy.}
 \end{figure}
 
 
 \begin{figure}[!bht]
 \center
-\includegraphics[scale=0.6]{img/LOVOptions.png}
+\includegraphics[scale=0.5]{img/LOVOptions.png}
 \caption{Three actions currently available in the plugin after looking up a term in LOV catalogue: (a) reuse direct, (b) add equivalent axiom and (c) add subClass axiom}
 \label{fig:LOVoptions}
 \end{figure}