sparqlwrapper | A wrapper for a remote SPARQL endpoint | Data Manipulation library

Was the servers version of django upgraded? patterns was deprecated in 1.10

https://stackoverflow.com/a/38799716/1464664

current implementations looks like this

You can convert DataFrame to list and then modify list into string to use it in your query

SPARQLWrapper defaults to adding

&format=turtle&output=turtle&results=turtle

to the request.

SPARQLWrapper has a method setOnlyConneg that turns off the adding of the additional query string parts.

1. The WARN SPARQL Query: Unrecognize request parameter (ignored): results happens because Fuseki does understand results and logs a warning about it. It is just a warning.

2. format is a mechanism to override the proper HTTP content negotiation mechanism because in some situations it is hard to set the HTTP headers. This does not apply to SPARQLWrapper which does correctly set Accept:.

3. format=turtle isn't in the list of names for a CONSTRUCT query. ttl is. (`turtle can be added to future version of Fuseki for completeness).

The best way is not to have the non-standard query string parameters with setOnlyConneg. SPARQLWrapper correctly sets the "Accept:" header in the request and Fuseki has content negotiation and will work with that header.

I think you can pass a dictionary to the node_color parameter of the draw function. If you construct that dictionary such that the keys are the node-names and the values are the colours you want to associate with those node-names, then you should be able to get the formatting you want.

e.g. if you have been able to run some SPARQL to generate a list of nodes you want to be green, and another list that you want to be blue, and assuming you've got a green_list and blue_list pair of lists of these nodenames, then you could construct your dict something like this:

The endpoint which you need to insert statements isn't the simple SPARQL endpoint you use for ordinary queries, but, rather, the dedicated /statements endpoint:

http:///repositories//statements

This endpoint is also used for DELETE statements.

You can look up some examples in the RDF4J documentation. Furthermore, if you are passing your data with a query string instead of it being a part of your request body, you need to be aware of the fact that it must start with a "?update=" instead of "?query=".opps

The problem is not in your code, but in one of the two servers that run the sparql.uniprot.org endpoint. If you request went to the 'good' machine it worked, if it went to the 'broken' machine it failed. Both machines should be good now.

The problem with your first code snippet is that the text you're passing as a parameter to the HTTP call is too long, if you print the response object you'll see:

that corresponds to 414 URI Too Long Reference

If you pass a smaller text, dbpedia-spotlight will be able to annotate the entities for you.

For the second code that you put, you have two problems, the first one is that dbpedia-spotlight may respond with 403 status after consecutive calls to the annotate service, to check that I suggest you to do:

You can't get the value of the UUID directly from the SPARQL update - if you want to retrieve it via SPARQL somehow, you'll have to do a query after you've inserted it - or, of course, you could adapt your second SPARQL update to do the selection for you by querying for the 'correct' UUID in its WHERE clause.

However, in this case, that looks difficult to do, and I think the easiest solution for you is that you don't create the UUID in the SPARQL operation itself, but instead create it in code and then use that in your query string, e.g. by adding a VALUES clause, something like this:

I am rewriting what @StanislavKralin mentioned in the above comment. I always try to use full URL in the SPARQL code, particularly when there is special character in SPARQL query.