Menu
▾
▴
dotnetrdf-support — User Help and Support
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
(9) |
Dec
(4) |
| 2011 |
Jan
(1) |
Feb
(6) |
Mar
(9) |
Apr
(9) |
May
(20) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
(6) |
Oct
(3) |
Nov
(13) |
Dec
(1) |
| 2012 |
Jan
(1) |
Feb
(12) |
Mar
(5) |
Apr
(8) |
May
|
Jun
(25) |
Jul
(7) |
Aug
(4) |
Sep
(14) |
Oct
(5) |
Nov
(22) |
Dec
(6) |
| 2013 |
Jan
(18) |
Feb
(28) |
Mar
(11) |
Apr
(18) |
May
(4) |
Jun
|
Jul
(9) |
Aug
(6) |
Sep
(4) |
Oct
(4) |
Nov
(6) |
Dec
(7) |
| 2014 |
Jan
(9) |
Feb
(15) |
Mar
(14) |
Apr
(7) |
May
(5) |
Jun
(15) |
Jul
(2) |
Aug
(6) |
Sep
(5) |
Oct
(7) |
Nov
(9) |
Dec
(16) |
| 2015 |
Jan
(4) |
Feb
(5) |
Mar
(1) |
Apr
(2) |
May
(2) |
Jun
(15) |
Jul
(8) |
Aug
|
Sep
(4) |
Oct
|
Nov
(4) |
Dec
(4) |
| 2016 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
(5) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Rob V. <rv...@do...> - 2014-12-01 12:26:01
|
Frank
Do you have a complete stack trace from the case where it fails?
UriFormatException implies there is some invalid data somewhere, the fact
that you are using SparqlRemoteEndpoint suggests that the remote server
may be returning some bad data that we can't process though this should
probably not manifest as a UriFormatException directly but as a
RdfParseException if this is the case.
As for why POST versus non-POST would make a difference I do not know, I
will try and take a proper look later today.
Note that SparqlRemoteEndpoint will automatically change to POST when a
query is above a certain length regardless of the explicit setting, the
explicit setting is mostly useful just to force a POST in all cases.
Rob
On 01/12/2014 12:14, "Frank Schumacher" <fs...@in...>
wrote:
>Hello again,
>
>I narrowed it down a bit more, the error seems to happen, when the
>endpoint is set to POST:
>
>SparqlRemoteEndpoint endpoint = new SparqlRemoteEndpoint(new
>Uri("http://creativeartefact.org/sparql"),
>"http://creativeartefact.org/");
>endpoint.HttpMode = "POST";
>
>SparqlResultSet sparqlResults = endpoint.QueryWithResultSet("PREFIX mbo:
><http://creativeartefact.org/ontology/> PREFIX rdfs:
><http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT * WHERE {?uri a
>mbo:Organiser. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:city ?city}.
>OPTIONAL {?uri mbo:street ?street}. OPTIONAL {?uri mbo:postalcode
>?postalcode}. }");
>
>SparqlResultSet sparqlResults = endpoint.QueryWithResultSet("SELECT *
>WHERE {?uri ?label ?city.}");
>
>The first statement executes, but the second throws the error. When
>commenting out the line endpoint.HttpMode = "POST"; - also the second
>one executes.
>
>As my statements can get rather long, I need post to make sure the
>SPARQL request doesn't exceed the allowed length for GET. Any idea, how
>to solve this problem?
>
>Thanks in advance,
>Frank
>
>#Am 28.11.2014 18:03, schrieb Frank Schumacher:
>> I made some more tests and it is getting even stranger. I tried more
>> test queries and even the simplest ones fail. For testing, I made two
>> call. The first one works, the second raises the error. When I try to
>> step into it with F11, it tells me:
>>
>> Aufruflistenort (callstackposition?):
>>
>>VDS.Common.dll!VDS.Common.Tries.AbstractTrie<string,char,System.Uri>.Move
>>ToNode(string
>> key) Zeile 211
>>
>> Here is the line that works:
>> SparqlResultSet sparqlResults = args.Endpoint.QueryWithResultSet("PREFIX
>> mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs:
>> <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT * WHERE {?uri a
>> mbo:Organiser. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:city ?city}.
>> OPTIONAL {?uri mbo:street ?street}. OPTIONAL {?uri mbo:postalcode
>> ?postalcode}. }");
>>
>> and here the one that raises the error:
>> SparqlResultSet sparqlResults = args.Endpoint.QueryWithResultSet("SELECT
>> * WHERE {?uri ?label ?city}");
>>
>> I'm really puzzled ...
>>
>> Ciao,
>> Frank
>>
>> Am 28.11.2014 17:08, schrieb Frank Schumacher:
>>> Hello Rob,
>>>
>>> I get a really strange UriFormatException (Ungültiger URI: Das
>>> URI-Format konnte nicht bestimmt werden.) when calling
>>> SparqlRemoteEndpoint.QueryWithResultSet with the following query:
>>>
>>> PREFIX mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs:
>>> <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT ?uri ?label
>>>?dis
>>> ?ann WHERE {?uri a mbo:Artist. ?uri rdfs:label ?label. OPTIONAL {?uri
>>> mbo:disambiguation ?dis}. OPTIONAL {?uri mbo:annotation ?ann}. }
>>>
>>> With a similar query, I don't get any error:
>>>
>>> PREFIX mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs:
>>> <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT * WHERE {?uri a
>>> mbo:Organiser. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:city ?city}.
>>> OPTIONAL {?uri mbo:street ?street}. OPTIONAL {?uri mbo:postalcode
>>> ?postalcode}. }
>>>
>>> When running the problematic query in the browser-frontend of my
>>> sparql-endpoint, I get the results as expected. Any idea, where the
>>> problem might be?
>>>
>>> Ciao,
>>> Frank
>>>
>>
>>
>
>
>--
>************************************************
>* Universität Leipzig, Institut für Informatik *
>* Abteilung Betriebliche Informationssysteme *
>* http://bis.informatik.uni-leipzig.de *
>* Tel.: 0341 / 97 32 256 *
>* *
>* ========== Opera Metal: molllust =========== *
>* http://www.molllust.com *
>* M'era Luna Newcomer 2013! *
>************************************************
>
>--------------------------------------------------------------------------
>----
>Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>with Interactivity, Sharing, Native Excel Exports, App Integration & more
>Get technology previously reserved for billion-dollar corporations, FREE
>http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clkt
>rk
>_______________________________________________
>dotNetRDF-Support mailing list
>dot...@li...
>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support
|
|
From: Frank S. <fs...@in...> - 2014-12-01 12:14:17
|
Hello again,
I narrowed it down a bit more, the error seems to happen, when the
endpoint is set to POST:
SparqlRemoteEndpoint endpoint = new SparqlRemoteEndpoint(new
Uri("http://creativeartefact.org/sparql"), "http://creativeartefact.org/");
endpoint.HttpMode = "POST";
SparqlResultSet sparqlResults = endpoint.QueryWithResultSet("PREFIX mbo:
<http://creativeartefact.org/ontology/> PREFIX rdfs:
<http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT * WHERE {?uri a
mbo:Organiser. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:city ?city}.
OPTIONAL {?uri mbo:street ?street}. OPTIONAL {?uri mbo:postalcode
?postalcode}. }");
SparqlResultSet sparqlResults = endpoint.QueryWithResultSet("SELECT *
WHERE {?uri ?label ?city.}");
The first statement executes, but the second throws the error. When
commenting out the line endpoint.HttpMode = "POST"; - also the second
one executes.
As my statements can get rather long, I need post to make sure the
SPARQL request doesn't exceed the allowed length for GET. Any idea, how
to solve this problem?
Thanks in advance,
Frank
#Am 28.11.2014 18:03, schrieb Frank Schumacher:
> I made some more tests and it is getting even stranger. I tried more
> test queries and even the simplest ones fail. For testing, I made two
> call. The first one works, the second raises the error. When I try to
> step into it with F11, it tells me:
>
> Aufruflistenort (callstackposition?):
> VDS.Common.dll!VDS.Common.Tries.AbstractTrie<string,char,System.Uri>.MoveToNode(string
> key) Zeile 211
>
> Here is the line that works:
> SparqlResultSet sparqlResults = args.Endpoint.QueryWithResultSet("PREFIX
> mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs:
> <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT * WHERE {?uri a
> mbo:Organiser. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:city ?city}.
> OPTIONAL {?uri mbo:street ?street}. OPTIONAL {?uri mbo:postalcode
> ?postalcode}. }");
>
> and here the one that raises the error:
> SparqlResultSet sparqlResults = args.Endpoint.QueryWithResultSet("SELECT
> * WHERE {?uri ?label ?city}");
>
> I'm really puzzled ...
>
> Ciao,
> Frank
>
> Am 28.11.2014 17:08, schrieb Frank Schumacher:
>> Hello Rob,
>>
>> I get a really strange UriFormatException (Ungültiger URI: Das
>> URI-Format konnte nicht bestimmt werden.) when calling
>> SparqlRemoteEndpoint.QueryWithResultSet with the following query:
>>
>> PREFIX mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs:
>> <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT ?uri ?label ?dis
>> ?ann WHERE {?uri a mbo:Artist. ?uri rdfs:label ?label. OPTIONAL {?uri
>> mbo:disambiguation ?dis}. OPTIONAL {?uri mbo:annotation ?ann}. }
>>
>> With a similar query, I don't get any error:
>>
>> PREFIX mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs:
>> <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT * WHERE {?uri a
>> mbo:Organiser. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:city ?city}.
>> OPTIONAL {?uri mbo:street ?street}. OPTIONAL {?uri mbo:postalcode
>> ?postalcode}. }
>>
>> When running the problematic query in the browser-frontend of my
>> sparql-endpoint, I get the results as expected. Any idea, where the
>> problem might be?
>>
>> Ciao,
>> Frank
>>
>
>
--
************************************************
* Universität Leipzig, Institut für Informatik *
* Abteilung Betriebliche Informationssysteme *
* http://bis.informatik.uni-leipzig.de *
* Tel.: 0341 / 97 32 256 *
* *
* ========== Opera Metal: molllust =========== *
* http://www.molllust.com *
* M'era Luna Newcomer 2013! *
************************************************
|
|
From: Frank S. <fs...@in...> - 2014-11-28 17:03:52
|
I made some more tests and it is getting even stranger. I tried more
test queries and even the simplest ones fail. For testing, I made two
call. The first one works, the second raises the error. When I try to
step into it with F11, it tells me:
Aufruflistenort (callstackposition?):
VDS.Common.dll!VDS.Common.Tries.AbstractTrie<string,char,System.Uri>.MoveToNode(string
key) Zeile 211
Here is the line that works:
SparqlResultSet sparqlResults = args.Endpoint.QueryWithResultSet("PREFIX
mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs:
<http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT * WHERE {?uri a
mbo:Organiser. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:city ?city}.
OPTIONAL {?uri mbo:street ?street}. OPTIONAL {?uri mbo:postalcode
?postalcode}. }");
and here the one that raises the error:
SparqlResultSet sparqlResults = args.Endpoint.QueryWithResultSet("SELECT
* WHERE {?uri ?label ?city}");
I'm really puzzled ...
Ciao,
Frank
Am 28.11.2014 17:08, schrieb Frank Schumacher:
> Hello Rob,
>
> I get a really strange UriFormatException (Ungültiger URI: Das
> URI-Format konnte nicht bestimmt werden.) when calling
> SparqlRemoteEndpoint.QueryWithResultSet with the following query:
>
> PREFIX mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs:
> <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT ?uri ?label ?dis
> ?ann WHERE {?uri a mbo:Artist. ?uri rdfs:label ?label. OPTIONAL {?uri
> mbo:disambiguation ?dis}. OPTIONAL {?uri mbo:annotation ?ann}. }
>
> With a similar query, I don't get any error:
>
> PREFIX mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs:
> <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT * WHERE {?uri a
> mbo:Organiser. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:city ?city}.
> OPTIONAL {?uri mbo:street ?street}. OPTIONAL {?uri mbo:postalcode
> ?postalcode}. }
>
> When running the problematic query in the browser-frontend of my
> sparql-endpoint, I get the results as expected. Any idea, where the
> problem might be?
>
> Ciao,
> Frank
>
--
************************************************
* Universität Leipzig, Institut für Informatik *
* Abteilung Betriebliche Informationssysteme *
* http://bis.informatik.uni-leipzig.de *
* Tel.: 0341 / 97 32 256 *
* *
* ========== Opera Metal: molllust =========== *
* http://www.molllust.com *
* M'era Luna Newcomer 2013! *
************************************************
|
|
From: Frank S. <fs...@in...> - 2014-11-28 16:08:56
|
Hello Rob, I get a really strange UriFormatException (Ungültiger URI: Das URI-Format konnte nicht bestimmt werden.) when calling SparqlRemoteEndpoint.QueryWithResultSet with the following query: PREFIX mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT ?uri ?label ?dis ?ann WHERE {?uri a mbo:Artist. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:disambiguation ?dis}. OPTIONAL {?uri mbo:annotation ?ann}. } With a similar query, I don't get any error: PREFIX mbo: <http://creativeartefact.org/ontology/> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> SELECT DISTINCT * WHERE {?uri a mbo:Organiser. ?uri rdfs:label ?label. OPTIONAL {?uri mbo:city ?city}. OPTIONAL {?uri mbo:street ?street}. OPTIONAL {?uri mbo:postalcode ?postalcode}. } When running the problematic query in the browser-frontend of my sparql-endpoint, I get the results as expected. Any idea, where the problem might be? Ciao, Frank -- ************************************************ * Universität Leipzig, Institut für Informatik * * Abteilung Betriebliche Informationssysteme * * http://bis.informatik.uni-leipzig.de * * Tel.: 0341 / 97 32 256 * * * * ========== Opera Metal: molllust =========== * * http://www.molllust.com * * M'era Luna Newcomer 2013! * ************************************************ |
|
From: Dr. I. P. C. <i.p...@ul...> - 2014-11-25 13:51:13
|
Hello, my name is Iván, I'm new to dtnetRDF and actually to .NET and C# technology itself. In a research project I started worked in, I would be required to develop a semantic framework based on dotnetRDF, in which the data (RDF triples) are downloaded from a BrightstarDB triplestore. Up now, I have reading some of the libraries documentation and the most similar approach I found to possibly doing this is by loading data from a SPARQL endpoint, i.e. by means of the SparqlRemoteEndpoint class, but I'm not completely sure if this would be the right or there would be a better way to do this with a different set of dotnetrdf classes. Could you please give me some more orientation this, before getting to implement some prototype of data loader, to make sure I'm going in the right way. Many thanks in advance, best regards. Iván -- *Iván Palomares Carrascosa* *Computer Science PhD* *Research Associate. School of Build Environment.* *University of Ulster, Jordanstown Campus, Room 16J25* Shore Road, Newtownabbey. BT37 0QB (Northern Ireland, UK) *Web:* *http://www.ulster.ac.uk/staff/i.palomares-carrascosa.html <http://www.ulster.ac.uk/staff/i.palomares-carrascosa.html>* *Phone*: +44 28 90368234 *E-mail*: i.p...@ul... |
|
From: Rob V. <rv...@do...> - 2014-11-25 10:43:45
|
Reading the Stardog support thread it sounds like we can just turn on Keep-Alive and keep using HTTP 1.1 Please go ahead and make the changes Rob From: Ron Michael Zettlemoyer <ro...@ze...> Reply-To: dotNetRDF User Help and Support <dot...@li...> Date: Thursday, 13 November 2014 16:22 To: dotNetRDF User Help and Support <dot...@li...> Subject: Re: [dotNetRDF-Support] "underlying connection was closed" errors when talking to Stardog > Thanks Rob. I have a message up on the Stardog forum to see if they have any > thoughts. I'll see what they say... > > > On Wed, Nov 12, 2014 at 4:32 AM, Rob Vesse <rv...@do...> wrote: >> Ron >> >> 1 - No idea why it would have changed, check with the Stardog folks to see if >> there have been any changes in their HTTP server implementation recently >> >> Particularly the fact that it tends to happen only with POSTs may imply some >> sort of issue on the server side. Have you tried reproducing this using the >> same queries that fail via CURL or another SPARQL API? >> >> 2 - Well it is a proxy so it is doing something with the requests and adds an >> additional connection hop to the pathway. Fiddler may be handling >> connections differently to .Net >> >> 3 - I'd prefer to see what the Stardog folks think before making these >> changes especially if there is a possibility of a bug in their server being >> the culprit. >> >> HTTP 1.0 is rather old now and there is a recent it is so infrequently used, >> one particular thing to be aware of is that it may not support more secure >> authentication mechanisms so you may be sending your Stardog credentials in >> clear text (or at best lightly encoded text) if you use HTTP 1.0 >> >> Rob >> >> From: Ron Michael Zettlemoyer <ro...@ze...> >> Reply-To: dotNetRDF User Help and Support >> <dot...@li...> >> Date: Wednesday, 12 November 2014 02:59 >> To: dotNetRDF User Help and Support >> <dot...@li...> >> Subject: [dotNetRDF-Support] "underlying connection was closed" errors when >> talking to Stardog >> >>> I've just recently started getting these weird "The underlying connection >>> was closed: A connection that was expected to be kept alive was closed by >>> the server" errors when talking to a Stardog database. Here are the >>> particulars: >>> * Mostly happens when the Stardog database is on a remote server - in this >>> case when I'm at home and querying a Windows 2012 server hosted at Azure. >>> When talking to the database locally from the same box (at Azure) it rarely >>> exhibits this behavior. >>> * Same thing happens if I query Stardog on a Linux server at Azure >>> * If I use a proxy between dotNetRDF and Stardog - like Fiddler - to examine >>> what's going on, it always works! But stop using the proxy and it fails. >>> Which makes it hard to diagnose. >>> * It only seems to fail when the SPARQL query is long and a POST is >>> necessary. GETs for query queries don't seem to fail. >>> After playing around and Googling for a while, I found this post >>> (http://stackoverflow.com/questions/13188058/httpwebrequest-the-underlying-c >>> onnection-was-closed) that suggested setting these options in the >>> WebRequest: >>> >>> request.KeepAlive = false; >>> request.ProtocolVersion = HttpVersion.Version10; >>> >>> I added this to the CreateRequest function in BaseStardogConnector and it >>> seems to have fixed the problem! >>> >>> So three questions: >>> >>> 1- Anyone have any ideas why this problem would seem to start for no reason, >>> after it'd been working fine for months? >>> >>> 2- Any idea why proxying through Fiddler would hide the problem? Shouldn't >>> it be passing the request straight through? >>> >>> 3- Is there any reason we shouldn't merge these changes into the codebase? >>> >>> >>> - Ron >>> >>> ---------------------------------------------------------------------------- >>> -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for >>> $9/Month. Get alerted through email, SMS, voice calls or mobile push >>> notifications. Take corrective actions from your mobile device. >>> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >>> _______________________________________________ dotNetRDF-Support mailing >>> list >>> dot...@li...https://lists.sourceforge.net/lists/l >>> istinfo/dotnetrdf-support >> >> ----------------------------------------------------------------------------->> - >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> _______________________________________________ >> dotNetRDF-Support mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support >> > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for > $9/Month. Get alerted through email, SMS, voice calls or mobile push > notifications. Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk__ > _____________________________________________ dotNetRDF-Support mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support |
|
From: Julien P. <jul...@re...> - 2014-11-24 13:34:04
|
Hi Rob, Here the normal query without the encoding problem : INSERT IN GRAPH <http://data.linkedevents.org/lastfm/> {< http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://www.w3.org/1999/02/22-rdf-syntax-ns#type> < http://xmlns.com/foaf/0.1/Agent> . <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://www.w3.org/2000/01/rdf-schema#label> "Flávio Vajman"@sk . <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://www.w3.org/2002/07/owl#sameAs> <http://www.last.fm> . <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://purl.org/dc/elements/1.1/publisher> <http://www.last.fm> . <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://purl.org/dc/elements/1.1/issued> "2014-10-20T14:24:10"^^< http://www.w3.org/2001/XMLSchema#dateTime> . } The query with the marker problem is how Virtuoso receive that query. Best. -- Julien Plu PhD Student at Eurecom. Personal webpage: http://jplu.developpez.com FOAF file : http://jplu.developpez.com/julien Email address : jul...@eu... && *plu...@gm... <plu...@gm...>* Phone : +33493008103 Twitter : @julienplu 2014-11-24 11:08 GMT+01:00 Rob Vesse <rv...@do...>: > Julien > > Tried to look at this last week but didn't get anywhere. Strangely your > email is UTF-8 encoded but your pasted query displays some unknown > character markers which implies something is screwed up in the encoding (of > at least your email) and possibly your original query. > > Can you post the query again as a paste bin/gist somewhere? > > Rob > > From: Julien Plu <plu...@gm...> > Reply-To: dotNetRDF User Help and Support < > dot...@li...> > Date: Thursday, 23 October 2014 14:57 > To: dotNetRDF User Help and Support < > dot...@li...> > Subject: Re: [dotNetRDF-Support] Problem with SPARQL INSERT query > > After few more tests, I confirm it's an encoding problem, but I don't know > if it comes from Virtuoso or from dotnetRDF or both. > > -- > Julien Plu > > PhD Student at Eurecom. > Personal webpage: http://jplu.developpez.com > FOAF file : http://jplu.developpez.com/julien > Email address : jul...@eu... && *plu...@gm... > <plu...@gm...>* > Phone : +33493008103 > Twitter : @julienplu > > 2014-10-23 13:56 GMT+02:00 Julien Plu <plu...@gm...>: > >> Hi Rob, >> >> Thanks for your answer. I understand it can be complicated to debug, but >> I investigated a bit and I suspect an encoding issue, I continue my >> investigation and I will let you know if I find something. >> >> Best. >> >> -- >> Julien Plu >> >> PhD Student at Eurecom. >> Personal webpage: http://jplu.developpez.com >> FOAF file : http://jplu.developpez.com/julien >> Email address : jul...@eu... && *plu...@gm... >> <plu...@gm...>* >> Phone : +33493008103 >> Twitter : @julienplu >> >> 2014-10-23 12:26 GMT+02:00 Rob Vesse <rv...@do...>: >> >>> Julian >>> >>> That could be a bug in either but it is hard to tell without debugging >>> which I haven't had chance to do yet (I just moved house and don't have my >>> full dev setup back up yet) >>> >>> The error messages comes from the Virtuoso layer but it could be caused >>> by dotNetRDF feeding it bad data in the first place so at a glance it is >>> unclear where the problem lies. >>> >>> Rob >>> >>> From: Julien Plu <plu...@gm...> >>> Reply-To: dotNetRDF User Help and Support < >>> dot...@li...> >>> Date: Monday, 20 October 2014 13:47 >>> To: <dot...@li...> >>> Subject: [dotNetRDF-Support] Problem with SPARQL INSERT query >>> >>> Hi all, >>> >>> Each that I try to make a SPARQL INSERT through my dotnet application I >>> have this error : >>> >>> Error : 20/10/2014 14:24:10 : Error on SPARQL insert | INSERT IN GRAPH >>> <http://data.linkedevents.org/lastfm/> {< >>> http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> < >>> http://xmlns.com/foaf/0.1/Agent> . >>> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>> <http://www.w3.org/2000/01/rdf-schema#label> "Fl��vio Vajman"@sk . >>> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>> <http://www.w3.org/2002/07/owl#sameAs> <http://www.last.fm> . >>> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>> <http://purl.org/dc/elements/1.1/publisher> <http://www.last.fm> . >>> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>> <http://purl.org/dc/elements/1.1/issued> "2014-10-20T14:24:10"^^< >>> http://www.w3.org/2001/XMLSchema#dateTime> . >>> } >>> Virtuoso Error: SQL_ERROR >>> SQLSTATE: RDFXX >>> Message: [Virtuoso .NET Data Provider][Virtuoso Server]Language is >>> specified for typed literal in DB.DBA.RDF_MAKE_LONG_OF_TYPEDSQLVAL() >>> >>> But if I execute the query directly into the isql-v command prompt of >>> Virtuoso there is no problem. So I'm asking me if it come from Virtuoso or >>> from dotnetRDF lib. >>> >>> I execute my application with mono 3.2.3 on a Fedora OS and my Virtuos >>> is the 7.1 stable. The application works without any problem on Windows 7 >>> with the same version of Virtuoso and mono. The version of dotnetRDF is >>> 1.0.6 with dotnet framework 4.0. >>> >>> Thanks in advance. >>> >>> -- >>> Julien Plu >>> >>> PhD Student at Eurecom. >>> Personal webpage: http://jplu.developpez.com >>> FOAF file : http://jplu.developpez.com/julien >>> Email address : jul...@eu... && *plu...@gm... >>> <plu...@gm...>* >>> Phone : +33493008103 >>> Twitter : @julienplu >>> ------------------------------------------------------------------------------ >>> Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for >>> $9/Month. Get alerted through email, SMS, voice calls or mobile push >>> notifications. Take corrective actions from your mobile device. >>> http://p.sf.net/sfu/Zoho_______________________________________________ >>> dotNetRDF-Support mailing list dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> dotNetRDF-Support mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support >>> >>> >> > ------------------------------------------------------------------------------ > _______________________________________________ dotNetRDF-Support mailing > list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support > > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-Support mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support > > |
|
From: Rob V. <rv...@do...> - 2014-11-24 10:08:55
|
Julien Tried to look at this last week but didn't get anywhere. Strangely your email is UTF-8 encoded but your pasted query displays some unknown character markers which implies something is screwed up in the encoding (of at least your email) and possibly your original query. Can you post the query again as a paste bin/gist somewhere? Rob From: Julien Plu <plu...@gm...> Reply-To: dotNetRDF User Help and Support <dot...@li...> Date: Thursday, 23 October 2014 14:57 To: dotNetRDF User Help and Support <dot...@li...> Subject: Re: [dotNetRDF-Support] Problem with SPARQL INSERT query > After few more tests, I confirm it's an encoding problem, but I don't know if > it comes from Virtuoso or from dotnetRDF or both. > > -- > Julien Plu > > PhD Student at Eurecom. > Personal webpage: http://jplu.developpez.com <http://jplu.developpez.com/> > FOAF file : http://jplu.developpez.com/julien > Email address : jul...@eu... && plu...@gm... > Phone : +33493008103 > Twitter : @julienplu > > 2014-10-23 13:56 GMT+02:00 Julien Plu <plu...@gm...>: >> Hi Rob, >> >> Thanks for your answer. I understand it can be complicated to debug, but I >> investigated a bit and I suspect an encoding issue, I continue my >> investigation and I will let you know if I find something. >> >> Best. >> >> -- >> Julien Plu >> >> PhD Student at Eurecom. >> Personal webpage: http://jplu.developpez.com <http://jplu.developpez.com/> >> FOAF file : http://jplu.developpez.com/julien >> Email address : jul...@eu... && plu...@gm... >> Phone : +33493008103 <tel:%2B33493008103> >> Twitter : @julienplu >> >> 2014-10-23 12:26 GMT+02:00 Rob Vesse <rv...@do...>: >>> Julian >>> >>> That could be a bug in either but it is hard to tell without debugging which >>> I haven't had chance to do yet (I just moved house and don't have my full >>> dev setup back up yet) >>> >>> The error messages comes from the Virtuoso layer but it could be caused by >>> dotNetRDF feeding it bad data in the first place so at a glance it is >>> unclear where the problem lies. >>> >>> Rob >>> >>> From: Julien Plu <plu...@gm...> >>> Reply-To: dotNetRDF User Help and Support >>> <dot...@li...> >>> Date: Monday, 20 October 2014 13:47 >>> To: <dot...@li...> >>> Subject: [dotNetRDF-Support] Problem with SPARQL INSERT query >>> >>>> Hi all, >>>> >>>> Each that I try to make a SPARQL INSERT through my dotnet application I >>>> have this error : >>>> >>>> Error : 20/10/2014 14:24:10 : Error on SPARQL insert | INSERT IN GRAPH >>>> <http://data.linkedevents.org/lastfm/> >>>> {<http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> >>>> <http://xmlns.com/foaf/0.1/Agent> . >>>> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>>> <http://www.w3.org/2000/01/rdf-schema#label> "Fl��vio Vajman"@sk . >>>> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>>> <http://www.w3.org/2002/07/owl#sameAs> <http://www.last.fm >>>> <http://www.last.fm/> > . >>>> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>>> <http://purl.org/dc/elements/1.1/publisher> <http://www.last.fm >>>> <http://www.last.fm/> > . >>>> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >>>> <http://purl.org/dc/elements/1.1/issued> >>>> "2014-10-20T14:24:10"^^<http://www.w3.org/2001/XMLSchema#dateTime> . >>>> } >>>> Virtuoso Error: SQL_ERROR >>>> SQLSTATE: RDFXX >>>> Message: [Virtuoso .NET Data Provider][Virtuoso Server]Language is >>>> specified for typed literal in DB.DBA.RDF_MAKE_LONG_OF_TYPEDSQLVAL() >>>> >>>> But if I execute the query directly into the isql-v command prompt of >>>> Virtuoso there is no problem. So I'm asking me if it come from Virtuoso or >>>> from dotnetRDF lib. >>>> >>>> I execute my application with mono 3.2.3 on a Fedora OS and my Virtuos is >>>> the 7.1 stable. The application works without any problem on Windows 7 with >>>> the same version of Virtuoso and mono. The version of dotnetRDF is 1.0.6 >>>> with dotnet framework 4.0. >>>> >>>> Thanks in advance. >>>> >>>> -- >>>> Julien Plu >>>> >>>> PhD Student at Eurecom. >>>> Personal webpage: http://jplu.developpez.com <http://jplu.developpez.com/> >>>> FOAF file : http://jplu.developpez.com/julien >>>> Email address : jul...@eu... && plu...@gm... >>>> Phone : +33493008103 <tel:%2B33493008103> >>>> Twitter : @julienplu >>>> --------------------------------------------------------------------------- >>>> --- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for >>>> $9/Month. Get alerted through email, SMS, voice calls or mobile push >>>> notifications. Take corrective actions from your mobile device. >>>> http://p.sf.net/sfu/Zoho_______________________________________________ >>>> dotNetRDF-Support mailing list >>>> dot...@li...https://lists.sourceforge.net/lists/ >>>> listinfo/dotnetrdf-support >>> >>> ---------------------------------------------------------------------------- >>> -- >>> >>> _______________________________________________ >>> dotNetRDF-Support mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support >>> >> > > ------------------------------------------------------------------------------ > _______________________________________________ dotNetRDF-Support mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support |
|
From: Ron M. Z. <ro...@ze...> - 2014-11-13 16:48:45
|
Thanks Rob. I have a message up on the Stardog forum to see if they have any thoughts. I'll see what they say... On Wed, Nov 12, 2014 at 4:32 AM, Rob Vesse <rv...@do...> wrote: > Ron > > 1 - No idea why it would have changed, check with the Stardog folks to see > if there have been any changes in their HTTP server implementation recently > > Particularly the fact that it tends to happen only with POSTs may imply > some sort of issue on the server side. Have you tried reproducing this > using the same queries that fail via CURL or another SPARQL API? > > 2 - Well it is a proxy so it is doing something with the requests and adds > an additional connection hop to the pathway. Fiddler may be handling > connections differently to .Net > > 3 - I'd prefer to see what the Stardog folks think before making these > changes especially if there is a possibility of a bug in their server being > the culprit. > > HTTP 1.0 is rather old now and there is a recent it is so infrequently > used, one particular thing to be aware of is that it may not support more > secure authentication mechanisms so you may be sending your Stardog > credentials in clear text (or at best lightly encoded text) if you use HTTP > 1.0 > > Rob > > From: Ron Michael Zettlemoyer <ro...@ze...> > Reply-To: dotNetRDF User Help and Support < > dot...@li...> > Date: Wednesday, 12 November 2014 02:59 > To: dotNetRDF User Help and Support < > dot...@li...> > Subject: [dotNetRDF-Support] "underlying connection was closed" errors > when talking to Stardog > > I've just recently started getting these weird "The underlying connection > was closed: A connection that was expected to be kept alive was closed by > the server" errors when talking to a Stardog database. Here are the > particulars: > > - Mostly happens when the Stardog database is on a remote server - in > this case when I'm at home and querying a Windows 2012 server hosted at > Azure. When talking to the database locally from the same box (at Azure) it > rarely exhibits this behavior. > - Same thing happens if I query Stardog on a Linux server at Azure > - If I use a proxy between dotNetRDF and Stardog - like Fiddler - to > examine what's going on, it always works! But stop using the proxy and it > fails. Which makes it hard to diagnose. > - It only seems to fail when the SPARQL query is long and a POST is > necessary. GETs for query queries don't seem to fail. > > After playing around and Googling for a while, I found this post ( > http://stackoverflow.com/questions/13188058/httpwebrequest-the-underlying-connection-was-closed) > that suggested setting these options in the WebRequest: > > request.KeepAlive = false; > request.ProtocolVersion = HttpVersion.Version10; > > I added this to the CreateRequest function in BaseStardogConnector and it > seems to have fixed the problem! > > So three questions: > > 1- Anyone have any ideas why this problem would seem to start for no > reason, after it'd been working fine for months? > > 2- Any idea why proxying through Fiddler would hide the problem? Shouldn't > it be passing the request straight through? > > 3- Is there any reason we shouldn't merge these changes into the codebase? > > > - Ron > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for > $9/Month. Get alerted through email, SMS, voice calls or mobile push > notifications. Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk_______________________________________________ > dotNetRDF-Support mailing list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-Support mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support > > |
|
From: Rob V. <rv...@do...> - 2014-11-12 09:33:52
|
Ron 1 - No idea why it would have changed, check with the Stardog folks to see if there have been any changes in their HTTP server implementation recently Particularly the fact that it tends to happen only with POSTs may imply some sort of issue on the server side. Have you tried reproducing this using the same queries that fail via CURL or another SPARQL API? 2 - Well it is a proxy so it is doing something with the requests and adds an additional connection hop to the pathway. Fiddler may be handling connections differently to .Net 3 - I'd prefer to see what the Stardog folks think before making these changes especially if there is a possibility of a bug in their server being the culprit. HTTP 1.0 is rather old now and there is a recent it is so infrequently used, one particular thing to be aware of is that it may not support more secure authentication mechanisms so you may be sending your Stardog credentials in clear text (or at best lightly encoded text) if you use HTTP 1.0 Rob From: Ron Michael Zettlemoyer <ro...@ze...> Reply-To: dotNetRDF User Help and Support <dot...@li...> Date: Wednesday, 12 November 2014 02:59 To: dotNetRDF User Help and Support <dot...@li...> Subject: [dotNetRDF-Support] "underlying connection was closed" errors when talking to Stardog > I've just recently started getting these weird "The underlying connection was > closed: A connection that was expected to be kept alive was closed by the > server" errors when talking to a Stardog database. Here are the particulars: > * Mostly happens when the Stardog database is on a remote server - in this > case when I'm at home and querying a Windows 2012 server hosted at Azure. When > talking to the database locally from the same box (at Azure) it rarely > exhibits this behavior. > * Same thing happens if I query Stardog on a Linux server at Azure > * If I use a proxy between dotNetRDF and Stardog - like Fiddler - to examine > what's going on, it always works! But stop using the proxy and it fails. Which > makes it hard to diagnose. > * It only seems to fail when the SPARQL query is long and a POST is necessary. > GETs for query queries don't seem to fail. > After playing around and Googling for a while, I found this post > (http://stackoverflow.com/questions/13188058/httpwebrequest-the-underlying-con > nection-was-closed) that suggested setting these options in the WebRequest: > > request.KeepAlive = false; > request.ProtocolVersion = HttpVersion.Version10; > > I added this to the CreateRequest function in BaseStardogConnector and it > seems to have fixed the problem! > > So three questions: > > 1- Anyone have any ideas why this problem would seem to start for no reason, > after it'd been working fine for months? > > 2- Any idea why proxying through Fiddler would hide the problem? Shouldn't it > be passing the request straight through? > > 3- Is there any reason we shouldn't merge these changes into the codebase? > > > - Ron > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for > $9/Month. Get alerted through email, SMS, voice calls or mobile push > notifications. Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk__ > _____________________________________________ dotNetRDF-Support mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support |
|
From: Ron M. Z. <ro...@ze...> - 2014-11-12 03:52:51
|
I've just recently started getting these weird "The underlying connection was closed: A connection that was expected to be kept alive was closed by the server" errors when talking to a Stardog database. Here are the particulars: - Mostly happens when the Stardog database is on a remote server - in this case when I'm at home and querying a Windows 2012 server hosted at Azure. When talking to the database locally from the same box (at Azure) it rarely exhibits this behavior. - Same thing happens if I query Stardog on a Linux server at Azure - If I use a proxy between dotNetRDF and Stardog - like Fiddler - to examine what's going on, it always works! But stop using the proxy and it fails. Which makes it hard to diagnose. - It only seems to fail when the SPARQL query is long and a POST is necessary. GETs for query queries don't seem to fail. After playing around and Googling for a while, I found this post ( http://stackoverflow.com/questions/13188058/httpwebrequest-the-underlying-connection-was-closed) that suggested setting these options in the WebRequest: request.KeepAlive = false; request.ProtocolVersion = HttpVersion.Version10; I added this to the CreateRequest function in BaseStardogConnector and it seems to have fixed the problem! So three questions: 1- Anyone have any ideas why this problem would seem to start for no reason, after it'd been working fine for months? 2- Any idea why proxying through Fiddler would hide the problem? Shouldn't it be passing the request straight through? 3- Is there any reason we shouldn't merge these changes into the codebase? - Ron |
|
From: Zahra J. <jab...@gm...> - 2014-10-29 19:08:29
|
Hi, I have done same as your project, I explaines an human activity ontology in protege and used its owl file in c#, you should import owl file that its format is same as xml,after that you should read that file line by line and extract its properties,individuals,classes and their relationships by reading their tag with some functions. be succeed On Fri, Oct 24, 2014 at 1:46 AM, <c.c...@gm...> wrote: > Hy, > I´m Carmelo Cacciato. I´m working in a project C# and i would like to open > an ontology with dotNetRDF . I´m not able with documentation > My Scope is writing in a Owl ontology individuals in a speciefied class > or subclasses and also create a property between two individuals in c# > (ObjectProperty of Protege). > I hope someone can help me. > Thanks for all support. > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > dotNetRDF-Support mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support > > |
|
From: <c.c...@gm...> - 2014-10-24 09:51:45
|
Hy, I would like open an ontology written in owl . i Need to modify it in C# i need to identify an object property and assiate i t to two individual one as domain ad one as range but it is very difficult to find a method . is there someone can help me? |
|
From: <c.c...@gm...> - 2014-10-24 08:46:21
|
Hy, I´m Carmelo Cacciato. I´m working in a project C# and i would like to open an ontology with dotNetRDF . I´m not able with documentation My Scope is writing in a Owl ontology individuals in a speciefied class or subclasses and also create a property between two individuals in c# (ObjectProperty of Protege). I hope someone can help me. Thanks for all support. |
|
From: Julien P. <plu...@gm...> - 2014-10-23 14:58:23
|
After few more tests, I confirm it's an encoding problem, but I don't know if it comes from Virtuoso or from dotnetRDF or both. -- Julien Plu PhD Student at Eurecom. Personal webpage: http://jplu.developpez.com FOAF file : http://jplu.developpez.com/julien Email address : jul...@eu... && *plu...@gm... <plu...@gm...>* Phone : +33493008103 Twitter : @julienplu 2014-10-23 13:56 GMT+02:00 Julien Plu <plu...@gm...>: > Hi Rob, > > Thanks for your answer. I understand it can be complicated to debug, but I > investigated a bit and I suspect an encoding issue, I continue my > investigation and I will let you know if I find something. > > Best. > > -- > Julien Plu > > PhD Student at Eurecom. > Personal webpage: http://jplu.developpez.com > FOAF file : http://jplu.developpez.com/julien > Email address : jul...@eu... && *plu...@gm... > <plu...@gm...>* > Phone : +33493008103 > Twitter : @julienplu > > 2014-10-23 12:26 GMT+02:00 Rob Vesse <rv...@do...>: > >> Julian >> >> That could be a bug in either but it is hard to tell without debugging >> which I haven't had chance to do yet (I just moved house and don't have my >> full dev setup back up yet) >> >> The error messages comes from the Virtuoso layer but it could be caused >> by dotNetRDF feeding it bad data in the first place so at a glance it is >> unclear where the problem lies. >> >> Rob >> >> From: Julien Plu <plu...@gm...> >> Reply-To: dotNetRDF User Help and Support < >> dot...@li...> >> Date: Monday, 20 October 2014 13:47 >> To: <dot...@li...> >> Subject: [dotNetRDF-Support] Problem with SPARQL INSERT query >> >> Hi all, >> >> Each that I try to make a SPARQL INSERT through my dotnet application I >> have this error : >> >> Error : 20/10/2014 14:24:10 : Error on SPARQL insert | INSERT IN GRAPH < >> http://data.linkedevents.org/lastfm/> {< >> http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> < >> http://xmlns.com/foaf/0.1/Agent> . >> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >> <http://www.w3.org/2000/01/rdf-schema#label> "Fl��vio Vajman"@sk . >> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >> <http://www.w3.org/2002/07/owl#sameAs> <http://www.last.fm> . >> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >> <http://purl.org/dc/elements/1.1/publisher> <http://www.last.fm> . >> <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> >> <http://purl.org/dc/elements/1.1/issued> "2014-10-20T14:24:10"^^< >> http://www.w3.org/2001/XMLSchema#dateTime> . >> } >> Virtuoso Error: SQL_ERROR >> SQLSTATE: RDFXX >> Message: [Virtuoso .NET Data Provider][Virtuoso Server]Language is >> specified for typed literal in DB.DBA.RDF_MAKE_LONG_OF_TYPEDSQLVAL() >> >> But if I execute the query directly into the isql-v command prompt of >> Virtuoso there is no problem. So I'm asking me if it come from Virtuoso or >> from dotnetRDF lib. >> >> I execute my application with mono 3.2.3 on a Fedora OS and my Virtuos is >> the 7.1 stable. The application works without any problem on Windows 7 with >> the same version of Virtuoso and mono. The version of dotnetRDF is 1.0.6 >> with dotnet framework 4.0. >> >> Thanks in advance. >> >> -- >> Julien Plu >> >> PhD Student at Eurecom. >> Personal webpage: http://jplu.developpez.com >> FOAF file : http://jplu.developpez.com/julien >> Email address : jul...@eu... && *plu...@gm... >> <plu...@gm...>* >> Phone : +33493008103 >> Twitter : @julienplu >> ------------------------------------------------------------------------------ >> Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for >> $9/Month. Get alerted through email, SMS, voice calls or mobile push >> notifications. Take corrective actions from your mobile device. >> http://p.sf.net/sfu/Zoho_______________________________________________ >> dotNetRDF-Support mailing list dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> dotNetRDF-Support mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support >> >> > |
|
From: Julien P. <plu...@gm...> - 2014-10-23 11:57:10
|
Hi Rob, Thanks for your answer. I understand it can be complicated to debug, but I investigated a bit and I suspect an encoding issue, I continue my investigation and I will let you know if I find something. Best. -- Julien Plu PhD Student at Eurecom. Personal webpage: http://jplu.developpez.com FOAF file : http://jplu.developpez.com/julien Email address : jul...@eu... && *plu...@gm... <plu...@gm...>* Phone : +33493008103 Twitter : @julienplu 2014-10-23 12:26 GMT+02:00 Rob Vesse <rv...@do...>: > Julian > > That could be a bug in either but it is hard to tell without debugging > which I haven't had chance to do yet (I just moved house and don't have my > full dev setup back up yet) > > The error messages comes from the Virtuoso layer but it could be caused by > dotNetRDF feeding it bad data in the first place so at a glance it is > unclear where the problem lies. > > Rob > > From: Julien Plu <plu...@gm...> > Reply-To: dotNetRDF User Help and Support < > dot...@li...> > Date: Monday, 20 October 2014 13:47 > To: <dot...@li...> > Subject: [dotNetRDF-Support] Problem with SPARQL INSERT query > > Hi all, > > Each that I try to make a SPARQL INSERT through my dotnet application I > have this error : > > Error : 20/10/2014 14:24:10 : Error on SPARQL insert | INSERT IN GRAPH < > http://data.linkedevents.org/lastfm/> {< > http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> < > http://xmlns.com/foaf/0.1/Agent> . > <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://www.w3.org/2000/01/rdf-schema#label> "Fl��vio Vajman"@sk . > <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://www.w3.org/2002/07/owl#sameAs> <http://www.last.fm> . > <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://purl.org/dc/elements/1.1/publisher> <http://www.last.fm> . > <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://purl.org/dc/elements/1.1/issued> "2014-10-20T14:24:10"^^< > http://www.w3.org/2001/XMLSchema#dateTime> . > } > Virtuoso Error: SQL_ERROR > SQLSTATE: RDFXX > Message: [Virtuoso .NET Data Provider][Virtuoso Server]Language is > specified for typed literal in DB.DBA.RDF_MAKE_LONG_OF_TYPEDSQLVAL() > > But if I execute the query directly into the isql-v command prompt of > Virtuoso there is no problem. So I'm asking me if it come from Virtuoso or > from dotnetRDF lib. > > I execute my application with mono 3.2.3 on a Fedora OS and my Virtuos is > the 7.1 stable. The application works without any problem on Windows 7 with > the same version of Virtuoso and mono. The version of dotnetRDF is 1.0.6 > with dotnet framework 4.0. > > Thanks in advance. > > -- > Julien Plu > > PhD Student at Eurecom. > Personal webpage: http://jplu.developpez.com > FOAF file : http://jplu.developpez.com/julien > Email address : jul...@eu... && *plu...@gm... > <plu...@gm...>* > Phone : +33493008103 > Twitter : @julienplu > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for > $9/Month. Get alerted through email, SMS, voice calls or mobile push > notifications. Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho_______________________________________________ > dotNetRDF-Support mailing list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > dotNetRDF-Support mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support > > |
|
From: Rob V. <rv...@do...> - 2014-10-23 10:42:12
|
Julian That could be a bug in either but it is hard to tell without debugging which I haven't had chance to do yet (I just moved house and don't have my full dev setup back up yet) The error messages comes from the Virtuoso layer but it could be caused by dotNetRDF feeding it bad data in the first place so at a glance it is unclear where the problem lies. Rob From: Julien Plu <plu...@gm...> Reply-To: dotNetRDF User Help and Support <dot...@li...> Date: Monday, 20 October 2014 13:47 To: <dot...@li...> Subject: [dotNetRDF-Support] Problem with SPARQL INSERT query > Hi all, > > Each that I try to make a SPARQL INSERT through my dotnet application I have > this error : > > Error : 20/10/2014 14:24:10 : Error on SPARQL insert | INSERT IN GRAPH > <http://data.linkedevents.org/lastfm/> > {<http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> > <http://xmlns.com/foaf/0.1/Agent> . > <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://www.w3.org/2000/01/rdf-schema#label> "Fl��vio Vajman"@sk . > <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://www.w3.org/2002/07/owl#sameAs> <http://www.last.fm > <http://www.last.fm/> > . > <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://purl.org/dc/elements/1.1/publisher> <http://www.last.fm > <http://www.last.fm/> > . > <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> > <http://purl.org/dc/elements/1.1/issued> > "2014-10-20T14:24:10"^^<http://www.w3.org/2001/XMLSchema#dateTime> . > } > Virtuoso Error: SQL_ERROR > SQLSTATE: RDFXX > Message: [Virtuoso .NET Data Provider][Virtuoso Server]Language is specified > for typed literal in DB.DBA.RDF_MAKE_LONG_OF_TYPEDSQLVAL() > > But if I execute the query directly into the isql-v command prompt of Virtuoso > there is no problem. So I'm asking me if it come from Virtuoso or from > dotnetRDF lib. > > I execute my application with mono 3.2.3 on a Fedora OS and my Virtuos is the > 7.1 stable. The application works without any problem on Windows 7 with the > same version of Virtuoso and mono. The version of dotnetRDF is 1.0.6 with > dotnet framework 4.0. > > Thanks in advance. > > -- > Julien Plu > > PhD Student at Eurecom. > Personal webpage: http://jplu.developpez.com <http://jplu.developpez.com/> > FOAF file : http://jplu.developpez.com/julien > Email address : jul...@eu... && plu...@gm... > Phone : +33493008103 > Twitter : @julienplu > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for > $9/Month. Get alerted through email, SMS, voice calls or mobile push > notifications. Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho_______________________________________________ > dotNetRDF-Support mailing list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support |
|
From: Julien P. <plu...@gm...> - 2014-10-20 12:47:41
|
Hi all, Each that I try to make a SPARQL INSERT through my dotnet application I have this error : Error : 20/10/2014 14:24:10 : Error on SPARQL insert | INSERT IN GRAPH < http://data.linkedevents.org/lastfm/> {< http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://www.w3.org/1999/02/22-rdf-syntax-ns#type> < http://xmlns.com/foaf/0.1/Agent> . <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://www.w3.org/2000/01/rdf-schema#label> "Fl��vio Vajman"@sk . <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://www.w3.org/2002/07/owl#sameAs> <http://www.last.fm> . <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://purl.org/dc/elements/1.1/publisher> <http://www.last.fm> . <http://data.linkedevents.org/agent/60f13cb8-004f-498d-9e8e-0c5b6331c92d> < http://purl.org/dc/elements/1.1/issued> "2014-10-20T14:24:10"^^< http://www.w3.org/2001/XMLSchema#dateTime> . } Virtuoso Error: SQL_ERROR SQLSTATE: RDFXX Message: [Virtuoso .NET Data Provider][Virtuoso Server]Language is specified for typed literal in DB.DBA.RDF_MAKE_LONG_OF_TYPEDSQLVAL() But if I execute the query directly into the isql-v command prompt of Virtuoso there is no problem. So I'm asking me if it come from Virtuoso or from dotnetRDF lib. I execute my application with mono 3.2.3 on a Fedora OS and my Virtuos is the 7.1 stable. The application works without any problem on Windows 7 with the same version of Virtuoso and mono. The version of dotnetRDF is 1.0.6 with dotnet framework 4.0. Thanks in advance. -- Julien Plu PhD Student at Eurecom. Personal webpage: http://jplu.developpez.com FOAF file : http://jplu.developpez.com/julien Email address : jul...@eu... && *plu...@gm... <plu...@gm...>* Phone : +33493008103 Twitter : @julienplu |
|
From: Rob V. <rv...@do...> - 2014-09-30 11:16:51
|
Frank
Nodes are by design immutable objects
To change the subject/predicate/object of a triple you need to retract the
original triple and assert a replacement triple e.g.
INode newSubject = g.CreateUriNode(new Uri("http://new-uri.com"));
foreach (INode item in g.Triples.SubjectNodes.ToList())
{
if (item.NodeType != NodeType.Uri) continue;
List<Triple> ts = g.GetTriplesWithSubject(item).ToList();
foreach (Triple t in ts)
{
g.Retract(t);
g.Assert(newSubject, t.Predicate, t.Object);
}
}
Note that it is necessary to use ToList() as otherwise you will get
concurrent modification exceptions
Alternatively you may be better off using a SPARQL Update if you are
ultimately transforming the stored data e.g.
DELETE
{
<http://old-uri.com> ?p ?o .
}
INSERT
{
<http://new-uri.com> ?p ?o .
}
WHERE
{
<http://old-uri.com> ?p ?o .
}
Regards,
Rob
On 25/09/2014 14:52, "Frank Schumacher" <fs...@in...>
wrote:
>Hello,
>
>I want to write a programm that adds triples from a ttl-file to a
>virtuoso store. I load them with:
>
>IGraph g = new Graph();
>FileLoader.Load(g, @"filename");
>
>Before I add a triple, I want to check, wheter the element already
>exists in the virtuoso store (via
>http://www.w3.org/1999/02/22-rdf-syntax-ns#type and
>http://www.w3.org/2000/01/rdf-schema#label). If it exists, I want to
>replace the URI from the file with the URI from the virtuoso store.
>Unfortunately, I cannot rename an URI like
>
>foreach (INode item in g.Triples.SubjectNodes)
> ((IUriNode)item).Uri = "newURI";
>
>Any idea how I can achieve this?
>
>Greetings,
>Frank
>--
>************************************************
>* Universität Leipzig, Institut für Informatik *
>* Abteilung Betriebliche Informationssysteme *
>* http://bis.informatik.uni-leipzig.de *
>* Tel.: 0341 / 97 32 256 *
>* *
>* ========== Opera Metal: molllust =========== *
>* http://www.molllust.com *
>* M'era Luna Newcomer 2013! *
>************************************************
>
>--------------------------------------------------------------------------
>----
>Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clkt
>rk
>_______________________________________________
>dotNetRDF-Support mailing list
>dot...@li...
>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support
|
|
From: Frank S. <fs...@in...> - 2014-09-25 13:52:55
|
Hello, I want to write a programm that adds triples from a ttl-file to a virtuoso store. I load them with: IGraph g = new Graph(); FileLoader.Load(g, @"filename"); Before I add a triple, I want to check, wheter the element already exists in the virtuoso store (via http://www.w3.org/1999/02/22-rdf-syntax-ns#type and http://www.w3.org/2000/01/rdf-schema#label). If it exists, I want to replace the URI from the file with the URI from the virtuoso store. Unfortunately, I cannot rename an URI like foreach (INode item in g.Triples.SubjectNodes) ((IUriNode)item).Uri = "newURI"; Any idea how I can achieve this? Greetings, Frank -- ************************************************ * Universität Leipzig, Institut für Informatik * * Abteilung Betriebliche Informationssysteme * * http://bis.informatik.uni-leipzig.de * * Tel.: 0341 / 97 32 256 * * * * ========== Opera Metal: molllust =========== * * http://www.molllust.com * * M'era Luna Newcomer 2013! * ************************************************ |
|
From: Chad C. <ch...@bs...> - 2014-09-19 14:10:20
|
Thanks Rob. I really appreciate the help. I'll continue working on this now that I have a better understanding of using blank nodes. Chad From: Rob Vesse [mailto:rv...@do...] Sent: Friday, September 19, 2014 5:09 AM To: dotNetRDF User Help and Support Subject: Re: [dotNetRDF-Support] Creating nested RDF/xml Chad Firstly sorry for taking so long to get back to you. The complication here is that your RDF/XML fragment is using a compression technique called striping (http://www.w3.org/TR/rdf-syntax-grammar/#example1) so not everything you see is a blank node: <bf:publication> Property <bf:Provider> Blank Node <bf:providerName> Property <bf:Organization> Blank Node <bf:label>Unwin Hyman</bf:label> Property with Literal Object </bf:Organization> </bf:providerName> <bf:providerPlace> Property <bf:Place> Blank Node <bf:label>London</bf:label> Property with Literal Object </bf:Place> </bf:providerPlace> <bf:providerDate>1987 ;</bf:providerDate> Property with Literal Object </bf:Provider> </bf:publication> The yellow annotations serve to illustrate which is which, generally a well designed ontology will use lowercase local names for properties and uppercase local names for types which usually makes it easy to distinguish which is which Your fragment here is incomplete because it starts with a property and it is unclear from your code what the root node is but I'll assume it is in the variable root for the purposes of the example INode pubProperty = g.CreateUriNode("bf:publication"); INode providerNode = g.CreateBlankNode(); INode providerType = g.CreateUriNode("bf:Provider"); g.Assert(root, pubProperty, providerNode); g.Assert(providerNode, rdfType, providerType); INode provNameProperty = g.CreateUriNode("bf:providerName"); INode orgNode = g.CreateBlankNode(); INode orgType = g.CreateUriNode("bf:Organization"); g.Assert(providerNode, provNameProperty, orgNode); g.Assert(orgNode, rdfType, orgType); INode labelProperty = g.CreateUriNode("bf:label"); INode labelValue = g.CreateLiteralNode("Unwin Hyman"); g.Assert(orgNode, labelProperty, labelValue); The above example creates just the first portion of your fragment but should hopefully point you in the right direction. Hope this helps, Rob From: Chad Cluff <cc...@bs...<mailto:cc...@bs...>> Reply-To: dotNetRDF User Help and Support <dot...@li...<mailto:dot...@li...>> Date: Tuesday, 9 September 2014 16:49 To: dotNetRDF User Help and Support <dot...@li...<mailto:dot...@li...>> Subject: Re: [dotNetRDF-Support] Creating nested RDF/xml Rob, I appreciate your help, and would like to ask a follow up question about the creation of the blank nodes. I'm still very new at this, so I apologize if the question is simple. Can you explain a bit, perhaps with an example about how to create the nodes? I've been working on getting it put together but I'm struggling. Let me show you what I've got and can you correct my thinking. /*previous creation of <bf:work> and <bf:instance> nodes and various triple assertions, such as ittle such as the line below g.Assert(bfInstance, g.CreateUriNode("bf:modeOfIssuance"), g.CreateLiteralNode("monographic")); IUriNode pubnode = g.CreateUriNode("bf:publication"); IBlankNode blnkPubNode = g.CreateBlankNode(); g.Assert(blnkPubNode, rdfType, pubnode); IUriNode providernode = g.CreateUriNode("bf:Provider"); IBlankNode blnkProvNode = g.CreateBlankNode(); g.Assert(blnkProvNode, rdfType, providernode); IUriNode providernamenode = g.CreateUriNode("bf:providerName"); IBlankNode blnkProvNameNode = g.CreateBlankNode(); g.Assert(blnkProvNameNode, rdfType, providernamenode); IUriNode orgnode = g.CreateUriNode("bf:Organization"); IBlankNode blnkOrgNode = g.CreateBlankNode(); g.Assert(blnkOrgNode, rdfType, orgnode); ILiteralNode publabel = g.CreateLiteralNode("Unwin Hyman"); /*End*/ It's at this point that I'm not sure how to make my assertions so that I get to an RDF like this (with the understanding that the formatting may not be exactly the same, based on how the library decides is the most efficient way of writing it out): <bf:publication> <bf:Provider> <bf:providerName> <bf:Organization> <bf:label>Unwin Hyman</bf:label> </bf:Organization> </bf:providerName> <bf:providerPlace> <bf:Place> <bf:label>London</bf:label> </bf:Place> </bf:providerPlace> <bf:providerDate>1987 ;</bf:providerDate> </bf:Provider> </bf:publication> Any help would be appreciated. Thanks, Chad From: Rob Vesse [mailto:rv...@do...] Sent: Tuesday, August 19, 2014 4:30 PM To: dotNetRDF User Help and Support Subject: Re: [dotNetRDF-Support] Creating nested RDF/xml Chad dotNetRDF may produce such RDF/XML but then it may not. See the email thread at http://sourceforge.net/p/dotnetrdf/mailman/message/32563380/ for some discussion around this, essentially it comes down to the fact that we prefer round trip correctness over readability so we provide limited configurability of the RDF writer. With an appropriate Graph created with the relevant triples and using the RDF/XML writer with the compression level turned up to high dotNetRDF may well produce that specific RDF/XML but it still may not. In your specific example you will need to ensure that you are using blank nodes as the intermediate nodes and ensuring that all the appropriate rdf:type triples are present RDF/XML provides multiple ways to encode the same graph and dotNetRDF will use whichever it decides is the most appropriate and most likely to round trip correctly. See https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Writing%20RDF#!advanced-usage for how to set the compression level, note that you can also set Options.DefaultCompressionLevel if your code won't have direct access to the write (see https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Global%20Options#!writing-options). As I stated in the email thread I linked earlier if a system relies on a specific format of RDF/XML then that is a bug in that system, a proper RDF system should only care about the underlying triples and the specific serialisation should be irrelevant. Rob From: Chad Cluff <cc...@bs...<mailto:cc...@bs...>> Reply-To: dotNetRDF User Help and Support <dot...@li...<mailto:dot...@li...>> Date: Tuesday, 19 August 2014 14:58 To: "dot...@li...<mailto:dot...@li...>" <dot...@li...<mailto:dot...@li...>> Subject: [dotNetRDF-Support] Creating nested RDF/xml I am trying to programmatically create a graph which will then export with nested RDF/xml elements. For example, I would like my output to look something like this: <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <bf:Instance xmlns:bf="http://bibframe.org/vocab/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>" rdf:about="http://bibframe.org/resources/backstage/3389308instance24"<http://bibframe.org/resources/backstage/3389308instance24%22>> <bf:publication> <bf:Provider> <bf:providerDate>1987</bf:providerDate> </bf:Provider> </bf:publication> </bf:Instance> </rdf:RDF> Is there any way to make this work with dotnetrdf? Thanks, Chad -- Chad Cluff IT/Programming Manager Backstage Library Works 800-288-1265 x696 cc...@bs...<mailto:cc...@bs...> ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/_______________________________________________ dotNetRDF-Support mailing list dot...@li...<mailto:dot...@li...> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk_______________________________________________ dotNetRDF-Support mailing list dot...@li...<mailto:dot...@li...> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support |
|
From: Rob V. <rv...@do...> - 2014-09-19 11:34:28
|
Chad Firstly sorry for taking so long to get back to you. The complication here is that your RDF/XML fragment is using a compression technique called striping (http://www.w3.org/TR/rdf-syntax-grammar/#example1) so not everything you see is a blank node: <bf:publication> Property <bf:Provider> Blank Node <bf:providerName> Property <bf:Organization> Blank Node <bf:label>Unwin Hyman</bf:label> Property with Literal Object </bf:Organization> </bf:providerName> <bf:providerPlace> Property <bf:Place> Blank Node <bf:label>London</bf:label> Property with Literal Object </bf:Place> </bf:providerPlace> <bf:providerDate>1987 ;</bf:providerDate> Property with Literal Object </bf:Provider> </bf:publication> The yellow annotations serve to illustrate which is which, generally a well designed ontology will use lowercase local names for properties and uppercase local names for types which usually makes it easy to distinguish which is which Your fragment here is incomplete because it starts with a property and it is unclear from your code what the root node is but I'll assume it is in the variable root for the purposes of the example INode pubProperty = g.CreateUriNode("bf:publication"); INode providerNode = g.CreateBlankNode(); INode providerType = g.CreateUriNode("bf:Provider"); g.Assert(root, pubProperty, providerNode); g.Assert(providerNode, rdfType, providerType); INode provNameProperty = g.CreateUriNode("bf:providerName"); INode orgNode = g.CreateBlankNode(); INode orgType = g.CreateUriNode("bf:Organization"); g.Assert(providerNode, provNameProperty, orgNode); g.Assert(orgNode, rdfType, orgType); INode labelProperty = g.CreateUriNode("bf:label"); INode labelValue = g.CreateLiteralNode("Unwin Hyman"); g.Assert(orgNode, labelProperty, labelValue); The above example creates just the first portion of your fragment but should hopefully point you in the right direction. Hope this helps, Rob From: Chad Cluff <cc...@bs...> Reply-To: dotNetRDF User Help and Support <dot...@li...> Date: Tuesday, 9 September 2014 16:49 To: dotNetRDF User Help and Support <dot...@li...> Subject: Re: [dotNetRDF-Support] Creating nested RDF/xml > Rob, > > I appreciate your help, and would like to ask a follow up question about the > creation of the blank nodes. I'm still very new at this, so I apologize if the > question is simple. > > Can you explain a bit, perhaps with an example about how to create the nodes? > I've been working on getting it put together but I'm struggling. Let me show > you what I've got and can you correct my thinking. > > > /*previous creation of <bf:work> and <bf:instance> nodes and various triple > assertions, such as ittle such as the line below > g.Assert(bfInstance, g.CreateUriNode("bf:modeOfIssuance"), > g.CreateLiteralNode("monographic")); > > > IUriNode pubnode = g.CreateUriNode("bf:publication"); > IBlankNode blnkPubNode = g.CreateBlankNode(); > g.Assert(blnkPubNode, rdfType, pubnode); > > IUriNode providernode = g.CreateUriNode("bf:Provider"); > IBlankNode blnkProvNode = g.CreateBlankNode(); > g.Assert(blnkProvNode, rdfType, providernode); > > IUriNode providernamenode = g.CreateUriNode("bf:providerName"); > IBlankNode blnkProvNameNode = g.CreateBlankNode(); > g.Assert(blnkProvNameNode, rdfType, providernamenode); > > IUriNode orgnode = g.CreateUriNode("bf:Organization"); > IBlankNode blnkOrgNode = g.CreateBlankNode(); > g.Assert(blnkOrgNode, rdfType, orgnode); > > ILiteralNode publabel = g.CreateLiteralNode("Unwin Hyman"); > > /*End*/ > > It's at this point that I'm not sure how to make my assertions so that I get > to an RDF like this (with the understanding that the formatting may not be > exactly the same, based on how the library decides is the most efficient way > of writing it out): > <bf:publication> > <bf:Provider> > <bf:providerName> > <bf:Organization> > <bf:label>Unwin Hyman</bf:label> > </bf:Organization> > </bf:providerName> > <bf:providerPlace> > <bf:Place> > <bf:label>London</bf:label> > </bf:Place> > </bf:providerPlace> > <bf:providerDate>1987 ;</bf:providerDate> > </bf:Provider> > </bf:publication> > > Any help would be appreciated. > > > Thanks, > > Chad > > > From: Rob Vesse [mailto:rv...@do...] > Sent: Tuesday, August 19, 2014 4:30 PM > To: dotNetRDF User Help and Support > Subject: Re: [dotNetRDF-Support] Creating nested RDF/xml > > > Chad > > > > dotNetRDF may produce such RDF/XML but then it may not. See the email thread > at http://sourceforge.net/p/dotnetrdf/mailman/message/32563380/ for some > discussion around this, essentially it comes down to the fact that we prefer > round trip correctness over readability so we provide limited configurability > of the RDF writer. > > > > With an appropriate Graph created with the relevant triples and using the > RDF/XML writer with the compression level turned up to high dotNetRDF may well > produce that specific RDF/XML but it still may not. In your specific example > you will need to ensure that you are using blank nodes as the intermediate > nodes and ensuring that all the appropriate rdf:type triples are present > > > > RDF/XML provides multiple ways to encode the same graph and dotNetRDF will use > whichever it decides is the most appropriate and most likely to round trip > correctly. See > https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Writing%20RDF#!advanc > ed-usage for how to set the compression level, note that you can also set > Options.DefaultCompressionLevel if your code won't have direct access to the > write (see > https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Global%20Options#!wri > ting-options). As I stated in the email thread I linked earlier if a system > relies on a specific format of RDF/XML then that is a bug in that system, a > proper RDF system should only care about the underlying triples and the > specific serialisation should be irrelevant. > > > > Rob > > > > From: Chad Cluff <cc...@bs...> > Reply-To: dotNetRDF User Help and Support > <dot...@li...> > Date: Tuesday, 19 August 2014 14:58 > To: "dot...@li..." > <dot...@li...> > Subject: [dotNetRDF-Support] Creating nested RDF/xml > > >> >> I am trying to programmatically create a graph which will then export with >> nested RDF/xml elements. >> >> For example, I would like my output to look something like this: >> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> >> <bf:Instance xmlns:bf="http://bibframe.org/vocab/" >> xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema# >> <http://www.w3.org/2000/01/rdf-schema> " >> rdf:about="http://bibframe.org/resources/backstage/3389308instance24" >> <http://bibframe.org/resources/backstage/3389308instance24%22> > >> <bf:publication> >> <bf:Provider> >> <bf:providerDate>1987</bf:providerDate> >> </bf:Provider> >> </bf:publication> >> </bf:Instance> >> </rdf:RDF> >> >> Is there any way to make this work with dotnetrdf? >> >> >> Thanks, >> >> Chad >> >> -- >> Chad Cluff >> IT/Programming Manager >> Backstage Library Works >> 800-288-1265 x696 >> cc...@bs... >> >> ----------------------------------------------------------------------------- >> - Slashdot TV. Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/_______________________________________________ >> dotNetRDF-Support mailing list dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support > ------------------------------------------------------------------------------ > Want excitement? Manually upgrade your production database. When you want > reliability, choose Perforce. Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk__ > _____________________________________________ dotNetRDF-Support mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support |
|
From: Chad C. <cc...@bs...> - 2014-09-09 15:49:41
|
Rob,
I appreciate your help, and would like to ask a follow up question about the creation of the blank nodes. I'm still very new at this, so I apologize if the question is simple.
Can you explain a bit, perhaps with an example about how to create the nodes? I've been working on getting it put together but I'm struggling. Let me show you what I've got and can you correct my thinking.
/*previous creation of <bf:work> and <bf:instance> nodes and various triple assertions, such as ittle such as the line below
g.Assert(bfInstance, g.CreateUriNode("bf:modeOfIssuance"), g.CreateLiteralNode("monographic"));
IUriNode pubnode = g.CreateUriNode("bf:publication");
IBlankNode blnkPubNode = g.CreateBlankNode();
g.Assert(blnkPubNode, rdfType, pubnode);
IUriNode providernode = g.CreateUriNode("bf:Provider");
IBlankNode blnkProvNode = g.CreateBlankNode();
g.Assert(blnkProvNode, rdfType, providernode);
IUriNode providernamenode = g.CreateUriNode("bf:providerName");
IBlankNode blnkProvNameNode = g.CreateBlankNode();
g.Assert(blnkProvNameNode, rdfType, providernamenode);
IUriNode orgnode = g.CreateUriNode("bf:Organization");
IBlankNode blnkOrgNode = g.CreateBlankNode();
g.Assert(blnkOrgNode, rdfType, orgnode);
ILiteralNode publabel = g.CreateLiteralNode("Unwin Hyman");
/*End*/
It's at this point that I'm not sure how to make my assertions so that I get to an RDF like this (with the understanding that the formatting may not be exactly the same, based on how the library decides is the most efficient way of writing it out):
<bf:publication>
<bf:Provider>
<bf:providerName>
<bf:Organization>
<bf:label>Unwin Hyman</bf:label>
</bf:Organization>
</bf:providerName>
<bf:providerPlace>
<bf:Place>
<bf:label>London</bf:label>
</bf:Place>
</bf:providerPlace>
<bf:providerDate>1987 ;</bf:providerDate>
</bf:Provider>
</bf:publication>
Any help would be appreciated.
Thanks,
Chad
From: Rob Vesse [mailto:rv...@do...]
Sent: Tuesday, August 19, 2014 4:30 PM
To: dotNetRDF User Help and Support
Subject: Re: [dotNetRDF-Support] Creating nested RDF/xml
Chad
dotNetRDF may produce such RDF/XML but then it may not. See the email thread at http://sourceforge.net/p/dotnetrdf/mailman/message/32563380/ for some discussion around this, essentially it comes down to the fact that we prefer round trip correctness over readability so we provide limited configurability of the RDF writer.
With an appropriate Graph created with the relevant triples and using the RDF/XML writer with the compression level turned up to high dotNetRDF may well produce that specific RDF/XML but it still may not. In your specific example you will need to ensure that you are using blank nodes as the intermediate nodes and ensuring that all the appropriate rdf:type triples are present
RDF/XML provides multiple ways to encode the same graph and dotNetRDF will use whichever it decides is the most appropriate and most likely to round trip correctly. See https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Writing%20RDF#!advanced-usage for how to set the compression level, note that you can also set Options.DefaultCompressionLevel if your code won't have direct access to the write (see https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Global%20Options#!writing-options). As I stated in the email thread I linked earlier if a system relies on a specific format of RDF/XML then that is a bug in that system, a proper RDF system should only care about the underlying triples and the specific serialisation should be irrelevant.
Rob
From: Chad Cluff <cc...@bs...<mailto:cc...@bs...>>
Reply-To: dotNetRDF User Help and Support <dot...@li...<mailto:dot...@li...>>
Date: Tuesday, 19 August 2014 14:58
To: "dot...@li...<mailto:dot...@li...>" <dot...@li...<mailto:dot...@li...>>
Subject: [dotNetRDF-Support] Creating nested RDF/xml
I am trying to programmatically create a graph which will then export with nested RDF/xml elements.
For example, I would like my output to look something like this:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<bf:Instance xmlns:bf="http://bibframe.org/vocab/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>" rdf:about="http://bibframe.org/resources/backstage/3389308instance24"<http://bibframe.org/resources/backstage/3389308instance24%22>>
<bf:publication>
<bf:Provider>
<bf:providerDate>1987</bf:providerDate>
</bf:Provider>
</bf:publication>
</bf:Instance>
</rdf:RDF>
Is there any way to make this work with dotnetrdf?
Thanks,
Chad
--
Chad Cluff
IT/Programming Manager
Backstage Library Works
800-288-1265 x696
cc...@bs...<mailto:cc...@bs...>
------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/_______________________________________________ dotNetRDF-Support mailing list dot...@li...<mailto:dot...@li...> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support
|
|
From: Rob V. <rv...@do...> - 2014-08-22 17:47:44
|
Jason NuGet Package versions do not have to correspond to assembly versions. This happens to be true of the current dotNetRDF releases and of Json.Net as well. If you look at Properties of the actual DLL in Windows Explorer and check the Details tab you should see that the actual File Version is indeed set to 1.0.6.3421 For us this isn't intentional (though it is for Json.Net) and it's something we will fix in our next release but it shouldn't in of itself cause problems because this is what Json.Net does all the time. As I said before if you want us to debug further then you will need to provide an actual project that reproduces this problem. Rob From: Jason Harris <JH...@bc...> Date: Friday, 22 August 2014 08:23 To: Rob Vesse <rv...@do...> Subject: RE: [dotNetRDF-Support] could not load assembly issue > Your note about being on 1.0.3 piqued my interest. I just started a new > workspace (clean copy of the branch) and confirmed that there are no dotNetRDF > packages in my packages directory. I then opened the package manager and did a > fresh install of dotnetrdf: > > PM> Install-Package dotNetRDF > Attempting to resolve dependency 'VDS.Common (= 1.3.0)'. > Attempting to resolve dependency 'Newtonsoft.Json (≥ 6.0.3)'. > Attempting to resolve dependency 'HtmlAgilityPack (≥ 1.4.6)'. > Installing 'VDS.Common 1.3.0'. > Successfully installed 'VDS.Common 1.3.0'. > Installing 'Newtonsoft.Json 6.0.4'. > Successfully installed 'Newtonsoft.Json 6.0.4'. > Installing 'dotNetRDF 1.0.6.3421'. > Successfully installed 'dotNetRDF 1.0.6.3421'. > Adding 'VDS.Common 1.3.0' to RSSReaderServiceModule. > Successfully added 'VDS.Common 1.3.0' to RSSReaderServiceModule. > Adding 'Newtonsoft.Json 6.0.4' to RSSReaderServiceModule. > Successfully added 'Newtonsoft.Json 6.0.4' to RSSReaderServiceModule. > Adding 'HtmlAgilityPack 1.4.6' to RSSReaderServiceModule. > Successfully added 'HtmlAgilityPack 1.4.6' to RSSReaderServiceModule. > Adding 'dotNetRDF 1.0.6.3421' to RSSReaderServiceModule. > Successfully added 'dotNetRDF 1.0.6.3421' to RSSReaderServiceModule. > > PM> > > Nuget reports that it installed 1.0.6 > > I then look at the properties of the dotNetRdf dll and see the following: > > Path: C:\Projects\92\packages\dotNetRDF.1.0.6.3421\lib\net40\dotNetRDF.dll > Version: 1.0.3.0 > > So it seems like somehow nuget is delivering me the wrong dll. > > > > From: Rob Vesse [mailto:rv...@do...] > Sent: Wednesday, August 20, 2014 3:55 PM > To: dotNetRDF User Help and Support > Cc: Jason Harris > Subject: Re: [dotNetRDF-Support] could not load assembly issue > > > Jason > > > > Your problem sounds similar to one recently discussed on StackOverflow - > http://stackoverflow.com/questions/25361130/nuget-dependency-installed-but-not > -found - though it is unclear if they are related but may be worth you reading > through my answer there and seeing if any of the suggestions resolve this for > you. If you have any other dependencies on Json.Net you may be running into > CORE-405 (http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?&id=405) which > has been resolved with more recent dotNetRDF releases. > > > > The latest dotNetRDF release is 1.0.6.3421 which should be the one NuGet > installs so I am surprised you get 1.0.3 > > > > The specific error you get sounds like the dotNetRDF (or one of its > dependencies) is not getting deployed into your output directory which means > it isn't being picked up by the build correctly or you aren't deploying > everything necessary when you deploy the app (you don't state where and how > you launch the app). The build output from a VS rebuild i.e. the MSBuild > output would be more useful for debugging purposes. Make sure you aren't > hiding Warnings in the error list because MSBuild will report some dependency > problems only as warnings while allowing you to build successfully and you > won't see the dependency problem until runtime. > > > > If you would like us to debug this further then we will need you to provide an > actual project that reliably reproduces the problem (it does not have to be > the specific project you mention if you can't share that) or instructions that > reliably reproduce the problem. Or you can send a non-public example directly > to me if that is preferable. > > > > Rob > > > > Ps This is a subscription based list and I have moderated through your email > and CC'd you on this initial response, please subscribe at > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support if you wish to > continue this discussion as future responses will only go to the mailing list > > > > From: Jason Harris <JH...@bc...> > Reply-To: dotNetRDF User Help and Support > <dot...@li...> > Date: Tuesday, 19 August 2014 07:18 > To: "dot...@li..." > <dot...@li...> > Subject: [dotNetRDF-Support] could not load assembly issue > > >> >> I used nuget to install dotNetRdf into an existing .net 4.5 project that >> reads rss feeds. It installed version 1.0.3.0. Once loaded, the app throws >> the following error: >> >> >> Could not load file or assembly 'dotNetRDF, Version=1.0.3.0, Culture=neutral, >> PublicKeyToken=6055ffe4c97cc780' or one of its dependencies. The system >> cannot find the file specified. >> >> >> The only thing I can find online is this: >> http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=298. Didn’t seem >> entirely relevant since it’s concerning older versions of everything, but I >> try manually installing (via nuget) the latest vds common package. Here’s the >> output of nuget if that helps. I’ll be happy to provide any other information >> too. >> >> >> PM> Install-Package vds.common >> 'VDS.Common 1.3.0' already installed. >> Adding 'VDS.Common 1.3.0' to RSSReaderServiceModule. >> Successfully added 'VDS.Common 1.3.0' to RSSReaderServiceModule. >> >> PM> Install-Package dotNetRDF >> Attempting to resolve dependency 'VDS.Common (= 1.3.0)'. >> Attempting to resolve dependency 'Newtonsoft.Json (≥ 6.0.3)'. >> Attempting to resolve dependency 'HtmlAgilityPack (≥ 1.4.6)'. >> 'dotNetRDF 1.0.6.3421' already installed. >> Adding 'Newtonsoft.Json 6.0.4' to RSSReaderServiceModule. >> Successfully added 'Newtonsoft.Json 6.0.4' to RSSReaderServiceModule. >> Adding 'HtmlAgilityPack 1.4.6' to RSSReaderServiceModule. >> Successfully added 'HtmlAgilityPack 1.4.6' to RSSReaderServiceModule. >> Adding 'dotNetRDF 1.0.6.3421' to RSSReaderServiceModule. >> Successfully added 'dotNetRDF 1.0.6.3421' to RSSReaderServiceModule. >> >> >> >> Thanks >> Jason Harris >> Buffalo Computer Graphics >> ----------------------------------------------------------------------------- >> - _______________________________________________ dotNetRDF-Support mailing >> list >> dot...@li...https://lists.sourceforge.net/lists/li >> stinfo/dotnetrdf-support |
|
From: Rob V. <rv...@do...> - 2014-08-20 19:56:20
|
Jason Your problem sounds similar to one recently discussed on StackOverflow - http://stackoverflow.com/questions/25361130/nuget-dependency-installed-but-n ot-found - though it is unclear if they are related but may be worth you reading through my answer there and seeing if any of the suggestions resolve this for you. If you have any other dependencies on Json.Net you may be running into CORE-405 (http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?&id=405) which has been resolved with more recent dotNetRDF releases. The latest dotNetRDF release is 1.0.6.3421 which should be the one NuGet installs so I am surprised you get 1.0.3 The specific error you get sounds like the dotNetRDF (or one of its dependencies) is not getting deployed into your output directory which means it isn't being picked up by the build correctly or you aren't deploying everything necessary when you deploy the app (you don't state where and how you launch the app). The build output from a VS rebuild i.e. the MSBuild output would be more useful for debugging purposes. Make sure you aren't hiding Warnings in the error list because MSBuild will report some dependency problems only as warnings while allowing you to build successfully and you won't see the dependency problem until runtime. If you would like us to debug this further then we will need you to provide an actual project that reliably reproduces the problem (it does not have to be the specific project you mention if you can't share that) or instructions that reliably reproduce the problem. Or you can send a non-public example directly to me if that is preferable. Rob Ps This is a subscription based list and I have moderated through your email and CC'd you on this initial response, please subscribe at https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support if you wish to continue this discussion as future responses will only go to the mailing list From: Jason Harris <JH...@bc...> Reply-To: dotNetRDF User Help and Support <dot...@li...> Date: Tuesday, 19 August 2014 07:18 To: "dot...@li..." <dot...@li...> Subject: [dotNetRDF-Support] could not load assembly issue > I used nuget to install dotNetRdf into an existing .net 4.5 project that reads > rss feeds. It installed version 1.0.3.0. Once loaded, the app throws the > following error: > > > Could not load file or assembly 'dotNetRDF, Version=1.0.3.0, Culture=neutral, > PublicKeyToken=6055ffe4c97cc780' or one of its dependencies. The system cannot > find the file specified. > > > The only thing I can find online is this: > http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=298. Didn’t seem > entirely relevant since it’s concerning older versions of everything, but I > try manually installing (via nuget) the latest vds common package. Here’s the > output of nuget if that helps. I’ll be happy to provide any other information > too. > > > PM> Install-Package vds.common > 'VDS.Common 1.3.0' already installed. > Adding 'VDS.Common 1.3.0' to RSSReaderServiceModule. > Successfully added 'VDS.Common 1.3.0' to RSSReaderServiceModule. > > PM> Install-Package dotNetRDF > Attempting to resolve dependency 'VDS.Common (= 1.3.0)'. > Attempting to resolve dependency 'Newtonsoft.Json (≥ 6.0.3)'. > Attempting to resolve dependency 'HtmlAgilityPack (≥ 1.4.6)'. > 'dotNetRDF 1.0.6.3421' already installed. > Adding 'Newtonsoft.Json 6.0.4' to RSSReaderServiceModule. > Successfully added 'Newtonsoft.Json 6.0.4' to RSSReaderServiceModule. > Adding 'HtmlAgilityPack 1.4.6' to RSSReaderServiceModule. > Successfully added 'HtmlAgilityPack 1.4.6' to RSSReaderServiceModule. > Adding 'dotNetRDF 1.0.6.3421' to RSSReaderServiceModule. > Successfully added 'dotNetRDF 1.0.6.3421' to RSSReaderServiceModule. > > > > Thanks > Jason Harris > Buffalo Computer Graphics > ------------------------------------------------------------------------------ > _______________________________________________ dotNetRDF-Support mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support |
22 messages has been excluded from this view by a project administrator.
