Re: [dotNetRDF-develop] Dotnetrdf-develop Digest, Vol 4, Issue 3

[Alexander S. <ale...@gm...>]

Hi Rob,

Thank you for the answer. I have chosen SparqlConnector but have problems
with queries that contain Virtuoso built-in functions (for example,
bif:contains): parser wants bif namespace to be set. Is there any
workaround?

Regards,
Alexander

2010/3/10 <dot...@li...>

> Send Dotnetrdf-develop mailing list submissions to
>        dot...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
> or, via email, send a message with subject or body 'help' to
>        dot...@li...
>
> You can reach the person managing the list at
>        dot...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dotnetrdf-develop digest..."
>
>
> Today's Topics:
>
>   1. Access general SPARQL-endpoint (Alexander Sidorov)
>   2. Re: Access general SPARQL-endpoint (Rob Vesse)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 9 Mar 2010 19:52:56 +0100
> From: Alexander Sidorov <ale...@gm...>
> Subject: [dotNetRDF-develop] Access general SPARQL-endpoint
> To: dot...@li...
> Message-ID:
>        <828...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello!
>
> I need to access Virtuoso but not their ADO.NET provider (so
> VirtuosoManager
> doesn't work for me) but through SPARQL protocol (
> lod.openlinksw.com/sparql).
> What classes should I use?
>
> Regards,
> Alexander
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Wed, 10 Mar 2010 01:41:28 -0800
> From: "Rob Vesse" <rv...@do...>
> Subject: Re: [dotNetRDF-develop] Access general SPARQL-endpoint
> To: "dotNetRDF Developer Discussion and Feature Request"
>        <dot...@li...>
> Message-ID: <6399325e$1cddbcd$269c081b$@com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Alexander
>
> You can either use the SparqlRemoteEndpoint
> (VDS.RDF.Query.SparqlRemoteEndpoint) class which provides specific methods
> for making SELECT/ASK and CONSTRUCT/DESCRIBE queries and can connect to any
> SPARQL endpoint with the ability to specify the default & named graph URIs
> you want to use.
>
> Or you can use the SparqlConnector (VDS.RDF.Storage.SparqlConnector) which
> has the same basic interface (IGenericIOManager) as the VirtuosoManager and
> gives you read-only storage access to an endpoint.  The disadvantage of
> this class is that it isn't as easy to specify default/named graph URIs if
> you need to (the advantage being that it implements the IGenericIOManager
> interface)
>
> Take a look at
> http://dotnetrdf.org/content.asp?pageID=Querying%20with%20SPARQL for
> details on using the SparqlRemoteEndpoint class
>
> If you have any further questions let me know
>
> Rob Vesse
>
> ----------------------------------------
> From: "Alexander Sidorov" <ale...@gm...>
> Sent: Tuesday, March 09, 2010 6:52 PM
> To: dot...@li...
> Subject: [dotNetRDF-develop] Access general SPARQL-endpoint
>
> Hello!
>
> I need to access Virtuoso but not their ADO.NET provider (so
> VirtuosoManager doesn't work for me) but through SPARQL protocol
> (lod.openlinksw.com/sparql). What classes should I use?
>
> Regards,
> Alexander
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
>
> ------------------------------
>
> _______________________________________________
> Dotnetrdf-develop mailing list
> Dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
>
> End of Dotnetrdf-develop Digest, Vol 4, Issue 3
> ***********************************************
>