Completely earnest question, and I hope you have the time to answer -- How do you effectively use SemWeb tech? Obviously you can't build your whole system with

Completely earnest question, and I hope you have the time to answer -- How do you effectively use SemWeb tech? Obviously you can't build your whole system with a triple store backend; that would be too slow. Especially if you have a data explosion of millions and millions of facts. I've thought of a neat little distributed p2p research project that exchanges news items like HN/Reddit with your interest graph as determined by the nodes you share upvotes with (or weighed by some scheme you can tweak). Do you simply use RDF/OWL ontologies like FOAF, SIOC, etc. as the data transport format and then actually store information in relational databases internally? I want to do this so people can curate their own interest graphs, essentially; it's like prismatic, but software under your own control. Such a platform would be extensible since you can add new ontologies to support new needs. The Slashdot crowd, for instance, might moderate with tags such as 'insightful' rather than simply 'upvoting'. And can you use these graph databases like Prolog systems? And can we make that intuitive for the end user? Or as a more practical example, what about a molecule database? I'd need to store representations, properties, etc. There's a potentially limitless amount of factual information that I could store on one particular molecule. How do you make your software flexible enough to "know" what data you have on any given molecule and decide which "context" to portray it? (ie. if it's of medicinal use, synthetic chemistry use, is simply a common reagent, etc.) Is some of this just inherently kept in a relational database for fast querying with the graph database backing an asynchronously updating view?