Sarven Capadisli

As said, I'm not opposed to closing the PR or even dropping the feature altogether. However: Incorporating implementation feedback *is* part of the review process. We could close the issue...

Current status based on meeting with @kjetilk is same as what mentioned in https://gitter.im/solid/specification?at=5f291b1ce3160e46baa2a17b: "PR reflects the consensus in the issues [however] it is not significant [..] for the [next...

The Solid Protocol works within the framework of HTTP (RFCs). The Protocol either tries to consistently echo RFC codes or recommends particular codes ones when describing specific behaviour. And there...

I think both kinds of responses can be accommodated. I would consider any response to have an element of "best effort" - at the time the communication took place. Mutable...

@acoburn Parent containers are required to be created in the multi-resource creation case. @michielbdejong I just take it as a given that server knows best and client takes the response...

@michielbdejong Sounds good. Let's do that.

Let me jot this down hopefully for some clarity: >i like how you phrased it with ‘not willing to commit to a response’, implying that best-effort responses are forbidden. >So...

We're not modifying the definition of 200 and 202. They are both final in the sense that server decided on something and communicates back to the client. End communication. 200...

I have no particular issue or objection to add this. As mentioned before, I wrote the Protocol text in a way that would make POST w/ RDF Merge possible one...

@kjetilk I think your response to the question is adequate. The point was to have it on record - which wasn't mentioned in the original comment. >It can't be just...