Skip to content

Commit

Permalink
small addings
Browse files Browse the repository at this point in the history
  • Loading branch information
Ghislain committed May 14, 2015
1 parent 79acd64 commit df386bc
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 8 deletions.
13 changes: 7 additions & 6 deletions paper-isemantics2015/src/intro.tex
Original file line number Diff line number Diff line change
@@ -1,8 +1,9 @@
TO DO we have to extend this RElated work
\todo{we have to extend this Related work}

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{Heath_Bizer_2011}. 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.

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}. However, at the time of writing we have not found specific and detailed guidelines that describe how to reuse available vocabularies at fine granularity level,i.e., reusing specific classes and properties. Our claim is that this difficulty in how to reuse vocabularies at low fine grained level is one of major barriers to the vocabulary development and in consequence to deployment of Linked Data.
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}. However, at the time of writing we have not found specific and detailed guidelines that describe how to reuse available vocabularies at fine granularity level,i.e., reusing specific classes and properties. Our claim is that this difficulty in how to reuse vocabularies at low fine grained level is one of major barriers to the reuse of vocabularies on the Web 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.

Expand All @@ -21,14 +22,14 @@

\section{Reusing vocabulary elements\\ when building ontologies}\label{sec:reuse}

We have to improve this section
\todo{We have to improve this section}

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 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 include a score for each term retrieved.
\item Select the most appropriate term taking into the account its score.
\item Search for suitable vocabulary terms to reuse from the any vocabulary repository, such as BioPortal, LOV, Biotec.org, etc. The search should be conducted by using the terms of the application domain.
\item Assess the set of candidate terms from the vocabulary repository. In the particular case of LOV, the results include a score related to their ``importance'' in the corpus for each term retrieved.
\item Select the most appropriate term taking into the account its score. Other criteria can be also considered here: (i) the stability of the URI namespace, (i) the
\item Include the selected term in the ontology that has being developed. The selected term will be the external term. There are three alternatives in this case:
\begin{itemize}
\item Include the external term and use it directly in the local ontology by defining local axioms to/from that term in the local ontology.
Expand Down
6 changes: 4 additions & 2 deletions paper-isemantics2015/src/isemantics2015.tex
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,9 @@
%\CopyrightYear{2015}
%\crdata{978-1-4503-2927-9/14/09.}

\title{How to access and reuse ontologies in real-world scenarios}

%\title{How to access and reuse ontologies in real-world scenarios}
\title{Practical Guidelines for reusing vocabularies in real-world scenarios: A LOV-based Application}

\numberofauthors{3}
\author{
Expand Down Expand Up @@ -74,7 +76,7 @@
\end{abstract}

% Categories for the papers.
\todo{Find the right one here}
\todo{Find the right categories of the paper for acm}
\category{H.4}{Information Systems Applications}{Miscellaneous}
\category{H.3.5}{Online Information Services}{Data sharing}[Web-based services]

Expand Down

0 comments on commit df386bc

Please sign in to comment.