#dbpedia — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dbpedia, aggregated by home.social.
-
⏰ Reminder: HMC FAIR Friday Seminar
How can FAIR infrastructures actually help researchers instead of increasing complexity?
Join Sebastian Hellmann and Jan Forberg for a pragmatic discussion on FAIR data practices and open-source infrastructure.
📅 27 March 2026 | Online
🔗 Register here: https://events.hifis.net/event/3754#FAIR #ResearchData #OpenScience #Databus #MOSS #DBpedia
@dbpedia @helmholtz
-
⏰ Reminder: HMC FAIR Friday Seminar
How can FAIR infrastructures actually help researchers instead of increasing complexity?
Join Sebastian Hellmann and Jan Forberg for a pragmatic discussion on FAIR data practices and open-source infrastructure.
📅 27 March 2026 | Online
🔗 Register here: https://events.hifis.net/event/3754#FAIR #ResearchData #OpenScience #Databus #MOSS #DBpedia
@dbpedia @helmholtz
-
⏰ Reminder: HMC FAIR Friday Seminar
How can FAIR infrastructures actually help researchers instead of increasing complexity?
Join Sebastian Hellmann and Jan Forberg for a pragmatic discussion on FAIR data practices and open-source infrastructure.
📅 27 March 2026 | Online
🔗 Register here: https://events.hifis.net/event/3754#FAIR #ResearchData #OpenScience #Databus #MOSS #DBpedia
@dbpedia @helmholtz
-
⏰ Reminder: HMC FAIR Friday Seminar
How can FAIR infrastructures actually help researchers instead of increasing complexity?
Join Sebastian Hellmann and Jan Forberg for a pragmatic discussion on FAIR data practices and open-source infrastructure.
📅 27 March 2026 | Online
🔗 Register here: https://events.hifis.net/event/3754#FAIR #ResearchData #OpenScience #Databus #MOSS #DBpedia
@dbpedia @helmholtz
-
⏰ Reminder: HMC FAIR Friday Seminar
How can FAIR infrastructures actually help researchers instead of increasing complexity?
Join Sebastian Hellmann and Jan Forberg for a pragmatic discussion on FAIR data practices and open-source infrastructure.
📅 27 March 2026 | Online
🔗 Register here: https://events.hifis.net/event/3754#FAIR #ResearchData #OpenScience #Databus #MOSS #DBpedia
@dbpedia @helmholtz
-
📢 HMC FAIR Friday Seminar
More than a decade after the FAIR Principles were introduced, a key question remains:
👉 What value has FAIR actually delivered to researchers?
In this talk, Sebastian Hellmann and Jan Forberg explore the microeconomics of FAIR adoption and present open-source tools #Databus and #MOSS from the #DBpedia Association ecosystem.
📅 27 March 2026 | Online
🔗 Register here: https://helmholtz-metadaten.de/events/fair-reality-check -
📢 HMC FAIR Friday Seminar
More than a decade after the FAIR Principles were introduced, a key question remains:
👉 What value has FAIR actually delivered to researchers?
In this talk, Sebastian Hellmann and Jan Forberg explore the microeconomics of FAIR adoption and present open-source tools #Databus and #MOSS from the #DBpedia Association ecosystem.
📅 27 March 2026 | Online
🔗 Register here: https://helmholtz-metadaten.de/events/fair-reality-check -
📢 HMC FAIR Friday Seminar
More than a decade after the FAIR Principles were introduced, a key question remains:
👉 What value has FAIR actually delivered to researchers?
In this talk, Sebastian Hellmann and Jan Forberg explore the microeconomics of FAIR adoption and present open-source tools #Databus and #MOSS from the #DBpedia Association ecosystem.
📅 27 March 2026 | Online
🔗 Register here: https://helmholtz-metadaten.de/events/fair-reality-check -
📢 HMC FAIR Friday Seminar
More than a decade after the FAIR Principles were introduced, a key question remains:
👉 What value has FAIR actually delivered to researchers?
In this talk, Sebastian Hellmann and Jan Forberg explore the microeconomics of FAIR adoption and present open-source tools #Databus and #MOSS from the #DBpedia Association ecosystem.
📅 27 March 2026 | Online
🔗 Register here: https://helmholtz-metadaten.de/events/fair-reality-check -
📢 HMC FAIR Friday Seminar
More than a decade after the FAIR Principles were introduced, a key question remains:
👉 What value has FAIR actually delivered to researchers?
In this talk, Sebastian Hellmann and Jan Forberg explore the microeconomics of FAIR adoption and present open-source tools #Databus and #MOSS from the #DBpedia Association ecosystem.
📅 27 March 2026 | Online
🔗 Register here: https://helmholtz-metadaten.de/events/fair-reality-check -
The current activities on the #DBpedia issue board (https://github.com/dbpedia/extraction-framework/issues) are curious: While there is no reaction by the maintainers on (mine and other) issues, there are a lot responses by enthusiastic users volunteering to work on the issues. Even if each of these comments looks valid on its own, the accumulation and similarity of them makes me doubt these users are all actual humans.
-
The current activities on the #DBpedia issue board (https://github.com/dbpedia/extraction-framework/issues) are curious: While there is no reaction by the maintainers on (mine and other) issues, there are a lot responses by enthusiastic users volunteering to work on the issues. Even if each of these comments looks valid on its own, the accumulation and similarity of them makes me doubt these users are all actual humans.
-
The current activities on the #DBpedia issue board (https://github.com/dbpedia/extraction-framework/issues) are curious: While there is no reaction by the maintainers on (mine and other) issues, there are a lot responses by enthusiastic users volunteering to work on the issues. Even if each of these comments looks valid on its own, the accumulation and similarity of them makes me doubt these users are all actual humans.
-
The current activities on the #DBpedia issue board (https://github.com/dbpedia/extraction-framework/issues) are curious: While there is no reaction by the maintainers on (mine and other) issues, there are a lot responses by enthusiastic users volunteering to work on the issues. Even if each of these comments looks valid on its own, the accumulation and similarity of them makes me doubt these users are all actual humans.
-
The current activities on the #DBpedia issue board (https://github.com/dbpedia/extraction-framework/issues) are curious: While there is no reaction by the maintainers on (mine and other) issues, there are a lot responses by enthusiastic users volunteering to work on the issues. Even if each of these comments looks valid on its own, the accumulation and similarity of them makes me doubt these users are all actual humans.
-
Added a hotfix to the #ABECTO space data comparison project: https://github.com/fusion-jena/abecto-space-travel-comparison/commit/4ec43c8e317e5f0535e82d85e217795894ed7751
Ironically, the hotfix is to use #Wikidata classes to locally query the fetched #DBpedia data. At the next regular refresh, on 2026-01-10, mismatches based on properly aligned data will be available in https://mismatch-finder.toolforge.org/. Unfortunately, I can not invalidate the current mismatches before.
@nightrose @wikidata -
Added a hotfix to the #ABECTO space data comparison project: https://github.com/fusion-jena/abecto-space-travel-comparison/commit/4ec43c8e317e5f0535e82d85e217795894ed7751
Ironically, the hotfix is to use #Wikidata classes to locally query the fetched #DBpedia data. At the next regular refresh, on 2026-01-10, mismatches based on properly aligned data will be available in https://mismatch-finder.toolforge.org/. Unfortunately, I can not invalidate the current mismatches before.
@nightrose @wikidata -
Added a hotfix to the #ABECTO space data comparison project: https://github.com/fusion-jena/abecto-space-travel-comparison/commit/4ec43c8e317e5f0535e82d85e217795894ed7751
Ironically, the hotfix is to use #Wikidata classes to locally query the fetched #DBpedia data. At the next regular refresh, on 2026-01-10, mismatches based on properly aligned data will be available in https://mismatch-finder.toolforge.org/. Unfortunately, I can not invalidate the current mismatches before.
@nightrose @wikidata -
Added a hotfix to the #ABECTO space data comparison project: https://github.com/fusion-jena/abecto-space-travel-comparison/commit/4ec43c8e317e5f0535e82d85e217795894ed7751
Ironically, the hotfix is to use #Wikidata classes to locally query the fetched #DBpedia data. At the next regular refresh, on 2026-01-10, mismatches based on properly aligned data will be available in https://mismatch-finder.toolforge.org/. Unfortunately, I can not invalidate the current mismatches before.
@nightrose @wikidata -
Added a hotfix to the #ABECTO space data comparison project: https://github.com/fusion-jena/abecto-space-travel-comparison/commit/4ec43c8e317e5f0535e82d85e217795894ed7751
Ironically, the hotfix is to use #Wikidata classes to locally query the fetched #DBpedia data. At the next regular refresh, on 2026-01-10, mismatches based on properly aligned data will be available in https://mismatch-finder.toolforge.org/. Unfortunately, I can not invalidate the current mismatches before.
@nightrose @wikidata -
Surprisingly, I could not find an Issue about this #DBpedia problem. Now there is one: https://github.com/dbpedia/extraction-framework/issues/820
Contrary to my initial guess of an extractor bug, further investigations made an SPARQL endpoint (#openlinksw #virtuoso) bug seem more likely.
-
Surprisingly, I could not find an Issue about this #DBpedia problem. Now there is one: https://github.com/dbpedia/extraction-framework/issues/820
Contrary to my initial guess of an extractor bug, further investigations made an SPARQL endpoint (#openlinksw #virtuoso) bug seem more likely.
-
Surprisingly, I could not find an Issue about this #DBpedia problem. Now there is one: https://github.com/dbpedia/extraction-framework/issues/820
Contrary to my initial guess of an extractor bug, further investigations made an SPARQL endpoint (#openlinksw #virtuoso) bug seem more likely.
-
Surprisingly, I could not find an Issue about this #DBpedia problem. Now there is one: https://github.com/dbpedia/extraction-framework/issues/820
Contrary to my initial guess of an extractor bug, further investigations made an SPARQL endpoint (#openlinksw #virtuoso) bug seem more likely.
-
Surprisingly, I could not find an Issue about this #DBpedia problem. Now there is one: https://github.com/dbpedia/extraction-framework/issues/820
Contrary to my initial guess of an extractor bug, further investigations made an SPARQL endpoint (#openlinksw #virtuoso) bug seem more likely.
-
Remarkably:
➡️ Despite the lack of #DBpedia types, equivalent #Wikidata types are present in DBpedia.
➡️ Not all resources are affected: e.g. https://dbpedia.org/page/John_Young_(astronaut) is typed as http://dbpedia.org/ontology/Astronaut.
➡️ Right and wrong typed astronauts have the astronaut infobox (which is properly mapped https://mappings.dbpedia.org/index.php/Mapping_en:Infobox_astronaut) on #Wikipedia.I guess an extractor bug 🪲.
Side effect: Many astronauts are displayed as "animals". Although on might consider this as ontologically correct, it is quiet odd.
-
Remarkably:
➡️ Despite the lack of #DBpedia types, equivalent #Wikidata types are present in DBpedia.
➡️ Not all resources are affected: e.g. https://dbpedia.org/page/John_Young_(astronaut) is typed as http://dbpedia.org/ontology/Astronaut.
➡️ Right and wrong typed astronauts have the astronaut infobox (which is properly mapped https://mappings.dbpedia.org/index.php/Mapping_en:Infobox_astronaut) on #Wikipedia.I guess an extractor bug 🪲.
Side effect: Many astronauts are displayed as "animals". Although on might consider this as ontologically correct, it is quiet odd.
-
Remarkably:
➡️ Despite the lack of #DBpedia types, equivalent #Wikidata types are present in DBpedia.
➡️ Not all resources are affected: e.g. https://dbpedia.org/page/John_Young_(astronaut) is typed as http://dbpedia.org/ontology/Astronaut.
➡️ Right and wrong typed astronauts have the astronaut infobox (which is properly mapped https://mappings.dbpedia.org/index.php/Mapping_en:Infobox_astronaut) on #Wikipedia.I guess an extractor bug 🪲.
Side effect: Many astronauts are displayed as "animals". Although on might consider this as ontologically correct, it is quiet odd.
-
Remarkably:
➡️ Despite the lack of #DBpedia types, equivalent #Wikidata types are present in DBpedia.
➡️ Not all resources are affected: e.g. https://dbpedia.org/page/John_Young_(astronaut) is typed as http://dbpedia.org/ontology/Astronaut.
➡️ Right and wrong typed astronauts have the astronaut infobox (which is properly mapped https://mappings.dbpedia.org/index.php/Mapping_en:Infobox_astronaut) on #Wikipedia.I guess an extractor bug 🪲.
Side effect: Many astronauts are displayed as "animals". Although on might consider this as ontologically correct, it is quiet odd.
-
Remarkably:
➡️ Despite the lack of #DBpedia types, equivalent #Wikidata types are present in DBpedia.
➡️ Not all resources are affected: e.g. https://dbpedia.org/page/John_Young_(astronaut) is typed as http://dbpedia.org/ontology/Astronaut.
➡️ Right and wrong typed astronauts have the astronaut infobox (which is properly mapped https://mappings.dbpedia.org/index.php/Mapping_en:Infobox_astronaut) on #Wikipedia.I guess an extractor bug 🪲.
Side effect: Many astronauts are displayed as "animals". Although on might consider this as ontologically correct, it is quiet odd.
-
With ABECTO 3.1.5, I restored regular pushes of space travel data deviations between #Wikidata and #DBpedia to https://mismatch-finder.toolforge.org @nightrose. But it provides (at first glance) strange results (🔗 https://mismatch-finder.toolforge.org/results?ids=Q107667|Q115651852), like:
➡️ John Young member of the crew of Apollo 16 mismatches http://dbpedia.org/resource/Apollo_16
➡️ SpaceX Crew-10 crew member Anne McClain mismatches http://dbpedia.org/resource/Anne_McClainReason: Missing http://dbpedia.org/ontology/SpaceMission, http://dbpedia.org/ontology/Astronaut, … type statements in @dbpedia.
-
With ABECTO 3.1.5, I restored regular pushes of space travel data deviations between #Wikidata and #DBpedia to https://mismatch-finder.toolforge.org @nightrose. But it provides (at first glance) strange results (🔗 https://mismatch-finder.toolforge.org/results?ids=Q107667|Q115651852), like:
➡️ John Young member of the crew of Apollo 16 mismatches http://dbpedia.org/resource/Apollo_16
➡️ SpaceX Crew-10 crew member Anne McClain mismatches http://dbpedia.org/resource/Anne_McClainReason: Missing http://dbpedia.org/ontology/SpaceMission, http://dbpedia.org/ontology/Astronaut, … type statements in @dbpedia.
-
With ABECTO 3.1.5, I restored regular pushes of space travel data deviations between #Wikidata and #DBpedia to https://mismatch-finder.toolforge.org @nightrose. But it provides (at first glance) strange results (🔗 https://mismatch-finder.toolforge.org/results?ids=Q107667|Q115651852), like:
➡️ John Young member of the crew of Apollo 16 mismatches http://dbpedia.org/resource/Apollo_16
➡️ SpaceX Crew-10 crew member Anne McClain mismatches http://dbpedia.org/resource/Anne_McClainReason: Missing http://dbpedia.org/ontology/SpaceMission, http://dbpedia.org/ontology/Astronaut, … type statements in @dbpedia.
-
With ABECTO 3.1.5, I restored regular pushes of space travel data deviations between #Wikidata and #DBpedia to https://mismatch-finder.toolforge.org @nightrose. But it provides (at first glance) strange results (🔗 https://mismatch-finder.toolforge.org/results?ids=Q107667|Q115651852), like:
➡️ John Young member of the crew of Apollo 16 mismatches http://dbpedia.org/resource/Apollo_16
➡️ SpaceX Crew-10 crew member Anne McClain mismatches http://dbpedia.org/resource/Anne_McClainReason: Missing http://dbpedia.org/ontology/SpaceMission, http://dbpedia.org/ontology/Astronaut, … type statements in @dbpedia.
-
With ABECTO 3.1.5, I restored regular pushes of space travel data deviations between #Wikidata and #DBpedia to https://mismatch-finder.toolforge.org @nightrose. But it provides (at first glance) strange results (🔗 https://mismatch-finder.toolforge.org/results?ids=Q107667|Q115651852), like:
➡️ John Young member of the crew of Apollo 16 mismatches http://dbpedia.org/resource/Apollo_16
➡️ SpaceX Crew-10 crew member Anne McClain mismatches http://dbpedia.org/resource/Anne_McClainReason: Missing http://dbpedia.org/ontology/SpaceMission, http://dbpedia.org/ontology/Astronaut, … type statements in @dbpedia.
-
An unconventional approach to avoid providing an email address in the User-Agent was chosen in #DBpedia by reusing the user agent of #curl: https://github.com/dbpedia/extraction-framework/commit/de3ca70694f347db84a2daeb88d8218506075f81
I proposed an alternative: https://github.com/dbpedia/extraction-framework/issues/819 -
An unconventional approach to avoid providing an email address in the User-Agent was chosen in #DBpedia by reusing the user agent of #curl: https://github.com/dbpedia/extraction-framework/commit/de3ca70694f347db84a2daeb88d8218506075f81
I proposed an alternative: https://github.com/dbpedia/extraction-framework/issues/819 -
An unconventional approach to avoid providing an email address in the User-Agent was chosen in #DBpedia by reusing the user agent of #curl: https://github.com/dbpedia/extraction-framework/commit/de3ca70694f347db84a2daeb88d8218506075f81
I proposed an alternative: https://github.com/dbpedia/extraction-framework/issues/819 -
An unconventional approach to avoid providing an email address in the User-Agent was chosen in #DBpedia by reusing the user agent of #curl: https://github.com/dbpedia/extraction-framework/commit/de3ca70694f347db84a2daeb88d8218506075f81
I proposed an alternative: https://github.com/dbpedia/extraction-framework/issues/819 -
An unconventional approach to avoid providing an email address in the User-Agent was chosen in #DBpedia by reusing the user agent of #curl: https://github.com/dbpedia/extraction-framework/commit/de3ca70694f347db84a2daeb88d8218506075f81
I proposed an alternative: https://github.com/dbpedia/extraction-framework/issues/819 -
It looks like DBpedia has gotten a lot less useful for my purposes 🙁It used to include a short summary of a topic (often in multiple languages) but now that has gone(?) (compare dbpedia.org/page/Blattidae with web.archive.org/web/20221226... from @[email protected] )
-
@awinkler @DNB_Aktuelles Bei "Examples" das aktuell letzte Beispiel: "Welche Titel von anderen Autoren gehören zur gleichen literarischen Gattung wie Friedrich Schiller?" https://sparql.dnb.de/dnbgnd/tRteun zeigt die Federated Query mit dbpedia
#dbpedia -
@awinkler @DNB_Aktuelles Bei "Examples" das aktuell letzte Beispiel: "Welche Titel von anderen Autoren gehören zur gleichen literarischen Gattung wie Friedrich Schiller?" https://sparql.dnb.de/dnbgnd/tRteun zeigt die Federated Query mit dbpedia
#dbpedia -
@awinkler @DNB_Aktuelles Bei "Examples" das aktuell letzte Beispiel: "Welche Titel von anderen Autoren gehören zur gleichen literarischen Gattung wie Friedrich Schiller?" https://sparql.dnb.de/dnbgnd/tRteun zeigt die Federated Query mit dbpedia
#dbpedia -
@awinkler @DNB_Aktuelles Bei "Examples" das aktuell letzte Beispiel: "Welche Titel von anderen Autoren gehören zur gleichen literarischen Gattung wie Friedrich Schiller?" https://sparql.dnb.de/dnbgnd/tRteun zeigt die Federated Query mit dbpedia
#dbpedia -
@awinkler @DNB_Aktuelles Bei "Examples" das aktuell letzte Beispiel: "Welche Titel von anderen Autoren gehören zur gleichen literarischen Gattung wie Friedrich Schiller?" https://sparql.dnb.de/dnbgnd/tRteun zeigt die Federated Query mit dbpedia
#dbpedia -
Slides for first #DBpedia talk by Sebastian Hellmann at #SemanticsConf sit at https://docs.google.com/presentation/d/1EDl3Yc3nicA_a9HYYqC1BEC7OTb8cXDmga0xRwwvI7c/edit?usp=drivesdk .
-
Slides for first #DBpedia talk by Sebastian Hellmann at #SemanticsConf sit at https://docs.google.com/presentation/d/1EDl3Yc3nicA_a9HYYqC1BEC7OTb8cXDmga0xRwwvI7c/edit?usp=drivesdk .
-
Slides for first #DBpedia talk by Sebastian Hellmann at #SemanticsConf sit at https://docs.google.com/presentation/d/1EDl3Yc3nicA_a9HYYqC1BEC7OTb8cXDmga0xRwwvI7c/edit?usp=drivesdk .
-
Slides for first #DBpedia talk by Sebastian Hellmann at #SemanticsConf sit at https://docs.google.com/presentation/d/1EDl3Yc3nicA_a9HYYqC1BEC7OTb8cXDmga0xRwwvI7c/edit?usp=drivesdk .