New DBpedia Website

We are proud to announce the completion of the new DBpediaWebsite. We used the New Year’s break as an opportunity to alter layout, design and content of the website, according to the requirements of the DBpedia Community and DBpedia Members. Have a look here https://www.dbpedia.org. We offer a tool for you, to make your voice heard. Just click the feedback button on the new website. If you find the content helpful, please click on Yep. If you think the content is not sufficient, please report to us!

Hi,

I was curious about DBpedia and wanted to try out the samples on your website:
https://wiki.dbpedia.org/apply
None of them work. I had a quick look: it is trying to access an insecure HTTP endpoint from a HTTPS page, so the browser blocks the request.
Please also allow me to give you feedback on the site in general. It has a modern and pretty layout. However, it feels like the site’s main focus is selling the project rather than attracting new users. It feels a bit more sender centric than user centric.

Best
Jens

PS:
While writing this, I get a stern warning panel that tells me not to criticize people.
That’s quite a welcome.
I wonder whether DBpedia had harshness issues in its community to come up with such a warning?

Hi,
Thank you for your feedback. Last week we announced the new DBpedia website. Does your feedback relate to this page? www.dbpedia.org
We have introduced the category, Data, Tools and Services on the new page. I already published popular tools and applications there, but we would like to present even more applications in the next few weeks. We are still working on the implementation. As soon as the page is ready, I can share it with you.
Have a nice day.
Best,
Julia

Hi,

I had simply googled for dbpedia and it led me to https://wiki.dbpedia.org/.
So the wiki subdomain including the buggy sample requests at https://wiki.dbpedia.org/apply will no longer maintained?

At some point they may or may not be replaced by new contant on a different page at www. dbpedia. org/community/data-tools-services/ ?

Thank you for the information, no need to notify me.

Best regards
Jens

Hi @jenssteckhan,
Yes, I will not update wiki.dbpedia.org/apply. We will publish new tools and applications on our new page www.dbpedia.org/community/data-tools-services/
Best regards,
Julia

That seems to be a default setting of the forum software discourse. Quite interesting, that it flagged your post. Why do you think that is?

Never or at least I can’t remember a single incident in the last 13 years. Our community gives very constructive feedback. They post issues and the core team or someone from the community tries to fix it, so DBpedia gets better.

Thanks for reporting, I filed it here: https://github.com/dbpedia/extraction-framework/issues/675

We already have a lot of users, in fact, you could argue that we have too many. We serve over 20 million requests daily on sparql, linked data, lookup, spotlight, etc. Plus there is over a petabyte of dump download traffic yearly. This is free for everybody. In the beginning, DBpedia was supported by three orgs, now it is 28, plus hundreds of individual volunteers. If there is no project, then there will be no resources (this is the tab, where we show the free resources). If there are no resources, then there will be no users.

There are plans to migrate the old stuff under apply to the new website. Maybe under a prominent “try” or “apply” again, but in principle wiki.dbpedia.org or www.dbpedia.org is a project page about the DBpedia project. Most of the content has been migrated here: https://www.dbpedia.org/resources/sparql/ (but still needs the https fix… )

That seems to be a default setting of the forum software discourse.
Quite interesting, that it flagged your post. Why do you think that is?

It came up before I even wrote a single word. So I don’t take it personally :slight_smile: Maybe the administrator for your forum set it up or it is simply the default setting of that software.

Never or at least I can’t remember a single incident in the last 13 years. Our community gives very constructive feedback. They post issues and the core team or someone from the community tries to fix it, so DBpedia gets better.

I am glad to hear that! So there was no particular reason why that warning appeared. Or maybe it works and makes people friendlier and more constructive, who knows.

Thanks for reporting, I filed it here: https://github.com/dbpedia/extraction-framework/issues/675

Thank you and I am happy that you found my report useful. So that’s where you track your issues, good to know. If I run into a problem again, I would report it there.

We already have a lot of users, in fact, you could argue that we have too many. (…)

I didn’t mean to question DBpedia’s success for sure. Good for you that people embrace it.
Also, I like the appearance of the www subdomain better. I was a bit confused. I didn’t really know whether the wiki subdomain content would still be supported. Thanks for clearing it up.

@jenssteckhan,

@pkleef just fixed several the hosting issues, so snorql works again. (clear cache with ctr-r in browser to reload snorql app).

regarding the don’t criticize message: discourse has too many options. I couldn’t find this one. Could you post the exact message, so we can google it?

Regarding the request:
When I click on the soccer players example in the Apply section, I now get a popup:
“DBpedia says: Cross-site requests prohibited. You will only be able to SPARQL the origin site: ReferenceError: netscape is not defined”

Regarding the “don’t criticise message”:
There was a note that it appears for the two first posts for every new user. So I can’t see it any more and am afraid I cannot quote the exact message. I think I remember the words “constructive” and “criticise ideas, not people”.
It didn’t feel super inviting, but maybe it’s working since you mentioned that your discussion culture is very healthy.

I am unable to reproduce this. It is working fine for in chrome and firefox.

Could you check whether the top of your page says https://dbpedia.org/sparql or http. You might need to hard refresh the browser cache and javascript with ctrl r or ctrl F5

1 Like

Excellent, I deleted the cache and reloaded the page. Now it’s working - thank you very much!

1 Like