Hi Alexandru, Based on what you and I have written, I would guess that when you try to load an .rdf file from dbpedia.org, it creates a query (with an internal redirect) that has a limit of 2000 rows (probably a Virtuoso configuration). I have no other explanation... let's wait for someone official's answer.
Kind regards, Zoltán On 2011.10.18. 14:47, Alexandru Todor wrote: > Hi Zoltán, > > I have no such problems with DBpedia Germany as you can see by looking > at http://de.dbpedia.org/data/Berlin.rdf and then > http://dbpedia.org/data/Berlin.rdf. > > I am pretty sure it is not an issue with Virtuoso itself or the > serialization format used but with the DBpedia Vad and some sort of > caching mechanism they use for the .rdf files. If you execute the > describe query directly you will get the entire dataset and not the > truncated one from the .rdf file, for example: > http://dbpedia.org/sparql?default-graph-uri=http%3A%2F%2Fdbpedia.org&query=describe+%3Chttp%3A%2F%2Fdbpedia.org%2Fresource%2FBerlin%3E&format=application%2Frdf%2Bxml&timeout=0&debug=on > > Kind Regards, > Alexandru > > > > On 10/18/2011 09:08 AM, Zoltán Sziládi wrote: >> Hi, >> >> This is something I had to work around a while ago, so I think I know >> the answer, but correct me if I'm wrong. >> The RDF XML, JSON and N3 representations return mostly triples in which >> the resource can be found as an object. Actually, JSON and N3 does not >> even contain triples where the resource is a subject, while in RDF XML >> in some cases it does. The problem is that unlike the NTRIPLES, ATOM and >> JSOD representations, these 3 contain the resource as objects as well >> and in some cases this leads to lots of triples but there is a limit of >> 2000 for the number of returned triples. Places as you said are a good >> example: there are so many triples containing places that it's easy for >> them to reach 2000 triples while persons do not have as many. >> If you want to obtain the triples in which the URI is a subject, I would >> suggest you use the NTRIPLES representation (it also contains language >> data for the labels unlike rdf xml, json, n3, jsod). >> >> Regards, >> Zoltán >> >> On 2011.10.17. 16:09, Alexandru Todor wrote: >>> Hi, >>> >>> I've noticed that the http://dbpedia.org/data/[resource name].rdf files >>> with the RDF/XML description of the resources are missing a big portion >>> of the data displayed on the http://dbpedia.org/resource/[resource name] >>> site. >>> >>> For example look at http://dbpedia.org/page/Berlin and then at: >>> http://dbpedia.org/data/Berlin.rdf . You will notice missing abstracts, >>> literals and possibly other information from the .rdf file. >>> >>> The strange thing about this bug is that it seems to be valid only for >>> entities of type place and subclasses of it. Entities of type person or >>> chemical elements seem to be ok, however I haven't checked all of >>> dbpedia and all of the properties so I can't estimate how wide-spread >>> this issue is. >>> >>> >>> Kind Regards, >>> Alexandru Todor >>> >>> ------------------------------------------------------------------------------ >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2d-oct >>> _______________________________________________ >>> Dbpedia-discussion mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2d-oct >> _______________________________________________ >> Dbpedia-discussion mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Dbpedia-discussion mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
