Dear all,
at OEG we are currently working on evaluating the DBpedia ontology
from different perspectives: using OOPS! [1], inspecting manually the
ontology for finding some modeling issues that could be improved
(subclassOf issues, instanceOf issues, partOf issues, etc.), looking for
modeling patterns in subdomains, and so on.
Of course, we will share our results when we finish the research in
order to know your opinions and suggestions.
In addition, I read the googleDoc and included a pair of comments.
In this regard, one of the possible improvement of the DBpedia ontology
could be to modularize the model in order to facilitate the search of
concepts and properties (something similar to restructure the monolitic
ontology into a kind of ontology network).
Unfortunately, I will not be able to attend the meeting, but at least
two of my colleagues will be in Dublin.
Best Regards,
Mari Carmen.
------
[1] http://oops.linkeddata.es/
El 03/02/2015 a las 9:44, Heiko Paulheim escribió:
Hi all,
I am currently working with Aldo Gangemi on exploiting the mappings to
DOLCE (and the high level disjointness axioms in DOLCE) for finding
modeling issues both in the instances and the ontology.
I will not be able to travel to the meeting either, but of course we
will share our findings once we're finished, and probably also ask for
some input and feedback.
Cheers,
Heiko
Am 03.02.2015 um 09:39 schrieb Harald Sack:
Dear Dimitris,
I'm happy to hear that more work will be invested into a
reorganization of the DBpedia ontology. As you might know, together
with Magnus we have already invested some thoughts (and publications)
into the topic with the focus on data cleansing based on an improved
DBpedia ontology.[1,2] Unfortunately, Magnus and I will not be able
to participate live at the Dublin Meeting in Feb 9. Nevertheless, we
would like to contribute.
From our perspective we would like to apply the DBpedia ontology to
detect inconsistencies and flaws in DBpedia facts. This should not
only be possible in a retroactive way, but should take place much
earlier. Besides the detection of inconsistencies during the mapping
process or afterwards in the extracted data, this could already be
possible right from the start when the user is changing the wikipedia
infobox content (in the sense of type checking for
domain/range, checking of class disjointness and further constraints,
plausibility check for dates in connection with basic axioms to be
defined, etc.). Another possibility would be a tool that makes
inconsistencies/flaws in wikipedia data visible directly in the
wikipedia interface, where users could either correct them or confirm
facts that are originally in doubt. To achieve this, not only a
formally sound and semantically enrichedDBpedia ontology including a
set of basic axioms would be necessary, but also the applications and
infrastructure that make use of the ontology.
Also the relation of the DBpedia ontology to other ontologies would
be a rather interesting topic. This includes the already proposed
schemata (schema.org <http://schema.org>, facebook OG, etc) as well
as established ontologies (yago, umbel, etc...) where mapping to
DBpedia entities already exist. Can we make use of these ontologies
(and existing mappings) to complement DBpedia ontology in som
(semi-)automated way?
Thanks and best regards,
Harald
[1] G. Töpper, M. Knuth, and H. Sack: DBpedia ontology enrichment for
inconsistency detection. i-SEMANTICS 2012
[2] J. Waitelonis, N. Ludwig, M. Knuth, H. Sack: Whoknows? -
Evaluating Linked Data Heuristics with a Quiz that cleans up DBpedia.
ITSE, vol.8, 2011 (3)
On 23 Jan 2015, at 20:06, Dimitris Kontokostas
<[email protected]
<mailto:[email protected]>> wrote:
Dear all,
We are in the process of reorganizing the DBpedia ontology. Anyone
who is interested to contribute to the future directions of the
project is welcome to join.
The plan is as follows:
1) We have a dedicated session in the next DBpedia meeting in Dublin
(Feb 9th) [1] where we will discuss the editing workflow, future
directions and the formation of the DBpedia ontology committee [2].
2) The committee will be responsible to set the future plans & rules
that will be announced shortly after the meeting.
Best regards,
Dimtiris
[1] wiki.dbpedia.org/meetings/Dublin2015
<http://wiki.dbpedia.org/meetings/Dublin2015>
[2] http://mappings.dbpedia.org/index.php/DBpedia_Ontology_Committee
--
Dimitris Kontokostas
Department of Computer Science, University of Leipzig
Research Group: http://aksw.org <http://aksw.org/>
Homepage:http://aksw.org/DimitrisKontokostas
Dr. Harald Sack
Hasso-Plattner-Institut für Softwaresystemtechnik GmbH
Prof.-Dr.-Helmert-Str. 2-3
D-14482 Potsdam
Germany
Amtsgericht Potsdam, HRB 12184
Geschäftsführung: Prof. Dr. Christoph Meinel
Tel.: +49 (0)331-5509-527
Fax: +49 (0)331-5509-325
E-Mail: [email protected]
<mailto:[email protected]>
http://www.hpi.uni-potsdam.de/meinel/team/sack.html
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now.http://goparallel.sourceforge.net/
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
--
Prof. Dr. Heiko Paulheim
Data and Web Science Group
University of Mannheim
Phone: +49 621 181 2646
B6, 26, Room C1.08
D-68159 Mannheim
Mail:[email protected]
Web:www.heikopaulheim.com
--
------------------------------------------------------
Dr. Mari Carmen Suárez-Figueroa
Teaching Assistant
Ontology Engineering Group (OEG)
Departamento de Inteligencia Artificial
Escuela Técnica Superior de Ingenieros Informáticos
(antes Facultad de Informática)
Universidad Politécnica de Madrid
Campus de Montegancedo, s/n
Boadilla del Monte - 28660 Madrid
Phone: (+34) 91 336 36 72
Fax: (+34) 91 352 48 19
e-mail: [email protected]
Office: 3205
------------------------------------------------------
