> Leigh Dodds suggested a built-in mechanism for POSTing RDF graphs to a > container resource which then responds with a 201 such that the server can > determine the URI used to store the payload as a new, named RDF graph and > indicate this to the client. The changes were made to 4.3 HTTP POST There now seem to be two concepts for "container" - graph store and graph. It would be worth pulling this out explicitly. Where is the "insertion use case" that is mentioned? AndyReceived on Monday, 14 December 2009 22:11:30 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:00:58 UTC