Menu
▾
▴
dbpedia-ontology — discussion on administering the DBpedia ontology
You can subscribe to this list here.
| 2015 |
Jan
(7) |
Feb
(16) |
Mar
(7) |
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
(17) |
Sep
(5) |
Oct
(1) |
Nov
|
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2016 |
Jan
(3) |
Feb
(12) |
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(3) |
Jul
(3) |
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(1) |
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2018 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dimitris K. <ji...@gm...> - 2018-01-27 20:03:00
|
One idea could be to add a rule that disallows equivalent statements when they infer equivalence to another DBpedia class that is not a sub or super class of the current class. Might be tricky to get this 100% right with pure sparql thought |
|
From: Kuys, G. <ger...@or...> - 2018-01-27 16:40:38
|
Hi all, Please give me one or two days, and I will present a draft text on principles that in my proposal should underpin the next version DBpedia ontology. These are principles on whether or not to adopt a metadata approach, and therefore have a bearing on the use of equivalence relations. In my text, I plead for the removal of all equivalence relations (owl:equivalentClass, owl:equivalentProperty) between data that describe a body of knowledge or a collection, and data that directly represent a state of affairs. If such approach be accepted, a dbo:Building cannot any longer be the equivalent of a skos:Concept of skos:type Building, and the same goes for Dulce. And yes, we should use SHACL to enforce this kind of constraints. I look forward to our discussion about this! Kind regards, Gerard Van: Gustavo Publio [mailto:gus...@in...] Verzonden: zaterdag 27 januari 2018 14:49 Aan: Magnus <ma...@13...> CC: dbp...@li... Onderwerp: Re: [DBpedia-ontology] [dbpedia/extraction-framework] dbo:MusicGenre mapping is wrong (#541) Hi Magnus, all, As far as I could notice, this is a problem that could occur whenever an user applies any type of equivalences (equivalentTo, sameAs, and so on). We could probably create a SHACL test that gives an error whenever a new equivalence is added, but this would not be desired - sometimes such equivalences are real and need to be added. So I don't see how a simple test or rule would be able to prevent users to make such wrongly assumptions; even if we use linking discovery approaches, it would not be enough, don't you agree? Regards, Gustavo Publio<http://aksw.org/GustavoPublio.html> PhD candidate @ AKSW<http://aksw.org/>/KILT<http://aksw.org/Groups/KILT.html> Group InfAI<http://infai.org/>, Universität Leipzig<http://uni-leipzig.de> On Fri, Jan 26, 2018 at 6:31 PM, Magnus <ma...@13...<mailto:ma...@13...>> wrote: Hey Gustavo, Lorenz just pointed out some ontology misalignments that should be detected by the tests. Don’t know yet how a rule should be constructed to recognize such types of error. Any ideas? Best Magnus Anfang der weitergeleiteten Nachricht: Von: Lorenz Bühmann <not...@gi...<mailto:not...@gi...>> Betreff: [dbpedia/extraction-framework] dbo:MusicGenre mapping is wrong (#541) Datum: 26. Januar 2018 um 17:57:57 MEZ An: dbpedia/extraction-framework <ext...@no...<mailto:ext...@no...>> Kopie: Subscribed <sub...@no...<mailto:sub...@no...>> Antwort an: dbpedia/extraction-framework <reply+00082000b3b41e09214602b...@re...<mailto:reply+00082000b3b41e09214602b...@re...>> I don't know who did it and why but in the current ontology the following axiom exists: Class: dbo:MusicGenre EquivalentTo: dul:Concept This doesn't make any sense and in addition brings a lots of problems into the ontology as there are even other classes made equivalent to dul:Concept - you know what this means for the transitive closure... Now, when I opened the ontology in Protege, I saw that there are much more issues suffering from the same problems. For sure, somebody misunderstood the semantics of the equivalence relation. I'll just add a screenshot of the Protege class hierarchy here for convenience. Please check all the weird equivalence relations even on this small part of the class hierarchy. (note, the list of red markers is probably incomplete, I just stopped after tagging just some the obvious issues in this part of the hierarchy: [bug]<https://user-images.githubusercontent.com/976029/35450508-8ce7d130-02c0-11e8-9937-6a9f1e0f81e7.png> For example: * dbo:Aircraft should not have been made equivalent to schema:Concept, the same for dbo:Locomotive, dbo:Ship etc - this indeed makes all entities equivalent entities. * something like dbo:Food owl:equivalentClass dbo:FunctionalSubstance is not what I would assume to be correct * Polyhedron a SpaceRegion and vice versa? Well, are we talking about the same concept of "polyhedron" in geometry? For me, this looks like a larger problem within the current ontology, especially as this makes all applications using reasoning behave strange and sometimes even useless. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://github.com/dbpedia/extraction-framework/issues/541>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAggADHIOc5gUEwXaLX-R1HSs2DuJO2oks5tOgQVgaJpZM4RulaJ>. Disclaimer Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de afzender te waarschuwen en dit bericht met eventuele bijlagen direct te verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht. This e-mail and any attachments are confidential and are solely intended for the addressee. If you are not the intended recipient, please notify the sender and delete and/or destroy this message and any attachments immediately. It is prohibited to copy, to distribute, to disclose or to use this e-mail and any attachments in any other way. Ordina N.V. and/or its group companies do not accept any responsibility nor liability for any damage resulting from the content of and/or the transmission of this message. |
|
From: Gustavo P. <gus...@in...> - 2018-01-27 13:49:20
|
Hi Magnus, all, As far as I could notice, this is a problem that could occur whenever an user applies any type of equivalences (equivalentTo, sameAs, and so on). We could probably create a SHACL test that gives an error whenever a new equivalence is added, but this would not be desired - sometimes such equivalences are real and need to be added. So I don't see how a simple test or rule would be able to prevent users to make such wrongly assumptions; even if we use linking discovery approaches, it would not be enough, don't you agree? Regards, Gustavo Publio <http://aksw.org/GustavoPublio.html> PhD candidate @ AKSW <http://aksw.org/>/KILT <http://aksw.org/Groups/KILT.html> Group InfAI <http://infai.org/>, Universität Leipzig <http://uni-leipzig.de> On Fri, Jan 26, 2018 at 6:31 PM, Magnus <ma...@13...> wrote: > Hey Gustavo, > > Lorenz just pointed out some ontology misalignments that should be > detected by the tests. Don’t know yet how a rule should be constructed to > recognize such types of error. Any ideas? > > Best > Magnus > > Anfang der weitergeleiteten Nachricht: > > *Von: *Lorenz Bühmann <not...@gi...> > *Betreff: **[dbpedia/extraction-framework] dbo:MusicGenre mapping is > wrong (#541)* > *Datum: *26. Januar 2018 um 17:57:57 MEZ > *An: *dbpedia/extraction-framework <extraction-framework@noreply. > github.com> > *Kopie: *Subscribed <sub...@no...> > *Antwort an: *dbpedia/extraction-framework <reply+ > 00082000b3b41e09214602b9a1723f4f0c11ef318c99722192cf00000001 > 168...@re...> > > I don't know who did it and why but in the current ontology the following > axiom exists: > > Class: dbo:MusicGenre > EquivalentTo: dul:Concept > > This doesn't make any sense and in addition brings a lots of problems into > the ontology as there are even other classes made equivalent to > dul:Concept - you know what this means for the transitive closure... > > Now, when I opened the ontology in Protege, I saw that there are much more > issues suffering from the same problems. For sure, somebody misunderstood > the semantics of the equivalence relation. > > I'll just add a screenshot of the Protege class hierarchy here for > convenience. Please check all the weird equivalence relations even on this > small part of the class hierarchy. (note, the list of red markers is > probably incomplete, I just stopped after tagging just some the obvious > issues in this part of the hierarchy: > > [image: bug] > <https://user-images.githubusercontent.com/976029/35450508-8ce7d130-02c0-11e8-9937-6a9f1e0f81e7.png> > > For example: > > - dbo:Aircraft should not have been made equivalent to schema:Concept, > the same for dbo:Locomotive, dbo:Ship etc - this indeed makes all > entities equivalent entities. > - something like dbo:Food owl:equivalentClass dbo:FunctionalSubstance > is not what I would assume to be correct > - Polyhedron a SpaceRegion and vice versa? Well, are we talking about > the same concept of "polyhedron" in geometry? > > For me, this looks like a larger problem within the current ontology, > especially as this makes all applications using reasoning behave strange > and sometimes even useless. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/dbpedia/extraction-framework/issues/541>, or mute the > thread > <https://github.com/notifications/unsubscribe-auth/AAggADHIOc5gUEwXaLX-R1HSs2DuJO2oks5tOgQVgaJpZM4RulaJ> > . > > > |
|
From: Marzieh T. <M.T...@lb...> - 2017-12-14 09:23:09
|
Dear all, My name is Marzieh Talebpour and I am a PhD researcher at Centre of Information Management, Loughborough University, UK. I am conducting a survey as a part of my research study to increase my understanding of how ontologies are evaluated before being reused. I would really like to get your thoughts in this area, and so would really appreciate it if you were able to complete the attached online survey that I have developed. The survey will only take 15 minutes to complete. The survey can be accessed by clicking on the link below: https://lborobusiness.eu.qualtrics.com/jfe/form/SV_cN5scAnvfy8QLoF As a thank you for giving your time, a prize draw for 3 individuals to win £50 of gift vouchers will be held (instructions on how to enter the draw can be found at the end of the survey); entry to the prize draw is separate from the survey to secure your anonymity. Please rest assured that your response is completely confidential. Thank you in advance for your help, Marzieh Talebpour ----------------------------- Marzieh Talebpour PhD Researcher Loughborough University |
|
From: Niketa <ni...@gm...> - 2017-09-30 20:16:17
|
Final Call for Papers South Asian University, Delhi, India December 14-16, 2017 Apologies for cross-posting. Kindly help to distribute this final CFP to your mailing list. 17th International Conference on Intelligent Systems Design and Applications (ISDA 2017) http://www.mirlabs.net/isda17/ 17th International Conference on Hybrid Intelligent Systems (HIS 2017) http://www.mirlabs.net/his17/ 7th World Congress on Information and Communication Technologies (WICT 2017) http://www.mirlabs.net/wict17/ 9th World Congress on Nature and Biologically Inspired Computing (NaBIC 2017) http://www.mirlabs.net/nabic17/ ISDA 2017, HIS 2017, WICT 2017, NaBIC 2017: Scopus & UGC Approved Proceedings All accepted and registered papers will be published in AISC Series of Springer, indexed in ISI Proceedings, EI-Compendex, DBLP, SCOPUS, Google Scholar and Springerlink. (Listed in UGC approved list, please refer List 1- Page 32 - S.No. - 1375) (http://www.ugc.ac.in/pdfnews/8919877_Journals-1.pdf) ** Important Dates ** (Extended) ---------------------------- Paper submission due: October 21, 2017 Notification of paper acceptance: November 05, 2017 Registration and Final manuscript due: November 15, 2017 Conference: December 14 - 16, 2017 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Submission Guidelines: --------------------------------- Submission of paper should be made through the submission page from the conference web page. Please refer to the conference website for guidelines to prepare your manuscript. Paper format templates: http://www.springer.com/series/11156 ISDA’17 Submission Link: https://easychair.org/conferences/?conf=isda2017 HIS’17 Submission Link: https://easychair.org/conferences/?conf=his20171 WICT’17 Submission Link: https://easychair.org/conferences/?conf=wict2017 NaBIC’17 Submission Link: https://easychair.org/conferences/?conf=nabic2017 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Organizing Committee * ---------------------------------- General Chairs: Ajith Abraham, Machine Intelligence Research Labs, USA Pranab Kr. Muhuri, South Asian University, Delhi Technical Committee (Please refer website): http://www.mirlabs.net/isda17/committees.php http://www.mirlabs.net/his17/committees.php http://www.mirlabs.net/wict17/committees.php http://www.mirlabs.net/nabic17/committees.php For technical contact: ---------------------------------- Ajith Abraham Email: aji...@ie... |
|
From: Markus F. <mar...@gm...> - 2017-08-03 09:22:20
|
Dear DBpedians, We will start preparing the next DBpedia release this month. In the meantime, as for every release cycle, we need you to lay last hands on the mappings (see below). Yet, this time will be the last in which mapping editors have to rely on the Mapping Wiki (http://mappings.dbpedia.org/ <http://mappings.dbpedia.org/index.php/Main_Page>) for editing. Shortly after the end of this sprint we will freeze the wiki and introduce the Git based RML mappings editor. Wouter Maroy <https://www.linkedin.com/in/wouter-maroy-746810114/>, Anastasia Dimou <http://rml.io/people/AnastasiaDimou.html>, Ben De Meester <http://users.ugent.be/~bjdmeest/> and Pieter Heyvaert <https://pieterheyvaert.com/research/> from Ghent University did make tremendous progress in preparing the RML-based extraction, while Ismael Rodríguez <http://ismaro3.github.io/> developed the Mappings UI in the course of our ongoing GSoC projects. Many thanks to all involved. *RML* The RDF Mapping language (RML - http://rml.io) is a generic scalable mapping language defined to express rules that map data in heterogeneous structures and serializations to the RDF data model. RML is defined as a superset of the W3C-recommended mapping language, R2RML <https://www.w3.org/TR/r2rml/>, that maps data in relational databases to RDF. RML also introduces the possibility of proper validation before data generation which leads to improved data quality. For integration in DBpedia, RML was extended to operate with a new data source, Wikipedia infoboxes. Generating the DBpedia mappings dataset by defining the mappings in RML is a more sustainable approach. The current RML mappings are translated mappings from the Mapping Wiki and are stored in a GitHub repository <https://github.com/dbpedia/mappings-tracker>. The last translation will be performed after this Mapping Sprint. The new UI for editing RML mappings is currently a work in progress, but a preview can be found here: http://mappings-ui.herokuapp.com/. Relevant publications: Declarative Data Transformations for Linked Data Generation: the case of DBpedia <https://biblio.ugent.be/publication/8525863/file/8525869.pdf> Assessing and Refining Mappings to RDF to Improve Dataset Quality <http://ceur-ws.org/Vol-1690/paper97.pdf>DBpedia Mappings Quality Assessment <https://biblio.ugent.be/publication/8133269/file/8133271.pdf> *Mapping Sprint* Until we switch to the RML editor, we would like to ask all members of the mapping editors community for their help with the upcoming DBpedia release in the form of a *MappingSprint*: 1. Could you please check whether the mappings that you have entered into the wiki over the last year still work correctly? 2. If you still want to refine and extend mappings and/or the ontology, now would be the perfect time to do so. 3. In order to help to increase the infobox coverage of the new release, it would also be great if you map additional templates or additional properties of existing templates to the ontology. Also, note that now we have separate issue trackers for the mappings and the ontology where we discuss design issues https://github.com/dbpedia/ontology-tracker/issues https://github.com/dbpedia/mappings-tracker/issues For helping you see which widely used templates still require additional property mappings, we have updated the Mapping Wiki statistics for all languages: http://mappings.dbpedia.org/server/statistics/ Further functionality for testing and exploring the current mappings is available at: http://mappings.dbpedia.org/server/ for example mapping syntax errors http://mappings.dbpedia.org/server/mappings/fr/validate/* *New additions since the last sprint* Redirects that need to be fixed (moved / merged) http://mappings.dbpedia.org/server/mappings/en/redirects/ Wrong mappings (according to our ontology). http://mappings.dbpedia.org/validation/ Wikidata mappings (create owl:equivalent classes & properties to Wikidata) http://mappings.dbpedia.org/server/ontology/wikidata/missing/ *Examples* For the English Wikipedia edition, you can see for instance at http://mappings.dbpedia.org/server/statistics/en/?show=100 that there is still room for improving the mappings. The statistics for German, Spanish and French are found below and also still show lots of gaps for these important languages: http://mappings.dbpedia.org/server/statistics/de/?show=100 http://mappings.dbpedia.org/server/statistics/es/?show=100 http://mappings.dbpedia.org/server/statistics/fr/?show=100 You also have a possibility to see the list of errors for the current mappings, for instance for French you can validate either a specific mapping or all mappings at once http://mappings.dbpedia.org/server/mappings/fr/ http://mappings.dbpedia.org/server/mappings/fr/validate/* - error list for all French mappings If you want to refine and extend the ontology, note that you can add links between the DBpedia ontology and other schemata/ontologies, e.g. to schema.org or Wikidata as in the example below http://mappings.dbpedia.org/index.php/OntologyProperty:Author Wikipedia infobox templates evolve over time and some of our mappings need to catch up as well. Some cases are simple where a simple move would do (double check the new mapToClass) while others require merging (we have a mapping both for the redirect and the target) http://mappings.dbpedia.org/server/mappings/en/redirects/ Invalid mappings report the use of properties in a mapping that does not comply with the property domain definition. In these case we could a) change the property and find a more appropriate one, b) broaden the domain of the property or c) adjust the class hierarchy. http://mappings.dbpedia.org/validation/ *Deadline* We will use all mappings that are entered into the Mapping Wiki until *August 31st* for the upcoming DBpedia release. Thus, it would be great if as many editors as possible participate in the mapping sprint and we as a community try to increase the mapping coverage as far as possible until this date. Lots of thanks advance to all mapping editors who participate. Let's all try to make the next DBpedia release even better! Cheers, Markus Freudenberg, Wouter Maroy and Sebastian Hellmann. |
|
From: Markus F. <mar...@gm...> - 2017-06-09 15:40:23
|
Hi Maria, thank you for pointing that out. I will remedy this matter. For now please get the ontology directly from GitHub: https://github.com/ dbpedia/DataId-Ontology/blob/master/dataid.ttl Cheers, Markus Freudenberg Release Manager, DBpedia <http://wiki.dbpedia.org> On Fri, Jun 9, 2017 at 4:51 PM, María Poveda <mp...@fi...> wrote: > Dear all, > > I've just realized the link "Ontology source" in > http://dataid.dbpedia.org/ns/core.html points to: > http://localhost:8080/lode/source?url=http://vmdbpedia. > informatik.uni-leipzig.de/temporary/dataid.owl > > I guess this is the list to mention that but if I'm wrong and you can > provide another contact to ask for it, it would be great. > > Best, > > María > > -- > María Poveda Villalón, PhD > > Ontology Engineering Group (OEG) > Universidad Politécnica de Madrid > Madrid, Spain > > e-mail: mp...@fi... > website: http://mariapoveda.github.io/ > blog: http://thepetiteontologist.wordpress.com/ > |
|
From: María P. <mp...@fi...> - 2017-06-09 15:23:04
|
Dear all, I've just realized the link "Ontology source" in http://dataid.dbpedia.org/ns/core.html points to: http://localhost:8080/lode/source?url=http://vmdbpedia.informatik.uni-leipzig.de/temporary/dataid.owl I guess this is the list to mention that but if I'm wrong and you can provide another contact to ask for it, it would be great. Best, María -- María Poveda Villalón, PhD Ontology Engineering Group (OEG) Universidad Politécnica de Madrid Madrid, Spain e-mail: mp...@fi... website: http://mariapoveda.github.io/ blog: http://thepetiteontologist.wordpress.com/ |
|
From: Gintautas S. <gin...@gm...> - 2017-02-22 10:02:54
|
Hello All, I am struggling to understand the semantics and the relationship between some of the datasets. Ideally, it would be perfect if you could refer me to the documentation that covers the subject. Alternatively, if you could spare a minute of your time and correct/clarify the following statements, I would be very grateful. A resource can have multiple anchor texts and their literal values can be identical, e.g: 1. <http://dbpedia.org/resource/example> <..wikiPageWikiLinkText> "Example 1" @en 2. <http://dbpedia.org/resource/example> <..wikiPageWikiLinkText> "Example 2" @en 3. <http://dbpedia.org/resource/example> <..wikiPageWikiLinkText> "Example 3" @en What do the entries above mean? Do they mean that the "example" resource is: 1. referenced by three resources 2. could be referenced by two resources, one of them having two different anchor links 3. could be referenced by a single resource? How do these anchor links then relate to page_links and redirects? Can we state that the number of anchor links should always be less or equal to the number of page_links? Thanks, Gintas |
|
From: Markus F. <mar...@gm...> - 2016-11-01 14:27:21
|
Dear DBpedians, To keep up with our two releases per year schedule, we are preparing the next release, due in March/April of next year. Therefore we are announcing our custom "Mapping Sprint" to encourage mapping activity to add new and improve/validate existing mappings until the end of this month. As a lot of new languages and infobox-to-ontology mappings for various languages have already been entered by the mapping editors community into the DBpedia Mapping Wiki (http://mappings.dbpedia.org/ <http://mappings.dbpedia.org/index.php/Main_Page>) since the last DBpedia release, we hope to be able to provide clean data for even more infoboxes in even more languages with the new release. Tasks: 1. Could you please check whether the mappings that you have entered into the wiki over the last year still work correctly? 2. If you still want to refine and extend mappings and/or the ontology, now would be the perfect time to do so. 3. In order to help increasing the infobox coverage of the new release, it would also be great if you map additional templates or additional properties of existing templates to the ontology. Also note that now we have separate issue trackers for the mappings and the ontology where we discuss design issues https://github.com/dbpedia/ontology-tracker/issues https://github.com/dbpedia/mappings-tracker/issues For helping you see which widely used templates still require additional property mappings, we have updated the Mapping Wiki statistics for all languages: http://mappings.dbpedia.org/server/statistics/ Further functionality for testing and exploring the current mappings is available at: http://mappings.dbpedia.org/server/ for example mapping syntax errors http://mappings.dbpedia.org/server/mappings/fr/validate/* *New additions since the last sprint* Redirects that need to be fixed (moved / merged) http://mappings.dbpedia.org/server/mappings/en/redirects/ Wrong mappings (according to our ontology). http://mappings.dbpedia.org/validation/ Wikidata mappings (create owl:equivalent classes & properties to Wikidata) http://mappings.dbpedia.org/server/ontology/wikidata/missing/ *Examples* For the English Wikipedia edition, you can see for instance at http://mappings.dbpedia.org/server/statistics/en/?show=100 that there is still room for improving the mappings. The statistics for German, Spanish and French are found below and also still show lots of gaps for these important languages: http://mappings.dbpedia.org/server/statistics/de/?show=100 http://mappings.dbpedia.org/server/statistics/es/?show=100 http://mappings.dbpedia.org/server/statistics/fr/?show=100 You also have a possibility to see the list of errors for the current mappings, for instance for French you can validate either a specific mapping or all mappings at once http://mappings.dbpedia.org/server/mappings/fr/ http://mappings.dbpedia.org/server/mappings/fr/validate/* - error list for all French mappings If you want to to refine and extend the ontology, note that you can add links between the DBpedia ontology and other schemata/ontologies, e.g. to schema.org or Wikidata as in the example below http://mappings.dbpedia.org/index.php/OntologyProperty:Author Wikipedia infobox templates evolve over time and some of our mappings need to catch up as well. Some cases are simple where a simple move would do (double check the new mapToClass) while others require merging (we have a mapping both for the redirect and the target) http://mappings.dbpedia.org/server/mappings/en/redirects/ Invalid mappings report the use of properties in a mapping that does not comply with the property domain definition. In these case we could a) change the property and find a more appropriate one, b) broaden the domain of the property or c) adjust the class hierarchy (BE Carefull with this one!!!) http://mappings.dbpedia.org/validation/ *Deadline* We will use all mappings that are entered into the Mapping Wiki until *Nov 30th* for the upcoming DBpedia release. It would thus be great if as many editors as possible participate in the mapping sprint and we as a community try to increase the mapping coverage as far as possible until this date. Lots of thanks advance to all mapping editors who participate. Let's all try to make the next DBpedia release even better! Cheers, Markus Freudenberg, Dimitris Kontokostas, Sebastian Hellmann |
|
From: Dimitris K. <ji...@gm...> - 2016-10-31 03:17:29
|
(cc'ing the DBpedia ontology list) Thank you Heiko for identifying the inconsistencies a big thank to Aldo for taking the effort of creating the original mappings. personally, I am not aware of any changes to the mappings (subClassOF / equivalentClass/Property) but I was not so involved in the releases before 2015-04 Markus and I have the overview of the current releases but we are not dolce experts and not sure how to proceed here. They way I see it we need 2 things here: 1) identifying the errors & 2) fixing them looks like Heiko has something wrt (1) that we can reuse for the following release. We need help with (2) though. If the mapping flexibility is an issue I would suggest to keep these mappings out of the mappings wiki. We plan to move the ontology out of the wiki as well when we switch to RML so it is something we will do anyway Any other suggestions / feedback? Cheers, Dimitris On Wed, Oct 26, 2016 at 6:35 AM, Aldo Gangemi <ald...@cn...> wrote: > Hi, thanks Heiko for spotting this. BTW in the original mappings for > version 3.9 those axioms were all subClassOf. Probably something has gone > weird in the versioning. > > My proposal, which I made two years ago, is that, since DOLCE mappings > have the main goal to help integrity checking or top-level querying, they > should be revised shortly before each new DBpedia ontology release, so that > no incoherences are accidentally introduced in the release. > > In fact, even with 3.9, some changes were made to the ontology after I > sent out the mappings, and some (just a few) axioms, which were defined > with unions, were removed, probably because unions were not intended to be > enforced in DBpedia. > > In absence of a clear management of top level mappings, I still hesitate > to update them, although there is a clear need to do it. > Cheers > Aldo > > > On 26 Oct 2016, at 15:23, Heiko Paulheim <heiko@informatik.uni- > mannheim.de> wrote: > > > > Hi all, > > > > I've recognized that in the latest DBpedia ontology (and maybe also in > previous versions), there are a few questionable equivalence statements, as > listed below. > > > > Note that, among other problems, those axioms imply that each MusicGenre > is a GovernmentType and vice versa, that each Year is a Holiday and vice > versa, etc. Moreover, some classes, such as MusicGenre, become > unsatisfiable when the DUL/D0 ontologies are used in a reasoner. > > > > How did those mappings get in? Shouldn't we replace them with subClassOf > axioms? > > > > Best, > > > > Heiko > > > > > > dbo:Ideology owl:equivalentClass d0:CognitiveEntity > > dbo:Monastery owl:equivalentClass d0:Location > > dbo:Tax owl:equivalentClass dul:Description > > dbo:GovernmentType owl:equivalentClass dul:Concept > > dbo:Sales owl:equivalentClass dul:Situation > > dbo:Database owl:equivalentClass dul:InformationObject > > dbo:Holiday owl:equivalentClass dul:TimeInterval > > dbo:MeanOfTransportation owl:equivalentClass dul:DesignedArtifact > > dbo:UnitOfWork owl:equivalentClass dul:Situation > > dbo:PenaltyShootOut owl:equivalentClass dul:Event > > dbo:MusicGenre owl:equivalentClass dul:Concept > > dbo:Year owl:equivalentClass dul:TimeInterval > > dbo:Food owl:equivalentClass dul:FunctionalSubstance > > dbo:Project owl:equivalentClass dul:PlanExecution > > dbo:List owl:equivalentClass dul:Collection > > dbo:Organisation owl:equivalentClass dul:SocialPerson > > dbo:Unknown owl:equivalentClass dul:Entity > > dbo:Polyhedron owl:equivalentClass dul:SpaceRegion > > dbo:LegalCase owl:equivalentClass dul:Situation > > > > > > > > -- > > Prof. Dr. Heiko Paulheim > > Data and Web Science Group > > University of Mannheim > > Phone: +49 621 181 2661 > > B6, 26, Room C1.09 > > D-68159 Mannheim > > > > Mail: he...@in... > > Web: www.heikopaulheim.com > > > > > ------------------------------------------------------------ > ------------------ > The Command Line: Reinvented for Modern Developers > Did the resurgence of CLI tooling catch you by surprise? > Reconnect with the command line and become more productive. > Learn the new .NET and ASP.NET CLI. Get your free copy! > http://sdm.link/telerik > _______________________________________________ > DBpedia-discussion mailing list > DBp...@li... > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion > -- Kontokostas Dimitris |
|
From: Markus F. <mar...@gm...> - 2016-10-15 13:15:25
|
Hereby we announce the release of DBpedia 2016-04. The new release is based on updated Wikipedia dumps dating from March/April 2016 featuring a significantly expanded base of information as well as richer and (hopefully) cleaner data based on the DBpedia ontology. You can download the new DBpedia datasets in a variety of RDF-document formats from: http://wiki.dbpedia.org/downloads-2016-04 or directly here: http://downloads.dbpedia.org/2016-04/ Support DBpedia During the latest DBpedia meeting in Leipzig we discussed about ways to support DBpedia <http://blog.dbpedia.org/?p=210> and what benefits this support would bring <http://wiki.dbpedia.org/why-is-dbpedia-so-important>. For the next two months, we are aiming to raise money to support the hosting of the main services and the next DBpedia release (especially to shorten release intervals). On top of that we need to buy a new server to host DBpedia Spotlight that was so generously hosted so far by third parties. If you use DBpedia and want us to keep going forward, we kindly invite you to donate here <http://wiki.dbpedia.org/donate> or become a member of the DBpedia association <http://wiki.dbpedia.org/membership>. Statistics The English version of the DBpedia knowledge base currently describes 6.0M entities of which 4.6M have abstracts, 1.53M have geo coordinates and 1.6M depictions. In total, 5.2M resources are classified in a consistent ontology, consisting of 1.5M persons, 810K places (including 505K populated places), 490K works (including 135K music albums, 106K films and 20K video games), 275K organizations (including 67K companies and 53K educational institutions), 301K species and 5K diseases. The total number of resources in English DBpedia is 16.9M that, besides the 6.0M resources, includes 1.7M skos concepts (categories), 7.3M redirect pages, 260K disambiguation pages and 1.7M intermediate nodes. Altogether the DBpedia 2016-04 release consists of 9.5 billion (2015-10: 8.8 billion) pieces of information (RDF triples) out of which 1.3 billion (2015-10: 1.1 billion) were extracted from the English edition of Wikipedia, 5.0 billion (2015-04: 4.4 billion) were extracted from other language editions and 3.2 billion (2015-10: 3.2 billion) from DBpedia Commons and Wikidata. In general, we observed a growth in mapping-based statements of about 2%. Thorough statistics can be found on the DBpedia website <http://wiki.dbpedia.org/dbpedia-2016-04-statisticsdatasets/dataset-2015-10/dataset-2015-10-statistics> and general information on the DBpedia datasets here <http://wiki.dbpedia.org/services-resources/datasets/dbpedia-datasets>. Community The DBpedia community added new classes and properties to the DBpedia ontology via the mappings wiki. The DBpedia 2016-04 ontology encompasses: - 754 classes (DBpedia 2015-10: 739) - 1,103 object properties (DBpedia 2015-10: 1,099) - 1,608 datatype properties (DBpedia 2015-10: 1,596) - 132 specialized datatype properties (DBpedia 2015-10: 132) - 410 owl:equivalentClass and 221 owl:equivalentProperty mappings external vocabularies (DBpedia 2015-04: 407 - 221) The editor community of the mappings wiki also defined many new mappings from Wikipedia templates to DBpedia classes. For the DBpedia 2016-04 extraction, we used a total of 5800 template mappings (DBpedia 2015-10: 5553 mappings). For the second time the top language, gauged by the number of mappings, is Dutch (646 mappings), followed by the English community (604 mappings). (Breaking) Changes - In addition to normalized datasets to English DBpedia (en-uris) we additionally provide normalized datasets based on the DBpedia Wikidata (DBw) datasets (wkd-uris). These sorted datasets will be the foundation for the upcoming fusion process with wikidata. The DBw-based uris will be the only ones provided from the following releases on. - We now filter out triples from the Raw Infobox Extractor that are already mapped. E.g. no more “<x> dbo:birthPlace <z>” and “<x> dbp:birthPlace|dbp:placeOfBirth|... <z>” in the same resource. These triples are now moved to the “infobox-properties-mapped” datasets and not loaded on the main endpoint. See issue 22 <https://github.com/dbpedia/extraction-framework/issues/22> for more details. - Major improvements in our citation extraction. See here <http://www.mail-archive.com/dbp...@li.../msg07762.html> for more details. - We incorporated the statistical distribution approach <http://www.heikopaulheim.com/docs/iswc2013.pdf> of Heiko Paulheim in creating type statements automatically and providing them as an additional datasets (instance_types_sdtyped_dbo). In case you missed it, what we changed in the previous release (2015-10) - English DBpedia switched to IRIs. This can be a breaking change to some applications that need to change their stored DBpedia resource URIs / links. We provide the “uri-same-as-iri” dataset for English to ease the transition. - The instance-types dataset is now split into two files: instance-types (containing only direct types) and instance-types-transitive containing the transitive types of a resource based on the DBpedia ontology - The mappingbased-properties file is now split into three (3) files: - “geo-coordinates-mappingbased” that contains the coordinated originating from the mappings wiki. the “geo-coordinates” continues to provide the coordinates originating from the GeoExtractor - “mappingbased-literals” that contains mapping based fact with literal values - “mappingbased-objects” that contains mapping based fact with object values - the “mappingbased-objects-disjoint-[domain|range]” are facts that are filtered out from the “mappingbased-objects” datasets as errors but are still provided - We added a new extractor for citation data that provides two files: - citation links: linking resources to citations - citation data: trying to get additional data from citations. This is a quite interesting dataset but we need help to clean it up - All datasets are available in .ttl and .tql serialization (nt, nq dataset were neglected for reasons of redundancy and server capacity). Upcoming Changes - Dataset normalization: We are going to normalize datasets based on wikidata uris and no longer on the English language edition, as a prerequisite to finally start the fusion process with wikidata. - RML Integration: Wouter Maroy did already provide the necessary groundwork for switching the mappings wiki to a RML based approach <https://drive.google.com/file/d/0B7je1jgVmCgISXBPOHc3NDktblU/view?usp=sharing> on Github. We are not there yet but this is at the top of our list of changes. - Starting with the next release we are adding datasets with NIF annotations <http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core/nif-core.html> of the abstracts (as we already provided those for the 2015-04 release <http://downloads.dbpedia.org/2015-04/ext/nlp/abstracts/>). We will eventually extend the NIF annotation dataset to cover the whole Wikipedia article of a resource. New Datasets - SDTypes: We extended the coverage of the automatically created type statements (instance_types_sdtyped_dbo) to English, German and Dutch (see above). - Extensions: In the extension folder (2016-04/ext <http://downloads.dbpedia.org/2016-04/ext/>) we provide two new datasets, both are to be considered in an experimental state: - DBpedia World Facts: This dataset is authored by the DBpedia association itself. It lists all countries, all currencies in use and (most) languages spoken in the world as well as how these concepts relate to each other (spoken in, primary language etc.) and useful properties like iso codes (ontology diagram <https://raw.githubusercontent.com/dbpedia/WorldFacts/master/DBpediaWorldFactsOntology.png>). This Dataset extends the very useful LEXVO <http://www.lexvo.org>dataset with facts from DBpedia and the CIA Factbook <https://www.cia.gov/library/publications/the-world-factbook/>. Please report any error or suggestions in regard to this dataset to Markus <mar...@gm...>. - Lector Facts: This experimental dataset was provided by Matteo Cannaviccio and demonstrates his approach <http://dl.acm.org/citation.cfm?id=2932203> to generating facts by using common sequences of words (i.e. phrases) that are frequently used to describe instances of binary relations in a text. We are looking into using this approach as a regular extraction step. It would be helpful to get some feedback from you. Credits Lots of thanks to - Markus Freudenberg (University of Leipzig / DBpedia Association) for taking over the whole release process and creating the revamped download & statistics pages. - Dimitris Kontokostas (University of Leipzig / DBpedia Association) for conveying his considerable knowledge of the extraction and release process. - All editors that contributed to the DBpedia ontology mappings via the Mappings Wiki. - The whole DBpedia Internationalization Committee for pushing the DBpedia internationalization forward. - Heiko Paulheim (University of Mannheim) for providing the necessary code for his algorithm to generate additional type statements for formerly untyped resources and identify and removed wrong statements. Which is now part of the DIEF. - Václav Zeman, Thomas Klieger and the whole LHD team (University of Prague) for their contribution of additional DBpedia types - Marco Fossati (FBK) for contributing the DBTax types - Alan Meehan (TCD) for performing a big external link cleanup - Aldo Gangemi (LIPN University, France & ISTC-CNR, Italy) for providing the links from DOLCE to DBpedia ontology. - Kingsley Idehen, Patrick van Kleef, and Mitko Iliev (all OpenLink Software) for loading the new data set into the Virtuoso instance that provides 5-Star Linked Open Data publication and SPARQL Query Services. - OpenLink Software (http://www.openlinksw.com/) collectively for providing the SPARQL Query Services and Linked Open Data publishing infrastructure for DBpedia in addition to their continuous infrastructure support. - Ruben Verborgh from Ghent University – iMinds for publishing the dataset as Triple Pattern Fragments <http://fragments.dbpedia.org/>, and iMinds for sponsoring DBpedia’s Triple Pattern Fragments server. - Ali Ismayilov (University of Bonn) for extending the DBpedia Wikidata dataset. - Vladimir Alexiev (Ontotext) for leading a successful mapping and ontology clean up effort. - All the GSoC students and mentors which directly or indirectly influenced the DBpedia release - Special thanks to members of the DBpedia Association <http://dbpedia.org/dbpedia-association>, the AKSW <http://aksw.org/About.html> and the department for Business Information Systems <http://bis.informatik.uni-leipzig.de/en/Welcome> of the University of Leipzig. The work on the DBpedia 2016-04 release was financially supported by the European Commission through the project ALIGNED – quality-centric, software and data engineering (http://aligned-project.eu/). More information about DBpedia is found at http://dbpedia.org as well as in the new overview article about the project available at http://wiki.dbpedia.org/Publications. Have fun with the new DBpedia 2016-04 release! Cheers, Markus Freudenberg, Dimitris Kontokostas, Sebastian Hellmann |
.){kind=link}
|
From: Jeff T. <je...@th...> - 2016-10-10 10:52:20
|
Hello all, At the DBpedia Day in Leipzig we talked a little about an ontology mapping that is more fine-grained (and accurate) than the categories on Wikipedia. For example "The Diamond Age has genre Science Fiction", "The Diamond Age has 455 pages" and "The Diamond Age has shipping weight 90 grams" are really about subjects of different types (an abstract work, an edition, and a physical thing). But they are all expressed on a single item in Wikipedia which can't have all these different types. My question: Has there been work to map WIkidata qualified statements? For example, Spain is a country where part of the country is in the Canary Islands. https://www.wikidata.org/wiki/Q29 . So there are statements for "located in time zone" with the qualifier "applies to part Canary Islands". located in time zone UTC ±00:00 applies to part Canary Islands valid in period standard time UTC +01:00 applies to part Canary Islands valid in period daylight saving time Adding this qualifier effectively creates an anonymous resource "the Canary Islands part of Spain". The type of this resource and domain of the property "located in time zone" is not "country" but "region". (And the extra qualifier "valid in period standard time" actually creates a more refined anonymous resource.) Hopefully you can see the idea. If DBpedia mapping can work with Wikidata qualified statements, maybe the same process can be used to create the more refined resources needed for "The Diamond age abstract work", "The Diamond Age edition" and "The Diamond Age physical thing". Then the properties like "number of pages" can have a more refined domain and apply to the correct refined subject. Thanks, - Jeff |
|
From: Sebastian H. <pr...@in...> - 2016-08-10 13:46:18
|
SEMANTiCS 2016 - The Linked Data Conference Workshops, Tutorials and the DBpedia Day 12th International Conference on Semantic Systems Leipzig, Germany September 12 -15, 2016 _http://2016.semantics.cc/_ *Workshops/Tutorials * This year's SEMANTiCS is starting on September 12th with a full day of exciting and interesting satellite events. In _6 parallel tracks_ <http://2016.semantics.cc/satellite-events> scientific and industrial workshops and tutorials are scheduled to provide a forum for groups of researchers and practitioners to discuss and learn about hot topics in Semantic Web research. Attending the SEMANTiCS workshops and tutorial is _free of charge_, but you need to register. Feel free to have a closer look and register for the events here: _http://2016.semantics.cc/satellite-events_. *DBpedia Day - Call for Participation * Following our successful meetings in Europe & US our next DBpedia meeting will be held at Leipzig on September 15th, co-located with SEMANTiCS. _Highlights_ - Keynote #1: Wikidata: bringing structured data to Wikipedia with 16000 volunteers by Lydia Pintscher, product manager of Wikidata - Keynote #2: Harald Sack, (title TBA) (Hasso-Plattner-Institut) - A session for the “_DBpedia references and citations challenge_ <http://wiki.dbpedia.org/ideas/idea/261/dbpedia-citations-reference-challenge/>” - A _session on DBpedia ontology_ <http://mappings.dbpedia.org/index.php/DBpedia_Ontology_Committee> by members of the DBpedia ontology committee - Tell us what cool things you do with DBpedia:<https://goo.gl/AieceU>_https://goo.gl/AieceU_ - As always, there will be tutorials to learn about DBpedia and a DBpedia showcase session _Quick facts_ - Web URL: _http://wiki.dbpedia.org/meetings/Leipzig2016_ - When: September 15th, 2016 - Where: University of Leipzig, Augustusplatz 10, 04109 Leipzig - Call for Contribution: _https://goo.gl/AieceU_ (submission form) - Registration: Free to participate but only through registration (Option for DBpedia support tickets)_https://event.gg/3396-7th-dbpedia-community-meeting-in-leipzig-2016_ We are looking forward to your contributions and to seeing you at the SEMANTiCS in Leipzig! |
|
From: Dimitris K. <kon...@in...> - 2016-07-27 10:47:51
|
Hello, Since it might be of interest to the DBpedia-* lists, we are organizing a Data Quality Tutorial as a SEMANTiCS 2016 satellite event. http://2016.semantics.cc/satellite-events/data-quality-tutorial The tutorial tries to cover a big range of data quality topics, industry views on quality and recent research developments. We also present some of the work that is deployed on DBpedia, e.g. Mappings Validation by Anastasia Dimou Attending the tutorial is *free of charge* as the tutorial is sponsored by the ALIGNED project (http://www.aligned-project.eu) but you need to register. Registering for the main conference is of course optional, although highly recommended. Note that you can combine this tutorial with the DBpedia meeting ( wiki.dbpedia.org/meetings/Leipzig2016) as they are both co-located with SEMANTiCS (http://2016.semantics.cc/) Best regards, Dimitris Kontokostas -- Dimitris Kontokostas Department of Computer Science, University of Leipzig & DBpedia Association Projects: http://dbpedia.org, http://rdfunit.aksw.org, http://aligned-project.eu Homepage: http://aksw.org/DimitrisKontokostas Research Group: AKSW/KILT http://aksw.org/Groups/KILT |
|
From: Nandana M. <nan...@gm...> - 2016-07-20 20:58:18
|
Hi all, >From version 3.4, the DBpedia ontology is available from the download page (e.g., http://downloads.dbpedia.org/3.4/). Is there a place to get the versions of the ontology used in the earlier versions of DBpedia such as 1.0, 2.0, 3.0 ~ 3.3? Thanks a lot in advance! Best Regards, Nadnana |
|
From: Dimitris K. <kon...@in...> - 2016-07-11 12:54:44
|
Hello everyone and thank you for voting on the new CF* posting policies <http://www.mail-archive.com/dbp...@li.../msg07740.html> . Based on your feedback we decided on the following rules that we expect everyone to respect from now on DBpedia discussion list: we allow only posts that are explicitly related to DBpedia. i.e. the term DBpedia in mentioned somewhere in the CFP or the sender makes a personal introduction of the CFP to our community. DBpedia developer lists: we do not allow any CF* posts are all in this list, we expect all people in this list to be subscribed in the discussion list and get updates from there. DBpedia ontology: Similar to the discussion list, we allow only CFPs regarding ontologies that are also explicitly related to DBpedia. We expect equivalent restrictions on other lists we maintain (e.g. local chapters) or future lists we may create. >From now on we will warn people who do not respect our rules and point them to this thread. People that are warned more than 3 times without conforming to our new policies will be banned from our lists. Best Dimitris on behalf of the DBpedia Association -- Dimitris Kontokostas Department of Computer Science, University of Leipzig & DBpedia Association Projects: http://dbpedia.org, http://rdfunit.aksw.org, http://aligned-project.eu Homepage: http://aksw.org/DimitrisKontokostas Research Group: AKSW/KILT http://aksw.org/Groups/KILT |
|
From: Agnieszka Ł. <agn...@cs...> - 2016-06-27 08:22:13
|
Apologies for cross posting --------------------------- SEMANTIC WEB JOURNAL - Call for papers: SPECIAL ISSUE ON Machine Learning for Knowledge Base Generation and Population --------------------------- In the last decade, in the Semantic Web field, knowledge bases have attracted tremendous interest from both academia and industry and many large knowledge bases are now available. However, both generation of new knowledge and population of already existing knowledge bases with new facts face several challenges. Most of the time knowledge bases have been manually built, resulting in a highly specialistic and time consuming activity. Nevertheless, sources of unstructured and semi-structured data are still growing at a much faster rate than structured ones, as such it could be desirable to exploit such a large non-structured sources to populate structured knowledge bases. In the Semantic Web, a major cornerstone of knowledge bases are ontologies and schemas that play a key role for providing common vocabularies and for describing and constructing the Web of Data. However, nowadays, schema level and instance level data are often decoupled and as such can be out of sync, e.g., schema level knowledge may be inconsistent with the actual usage of its conceptual vocabulary in the assertions. In order to cope with this issue, the availability of automatic methods for schema aware generation and population of knowledge bases results fundamental. Furthermore, even in the cases of largely populated knowledge bases, they still often result incomplete and/or noisy with respect to the domain of reference. Automatic methods for dealing with such problems, namely for enriching and completing knowledge bases, both at schema and instance level are needed. In this scenario, by exploiting evidence derived from the data, new machine learning and data mining methods, that are able to deal with the heterogeneity, the intrinsic uncertainty and complexity of Semantic Web data, can be used for: learning new concept definitions, capturing emerging concepts (only extensionally defined) and/or concepts drift, predicting new links among resources and new assertions, discovering matches among resources and many others, with the final goal of constructing new knowledge bases, enriching existing ones, supporting their continuous evolution. The primary goal of the special issue is to provide novel machine learning/data mining methods for knowledge base generation, population, enrichment, evolution showing advances in the Semantic Web field. Topics of Interest ------------------------------ We welcome original high quality submissions on (but are not restricted to) the following topics: - Machine Learning for constructing, enriching, refining, maintaining, interlinking Semantic Web Knowledge Bases - (Statistical) relational learning for the Web of Data - Semi-supervised, unbalanced, inductive learning for mining and maintaining Semantic Web Knowledge Bases - Data mining and knowledge discovery in Semantic Web Knowledge Bases - Population of Knowledge Bases from unstructured and semi-structured sources - Feature extraction, pre-processing and transformation of Semantic Web Knowledge Bases - Machine Learning for ontology/instance matching - Deep Learning for Semantic Web Knowledge Bases - Scalable Machine Learning algorithms for the Web of Data - Machine Learning methods for handling uncertain knowledge - Combination of logic reasoning and machine learning for Knowledge Base construction, population and enrichment - OWA vs. CWA in Knowledge Base generation, population and enrichment - Link Prediction in the Linked Data Cloud - Evaluation and benchmarking of machine learning models for Knowledge Base generation and population Submission Instructions ----------------------------- Submission deadline: December 12, 2016 Hawaii-Time -------------------- Submissions shall be made through the Semantic Web journal website at http://www.semantic-web-journal.net. Prospective authors must take notice of the submission guidelines posted at http://www.semantic-web-journal.net/authors. Note that you need to request an account on the website for submitting a paper. Please indicate in the cover letter that it is for the Special Issue on Machine Learning for Knowledge Base Generation and Population. Submissions are possible in the full research papers category. Papers describing application reports, tools and systems are also welcome, provided that the main contribution still remains an advance of the state of the art with respect to the research perspective. While there is no upper limit, paper length must be justified by content. Guest editors -------------------- Claudia d’Amato, University of Bari, Italy Agnieszka Lawrynowicz, Poznan University of Technology, Poland Jens Lehmann, University of Bonn and Fraunhofer IAIS, Germany The call is also available at the official journal website: http://www.semantic-web-journal.net/blog/call-papers-special-issue-machine-learning-knowledge-base-generation-and-population |
|
From: Dimitris K. <ji...@gm...> - 2016-06-24 11:18:04
|
Following our successful meetings in Europe & US our next DBpedia meeting will be held at Leipzig on September 15th, co-located with SEMANTiCS: http://2016.semantics.cc/ * Highlights * - Keynote by Lydia Pintscher, Wikidata - A session for the “DBpedia references and citations challenge”: http://wiki.dbpedia.org/ideas/idea/261/dbpedia-citations-reference-challenge/ - A session on DBpedia ontology by members of the DBpedia ontology committee: http://mappings.dbpedia.org/index.php/DBpedia_Ontology_Committee - Tell us what cool things you do with DBpedia: https://goo.gl/AieceU - As always, there will be tutorials to learn about DBpedia * Quick facts * - Web URL: http://wiki.dbpedia.org/meetings/Leipzig2016 - Hashtag: #DBpediaLeipzig - When: September 15th, 2016 - Where: University of Leipzig, Augustusplatz 10, 04109 Leipzig - Call for Contribution: submission form <https://goo.gl/AieceU> - Registration: Free to participate but only through registration <https://event.gg/3396-7th-dbpedia-community-meeting-in-leipzig-2016> (Option for DBpedia support tickets) https://event.gg/3396-7th-dbpedia-community-meeting-in-leipzig-2016 * Sponsors and Acknowledgments * - University of Leipzig (http://www.uni-leipzig.de/) - National Library of the Netherlands (http://www.kb.nl/) - ALIGNED Project (http://aligned-project.eu/) - Institute for Applied Informatics (InfAI, http://infai.org/en/AboutInfAI) - OpenLink Software (http://www.openlinksw.com/) - SEMANTICS Conference Sep 12-15, 2016 in Leipzig (http://2016.semantics.cc/ ) If you would like to become a sponsor for the 7th DBpedia Meeting, please contact the DBpedia Association (db...@in...) * Organisation * - Magnus Knuth, HPI, DBpedia German/Commons - Monika Solanki, University of Oxford, DBpedia Ontology - Julia Holze, DBpedia Association - Dimitris Kontokostas, AKSW/KILT, DBpedia Association - Sebastian Hellmann, AKSW/KILT, DBpedia ASsociation -- Kontokostas Dimitris |
|
From: Dimitris K. <kon...@in...> - 2016-06-07 12:01:08
|
Dear all, Following the recent policy changes of W3c regarding CFP posting [1] we would like to see how the DBpedia community would like to handle such cases. We believe that posts that are unrelated (or very loosely related) to Semantic Web / Linked Data should not be allowed in the DBpedia* lists and we already started some effort in this regard. However, we would like to see the community's position regarding all CFPs and we prepared the following questionnaire. http://goo.gl/forms/Yp495LmphFKV72u42 please sign in with your google account and vote *until 30/6/2016* [1] https://lists.w3.org/Archives/Public/public-lod/2016May/0032.html Best regards, Dimitris on behalf of the DBpedia Association -- Dimitris Kontokostas Department of Computer Science, University of Leipzig & DBpedia Association Projects: http://dbpedia.org, http://rdfunit.aksw.org, http://aligned-project.eu Homepage: http://aksw.org/DimitrisKontokostas Research Group: AKSW/KILT http://aksw.org/Groups/KILT |
|
From: Monika S. <mso...@gm...> - 2016-05-02 12:51:11
|
*Apologies for Cross posting* ==================================================================================================== Venue: Kobe, Japan Hashtag: #wop2016 Workshop Website: http://ontologydesignpatterns.org/wiki/WOP:2016 Easychair Submission Page: https://easychair.org/conferences/?conf=wop2016 Abstract submission (required): June 24th, 2016 Submission date: June 30th, 2016 ==================================================================================================== This is the seventh edition in a series of workshops addressing the topic of *ontology and semantic web patterns as best practices*, related to the /ontologydesignpatterns.org/ <http://ontologydesignpatterns.org/wiki/Ontology_Design_Patterns_._org_%28ODP%29> initiative. This workshop is a gathering point for the ontology design pattern community for semantic web and linked data. As interest in the Semantic Web increases and technologies for realizing the Semantic Web become more mature, the need for high-quality and reusable Semantic Web ontologies increases as well. To address the quality and reusability issues, different types of Ontology Design Patterns (ODPs) have emerged, and methods for devising or discovering new ones from heterogeneous knowledge sources are needed. Patterns need to be shared by a community in order to provide a common language, and to stimulate pattern usage and development. Hence, the aim of this workshop is twofold * providing an arena for proposing and discussing good practices, patterns, pattern-based ontologies, systems etc., and * broadening the pattern community that is developing its own “language” for discussing and describing relevant problems and their solutions. For more background on the workshop series, see http://ontologydesignpatterns.org/wiki/WOP:2016 . WOP2016 is planned to be a /full-day workshop/ consisting of two parts: paper presentations and pattern poster presentations. ==================================================================================================== * Call for Papers - Topics* Submission instruction for research papers (including position papers) can be found at http://ontologydesignpatterns.org/wiki/WOP:2016/Submission The main aim of the workshop is to discuss and collect solutions to recurrent problems that matter to researchers and practitioners of the Semantic Web field, and that impact on design and engineering of ontologies, linked data, knowledge extraction, and other semantic web applications. We invite the submission of original research results related to the focus areas of the workshop. Research papers (maximum 12 pages LNCS style) should present mature work and document established results, or be short papers presenting proposed research directions, novel ideas, or more general positions or discussions (maximum 5 pages LNCS style). This year we particularly welcome papers which evaluate the current practice of ontology modeling. Original research papers and short papers are invited to consider the following (non exhaustive) list of topics: Ontology design patterns (ODPs) and pattern-based ontologies Ontology patterns and their relation with standards Correspondence patterns for ontology matching and integration Knowledge patterns and knowledge reengineering based on patterns Processes and services process patterns Antipatterns and their relations to ODPs Pattern-based ontology design Tools and applications for pattern-based knowledge engineering Pattern-based methods and methodologies for development of semantic applications Ontology pattern extraction Pattern-based information extraction Pattern-based ontology learning Pattern-based ontology evaluation and selection Patterns and Linked data (usage, emerging patterns, pattern-driven data publishing, etc.) Analysis of ontology pattern usage Data mining patterns and Semantic Web design Web semantics from a pattern perspective Reasoning with or using patterns Relation between NLP patterns (either for learning, or procedural) and ontologies/linked data design Usage of patterns in business intelligence and conceptual modeling Patterns in semantic social networks, semantic wikis, semantic blogs ODPs development and use in specific domains including geosciences, life sciences, digital humanities, cultural heritage, e-history, etc. ==================================================================================================== *Call for Patterns* Submission instruction can be found at http://ontologydesignpatterns.org/wiki/WOP:2016/Submission. We invite the submission of research results in the form of ontology design patterns (ODPs). Patterns submitted should have a general relevance to the ontology engineering field, or specific interest within a knowledge domain. Patterns should solve some particular modeling problem, and be of significant interest for discussion at the workshop. Patterns should be original, in the sense that they are the intellectual product of the author(s), however they may still be based on the collective experience of a community. Pattern submissions for the pattern session will be collected: through the ODP portal and by submitting a description of the pattern (pattern description) via EasyChair. Detailed instructions for patterns submission, including how to submit via the ontologydesignpatterns.org portal, are found at the submission page. Note that an account in the ODP portal is needed for submitting patterns; thus, authors should take care to request an account at least one week before their intended submission. Pattern submissions can be made in any type of ODPs. Currently, portal templates for submission are provided for the following types of patterns (see general typology for explanation of the types): Content patterns Structural patterns: logical and architecture patterns. Correspondence patterns: re-engineering and alignment patterns. For other types of patterns, the author is welcome to submit only a pattern description. Submission and Important Dates For details on how to submit to WOP2016 see the submission page. ==================================================================================================== *Important dates* Abstract submission (required): June 24th, 2016 Submission date: June 30th, 2016 Author notifications: July 31st, 2016 Camera-ready papers: August 12th, 2016 Workshops will be held on: 17th or 18th October, 2016 (TBD) *Best Poster Award* Workshop participants will be able to vote for the best poster, final decision to be made by the chairs. The best poster award takes into account criteria such as the quality of the submission, the relevance and significance of patterns or pattern usages presented, the presentation of the poster during the "lightning talks", and the level of involvement of the author during the revision phase and poster session discussions during the workshop. Proceedings Accepted papers and pattern descriptions will be made available on the workshop's website. We will also publish post-workshop proceedings with (possibly extended) accepted papers, in the IOS Press/AKA book series Studies on the Semantic Web. Copies can be ordered at a special discount of 30%, order requests should be sent to in...@ak.... *WOP2016 Chairs* Pascal Hitzler, Wright State University, USA ( general chair) Karl Hammar, Jönköping University, Sweden (papers co-chair) Monika Solanki, University of Oxford, UK (papers co-chair) Agnieszka Lawrynowicz, Poznan University of Technology, Poland (patterns co-chair) Andrea Giovanni Nuzzolese, ISTC-CNR Rome, Italy (patterns co-chair) Adila Krisnadhi, Wright State University, USA (proceedings chair) For general inquiries, please contact Pascal Hitzler at pascal.hitzler @ wright.edu |
|
From: Vladimir A. <vla...@on...> - 2016-04-21 10:24:13
|
DBPedia 2015-10 has extracted excellent bibliographic info. But it uses raw dbp: props. Please vote what to map them to (dbo:, bibo: etc) https://github.com/dbpedia/mappings-tracker/issues/79 |
|
From: Marcin R. <m.r...@uw...> - 2016-04-01 17:21:47
|
Dear DBpedia enthusiasts, a while ago Dimitris send me the message that I may become a member of your community. I'm very happy that I can join to your group and contribute to this great project. I am researcher at Institute of Information Science and Book Studies, University of Warsaw (Poland). I'm interested in bibliographic ontologies and conceptual modeling. Currently I'm working on consistency and expressiveness issues of bibliographic ontologies. I'll be more than happy to start my contribution with polish language mappings and take part with ongoing discussion. http://mappings.dbpedia.org/index.php/Mapping_pl In the mean time I appreciate getting the editor rights for the account Mroszkowski With regards, Marcin -- *dr Marcin Roszkowski* Zakład Systemów Informacyjnych Instytut Informacji Naukowej i Studiów Bibliologicznych Uniwersytet Warszawski |
|
From: Dimitris K. <ji...@gm...> - 2016-03-09 20:10:49
|
Dear all, we plan to move away from the mappings wiki in the near future and use RDF for storing the mappings. We need some feedback from the community, especially from mapping & ontology editors, on which syntax to use. Please read the doc below and cast your vote & comments at the end https://docs.google.com/document/d/1gUX7-qNuCEsNu-hgVrVtvQmBew9BHXUASUmIvDX1C1o/edit -- Kontokostas Dimitris |
|
From: Dimitris K. <kon...@in...> - 2016-02-22 16:01:09
|
Dear all, One big first decision we need to take as group is how to deal with multiple rdfs:domain/range. Monika Solanki and I drafted a document based on the existing feedback from you and came up with 3 options 1) Do not allow them at all 2) allow them (with different options) 3) remove all rdfs:domain/range axioms from the ontology some rationals and problems are summarized on the following document and your feedback is needed to choose our way forward. https://docs.google.com/document/d/1pQPO61d3RJY05yHSxlcu4DsR1NEcW8n9URoTci4lFJY/edit#heading=h.btsd7n2canhm (Pleased try to put you feedback directly on the gdoc inline or as comments. ) Best, Dimitris (on behalf of the OC) -- Dimitris Kontokostas Department of Computer Science, University of Leipzig & DBpedia Association Projects: http://dbpedia.org, http://rdfunit.aksw.org, http:// http://aligned-project.eu Homepage:http://aksw.org/DimitrisKontokostas Research Group: AKSW/KILT http://aksw.org/Groups/KILT |