Re: [dotNetRDF-Develop] Different means to accessing RDF

[Rob V. <rv...@do...>]

Well IGraph and ITripleStore can both be wrapped by ISparqlDataset
instances

For remote things I am planning to write a dataset implementation that
would wrap another query engine (I.e. convert the calls into SPARQL
queries onto whatever the underlying engine is) because that helps address
another open task I have but I haven't got very far with it just yet.

So I'd recommend using ISparqlDataset as the common denominator provided
you're OK with talking to remote endpoints via this interface not being
supported just yet.

Rob

On 9/21/12 1:08 PM, "Tomasz Pluskiewicz" <tom...@gm...>
wrote:

>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
>
>--------------------------------------------------------------------------
>----
>Got visibility?
>Most devs has no idea what their production app looks like.
>Find out how fast your code is with AppDynamics Lite.
>http://ad.doubleclick.net/clk;262219671;13503038;y?
>http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>_______________________________________________
>dotNetRDF-develop mailing list
>dot...@li...
>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop