I would like to have good performances when dealing with Roads+Towns in dbPedia.

To achieve that, I plan to:

  1. extract all Roads molecules from dbPedia. (a Road molecule being "any resource of type dbpedia:Road + its label + its longitude + its latitude + its thumbnail").

  2. extract all Towns molecules from dbPedia, in a similar way. (a Town molecule being "any resource of type dbpedia:City+ its abstract + its longitude + its latitude + its thumbnail").

  3. load all those molecules in a dedicated DB (RDF store, or NoSQL database [1]).

  4. query that dedicated DB for Roads+Towns information with acceptable performances

I would like your opinion on such a partitioning strategy.

Will it really improve performances to query a dedicated DB, vs running the same query on the full dbPedia DB?

Do existing RDF DBs already provide a similar feature (afaiu, this feature is called "rdf materialized views")?

[1]: my molecules have no cycles and can be serialized as trees. So NoSQL is an option for storage, indexation and retrieval.

asked 23 Jan '13, 09:13

lOlive's gravatar image

accept rate: 0%

edited 23 Jan '13, 09:13

I think Alexandre answered my question ahead of time : http://seevl.net/blog/2013/01/15/storing-and-querying-rdf-data-with-redis/

permanent link

answered 23 Jan '13, 09:37

lOlive's gravatar image

accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 23 Jan '13, 09:13

question was seen: 926 times

last updated: 23 Jan '13, 09:37