From: Tomasz P. <tom...@gm...> - 2012-09-21 20:09:47
|
Hi Rob As you already know I have started working on a ORM-like mapper based on dotNetRDF. I intend it to be as thin as possible and rely mostly on the underlying powers of your library. To make it possible I have defined an interfaces called IRomanticContext+dynamic proxies, which will hide the details of how RDF triples and graphs are manipulated. The question I have comes form the fact the I need multiple context types for different types of underlying data. I have indentified the IGraph, ITripleStore, ISparqlDataset and BaseEndopint types, which give access to various sources of RDF. Will I really need to wrap all of those to provide a uniform abstraction layer over dotNetRDF? Is there some kind of common denominator? Regards, Tom |