Tim Berners-Lee wrote: > > On 2007-12 -30, at 13:14, Kingsley Idehen wrote: > >> Richard, >> >> Where are we re. the transition from Germany to Burlington re. >> resolution of the dbpedia.org domain and related URI dereferencing >> via Pubby hosted in Virtuoso? >> >> openlink.dbpedia.org has been resolving for a while now and the URIs >> are dereferencing fine. >> >> >> Tim: Re. # vs slash and the resulting 303 related dereferencing >> network hops overhead, I do have <http://dbpedia2.openlinksw.com> >> in place such that you can evaluate both instances concurrently. >> Thus, you can compare the following URIs: >> >> 1. <http://dbpedia.org/resource/Tim_Berners-Lee> > > That hangs for minutes and eventually times out, trying to load the > ontologies. I don't understand why this is soo slow just now, with > things like > http://dbpedia.openlinksw.com:8890/sparql?default-graph-uri=http%3A%2F%2Fdbpedia.org&query=DESCRIBE+%3Chttp%3A%2F%2Fdbpedia.org%2Fproperty%2Fbirth%3E > > <http://dbpedia.openlinksw.com:8890/sparql?default-graph-uri=http%3A%2F%2Fdbpedia.org&query=DESCRIBE+%3Chttp%3A%2F%2Fdbpedia.org%2Fproperty%2Fbirth%3E> > which only gives the two triples > > :birth a rdf:Property; s:label "birth" . > > There were about 36 of them before tabulator timed out (around 60s). > The redirect takes from here 0.3s and the query around 1s. > That would take round 36 * 1.3 = 48s if serialized. > Does the server run parallel threads? This is the current pubby setup in Berlin. > > > > >> 2. <http://openlink.dbpedia.org/resource/Tim_Berners-Lee> - >> Burlington with Slash URI scheme > > That has a conneg problem and gives me the HTML instead of the RDF -- > it doesn't prefer the RDF, and tabulator extension will accept either. This is pubby in Burlington, but there is a possibility that the content negotiation rules aren't in place etc..
Zdravko: Please take note re. DBpedia instance. > >> 3. <http://dbpedia2.openlinksw.com/about/Tim_Berners-Lee#this> - >> Burlington Mirror Server with # URI scheme > > That works fine. It is faster than 1 but partly because the > vocabulary terms just 404 -- which takes less time , it seems, that > redirecting to a sparql query! > > ... linksw.com/class/yago/Academician109759069 > expandfailedhttp://dbpedia2.openlinksw.com/class/yago/Blogger109860415 > expandfailedhttp://dbpedia2.openlinksw.com/class/yago/Colleague109935990 > expandfailedhttp://dbpedia2.openlinksw.com/class/yago/Entity100001740 > expandfailedhttp://dbpedia2.openlinksw.com/class/yago/Inventor110214637 > expandfailedhttp://dbpedia2.openlinksw.com/class/yago/Laureate110249011 > expandfailedhttp://dbpedia2.openlinksw.com/class/yago/Person100007846 > expandfailedhttp://dbpedia2.openlinksw.com/class/yago/Programmer110481268 > expandfailedhttp://dbpedia2.openlinksw.com/class/yago/Scientist110560637 > expandfailedhttp://dbpedia2.openlinksw.com/class/yago/Writer110794014 This is Burlington, and using Virtuoso's content negotiation features via it's in-built Linked Data Deployment functionality realm. We'll look into the 404 issues above. Note, this setup will still be faster once this matter is resolved. Zdravko: Please take note re. DBpedia2 instance. -- Regards, Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen President & CEO OpenLink Software Web: http://www.openlinksw.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
