>'yes, i also consider DBpedia buggy in this sense (hence the crossposting)'
Just a small note. I think you mean that the SPARQL engine behind a particular deployment of DBpedia is behaving differently from what you would desire. Although there are bugs in DBpedia, this is not one of them. :) I think it is important to make this distinction between DBpedia and the SPARQL endpoints serving its contents exactly to point out that you could provide your own implementation/wrapper that sorts/limits results the way you want. With more deployments, everybody benefits from the collaboration and the competition. On the one hand maybe the traffic will be more evenly spread, and on the other hand one improvement by a player may push other players to keep pace. I would be curious to hear about advantages provided by one endpoint over another, for example. Has anybody done that? Cheers Pablo On Aug 9, 2011 12:30 PM, "Jörn Hees" <[email protected]> wrote:
------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
