Michiel de Jong
Michiel de Jong
Solid OS uses this [willful violation](https://github.com/solid/solid-spec/pull/193). NSS and PSS support it. Neither CSS nor ESS do. @acoburn is right, we could achieve a very similar effect with `If-Match`. It wouldn't...
OK, so to summarize, the proposed change would be: * instead of `application/sparql-update` all Solid apps will send content-type `application/sparql-update; remove=true` * instead of `DELETE DATA { ... }; INSERT...
Looks like after almost two years we all agree now, awesome!! * Changed it in v5.0.0 of the [CRUD tests](https://github.com/solid/solid-crud-tests) to send the new content type * Changed it in...
OK, sorry I wasn't aware. What are the steps?
FWIW, NSS now accepts both `application/sparql-update` and `application/sparql-update-single-match` as the content-type. In both cases, the behaviour is "Solid-flavoured" sparql-update (as it has been for years in the case of `application/sparql-update`)....
OK, too bad, I thought we had finally found a solution but sounds like this will take a few more rounds. I removed the `-single-match` from the content type again...
I'll also mark the test for this as disputed again, since it seems the dispute will still go on. For now, we need to tell clients to avoid sending DELETE/INSERT...
OK sorry maybe the word 'dispute' is too strong. Maybe we should call it an 'undecided issue'? Let's use that word from now on. What I try to cover with...
@Mitzi-Laszlo can you add this to https://github.com/solid/specification/milestone/1?