Does Vivo sparql update API support delete/insert operation ?

[J. Dornbusch]

Hello

I want to execute my update requests to Vivo inside transactions. I'm interested in delete/insert operations.

But as soon as I tell my sparql client (ruby sparql client) to go to 1.1, I get errors on the simplest queries.

SPARQL::Client::MalformedQuery (<H1>400 Query string was not supplied.</H1>
 Processing query SELECT * WHERE { ?s <http://vivo.mydomain.edu/ontology/ehess#hasTechnicalidentifier> "ldap_ehess#1234" . }):

While it works very well with the default protocol.

I can't determine where the problem come from, ruby gem or sparql API.

Does anyone have information?

Thanks, J.Dornbusch

 

[Gross, Benjamin]

Hi,

Can you show us the difference between what you are trying here and the default protocol that works? The VIVO update API definitely works, but you have to follow the format shown on the wiki which might not be the format your client is supplying. I'm not sure if the format VIVO expects is compliant with what you'll find on the W3C page or not, but as far as I can tell the update api code really only serves as an interface to the Jena update library.

Benjamin

_____________________________
Benjamin Gross
Science and Academic Research | Clarivate Analytics

--
You received this message because you are subscribed to the Google Groups "VIVO Tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vivo-tech+...@googlegroups.com.
To post to this group, send email to vivo...@googlegroups.com.
Visit this group at https://groups.google.com/group/vivo-tech.
To view this discussion on the web visit https://groups.google.com/d/msgid/vivo-tech/1170ccbc-90f8-4821-a6f2-4b4f375db123%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.