the issue surfaced that SPARQL UPDATE clients that send the update string as the pure post body are not supported by VIVO's update API. VIVO only supports posting the update string as the www-form-encoded value of the "update" parameter.
Although VIVO's update API does not necessarily bill itself as a genuine SPARQL UPDATE endpoint, it would be good to support both approaches – and, generally, to adhere as closely as possible to the SPARQL UPDATE spec.
Brian Lowe (Migrated from VIVO-1841) said:
In the context of the following email discussion
[https://groups.google.com/forum/#!topic/vivo-tech/RlPFVvoOenQ]
the issue surfaced that SPARQL UPDATE clients that send the update string as the pure post body are not supported by VIVO's update API. VIVO only supports posting the update string as the www-form-encoded value of the "update" parameter.
Although VIVO's update API does not necessarily bill itself as a genuine SPARQL UPDATE endpoint, it would be good to support both approaches – and, generally, to adhere as closely as possible to the SPARQL UPDATE spec.