Skip to content

Commit

Permalink
added related work + some bib references
Browse files Browse the repository at this point in the history
  • Loading branch information
Ghislain committed Feb 22, 2015
1 parent ad63ed3 commit 6b0b6db
Show file tree
Hide file tree
Showing 5 changed files with 65 additions and 17 deletions.
18 changes: 12 additions & 6 deletions paper-eswc2015/src/eswc2015.tex
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,8 @@
\usepackage{color}
\newtheorem{deflda}{Axiom}
\newcommand{\todo}[1]{\noindent\textcolor{red}{{\bf \{TODO}: #1{\bf \}}}}
\newcommand{\neon}{NeOn }
\newcommand{\protege}{Prot{\'e}g{\'e}}

% Language Definitions for Turtle
\definecolor{olivegreen}{rgb}{0.2,0.8,0.5}
Expand Down Expand Up @@ -49,10 +51,11 @@
\institute{
Expert System Iberia, Campo de las Naciones, Madrid, Spain. \\
\and MONDECA, 35 boulevard de Strasbourg, Paris, France .\\
\email{[email protected],gatemezing@eurecom,[email protected] \\
\email{[email protected],[email protected],[email protected] \\
}
}

\authorrunning{Nuria Garc\'ia, G.A. Atemezing, B. Villaz{\'o}n}
\maketitle

%%%%%%%%%%%%%%%%%%
Expand All @@ -74,29 +77,32 @@ \section{Introduction}\label{sec:introduction}



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%% 2. Related work %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Related Work}\label{sec:soa}
\input{relatedwork}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%% 3.LOV APIs Description %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\section{Linked Open Vocabulaires (LOV)}\label{sec:lov}
\input{lov}



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%% 3.ProtegeLOV Description %%%
%%% 4.ProtegeLOV Description %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\section{Prot{\'e}g{\'e}LOV}\label{sec:classification}
\input{plugin-core}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%% 4. Conclusion and Future Work %%%
%%% 5. Conclusion and Future Work %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\section{Evaluation and Future Work}\label{sec:conclusion}
Expand All @@ -109,7 +115,7 @@ \section{Evaluation and Future Work}\label{sec:conclusion}
%%%%%%%%%%%%%%%%%%%%%%%%%

\paragraph{\textbf{Acknowledgments.}} %\label{sec:acknowledgments}
Thanks to Pierre-Yves and the LOV team for providing and maintaining a curated vocabularies and API access. We want to thank Antoine Zimmermann for the discussion we have long time ago.
Thanks to Pierre-Yves and the LOV team for providing and maintaining a curated vocabularies and API access.
% More acknowledgments here

\bibliographystyle{abbrv}
Expand Down
41 changes: 39 additions & 2 deletions paper-eswc2015/src/eswcbib.bib
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,17 @@ @incollection{protegevowl
publisher={Springer}
}

@BOOK{Heath_Bizer_2011,
title = {Linked Data: Evolving the Web into a Global Data Space: Theory and
Technology},
publisher = {Morgan \& Claypool Publishers},
year = {2011},
author = {Heath, Tom and Bizer, Christian},
volume = {1},
pages = {136},
journal = {Topology},
note = {http://www.morganclaypool.com/doi/abs/10.2200/S00334ED1V01Y201102WBE001}
}

@misc{pybernard12,
author = {Pierre-Yves Vandenbussche and Bernard Vatant},
Expand All @@ -18,7 +29,33 @@ @misc{pybernard12

@article{vandenbusschelov,
title={LOV: a gateway to reusable semantic vocabularies on the Web},
author={Vandenbussche, Pierre-Yves and Atemezingb, Ghislain A and Poveda-Villal{\'o}nc, Mar{\'\i}a and Vatant, Bernard},
booktitle= {under review at SWJ}
author={Vandenbussche, Pierre-Yves and Atemezing, Ghislain A and Poveda-Villal{\'o}nc, Mar{\'\i}a and Vatant, Bernard},
year = {2015},
note= {\url{http://www.semantic-web-journal.net/system/files/swj974.pdf}},
journal= {Semantic Web Journal (under review)}

}

@misc{neonguide2008 ,
author = {D'Aquin, Mathieu and Su\'arez-Figueroa, Mari Carmen},
title = {A Quick Guide to Knowledge Reuse with the Watson Plugin for the NeOn Toolkit},
year ={2008},
note = {\url{http://watson.kmi.open.ac.uk/DownloadsAndPublications_files/WNTP-guide.pdf}}

}

@ARTICLE{d2007watson,
author = {D'Aquin, M. and Baldassarre, C. and Gridinoc, L. and Sabou, M. and
Angeletou, S. and Motta, E.},
title = {Watson: Supporting next generation semantic web applications},
year = {2007}
}

@ARTICLE{haase2008neon,
author = {Haase, P. and Lewen, H. and Studer, R. and Tran, DT and Erdmann,
M. and d'Aquin, M. and Motta, E.},
title = {The neon ontology engineering toolkit},
journal = {In WWW},
year = {2008},
publisher = {Citeseer}
}
12 changes: 6 additions & 6 deletions paper-eswc2015/src/intro.tex
Original file line number Diff line number Diff line change
Expand Up @@ -2,22 +2,22 @@

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.

In this paper we propose an initial set of guidelines for this task, and provide technological support by means of a plugin for Prot{\'e}g{\'e}, 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 Prot{\'e}g{\'e} also lies on the availability to extend the core framework adding new functionalities by means of plug-ins.
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.

At the same time, 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.

Moreover, we propose in this paper to explore, design and implement a plug-in of LOV in Prot{\'e}g{\'e} 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}:
Moreover, we propose in this paper 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}
\item Import easily vocabularies from LOV into Prot{\'e}g{\'e}.
\item Import easily vocabularies from LOV into \protege.
\item Propose to the user a list of candidate vocabularies in LOV matching the term
\item Have an updating mechanism (synchronization) to LOV catalog
\item Check if a new vocabulary created in Prot{\'e}g{\'e} satisfied the LOV recommendations
\item Check if a new vocabulary created in \protege satisfied the LOV recommendations \cite{pybernard12}

\item Suggest to LOV a new created vocabulary within Prot{\'e}g{\'e}.
\item Suggest to LOV a new created vocabulary within \protege.
\end{itemize}

This paper presents Prot{\'e}g{\'e}, a first implementation of the LOV realized as a plugin for the ontology editor Prot{\'e}g{\'e}.
This paper presents \protege, a first implementation of the LOV realized as a plugin for the ontology editor \protege.

\section{Methodological discussion? - based on Antoine discussions}
The activity of building vocabularies by reusing available vocabularies consits of
Expand Down
4 changes: 2 additions & 2 deletions paper-eswc2015/src/lov.tex
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,12 @@ \subsection{LOV Catalogue}
The intended purpose of the LOV is to help users to find and reuse terms of vocabularies in Linked Open Data. For achieving that purpose, the LOV gives access to vocabularies metadata and terms using programmatic access with APIs, which are described in the following section.

\subsection{LOV API}
LOV APIs give a remote access to the many functions of LOV through a set of Restful services\footnote{\url{http://lov.okfn.org/dataset/lov/apidoc/}}. The basic design requirements for these APIs is that they should allow applications to get access to the very same information humans do via the User Interfaces. More precisely the APIs give access, through three different type of services (cf. figure \ref{fig:apis}), to functions related to:
LOV APIs give a remote access to the many functions of LOV through a set of Restful services\footnote{\url{http://lov.okfn.org/dataset/lov/apidoc/}}. The basic design requirements for these APIs is that they should allow applications to get access to the very same information humans do via the User Interfaces. More precisely the APIs give access, through three different type of services and functions related to:
\begin{enumerate}
\item vocabulary terms (classes, properties, datatypes and instances) providing functions to query the LOV search engine, with autocompletion features;
\item vocabulary browsing, in which a client can get access to the current list of vocabularies contained in the LOV catalogue and search for vocabularies for further purpose;
\item agents, or the ontology's creators, contributors or organizations. It also contains the search with autocompletion of an agent.
\end{enumerate}


%to continue

7 changes: 6 additions & 1 deletion paper-eswc2015/src/relatedwork.tex
Original file line number Diff line number Diff line change
@@ -1 +1,6 @@
Show here some work related to plugin for helping in ontology development:Neon and other
%Show here some work related to plugin for helping in ontology development:Neon and other
The BioPortal Reference Plugin\footnote{\url{http://protegewiki.stanford.edu/wiki/BioPortal_Reference_Plugin}} allows the user to insert into the ontology references to external ontologies and terminologies stored in BioPortal\footnote{\url{http://bioportal.bioontology.org/}}. The plugin allows to generate generate external reference of a selected term. Additionally, the BioPortal Import Plugin\footnote{\url{http://protegewiki.stanford.edu/wiki/BioPortal_Import_Plugin}} allows users to import classes from external ontologies stored in the BioPortal ontology repository. The user can import entire trees of classes with a desired depth and choose which properties to import for each class. However, those plugins work only with \protege 3.x releases and are not ported yet to recent versions.

Most closely related to the {\protege}LOV plugin are approaches that use semantic search engine to support the process of editing an ontology and make large scale knowledge reuse automatically integrated in the tool. An example is the Watson Plugin \cite{neonguide2008} for the \neon Toolkit \cite{haase2008neon}, a plugin supporting the \neon life-cycle management using the Watson \cite{d2007watson} APIs\footnote{\url{http://watson.kmi.open.ac.uk/WS_and_API.html}}.However the similar plugin for Protege\footnote{\url{http://protegewiki.stanford.edu/wiki/Watson_Search_Preview}} is just a proof of concept rather than a real plugin.


0 comments on commit 6b0b6db

Please sign in to comment.