Re: DBpedia now available as triple pattern fragments

On 10/31/14 9:44 AM, Ruben Verborgh wrote:
>>> I also track the DBpedia public SPARQL endpoint; however this is more tricky.
>>> >>The Pingdom server only pings one URL, and I have sometimes get cached results,
>>> >>even at times when DBpedia was down.

Because the is an ngnix proxy in front of the Linked Data resources. 
Again, we handle the following, re: DBpedia:

1. SPARQL endpoint
2. Linked Data Deployment -- that includes URL re-writes and content 
negotiation etc..

>> >
>> >That's weird... any idea why that happens?
> One of the layers of caching, I think.
> I.e., simple, previously asked queries still go through because they're cached,
> but any new query does not work anymore.
>
> Perhaps the SPARQLES guys have some insights into this?
> http://aidanhogan.com/docs/epmonitorISWC.pdf

Back to why I said, we need to produce yet another report about DBpedia.


Links:

[1] http://bit.ly/dbpedia-usage-analysis -- last report we publish, in 
regards to DBpedia 3.8 (we have one in the works for 3.9, and will try 
to make these a quarterly affair)

-- 
Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this